TS/MP 2.5 Management Programming Manual

Table 7 Required Object States for Continuation (continued)
Required StateObject TypeCommand
RUNNING, FROZENSCSTOP
FROZENSCTHAW
Continuation Example
These steps describe what occurs when a management application obtains information about the
SC objects named CLASS-A, CLASS-B, and CLASS-C:
The PATHMON Process…The Application…
1. Specifies ZPWY-CMD-INFO and ZPWY-OBJ-SC with
the SSINIT call.
2. Assigns the constant ZPWY-VAL-ALLSC to the
ZSERVERCLASS field in ZPWY-DDL-SEL-SC.
3. Adds ZPWY-DDL-SEL-SC to the command message using
SSPUT.
4. Issues the command INFO SC.
5. Returns the name of CLASS-A and a context token.
6. Reissues the INFO SC command with the special
selector and adds the context token from the previous
response to the message.
7. Returns the name of CLASS-B and a context token.
8. Reissues the INFO SC command with the special
selector and adds the context token from the previous
response to the message.
9. Returns the name of CLASS-C and a context token.
10. Reissues the INFO SC command with the special
selector and adds the context token from the previous
response to the message.
11. Returns an empty response buffer (the context token is
absent) and the error value ZPWY-ERR-PM-NODATA.
12. Interprets that there are no more SC objects about which
to obtain information.
32-Byte File Names
Some commands require that you send a file name to the PATHMON process through the SPI
interface. A 32-byte field is required to represent file names for DSM, rather than the 24-byte field
that is typically used for this purpose.
Whenever you assign a file name to a field, you must supply the file name such that:
• Bytes 0 to 7 contain the name of the system that hosts the file. The name must include the
leading backslash character (\) and be left justified with filler tokens (ZPWY-DDL-FILLER).
If the system is not part of a network and is not named, bytes 0 to 7 contain the backslash
character (\) followed by 7 blank characters.
• Bytes 8 to 31 contain the file name in local internal form.
Example 1 (page 43) shows examples of acceptable formats for file names:
42 SPI Programming Considerations