Cluster I/O Protocols (CIP) Configuration and Management Manual (H06.16+, J06.05+)

Table 27 Command and Object Type Abbreviations
AbbreviationObject TypeAbbreviationCommand
CLICLIMABABORT
MOMONADADD
PROCPROCESSALTALTER
PROVPROVIDERDELEDELETE
ROUROUTEINFINFO
LISTOLISTOPENS
NANAMES
PRIPRIMARY
STARSTART
STATUSTATUS
SWSWITCH
TRTRACE
VERSVERSION
Summary States
The CIP subsystem objects have operational states, known as summary states. The summary state
of an object at a given instant is important; certain commands have no effect on an object when
it is in one state but can affect the object when it is in another state.
The summary states supported by the CIP subsystem are STARTED/UP, STARTING, STOPPING,
and STOPPED/DOWN. Table 28: Object Summary States shows states for each object:
Table 28 Object Summary States
STOPPINGSTARTINGSTARTEDSTOPPEDObject
null
XXXCLIM
XXXXMON
XXPROCESS (CIPMAN
or CIPSAM)
XXXPROVIDER
XSUBNET
ROUTE
Table 29: Object State Descriptions describes object states:
Table 29 Object State Descriptions
The object is...In this state...
Running and ready to accept requests from other subsystem components. This state is called STARTED
in SCF and UP in CIP.
STARTED
Defined (that is, the object exists) but is not accepting requests from other subsystem components.
The STOPPED summary state is not applicable to the PROCESS object. If the PROCESS object is
not STARTED, it is undefined (that is, the process does not exist).
STOPPED
222 SCF Reference for CIP