NetBatch Management Programming Manual

Glossary
NetBatch Management Programming Manual—522462-003
Glossary-10
null object type
null object type. A place-holder object type that management applications can use in
programmatic commands that do not require explicit specification of a particular
object type.
null value. A value indicating that a program has made no explicit assignment to a variable
or field. For SPI, a field of a structure has a null value if the application has made no
explicit assignment to that field after calling the SSNULL procedure to initialize the
structure.
object. (1) In SPI, an entity subject to independent reference and control by a subsystem:
for example, in NetBatch, an attachment set, class, executor, job, or scheduler. An
object typically has a name and a type known to the controlling subsystem. (2) In DDL,
an item in a dictionary. DDL assigns each object a unique object number for
identification.
object type. The category of objects to which a specific object belongs. A subsystem
identifies a set of object types for the objects it manages. The operator interface to the
subsystem might have keywords to identify the types. The programmatic interface
would have object-type numbers suitable for passing to the SSINIT procedure.
object-name token. A parameter or response token that identifies, by name, a particular
object of a given object type. An object-name token is a type of object-selector token.
See object-selector token.
object-selector token. A token (of the object type given in the command) that identifies one
or more specific objects to operate on. Typically, the value of such a token is either
some form of object name or an object number. An object-name token is a type of
object-selector token. See object-name token.
object-type number. A number representing an object type managed by a subsystem.
Each subsystem with a token-oriented programmatic interface can have its own set of
object-type numbers, represented in DDL by constants and in programs by TAL
LITERAL or DEFINE declarations, C #define directives, COBOL level-01 variables, or
TACL text variables. (In some cases, as with the data communications subsystems,
object-type numbers are shared by several subsystems.) The object-type number is a
header token in commands and responses. See object type.
owner. (1) For a disk file, the user or program that created the file, or a user or program to
whom the creator has given the file with the FUP GIVE command. (2) For a process,
the user or program that created the process or, if the PROGID option was specified in
the FUP SECURE command for the code file, the user or program that owns the code
file. (3) For a token or other definition, the subsystem that provided the definition. (4)
For a subsystem, the company or organization that provides the subsystem, or the
eight-character string identifying that company.
PARAM. A parameter that supplies a user-defined value to a process requesting that value
at creation time. For more information, see the TACL Reference Manual and the TACL
Programming Guide.