TS/MP Pathsend and Server Programming Manual (H06.05+, J06.03+)

partially qualified
file name
A Guardian file name in which only the right-hand file-name parts are specified. The remaining
parts of the file name assume default values. See also fully qualified file name.
PATHCOM The interactive interface to the PATHMON process, through which users enter commands
to configure and manage Pathway applications.
1.
2. The process that provides this interface.
PATHCOM
command file
A file of PATHCOM commands that define and add the PATHMON-controlled objects required
to execute an application. This file can contain all the commands needed to start a PATHMON
environment.
PATHCOM
command terminal
See command terminal.
PATHCTL See PATHMON configuration file.
Pathmaker product A menu-driven application generator, provided by HP, that increases the productivity of
programmers developing Pathway applications. The Pathmaker software generates requester
programs in SCREEN COBOL and server programs in C or COBOL85.
PATHMON
configuration file
A disk file in which a PATHMON process maintains configuration information for the objects
under its control. The name of this file is PATHCTL.
PATHMON
environment
The servers, server classes, TCPs, terminals, SCREEN COBOL programs, and tell messages that
run together under the control of one PATHMON process.
PATHMON log file A file used by a PATHMON process for reporting errors and changes in status.
PATHMON object An object of type PATHMON; that is, a PATHMON process. See also PATHMON process and
PATHMON-controlled object.
PATHMON process The central controlling process in the Pathway environment. The PATHMON process maintains
configuration-related data; grants links to server classes in response to requests from TCPs and
LINKMON processes; and performs all process control (starting, monitoring, restarting, and
stopping) of server processes and TCPs.
PATHMON-controlled
object
An object defined and managed by a PATHMON process, through PATHCOM or the Pathway
management programming interface. In the PATHCOM interface, such an object can be of type
PATHWAY, PATHMON, SERVER, TCP, TERM, PROGRAM, or TELL. See also object and Pathway
object.
pathname See OSS pathname.
Pathsend
procedures
The set of Guardian procedure calls that provide general access to Pathway server classes from
any process on a NonStop system.
Pathsend process A process, written as a Guardian program in C, C++, COBOL85, Pascal, pTAL, or TAL, that
makes calls to Pathsend procedures to request services from a Pathway server. A Pathsend process
can be either a standard requester, which initiates application requests, or a nested server, which
is configured as a server class but acts as a requester by making requests to other servers. A
Pathsend process is also known as a Pathsend requester.
Pathsend program A Guardian program, written in C, C++, COBOL85, Pascal, pTAL, or TAL, that makes calls to
Pathsend procedures to request services from a Pathway server. A running Pathsend program is
called a Pathsend process. See also Pathsend process.
Pathsend requester See Pathsend process.
PATHTCP2 The TCP object file, usually identified by the file name $SYSTEM.SYSTEM.PATHTCP2.
PATHTCPL The TCP user library object file.
Pathway
application
A set of programs that perform online transaction processing tasks in the Guardian environment,
using interfaces defined by HP. A Pathway application can include SCREEN COBOL requesters,
Pathsend requesters, and Pathway servers running on NonStop systems. It can also include GDSX
front-end processes and clients that use RSC/MP or POET. See also NonStop Tuxedo application.
Pathway
application
development
environment
A set of tools supporting the development of applications for the Pathway transaction processing
environment. Depending on the customer’s needs and software configuration, this set of tools
could include the SCREEN COBOL compiler and the SCREEN COBOL Utility Program (SCUP),
the POET application development tools, the Pathmaker product, and various tools from Tandem
Alliance partners. See also Pathway transaction processing environment.
207