TS/MP Management Programming Manual (G06.24+, H06.03+)

SPI Programming Considerations
NonStop TS/MP Management Programming Manual—540082-001
3-26
Server Objects
3. Use the SWITCH PM and CONTROL PM commands to move the primary
PATHMON process back to the configured CPU. The last command in the
sequence should be a CONTROL PM command so that the changes are
recorded in the PATHCTL file.
•
The PATHCOM LOG1 and LOG2 commands are implemented by issuing the
ZPWY-CMD-CONTROL command with the ZPWY-OBJ-PM object.
•
The equivalent of the PATHCOM STATUS PATHMON command is implemented
by issuing the ZPWY-CMD-STATUS command with the ZPWY-OBJ-PM object
followed by the ZPWY-CMD-STATUS command with the ZPWY-OBJ-
PMREQUESTER object.
Server Objects
When developing a management application that defines and manages server classes,
consider:
•
To add a full server class definition, issue an ADD SC command followed by ADD
commands for each of the optional object types desired, namely SCPROCESS,
SCASSIGN, SCPARAM, and SCSTARTUP.
•
When you delete an SC object, all associated objects for that SC are also deleted.
•
An associative server is a process within a server class. An associative server may
be started outside of the Pathway subsystem by a process other than the
PATHMON process that controls the server class but is used by that PATHMON
process. Associative servers are configured with the ZASSOCIATIVE field in
ZPWY-DDL-DEF-SCPROCESS set to ZPWY-VAL-ON.
The PATHMON process can change the state of an associative server from
STOPPED to RUNNING without actually creating a new server. If the PATHMON
process attempts to create an associative server and discovers that the server
already exists, the PATHMON process changes the server state to RUNNING and
uses the existing server (instead of reporting an error).
Similarly, the PATHMON process can change the state of an associative server
from RUNNING to STOPPED even though the process might still be running. This
can occur when:
•
A STOP SC command is issued. The PATHMON process only waits until all
links to the associative server known to the PATHMON are returned by the link
manager (such as the LINKMON process).
or
•
The last link to the associative server known to the PATHMON process is
returned by a link manager (such as the LINKMON process), but the server
was not started by the PATHMON process.
In both of these cases, the PATHMON process changes the state to STOPPED
without waiting for the server to terminate.