SCF Reference Manual for J-Series and H-Series RVUs

SCF Commands
SCF Reference Manual for J-Series and H-Series RVUs—529649-003
5-115
STOP Command
STOP Command
The STOP command terminates the activity of an object in a normal manner. It
terminates all connections to and from the object in a nondisruptive way. Upon
successful completion of the STOP command, configured objects are left in the
STOPPED state and nonconfigured objects are deleted. The use of this command is
subsystem-specific.
This command is sensitive.
OUT file-spec
causes any SCF output generated for this command to be directed to the specified
file. The variable file-spec is defined on page 5-9.
object-spec
designates the objects to be stopped. The variable object-spec is defined on
page 5-2. If object-spec is omitted, the assumed object is stopped. (See
ASSUME Command on page 5-36.) The objects that can be stopped and the
speed with which they can be stopped depend on the subsystem.
ORDERLY
optionally allows the data flow between the object and application programs to
continue until a request or set of requests finishes. The object is then stopped.
FORCED
optionally stops the object immediately.
SUB [ subobjtype ]
selects the subordinate objects the command affects. The variable subobjtype
can be a subordinate object type or one of the keywords ONLY, ALL, or NONE, as
explained under SCF Subdevices on page 3-5.
SEL [ NOT ] state
directs the command only at objects in the specified state or only at those not in
the specified state. Valid states are listed in Table 3-1 on page 3-7. The use of
this option is subsystem-specific.
STOP [ /OUT file-spec / ] [ object-spec ]
[ , { ORDERLY | FORCED } ] [ , SUB [ subobjtype ] ]
[ , SEL [ NOT ] state ]