TS/MP 2.5 Management Programming Manual

Using ZSPI-TKN-MAXRESP
ZSPI-TKN-MAXRESP is used by some subsystems to enable multiple responses in a single response
buffer. Because the Pathway subsystem does not support multiple responses in a single response
buffer, ZSPI-TKN-MAXRESP is only useful if your management application must handle all subsystems
in a consistent manner; that is, if Pathway responses must be enclosed in data lists. To reference
the Pathway subsystem alone, you do not have to specify ZSPI-TKN-MAXRESP.
You can include ZSPI-TKN-MAXRESP by using SSINIT or SSPUT. If you do not include this token in
the command message or set the value to zero (if included), then the PATHMON process returns
a single response. If you include ZSPI-TKN-MAXRESP and assign a nonzero value, the PATHMON
process returns a single response and encloses that response in a data list. (The ZSPI-TKN-DATALIST
token precedes the response, and the ZSPI-TKN-ENDLIST token follows the response.)
Declaring the Pathway Subsystem ID
The Pathway subsystem ID is expressed by the value ZPWY-VAL-SSID, defined in “SPI and EMS
Standard Definitions” (page 50).
These declarations produce an appropriately initialized structure for COBOL. For TAL, TACL, and
C, your program must initialize the structure explicitly. For example:
For TAL:
ZPWY^VAL^SSID.Z^OWNER.Z^B ':=' [ ZSPI^VAL^TANDEM ];
ZPWY^VAL^SSID.Z^NUMBER := ZSPI^SSN^ZPWY;
ZPWY^VAL^SSID.Z^VERSION := ZPWY^VAL^VERSION;
For TACL:
#SET ZPWY^VAL^SSID &
[ZSPI^VAL^TANDEM].[ZSPI^SSN^ZPWY].[ZPWY^VAL^VERSION]
For C:
zpwy_val_ssid_def zpwy_val_ssid ={ ZSPI_VAL_TANDEM,
ZSPI_SSN_ZPWY
ZPWY_VAL_VERSION };
or
#string.h
strcpy ( zpwy_val_ssid.z_owner, ZSPI_VAL_TANDEM };
strcpy ( zpwy_val_ssid.z_number = ZSPI_SSN_ZPWY };
strcpy ( zpwy_val_ssid.z_version = ZPWY_VAL_VERSION };
Considerations for SSPUT
The Pathway subsystem does not support multiple commands in the same message or arrays or
multiple occurrences of the same token.
Considerations for SSNULL and Extensible Structured Tokens
Your program calls SSNULL to initialize an extensible structured token before assigning values to
fields in that token, even if you assign a value to each field and even if the extensible structured
token has only one field. Using SSNULL allows your program to accommodate future expansion
in the extensible structured tokens.
Null Values and Defaults
You can set all the fields in any of the Pathway extensible structured tokens to null values by calling
SSNULL. In an ADD command, required fields containing the null value cause the PATHMON
process to return an error. Fields that are not required and that contain a null value take on their
default values when sent with an ADD command. Any field can be null in an ALTER command;
the null value means NO CHANGE.
Issuing an INFO command with a null object-selector (SEL-) token returns the default values for an
object attributes—the object-selector token is returned with null values in each required field and
Building and Sending a Command Message 39