NetBatch Management Programming Manual

Glossary
NetBatch Management Programming Manual522462-003
Glossary-8
job
job. A process or a sequence of processes that performs specified tasks. All NetBatch jobs
have an executor program and, depending on the program, an input file. The input file
contains commands executed by the executor program, which the NetBatch scheduler
starts as the job’s initial process. The executor-program process can start other
processes after the initial process has been started.
list. In a SPI message, a group of tokens that defines a context for scanning the buffer and
extracting tokens with the SSGET procedure. A list construct imposes hierarchy in the
buffer. To retrieve the tokens from a list, the application must first position to the start of
the list by retrieving the initial list token, retrieve tokens from the list, then pop out of the
list to the next higher level of tokens by retrieving the end-list token. SPI defines three
types of lists: data lists, error lists, and generic lists.
list token. A syntax token that begins a list. SPI defines three different tokens to begin a list,
depending on the type of list: the data-list token, the error-list token, and the generic-
list token. See also end-list token; syntax token.
low PIN. A PIN in the range 0 through 254. (Technically, PIN 255 also is a low PIN although
it is never assigned to a running process.) See also high PIN.
macro. A sequence of TACL commands and built-in functions that can contain dummy
arguments, thus providing a means for simple argument substitution. No validity
checking of the arguments is performed. When the macro name is given to the TACL
program, the program substitutes the expansion of the command sequence for the
name, replacing any dummy arguments with parameter values supplied when the
macro was invoked. See also routine.
management application. A program or set of programs that issues commands to
subsystems, retrieves event messages, or performs both functions, to aid in
managing a computer system or a network of systems. A management application is a
requester with respect to the subsystems to which it sends commands. The
subsystems are servers with respect to the management application.
management interface. An interactive or programmatic interface through which one can
manage a subsystem and its objects. In some subsystems, a specific process is
dedicated to the management interface. In other subsystems, the process that
provides the management interface also performs other functions.
management process. The process through which an application issues commands to a
subsystem. A management process can be part of a subsystem, or it can be
associated with more than one subsystem. In the latter case, the management process
is logically part of each of the subsystems. PATHMON is an example of a management
process.
master job. A job specified by a dependent job’s WAITON attribute. Execution of the
dependent job depends on its release by the master job. See also dependency;
dependent job.