NetBatch Management Programming Manual

Glossary
NetBatch Management Programming Manual—522462-003
Glossary-13
scheduler
scheduler. A process-pair server that stores job records in its database, schedules and
starts jobs, monitors their execution, and records job termination details. The
scheduler’s program file is NETBATCH and its command interface BATCHCOM. The
scheduler queues jobs according to the jobs’ scheduling criteria and dependencies. It
starts the jobs’ executor programs, monitors job execution, and acts as a home
terminal for the jobs’ processes. If any of the job’s processes fail, the scheduler also
can stop, restart, or reschedule a job if the job’s attributes specify such action. A
scheduler records events such as the creation of executor-program processes in a log
file. The scheduler has an EMS interface through which it sends information about
certain scheduler-related and job-related events to an EMS collector. Each scheduler
has its own database whose files record information about the scheduler, its classes
and executors, attachment sets, and jobs. See also NETBATCH.
sensitive command. A command available to a restricted set of users because the
subsystem restricts access to the command. See also nonsensitive command.
server version. The software release version of the server to which a requester using SPI
(such as a management application) is sending a command. If the server version is
older than the maximum field version in a request, the server rejects the request. SPI
puts the maximum field version into the command buffer. The server puts its own
version into each response buffer. See maximum field version.
session. The period during which two entities can exchange data. (1) For a management
application, the period during which an application can issue commands to a
subsystem. (2) For a command interpreter, the period during which a user can issue
commands to the command interpreter. (3) For the ViewPoint console application, the
period between the user’s invoking the application and exiting the application.
simple token. A token consisting of a token code and a value that is either a single
elementary field, such as an integer or a character string, or a fixed
(nonextensible) structure. See also extensible structured token.
special operation. An operation, such as a control operation or an operation that gets
information from the buffer (rather than the header), performed by the SSGET
procedure or the SSPUT procedure. Special operations include getting the length or
number of occurrences of a token, changing the current position, clearing the last-error
information, or deleting a token from the buffer. A program directs SSGET or SSPUT to
perform a special operation by passing to the procedure one of a set of special SPI
token codes. These special token codes do not represent tokens in the buffer but
simply direct SSGET or SSPUT to perform the indicated operations.