TS/MP 2.5 Management Programming Manual
Table 5 TS/MP Programmatic Commands (continued)
DescriptionCommand
Prohibits all link managers (such as ACS subsystem process
or Pathway/iTS TCPs) from sending requests to a server
class if the object is not active
ZPWY-CMD-FREEZE
Obtains the version of an objectZPWY-CMD-GETVERSION
Obtains the configuration of an objectZPWY-CMD-INFO
Stops a Pathway subsystem more quickly and easily than
the STOP PATHWAY command
ZPWY-CMD-SHUTDOWN2
Initiates operation of an objectZPWY-CMD-START
Obtains resource usage and performance statistics for an
object
ZPWY-CMD-STATS
Obtains current status of an object or ACS subsystem
process
ZPWY-CMD-STATUS
Stops an object if the command is used after certain
conditions are met
ZPWY-CMD-STOP
Exchanges the function of an object primary process with
the function of the backup process
ZPWY-CMD-SWITCH
Allows link managers (such as ACS subsystem process and
Pathway/iTS TCPs) to send to the server class
ZPWY-CMD-THAW
These commands and the Pathway subsystem responses to them are described in “Pathway
Subsystem Control Commands” (page 117) and “Server Class Commands” (page 130).
Object Types
All commands and responses contain an object-type token in the header. For the Pathway subsystem,
object types are identified in programs by symbolic names of the form ZPWY-OBJ-name, where
name identifies the object type. For example, the PM object type is represented by the name
ZPWY-OBJ-PM. The object-type header token, ZSPI-TKN-OBJECT-TYPE, always has one of these
names.
For TS/MP commands, the Pathway subsystem supports the programmatic objects listed in Table 6
(page 32).
Table 6 TS/MP Object Types
DescriptionObject Type
LINKMON Object
A LINKMON process.ZPWY-OBJ-LM
PATHWAY Objects
The PATHMON configuration file.ZPWY-OBJ-PATHCTL
The Pathway subsystem (that is, a single PATHMON process
and all objects controlled by that process).
ZPWY-OBJ-PATHWAY
PATHMON Objects
The PATHMON process that controls the Pathway subsystem.ZPWY-OBJ-PM
A single requester of a PATHMON process. The requester can
be a PATHCOM process, an SPI process, a Pathway/iTS
ZPWY-OBJ-PMREQUESTER
32 SPI Programming Considerations










