OSI/AS Management Programming Manual

SUSPEND PROCESS Command
Commands and Responses
5–290 056785 Tandem Computers Incorporated
process, ZCOM-TKN-OBJNAME must occur only once, and it must be the process-
name of that TAPS process. If you are sending the command to the OSI manager
process using an indirect-process-name, ZCOM-TKN-OBJNAME can occur multiple
times.
If the object is a TAPS or TSP process that is not running but is configured in the
MIB (that is, it has been added with an ADD command), the OSI manager runs the
specified process, configures the SERVICE objects of the process as specified in the
MIB, and then puts the process in the suspended (SUSP) state. In this case, you
must use the indirect-process-name.
If the specified process is currently running, the OSI manager process places the
process in the SUSPENDED state. In this case, 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 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.
Tokens in Response Buffer
ZSPI-TKN-DATALIST
introduces a data list, as described in the Distributed Systems Management (DSM)
Programming Manual; the final ZSPI-TKN-ENDLIST ends the data list. These
tokens enclose the other response tokens only if the value of the header token
ZSPI-TKN-MAXRESP is nonzero.
ZCOM-TKN-OBJTYPE and ZCOM-TKN-OBJNAME
are described in the Communications Management Programming Manual.
ZSPI-TKN-RETCODE, ZSPI-TKN-ERRLIST, ZSPI-TKN-ENDLIST, and ZSPI-
TKN-CONTEXT
are described in the Distributed Systems Management (DSM) Programming Manual.
Operational Note
The OSI/AS SUSPEND command is not valid for NSP processes.