LAN Configuration and Management Manual

SCF Commands for the SLSA Subsystem
LAN Configuration and Management Manual520469-012
4-129
STOP ATMSAP Command
Examples
The following are examples of the STOP ADAPTER command:
STOP ADAPTER $ZZLAN.G11123
STOP ADAPTER ($ZZLAN.G11021, $ZZLAN.G11123)
STOP ADAPTER $ZZLAN.G*
STOP ADAPTER $ZZLAN.G11123, SUB
STOP ATMSAP Command
The STOP ATMSAP command requests an ATMSAP object subordinate to a PIF
object to halt operation. The ATMSAP object enters the STOPPED summary state if
the command is successful. In order for the command to succeed, the LIF object
associated with the ATMSAP object must be in the STOPPED summary state or there
must not be a LIF object associated with the ATMSAP object. If the ATMSAP object
and the LIF object associated with it are both in the STARTED summary state, then
STOP ATMSAP will be rejected. An ABORT LIF command must be issued to the LIF
object before a STOP ATMSAP command can succeed. The command is rejected if
the ATMSAP object is already in the STOPPED summary state.
OUT file-spec
causes any SCF output generated for this command to be directed to the specified
file.
ATMSAP atmsap-name
is the name of the target ATMSAP object. atmsap-name is in the form
$ZZLAN.adapter-id.sac-id.pif-id.atmsap-id
where:
adapter-id
is a 1 to 8-character alpha-numeric string, beginning with an alpha character,
that identifies the parent SLSA ADAPTER. Wildcard characters are allowed.
sac-id
is a number that identifies the parent SAC object. The only valid sac-id for the
ATM3SA adapter is the number “0.” Wildcard characters are allowed.
pif-id
is an alpha character that identifies the parent PIF object. The only valid pif-id
for the ATM3SA adapter is the letter “A.” Wildcard characters are allowed.
STOP [ /OUT file-spec/ ] ATMSAP atmsap-name