Distributed Name Service (DNS) Management Programming Manual

Glossary
Glossary–14 46958 Tandem Computers Incorporated
Restored name definition. A name definition that was resynchronized throughout the
network, after loss and re-availability of the definition node. The user requests
restoration using the DNS RESTORE command. This command deletes copied (and
possibly altered) name definitions resulting from issuance of the DNS COPY
command, and makes the definition node’s version of the definition visible again.
Routine. A sequence of TACL commands and built-in functions that can perform
complex argument interpretation. A routine can interpret an item in its argument
string depending on previous arguments or on the results of any function or program
executed before the argument item is read. Routines construct their own expansions
through the use of the built-in function #RESULT. When the routine name is given to
TACL, the arguments that the routine uses with #RESULT are substituted for the
name. A routine can have a null expansion. Compare with Macro.
Running state. The state in which some required piece of software is present, initialized,
and available to receive requests. In the case of DNS, running state is the operational
state in which all named DNS processes are currently active.
SCF. Abbreviation for Subsystem Control Facility.
SCP. Abbreviation for Subsystem Control Point.
Server class. A set of identical servers whose number can vary with changes in
workload. A requester does not open a specific server of the class; rather, it opens the
class and is assigned a link to an available server.
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 also Maximum field version.
Session. The period during which two entities can exchange data. In the context of a
management application, the period during which an application can issue commands
to a subsystem. In the context of a command interpreter, the period during which a
user can issue commands to the command interpreter.
Simple object. An object that is managed by a single subsystem.
Simple token. A token consisting of a token code and a value of the type indicated in
the token code. Although simple token values can in fact possess an internal structure,
SPI stores and retrieves those values without any knowledge of their structure.
Compare Extensible structured token.
Single-valued. Having one value, rather than an array of values.
SPI. Abbreviation for Subsystem Programmatic Interface.
SPI buffer. A sequence of memory locations used for a message produced by SPI
procedures.