Pathway Products Glossary

Glossary
Compaq NonStop™ Pathway Products Glossary—426762-001
Glossary-16
Message Section
clauses in the Procedure Division to interact with the intelligent devices or front-end
processes. See also screen-oriented requester.
Message Section. A section in the Data Division of a SCREEN COBOL source program that
describes the data type, size, and relative position (sequence) of each field in a message
template. This section also defines the editing and conversion that must be performed on
each field. See also message-oriented requester
.
migration plan. A set of PLAN objects created by the PXMCFG INVENTORY statement.
A migration plan describes the changes to be made to migrate to a new configuration
online. See also PLAN object
and rolling configurations.
mixed data item. A data item that contains both single-byte and double-byte characters; in a
COBOL or SCREEN COBOL program, these data items are declared as PIC X.
modified data tag (MDT). In SCREEN COBOL, a bit that is set or reset to indicate whether
data in an associated field is to be sent to the computer from the terminal.
multithreaded. A programming model that provides more than one thread of control within a
program. Multithreading allows multiple sequential processing tasks to be executed
concurrently within a process: for example, a terminal control process (TCP). See also
thread
and single-threaded.
N
native System/T client. In the NonStop™ TUXEDO environment, a client program that
executes in the Open System Services (OSS) environment and communicates directly
with System/T. An example of this type of client is the Pathway to TUXEDO translation
server. Also called a NonStop™ TUXEDO native client.
nested server. A server that acts as a requester by sending requests to other servers. In the
Pathway environment, such requests are made by calls to Pathsend procedures.
nld utility. A utility that collects, links, and modifies code and data blocks from one or more
object files to produce a target TNS/R native object file.
node. A system or device that follows the protocols of a specific network and that other
systems or devices in that network can address; for example, a NonStop™ Himalaya
system that is part of an Expand network. The name of the node, also called the system
name, is the first of four parts of a file name in the Guardian environment. See also
Expand networking software
.
NODE object. A configured object in a Pathway/XM environment that defines the system
resources and default object attributes used for either requesters or servers. The ROLE
attribute identifies whether a NODE object will be used for requesters (a client NODE
object) or servers (a server NODE object). A NODE object represents a logical, rather
than a physical (Expand) node. However, it is associated with a physical node.
A Pathway/XM environment includes one or more client NODE objects and one or
more server NODE objects.