NetBatch Management Programming Manual

Glossary
NetBatch Management Programming Manual—522462-003
Glossary-12
response message
response message. An SPI message that is sent from a subsystem to an application
program in reaction to a command message. See SPI message; command message.
response record. A set of response tokens, usually describing the results of performing a
command on one object. A response can consist of multiple response records,
distributed among one or more response messages. A response message always
contains a whole number of response records (that is, a response record cannot be
split between two messages). If there are multiple response records in a response
message, each response record is enclosed in a data list. See also data list. Each
response record must contain a return token; see also return token.
response token. A token returned as an element of a response. Response tokens include
information tokens (which contain response data of interest to the application), syntax
tokens (such as list tokens), one special response-control token (the context token),
the return token, and error tokens.
response-control token. A parameter token or response token that influences or reflects
how a subsystem packages its response to a command. Response-control tokens are
defined by SPI rather than by subsystems. They include the maximum-response token,
the response-type token, and the context token.
return token. The response token that indicates whether a command was successful and
why it failed if it did. Every response record in a response from a NonStop subsystem
contains a return token. A response record also can contain error lists that include
error tokens. The token code for the return token is ZSPI-TKN-RETCODE. Its value
consists of a single integer field. See also error token.
routine. A sequence of TACL commands and built-in functions that can perform complex
argument interpretation. A routine can interpret an item in its argument string by
applying the information received from the execution of previous arguments or by
applying the information received from the results of any function or program executed
before the argument item is read. Routines construct their own expansions by using
the built-in function #RESULT. When the routine name is given to the TACL program,
the arguments that the routine uses with #RESULT are substituted for the name. A
routine can have a null expansion. See also macro.
run calendar. A disk file generated from user-supplied source data by the BATCHCAL
program. The file contains a series of dates and times called run times. You can
schedule a job to run automatically at those times by using the CALENDAR
attribute to assign the file to the job.
run time. The date and time when a job runs.