NetBatch Management Programming Manual
Glossary
NetBatch Management Programming Manual—522462-003
Glossary-6
event message
event message. (1) In programmatic interfaces based on SPI, a special type of SPI 
message that describes an event occurring in the system. (2) In the ViewPoint console 
application, the displayed form of such a message, shown as one text line. 
executor. A logical entity in the scheduler. An executor’s purpose is to link jobs through 
their classes to a processor. This link enables the scheduler to execute, in the specified 
processor, the initial process (the executor program) of each job. Executors act as 
gateways between classes and processors. When started, an executor allows one job 
at a time from the classes to run in its processor. No other jobs can use the executor 
until the job finishes. Stopping an executor prevents jobs from using it to gain access to 
its processor. The number of started executors determines how many jobs can run 
together. For example, a scheduler with 10 started executors can run up to 10 jobs 
concurrently. 
executor program. A program file started as the initial process of a job by a NetBatch 
scheduler. (The process executes the commands contained in the job’s input file.) 
explicit command. A command entered by a user or specified in an input file. 
extensible structure. A structure declared for the value of an extensible structured token. 
See also extensible structured token; fixed structure. 
extensible structured token. A token consisting of a token code and a value that is an 
extensible structure. HP can extend extensible structures by adding new fields at the 
ends of the structures. Such structures are typically used to indicate the attributes of an 
object being operated on and to return status and statistics information in responses. 
They can also be used for other purposes. The token is referenced by a token map 
that describes the structure to SPI so SPI can provide compatibility between different 
versions of the structure. See also simple token; structure; structured token.
filter. A file containing a list of criteria against which incoming event messages can be 
compared. The filter allows messages that satisfy the criteria to pass through it to the 
application. Messages that do not satisfy the criteria cannot pass through the filter. 
fixed structure. A structure declared for the value of a simple token that includes several 
fields. Fields cannot be added to fixed structures. See also extensible structure.
forwarding distributor. An EMS distributor process that sends selected event messages to 
an EMS collector on another node. See also consumer distributor; printing distributor.
GETVERSION command. An information command that reports to the requester the server 
version of the subsystem server and possibly additional version information about 
objects defined by the subsystem. All NonStop subsystems with a programmatic 
command interface based on SPI have a GETVERSION command. 
group manager. A user whose Guardian user ID is n,255 (for example, 205,255). See also 
non-super-group user; super ID; super-group user.
header. See SPI message header. 










