OSI/AS Management Programming Manual

ALTER PROCESS Command
Commands and Responses
056785 Tandem Computers Incorporated 5–55
Tokens in Response Buffer
ZSPI-TKN-DATALIST token-type ZSPI-TYP-LIST.
ZCOM-TKN-OBJTYPE token-type ZSPI-TYP-ENUM.
ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING.
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.
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 process to which SCP is to
send this command. This token is optional and can occur only once in the
command.
ZCOM-TKN-OBJNAME
is the indirect-process-name of the TAPS, TSP, or NSP process to be altered. This
token is required and can occur only once.
ZOSI-MAP-ALTER-PROC
is an extensible structured token that contains the attributes for the specified
process being altered. ZOSI-DDL-ALTER-PROC contains the following fields:
ZNAME
specifies a TAPS, TSP, or NSP Guardian 90 C-series system process name of
the server. This attribute is for C series systems only. The equivalent token
for D series systems is ZXNAME. It is used to run a process or to try to establish
communication with a process that is already running. ZNAME is the only
attribute that can be altered for NSP processes; all other attributes are ignored.
The value is a TAPS, TSP, or NSP process name in the following format:
$process-name
TAPS, TSP, and NSP process names can be up to 6 characters (the $ sign
followed by 5 characters). For example:
$TAPS1
$TSP10
$X2510
If two or more TSP processes share the same X25AM line, the first 4 characters
after the $ sign are used by TSP to build the SU name and must be unique. For
example, the following three TSP processes share the same X25AM line: