Distributed Systems Network Management (DSNM) Subsystem Interface Development Guide
DSNM Commands
Distributed Systems Network Management (DSNM) Subsystem Interface Development 
Guide—109759 2-21
The STOP Command
The STOP Command
Use the STOP command to stop objects.  The command causes DSNM to issue the 
appropriate subsystem commands to stop each object after all current and outstanding 
operations are complete.
If all objects specified in the command are successfully stopped, there is no command 
response. If the command fails to stop any object, there is a response, listing the objects 
that were not stopped. If the command contains a syntax error, you receive an error 
message, and the objects are not stopped.
If you wish to stop objects immediately, regardless of outstanding operations, use the 
ABORT command.
objectspec
is the object specification.  The syntax for the object specification is provided in 
“Object Specification” on page 2-2.
hierarchy-modifier
determines which objects are affected by the command, based on the subsystem 
object hierarchy: ONLY, SUBONLY, or ALL (default).
error-modifier
determines how much information is reported when the command is correct but the 
objects against which the command is being applied produce errors. The error 
modifier does not affect the command response for errors that result when a 
command is entered incorrectly or when a name cannot be resolved. Possible error 
modifiers are ERROR-BRIEF (default), ERROR-DETAIL, and 
ERROR-SUPPRESS.
state-modifier
restricts the scope of the command to a subset of the specified objects, depending on 
their states: UP, NOT-UP, DOWN, or NOT-DOWN. If you do not specify a value 
for the state modifier, DSNM applies the command to all objects that match your 
object specification, regardless of their states.
Considerations
An object engaged in a lengthy operation can take a long time to stop. Therefore, the 
subsystem commands issued by DSNM to stop the objects, and thus the DSNM STOP 
command itself, can be complete before the objects actually stop. Consequently, some 
of the objects can still be stopping for some time after the STOP command is issued, 
STOP objectspec [, objectspec ]...
 [, hierarchy-modifier ]
 [, error-modifier ]
 [, state-modifier ]










