NetBatch Management Programming Manual

Glossary
NetBatch Management Programming Manual—522462-003
Glossary-11
parameter token
parameter token. (1) In control and inquiry, a token supplying parameter information for a
command. Most tokens in a command message are parameter tokens. Depending on
the subsystem, they can include attribute tokens, object-selector or object-name
tokens, and subsystem-control tokens. See also syntax token. (2) In event
management, a token representing a parameter passed by an application to an event-
message filter. Such tokens are kept in a parameter buffer. For more information, see
the EMS Manual.
PIN. A unique, system-assigned identifier of a process running in a processor. See also high
PIN; low PIN.
predefined value. A commonly used value that is given a name in a definition file.
printing distributor. An EMS distributor process that sends selected event messages to
printers, devices, or files. See also consumer distributor; forwarding distributor.
private token type. A token type defined by, and specific to, a particular subsystem. A
private token type is built from standard SPI token data types although it might have
additional semantic connotations for the subsystem. See token type.
procedural interface. A means of getting system or application program services through
procedure calls. Also, the set of procedures through which services are obtained. For
instance, an application has a procedural interface to SPI. That interface comprises the
procedures SSINIT, SSNULL, SSPUT, SSPUTTKN, SSGET, SSGETTKN, SSMOVE,
and SSMOVETKN.
processor. A computer component whose parts include circuits controlling the interpretation
and execution of instructions.
process identification number (PIN). See PIN.
programmatic command. A command issued by a program rather than by a human user.
programmatic interface. A means for a program to communicate with another program.
On a NonStop system, a programmatic interface typically includes a message format,
a set of message formats, or a set of procedures (such as the SPI procedures) to build
and decode messages; definitions of message elements (commands, data types,
objects, parameters, response data, errors, and so on); rules for communication
between the requester and the server; and software to receive and respond to
messages defined for the interface.
requester version. The software revision level of the definition files used in the compilation
of a requester. Each subsystem has its own definitions, so the requester version can
differ in requests to different subsystems.
response. The information or confirmation supplied by a subsystem in reaction to a
command. A response is typically conveyed as one or more interprocess messages
(response messages) from a subsystem to an application.