SPI Common Extensions Manual

ZCMK Definitions
SPI Common Extensions Manual—427508-001
B-41
GETVERSION
sent to the new collector. This token corresponds to the COLLECTOR startup
parameter described in Process Options and Startup Parameters on page B-4.
ZCMK-TKN-LOG-XFNAME
specifies the identity of the log file. A zero-length name stops logging.
To leave the log unchanged, omit this token from the ALTER command message.
Altering the log file causes an event to be generated, an event message to be sent
to the old and the new log files announcing the change, and the banner line to be
sent to the new log file.
This token corresponds to the OUT startup parameter described in Process
Options and Startup Parameters on page B-4.
ZCMK-TKN-MSG-XFNAME
identifies the message file.
Any edit file can be used as a message file, so take care not to assign an
inappropriate file. Subsystem processes can operate without a message file, but
error messages and event logging might not perform as expected.
To continue using the current message file, omit this token from the command.
GETVERSION
A ZCMK-based subsystem returns these tokens in response to a GETVERSION
command that is directed to the subsystem’s native object type:
ZCOM-TKN-OBJTYPE
contains the native object type of the responding subsystem process.
ZCMK-TKN-PKG-BANNER
contains the version banner of the ZCMK definitions. The banner is blank-filled to
align the banner of the server.
ZSPI-TKN-SERVER-BANNER
contains the subsystem product banner, which consists of:
product name - T9cnnvff - ddmmmyy - misc
GETVERSION Response Tokens
ZCMK-TKN-PKG-BANNER token-type ZSPI-TYP-CHAR50
ZSPI-TKN-SERVER-BANNER token-type ZSPI-TYP-CHAR50
ZCOM-TKN-OBJNAME token-type ZSPI-TYP-ENUM
ZCOM-TKN-OBJTYPE token-type ZSPI-TYP-STRING
ZCOM-TKN-GETVSN-LVL token-type ZSPI-TYP-INT