Distributed Systems Network Management (DSNM) Subsystem Interface Development Guide

The STOP Command
4-20
109759—Distributed Systems Network Management (DSNM) Subsystem Interface
Development Guide
DSNM Command Requirements
The STOP Command
STOP issues the subsystem command(s) that bring objects to a nonoperational state (the
subsystem state equivalent to the DSNM state ZDSN^STATE^DOWN or
ZDSN^STATE^RED). Objects should be brought down gracefully if the subsystem
supports it, allowing current operations to terminate normally.
Valid Modifiers
HMOD, EMOD, SMOD.
RMOD does not apply and should be ignored if present.
Output Object Requirements
Commands to stop subsystem objects should be issued for objects obtained by applying
the hierarchy (HMOD) and state (SMOD) modifiers to each input list object.
STOP must be performed on objects in the order they appear in the input list.
Build an output object structure for only those objects that cannot be aborted, consistent
with the EMOD value (see the error modifier discussion in “The Error Modifier
(_INPUT.MOD.Z^EMOD)” on page 4-6).
Objects stopped successfully do not generate a response. ZDSN^EMOD^SUPPRESS
causes all objects to be omitted from the response.
Note. If the subsystem makes no distinction between stopping objects gracefully and
otherwise, the DSNM STOP and ABORT commands perform the same operation.
Note. Many subsystems produce a warning if a STOP operation is issued for an object that is
already stopped. Such a warning should be ignored; do not report it as an error.