OSI/FTAM and OSI/APLMGR SCF Reference Manual

SCF Commands for Tandem FTAM
OSI/FTAM and OSI/APLMGR SCF Reference Manual—421943-001
3-108
STOP PROCESS
STOP PROCESS
The STOP PROCESS command terminates the operation of a process, placing it in the
STOPPED state, if no work is currently in progress using that process. STOP PROCESS
is a sensitive command.
The STOP PROCESS command has the following syntax:
\system-name
identifies the system in which the APLMGR process is running.
$appl-mgr-name
identifies the APLMGR process you want to stop.
indirect-process-name
identifies the initiator or responder process you want to stop.
STOP PROCESS Considerations
•
You cannot send this command directly to an initiator or a responder process. If you
specify indirect-process-name, the APLMGR process routes it to the
specified initiator or responder process.
•
The specified process must be in the STARTED or SUSPENDED state for this
command to be completed successfully.
•
The STOP PROCESS command places the specified process in the STOPPED state
if no work is in progress—that is, if no opens to the subdevices currently exist for
that process.
•
If a STOP PROCESS command is sent to an initiator or a responder process that is
currently active—that is, opens to the subdevices currently exist for that process—
the command is rejected with error E00003, “Command not allowed when object is
in use.”
•
If a STOP PROCESS command is sent to an APLMGR process that is currently in
the STARTED state, regardless of any activity, the APLMGR process is placed in
the STOPPED state. In this case, the initiator and responder processes managed by
that APLMGR continue their processing over currently existing associations. They
can also perform sensitive SCF commands (such as TRACE, for example).
However, no new associations can be initiated.
When this command is completed successfully, the process ceases to exist, but the
attributes of the process are still defined in the APLMGR MIB.
STOP PROCESS [\system-name.]{$appl-mgr-name }
{indirect-process-name }