OSI/AS Management Programming Manual

ABORT PROCESS Command
Commands and Responses
5–10 056785 Tandem Computers Incorporated
ZCOM-TKN-OBJNAME can 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 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 Notes
The OSI/AS ABORT command is not valid for NSP processes. To abort an NSP
process, you must send an ABORT LINE command to the X25AM or TLAM
subsystem, as described in the management programming manual for that
subsystem.
The ABORT PROCESS $OSIMGR or ABORT PROCESS $TAPS command does not
cause any session, presentation, or ACSE protocol actions. Any TSP subdevices
opened by a TAPS subdevice will be closed.
When subdevices are internally added, they are created and automatically put in
the STARTED state. When an ABORT PROCESS $TAPS command is issued, the
process and any opened subdevices subordinate to that process are deleted.