OSI/AS Management Programming Manual

STATUS PROCESS Command
Commands and Responses
056785 Tandem Computers Incorporated 5–259
Tokens in Response Buffer (continued)
02 ZCREATE-TIME type ZSPI-DDL-TIMESTAMP.
02 ZXDEVNAME type ZOSI-DDL-CHAR36.
02 ZXDEVNAME-LEN type ZSPI-DDL-INT.
end.
ZSPI-TKN-RETCODE token-type ZSPI-TYP-ENUM.
ZSPI-TKN-ERRLIST token-type ZSPI-TYP-LIST.
. . .
ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SSCTL.
ZSPI-TKN-ENDLIST token-type ZSPI-TYP-SSCTL.
ZSPI-TKN-CONTEXT token-type ZSPI-TYP-BYTESTRING.
Tokens in Command Buffer
ZSPI-TKN-MANAGER or ZCOM-TKN-XMGR
is the Guardian 90 C-series system (ZSPI-TKN-MANAGER) or D-series system
(ZCOM-TKN-XMGR) process name of the OSI manager or TAPS process to which
SCP is to send this command. This token is optional and must occur only once in
the command.
ZCOM-TKN-OBJNAME
is the name of the OSI manager, TAPS, or TSP process for which you want status
information. This token is required and can be an object-name template (wild card
name). If you are sending the command directly to a TAPS process, bypassing the
OSI manager process, ZCOM-TKN-OBJNAME must occur only once, and it must
be the name of that TAPS process. If you are sending the command to the OSI
manager process, ZCOM-TKN-OBJNAME can occur multiple times. The process-
name format depends on the type of process, as follows:
If the object is the OSI manager process, use process-name.
If the object is a TSP or NSP process, use indirect-process-name.
If the object is a TAPS process, use indirect-process-name.
ZCOM-TKN-CMD-TIMEOUT
is described in the Communications Management Programming Manual.
ZSPI-TKN-RESPONSE-TYPE, ZSPI-TKN-ALLOW-TYPE, ZSPI-TKN-COMMENT,
and ZSPI-TKN-CONTEXT
are described in the Distributed Systems Management (DSM) Programming Manual.