SPI Programming Considerations
NonStop Pathway/iTS Management Programming Manual—426749-002
3-32
Programming Considerations for Specific Object
Types
Programming Considerations for Specific
Object Types
The following paragraphs discuss special programming considerations for each
Pathway/iTS object type.
TCP Objects
When developing a management application that defines and controls TCPs, consider
the following:
•
To perform the equivalent of the PATHCOM STATS TCP, DETAIL command,
follow these steps:
1. Issue the STATS TCP command, initializing the ZTCP field in
ZPWY-DDL-SEL-TCP to the TCP name.
2. Issue the STATS TCPSC command, initializing the ZTCP field in
ZPWY-DDL-SEL-TCPSC to the TCP name and initializing the
ZSERVERCLASS field to ZPWY-VAL-ALLSC. Reissue the STATS TCPSC
command repeatedly, using the context token returned by PATHMON, until no
data is returned in the reply buffer.
3. Issue the STATS TCP command, initializing the ZTCP field in
ZPWY-DDL-SEL-TCP to ZPWY-VAL-ALLTCP. Reissue the STATS TCP
command repeatedly, using the context token returned by PATHMON, until no
data is returned in the reply buffer.
4. Issue the STATS TCPTERM command, initializing the ZTCP field in
ZPWY-DDL-SEL-TCPTERM to the TCP name identified in Step 1, and
initializing the ZTERM field to ZPWY-VAL-ALLTERM. Reissue the STATS
TCPTERM command repeatedly, using the context token returned by
PATHMON, until no data is returned in the reply buffer.
•
To perform the equivalent of the PATHCOM PRIMARY TCP command, follow
these steps:
1. Use LOOKUPPROCESSNAME to find the processor in which the TCP is
actually running.
2. Use INFO TCP to determine the TCP’s configured processor.
3. Use SWITCH TCP and CONTROL TCP to move the TCP’s primary process
back to the configured processor. The last command in the sequence should
be a CONTROL TCP command so that the changes are recorded in the
PATHCTL file.
•
To perform the equivalent of the PATHCOM STATUS TCP, DETAIL command,
follow these steps:
To Next Page
Loading...
Need help?
General