NetBatch Management Programming Manual

Glossary
NetBatch Management Programming Manual—522462-003
Glossary-7
header token
header token. A special token type containing information about an SPI message. Header
tokens are common to all or most messages of a specific type and differ from other
tokens in several ways: they exist in the buffer at initialization; their values are usually
set by SSINIT; they occur only once in a buffer; they are never enclosed in a list; they
cannot be moved to another buffer with SSMOVE; and programs cannot position to
them or retrieve their values using a NEXTCODE or NEXTTOKEN operation.
Programs retrieve header-token values by passing appropriate token codes to SSGET
and can change some header-token values by passing the token codes to SSPUT.
Examples of command header tokens are the command, object type, maximum-
response, server-version, maximum-field-version, and checksum tokens. Examples of
event-message header tokens are the event number, the event generation time, the
logging time, the maximum-field-version token, and the checksum token.
header type. A header token in an SPI message that indicates whether the message is a
command or response message, or an event message.
high PIN. A process identification number in the range 256 through 65535. See also low
PIN.
implicit command. A default command effective in the absence of an explicit command.
information token. A response token that conveys information requested by a command,
as opposed to one that serves a syntactical purpose such as delimiting a list, indicates
response continuation, identifies how a command completed, or identifies an error.
Object-selector tokens, attribute tokens, status tokens, and statistics tokens are types
of information tokens.
initial position. The location in an SPI buffer just prior to the first token that is not a header
token. See also current position; next position.
initialize. To prepare a data structure to have values assigned to it. For example, the SPI
SSINIT procedure initializes the buffer by building the message header. The SSNULL
procedure initializes an extensible structured token by assigning null values to the
fields of the structure.
input file. A file containing information an executor program needs to execute a job. For
example, the input file for an NBEXEC process contains NBEXEC commands. The
input file for a COBOL compiler process contains the program source.
interactive session. See session.