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

SPI Programming Considerations

NonStop TS/MP Management Programming Manual—540082-001

3-16

Considerations for SSPUT

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 };

#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 should always call 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 of 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’s attributes—the object-selector token is returned with null values

in each required field and default values in each optional field. Consequently, it is not

necessary for the program to determine either the PATHMON process’s null values or

its defaults.