TS/MP 2.5 Pathsend and Server Programming Manual

link manager A process that requests links to server processes and provides link access after the link is granted.
TCPs and ACS Subsystem processes are the link managers in the Pathway environment. See also
link access and link granting.
lock A mechanism that coordinates access to the same data; locks are either shared or exclusive.
log file See PATHMON log file and event log file.
low PIN A process identification number (PIN) in the range 0 through 255. (PIN 255 is reserved by the
system; it is never assigned to a running process, but is used by high-PIN processes to communicate
with low-PIN processes.) See also process identification number (PIN) and high PIN.
LP64 The C/C++ programming model where the int data type is 32 bits wide, but long and pointer
data types are 64-bits wide; also used as the C/C++ 64-bit compiler pragma. See also
“ILP32” (page 210).
MAKEUL A TACL macro used to perform pTAL compilation of user-written conversion routines for use with
the Pathway/TS TCP and SCREEN COBOL requestors and to create the TNS/R native TCP user
library containing these routines.
manageability The ability to easily and comprehensively manage a subsystem, system, or network.
management
application
An application program that automates configuration and management tasks. Such a program
can request from the PATHMON process the same kinds of services that system managers can
request through the PATHCOM interface. A management application can also interact with
subsystems other than the Pathway subsystem. Management applications use the Subsystem
Programmatic Interface (SPI) to send commands to subsystems and the Event Management Service
(EMS) to receive notification of significant events.
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
requestor.
message-oriented
requestor
A SCREEN COBOL requestor that sends data from working storage to a device (or to a front-end
process that controls a device) and receives data from the device or process into working storage
by way of Message Section templates. SCREEN COBOL requestors that use the intelligent device
support (IDS) facility are message-oriented. These requestors use SEND MESSAGE statements
and their REPLY clauses in the Procedure Division to interact with the intelligent devices or front-end
processes. See also screen-oriented requestor.
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.
mixed data-model
programming
Programming in an environment in which both 32-bit and 64-bit pointers are used within the
same compilation unit.
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.
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 translation server for the NonStop Tuxedo system. Also called a NonStop Tuxedo
native client.
nested server A server that acts as a requestor 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.
no-early-reply rule The rule that states that when a server process reads a request message, it must completely process
the request before it replies to it.
node A NonStop 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.
211