TS/MP 2.5 Pathsend and Server Programming Manual

Pathway server A server process or program in the Pathway transaction processing environment. See also NonStop
Tuxedo server.
Pathway
subsystem
The PATHMON environment components to which SPI commands are sent under the Pathway
subsystem ID and which generate EMS event messages with the Pathway subsystem ID. All SPI
commands for the Pathway subsystem are sent to the PATHMON process, but the processsing
for the command might involve other processes, such as a TCP. Likewise, all EMS messages from
the Pathway subsystem are generated by the PATHMON process, but the information might
originate from another process. See also subsystem ID.
Pathway system A term formerly used for the set of objects managed by a particular PATHMON process; now
called PATHMON environment. See PATHMON environment.
Pathway
transaction
processing
environment
A run-time environment consisting of HP’s transaction-processing products for the Guardian
operating environment. This term is often shortened to “Pathway environment.” Depending on
the customer’s needs and software configuration, the Pathway environment could include TS/MP,
the runtime portions of Pathway/iTS (the TCP and the SCREEN COBOL run-time environment),
TMF, GDSX processes, the run-time portion of the RSC/MP product, the POET run-time environment,
and the TRANSFER delivery system (when used as a workflow aid in transaction processing). See
also NonStop Tuxedo transaction processing environment.
Pathway
translation server
for the NonStop
Tuxedo system
A server process, provided by HP as part of the NonStop Tuxedo product, that allows a Pathway
(SCREEN COBOL or Pathsend) requestor to use the services of a NonStop Tuxedo server. The
translation server therefore acts as a gateway process between the Pathway environment and
the NonStop Tuxedo environment. Requestors that use this translation server must include special
information in the header of each request message to identify the target NonStop Tuxedo
application and service.
Pathway/iTS An HP product that provides tools for developing and interpreting screen programs to support
OLTP applications in the Guardian environment on NonStop systems. Pathway/TS screen programs
communicate with terminals and intelligent devices. Pathway/TS includes the TCP, the SCREEN
COBOL compiler and run-time environment, and the SCREEN COBOL Utility Program (SCUP). It
requires the services of the TS/MP product. See also NonStop Transaction Services/MP (TS/MP).
PIN See process identification number (PIN).
POBJ The default prefix, or file-name root, used by the SCREEN COBOL compiler in naming its output
files. If no prefix is specified in the RUN command to run the compiler, the compiler produces a
code file named POBJCOD, a directory file named POBJDIR, and (if the SYMBOLS option is
enabled) a symbols file named POBJSYM.
POET See Pathway Open Environment Toolkit (POET).
Portable
Transaction
Application
Language (pTAL)
A machine-independent systems programming language based on TAL. The pTAL language
excludes architecturespecific TAL constructs and includes new constructs that replace the
architecturespecific constructs. See also Transaction Application Language (TAL).
primary process The currently active process of a process pair in the Guardian environment. See also backup
process and process pair.
process A unique execution of a program in the Guardian environment.1.
2. An entity in the OSS environment consisting of an address space, a single thread of control
that executes within that address space, and the system resources required by that thread
of control. See also process type.
process
identification
number (PIN)
An unsigned integer that identifies a process within a processor module in a NonStop system.
process
management
The act of configuring, creating, and initializing processes; the monitoring and stopping of
processes; and the recovery of failed processes. The PATHMON process provides process
management functions for OLTP applications on NonStop systems.
process pair A fault-tolerant arrangement of processes in the Guardian environment, whereby two processes
in separate processors share the same name and execute identical code. One process functions
as the primary process and the other functions as the backup process. The two processes are
kept in sync through checkpoint messages sent from the primary to the backup process. If the
215