TS/MP 2.5 Management Programming Manual

is a message buffer of the appropriate size for use with the SPI procedures in
applications that manage Open System Services (OSS) server processes.
def
ZPWY-DDL-MAX-MSG-BUFFER.
token-type ZSPI-DDL-INT. 02 Z-MSGCODE
token-type ZSPI-DDL-INT. 02 Z-BUFLEN
token-type ZSPI-DDL-INT. 02 Z-OCCURS
token-type ZSPI-DDL-CHAR 02 Z-FILLER
occurs 0 to ZPWY-VAL-MAX-BUFLEN
times depending on Z-OCCURS.
end.
This buffer message declaration is also defined in the ZSPIDEF.ZPWYTACL file, with
the size of the Z-FILLER field set to 4994 bytes. It is defined in the ZSPIDEF.ZPWYTAL
file, with the size of the Z-FILLER field set to 30000 bytes.
Object Names
The DDL definitions for object names are used to define the object-selector tokens referenced with
token maps (not token codes). For object-selector tokens, whether each field is required or optional
depends upon the command in which the token type is used; required and optional fields are
therefore marked in the individual command descriptions.
The DDL definitions for object names are also used to define the error tokens
ZPWY-TKN-REQobjecttypeNAME and ZPWY-TKN-objecttypeNAME and the subject tokens
for event messages.
Token Codes for Object Names
The DDL definitions for object names describe token types that have the prefix ZPWY-TYP-. The
token types are used to build token codes, which have the prefix ZPWY-TKN-. Each token code
for an object name has the same name as the corresponding token type. For example, the token
type ZPWY-TYP-SCNAME is used to build the token code ZPWY-TKN-SCNAME.
ZPWY-DDL-LMNAME
ZPWY-DDL-LMNAME identifies a LINKMON process.
def ZPWY-DDL-LMNAME.
token-type ZPWY-DDL-OBJECT-NAME. 02 ZLINKMON
token-type ZPWY-DDL-FILLER. 02 FILLER-1
end.
ZLINKMON
specifies the name of a LINKMON process.
Object Names 55