TS/MP 2.5 System Management Manual

• Application Cluster Services (ACS) Subsystem Processes— These processes use Pathsend
requestors to provide link management functions for applications. (Pathsend requestors are
user applications that use Pathsend procedure calls to send requests to server classes.) In
TS/MP, ACS subsystem core processes replace the TS/MP 2.0 LINKMON process. (Although
TS/MP has a ROUT process with $ZLnn names, similar to what TS/MP 2.0 uses, the TS/MP
ROUT is a redirector process that is part of the ACS subsystem. The TS/MP ROUT object is
also located in the SYSnn subvolume, not in the SYSTEM subvolume.) The ACS subsystem must
be configured and started (that is, $ZACS must be running) before using Pathsend requestors.
For more information on ACS subsystem, see the TS/MP 2.5 Release Supplement.
• Pathway Domain Management Interface (PDMI)— A new management interface introduced
in TS/MP. PDMI is an interactive management interface with a set of commands to configure,
operate, control, and collect information for multiple PATHMON processes, with replicated
configurations, under a single Pathway domain. Additionally, TS/MP has enhanced PATHMON
and PATHCOM processes, which now provide support for the new PDMI. For more information
on PDMI, see the TS/MP 2.5 Release Supplement.
NOTE: PDMI is configured and managed by a new program, called PDMCOM, which
provides a command-line interface. The PDMCOM program is a superset of the PATHCOM
command interface, and by default, the PDMCOM object resides in $SYSTEM.SYSTEM.
Objects and Processes Provided by Pathway/iTS
The elements of a Pathway environment are provided by the Pathway/iTS product. Information
about configuring and managing these items is covered in the Pathway/iTS System Management
Manual.
• TCP objects—Terminal control processes that run screen (SCREEN COBOL) programs and
coordinate communication between screen programs, input-output devices or processes, server
processes, and the PATHMON process.
• TERM objects—Definitions of tasks that use screen programs to control inputoutput devices
such as terminals and workstations, or input-output processes that allow users to communicate
with an OLTP application.
• PROGRAM objects—Templates for creating and starting temporary TERM objects.
Pathway Environment Configurations
Depending on your configuration, a Pathway environment might also include other software, such
as TMF and the run-time portion of the Remote Server Call (RSC) product, and the Pathway Open
Environment Toolkit (POET) run-time environment.
Figure 1 (page 19) illustrates a Pathway environment that includes the NonStop TS/MP product
and the Pathway/iTS product. In this example, a remote system uses Pathsend requestors to access
the server processes, with link management provided by ACS subsystem processes. A set of
Pathway/iTS application terminals makes requests through the TCP. Additional elements of the
application include the PATHMON process that manages the TCP, TERM, and SERVER objects, a
command terminal running PATHCOM, and a management programming application.
Figure 2 (page 20) shows an example of a NonStop TS/MP application configured in two operating
environments. A remote system sends Pathsend requests to the ACS subsystem processes, which
manages communications with the server classes. One server class is configured in the OSS
operating environment. The other server class resides in the Guardian operating environment. The
PATHMON process, the PATHCOM interactive interface, and a management programming
application are all Guardian processes.
18 Introduction to NonStop TS/MP System Management