OSI/FTAM and OSI/APLMGR SCF Reference Manual

SCF Commands for Tandem FTAM
OSI/FTAM and OSI/APLMGR SCF Reference Manual—421943-001
3-29
ALTER SUBSYS Considerations
ALTER SUBSYS Considerations
•
The APLMGR process must be in the SUSPENDED state before you can change
SUBSYS attributes. When the APLMGR process is placed in the SUSPENDED
state, the initiator and responder processes managed by that APLMGR continue
their processing over currently existing associations. However, no new associations
can be initiated. In addition, the initiators and responders cannot perform any
sensitive SCF commands.
•
The subsystem (the APLMGR process) is created by issuing a RUN command from
the TACL command interpreter. The following subsystem attributes cannot be set in
the RUN command and default to the values shown:
After issuing the TACL RUN command, you can modify the values of these attributes
using the SCF ALTER SUBSYS command.
ALTER SUBSYS Errors
The following table lists the most common errors that can occur during the processing of
the ALTER SUBSYS command:
Attribute Default
FTAMIFILE file-spec
FTAMIOBJ, with the same volume and
subvolume names as the APLMGR code file
FTAMRFILE file-spec
FTAMROBJ, with the same volume and
subvolume names as the APLMGR code file
MAXFTAMI integer
128
MAXFTAMR integer
128
MIB file-spec
ZOSADB with the same volume and
subvolume names as the APLMGR code file
OMGRNAME process-name
$OSIM
Message Definition
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
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.
OSIAPLMG E-00003 Command not allowed
when object is in object-state state for
object-name
The APLMGR process was not in the
SUSPENDED state. Use STATUS
PROCESS to display process states.