EasyManuals Logo

HP NonStop Pathway/iTS User Manual

HP NonStop Pathway/iTS
694 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Page #70 background imageLoading...
Page #70 background image
SPI Programming Considerations
NonStop Pathway/iTS Management Programming Manual426749-002
3-36
Unlisted Tokens
The notation used for simple tokens in the syntax box is an abbreviated version of the
essential information given in the DDL TOKEN-CODE statement. You define
extensible structured tokens by using DDL DEFINITION statements.
The order of the tokens in the syntax box is not necessarily the order in which they
must occur in a command or response buffer—except for the ZSPI-TKN-ENDLIST
token. The ZSPI-TKN-ENDLIST token always appears at the end of a list that begins
with the ZSPI-TKN-DATALIST or ZSPI-TKN-ERRLIST token.
Data lists and error lists are always indicated with an ellipsis (...). Data lists begin with
the ZSPI-TKN-DATALIST token (followed by an ellipsis), and error lists begin with the
ZSPI-TKN-ERRLIST token (followed by an ellipsis). Both types of lists (data and error)
end with the ZSPI-TKN-ENDLIST token. The ZSPI-TKN-ENDLIST token is indented to
symbolize that it is only used if a list token is present. For more information on data
lists and error lists, see the SPI Programming Manual.
Unlisted Tokens
The following tokens can be present in command and response buffers but are not
repeatedly listed or described in each command unless command-specific information
is necessary:
See the descriptions of these tokens earlier in this section. For information about error
tokens and error lists, see Section 11, TCP Event Messages, and Section 12, TCP
Error Messages.
Required Tokens and Fields
For each token in the command buffer and for each field of an extensible structured
token in the command buffer, the syntax box contains an indication of whether or not
the token or field must be present in the command.
For a token, the notation “!r” means that the token must be present (is required) in the
command. The absence of the notation “!r” means that the token is optional. For a field
of an extensible structured token, the notation “!r” means that the field must have a
Description Token Token Type
Message header tokens N.A. N.A.
Response-control token ZSPI-TKN-MAXRESP ZSPI-TYP-INT
Data list tokens
(These are present only when the
response-control token is used and
set to any nonzero value.)
ZSPI-TKN-DATALIST
ZSPI-TKN-ENDLIST
ZSPI-TYP-LIST
ZSPI-TYP-SSCTL
Return code token ZSPI-TKN-RETCODE ZSPI-TYP-INT
Error list tokens
(These are returned only when an
error is detected.)
ZSPI-TKN-ERRLIST
ZSPI-TKN-ENDLIST
ZSPI-TYP-LIST
ZSPI-TYP-SSCTL

Table of Contents

Questions and Answers:

Question and Answer IconNeed help?

Do you have a question about the HP NonStop Pathway/iTS and is the answer not in the manual?

HP NonStop Pathway/iTS Specifications

General IconGeneral
BrandHP
ModelNonStop Pathway/iTS
CategorySoftware
LanguageEnglish

Related product manuals