OSI/FTAM and OSI/APLMGR SCF Reference Manual

SCF Commands for Tandem FTAM
OSI/FTAM and OSI/APLMGR SCF Reference Manual421943-001
3-5
ABORT PROCESS Errors
ABORT PROCESS Errors
The following table lists the most common errors that can occur during the processing of
the ABORT PROCESS command:
For more information on errors specific to APLMGR (OSIAPLMG errors having
positive error numbers), see Appendix B, SCF Error Messages for the APLMGR
Subsystem. For more information on common SCF error messages (errors having
negative error numbers), see the Subsystem Control Facility (SCF) Reference Manual
(for D-series releases) or the SCF Reference Manual for G-Series Releases.
ABORT PROCESS Examples
You can use the following command to abort an APLMGR process named $AMGR
running in the \MARS system:
ABORT PROCESS \MARS.$AMGR
To abort an initiator process named FTI1 that is managed by the APLMGR process
named $AMGR, enter the command
ABORT PROCESS \MARS.$AMGR.#FTAMI.FTI1
Message Meaning
Expecting an existing SCF
supported object name or
the character “(“
No APLMGR process by the specified name could be found.
To display valid APLMGR process names, use the following
command:
LISTDEV OSIAPLMG
OSIAPLMG E-00017
Object object-name not
found
The internal-name specified as part of indirect-process-name
was not recognized by the APLMGR process as a registered
internal process name. To display the currently registered
process names, use the following NAMES command:
NAMES $appl-mgr-name.*.*
OSIFTAM E-00004
Command/object type
combination is not valid for
this subsystem
You issued the command directly to the initiator or responder
process. Use indirect-process-name to specify the
desired initiator or responder process.
SCP E-00022
Security Violation for
process-name
You are not allowed to perform sensitive commands. For
further information on sensitive commands, see Sensitive and
Nonsensitive Commands on page 1-9.