TS/MP 2.5 System Management Manual

Intelligent Devices
Intelligent devices—such as automated teller machines (ATMs), workstations, and barcode
readers—can access server classes through SCREEN COBOL requestor programs and the TCP, a
process supported under the Pathway/iTS product.
This access route is possible when the intelligent device support (IDS) facility, which is part of the
TCP, is used. By delegating some processing to the intelligent device, IDS makes better use of the
device’s processing ability and reduces the workload of the NonStop system.
SNA Devices
Requests from SNA devices can be handled by SNAX High-Level Support (SNAX/HLS), which
allows NonStop application programs to communicate with SNA devices and host software. Using
SNAX/HLS, NonStop applications can:
• Access IBM host software products (such as CICS and IMS) for distributed transaction processing
• Communicate with intelligent SNA controllers such as the IBM 3600 or 4700 Financial
Subsystems, or the IBM 3650 Retail Subsystem
The application interface to SNAX/HLS requires little detailed knowledge of SNAX or SNA. For
more information about the SNAX/HLS product, see the SNAX/HLS Configuration and Control
Manual.
Unsupported or Special-Function I/O Devices
Requests from unsupported or special-function I/O devices can be handled by the HP Extended
General Device Support (GDSX) product. GDSX is designed to help you develop a front-end process
that translates requests into a format supported by the ACS subsystem processes, or (under
Pathway/iTS) a TCP.
GDSX is a complex product. Before choosing to use GDSX, determine whether the ACS subsystem
processes can manage the requests alone. If your environment includes Pathway/iTS, investigate
whether the PATHMON process and TCP can handle your application requirements. If the specified
data communications protocols are not supported by existing Pathsend requestors or (under
Pathway/iTS) a TCP, you might decide to use a GDSX process as a front end to the application.
Using the GDSX product, you can implement message switching, develop and modify data
communications protocols, and perform data-stream conversions, all of which facilitate access to
server processes. For more information about the GDSX product, see the Extended General Device
Support (GDSX) Manual.
Pathsend Processes
Pathsend processes (also called Pathsend requestors) are user applications that access server
classes using Pathsend procedure calls. These procedure calls are part of the Guardian procedure
library. RSC and POET workstation clients are examples of applications that communicate with
server processes indirectly by means of Pathsend requestors created by RSC on behalf of the clients.
The ACS subsystem processes manage communications between Pathsend processes and server
classes. System management issues related to Pathsend are described in “Managing the Pathsend
Environment” (page 109) of this manual. (For information about how to write Pathsend programs,
see the TS/MP 2.5 Pathsend and Server Programming Manual).
Figure 6 (page 27) shows a PATHMON environment with Pathsend requestors. Link management
functions for Pathsend requestors are provided by the ACS subsystem processes $ZL01 and $ZL02.
The ACS subsystem processes service requests only from Pathsend processes executing in its
processor. $PMB is the PATHMON process controlling the pathway environment.
26 Introduction to NonStop TS/MP System Management