Safeguard Management Programming Manual (G06.29+, H06.08+, J06.03+)

Glossary
Safeguard Management Programming Manual—422086-028
Glossary-2
command number
command number. A number that represents a particular command to a subsystem. Each
subsystem or management process with a token-oriented programmatic interface can
have its own set of command numbers, which are represented in DDL by constants
and in programs by TAL literals or defines, COBOL level-01 variables, C #defines, or
TACL text variables. The command number is a header token in command and
response messages.
compatibility. The ability of two or more elements in a system to work together correctly.
See also version compatibility.
compatibility distributor. An Event Management Service (EMS) distributor process that
filters event messages according to fixed (rather than user-specified) criteria, obtains
text for these messages that is compatible with the operator console for RVUs earlier
than C00, and writes it to the standard console-message destinations. See also
distributor, consumer distributor, forwarding distributor, and printing distributor.
conditional token. A token that is sometimes, but not always, present in a particular event
message. See also unconditional token and NonStop internal token.
configuration file. A file that contains only configuration data.
consumer distributor. An Event Management Service (EMS) distributor process that
returns selected event messages to management applications upon request. See also
compatibility distributor, forwarding distributor, and printing distributor.
constant (DDL). A DDL object that associates a name with a number or string. When DDL
is used to create a set of definitions, a constant defined to DDL becomes a literal or
define in TAL, a level-01 variable in COBOL, a #define in C, and a text variable in
TACL. In the definition files supplied by HP, DDL constants are used for command
numbers, object-type numbers, error numbers, subsystem numbers, token data-type
numbers, token numbers, and other useful values.
context, context information. The information required by a subsystem to process a
command that requires more than one interchange of command and response
messages. Continuation of a response in multiple response messages from the
subsystem requires the subsystem to send the context information to the application
program. The application program, in turn, must send that information back to the
subsystem in a new command message so that the subsystem can continue with the
response. See context token
.
context-free server. A server that does not retain any information about previous
processing. It knows only about its processing of the current request message. For
instance, a context-free subsystem that is performing a command on a list of objects
and sending its response in a series of response messages does not retain the name
of the last object it processed in the last response message. The application program
must therefore resend the command with a context token that contains that
information. A context-free server allows the requester to interrupt or abandon the
continuation of a series of response messages.