Introduction to Networking for NonStop S-Series Servers

Device-Specific Connections
Introduction to Networking for HP NonStop S-Series Servers—520670-005
6-15
Developing Your Own Front-End Process
•
6100 BSC Multipoint Tributary. Allows a NonStop S-series server to act as a
tributary on a binary synchronous multipoint line.
•
6100 ADCCP. Allows a NonStop S-series server to be a supervisor, tributary, or
combined station on an ADCCP, HDLC, or SDLC bit-synchronous line.
•
6100 Multipoint Supervisor Burroughs. Allows a NonStop S-series server to act
as a supervisor on a multipoint line for terminals using the Burroughs Basic
Poll/Select protocol, the NCR Multipoint protocol, or the protocol for Lear-Siegler
ADM-2 Data Display Terminals with the polling option.
•
SWIFT. Allows a NonStop S-series server to be either a primary or secondary
station on a SWIFT I or SWIFT II line.
•
Generalized Full-Duplex Protocol. Allows the NonStop S-series server to act as
supervisor of a full-duplex asynchronous or synchronous line.
Envoy and CP6100 differ in a few important respects. They have different
programming interfaces and run on different hardware. Also, there are some
differences in the selection of protocols supported. In general, CP6100 supersedes
Envoy.
Developing Your Own Front-End Process
Extended General Device Support (GDSX) is a skeleton process that you fill in to
support nonstandard devices. A GDSX process acts as an interface between an
application execution environment, such as Pathway/TS, and an IOP such as CP6100,
ATP6100, or X25AM. The GDSX process simulates a supported terminal type and
converts data to and from the required protocol format. The GDSX product consists of
generic routines and services that allow you to create a multithreaded process pair;
you add procedures that provide specific communications functions.
Figure 6-3 illustrates the structure of GDSX and its typical role in a Pathway
environment.