Pathway/iTS System Management Manual (G06.24+)

Introduction to Pathway/iTS System Management

HP NonStop Pathway/iTS System Management Manual—426748-002

1-17

Intelligent Devices

Intelligent devices—such as automated teller machines (ATMs), workstations, bar-code

readers, and machines running the Unix operating system—can access Pathway

server classes through SCREEN COBOL requester programs and the TCP.

This access route is possible when you use the intelligent device support (IDS) facility,

which is part of the TCP. 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. For Unix machines and other intelligent devices that use the sockets

protocol, the Pathway/iTS router process provides link-management and load-

balancing functions.

SNA Devices

Requests from SNA devices can be handled by SNAX High-Level Support

(SNAX/HLS), which allows Pathway application programs to communicate with SNA

devices and host software. Using SNAX/HLS, Pathway 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

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

TCP or the LINKMON process.

Because GDSX is a complex product, you should not use it to implement an

application if the PATHMON process and the TCP can handle the application

requirements. However, you might want to use a GDSX process as a front end to a

Pathway application if:

•

The specified data communications protocols are not supported by the TCP or the

LINKMON process.

•

Performance is critical. Interpreted SCREEN COBOL might not be efficient enough

when used to program a data communications protocol.

•

Simplicity of programming is critical. Handling a data communications protocol can

be awkward with SCREEN COBOL, which has a limited set of data types and

verbs.