GDSX (Extended General Device Support) Manual

Overview of GDSX
Extended General Device Support (GDSX) Manual—529931-001
1-16
Communicating Directly With a NonStop TS/MP
Server
Communicating Directly With a NonStop TS/MP Server
In general, you do not need a SCREEN COBOL program to handle the data
transmissions with terminals. You can use the TS/MP pseudo procedure
^SERVERCLASS_SEND_ to send terminal data from GDSX directly to a TS/MP
server. Another pseudo procedure, ^SERVERCLASS_SEND_INFO_, can be used
when an error occurs to retrieve more information about the failed call to
^SERVERCLASS_SEND_.
See Section 8, “Service Routines,” for more information about these procedures and
Section D, “Using Pseudo Procedures in a TS/MP Environment,” for an example of
using them in a user task.
When to Use GDSX
GDSX is a very complex product, and should not be used to implement an application
if Pathway/iTS alone can handle the application requirements. For any of the following
reasons, however, a GDSX process may be used as a front end to a Pathway/iTS
application:
•
The specified data communications protocols are not supported by the
Pathway/iTS TCP. One example is HP OSI/TS.
•
Performance is critical. Interpreted SCREEN COBOL may 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.
For more information about alternatives to GDSX, including RSC, see Introduction to
NonStop Transaction Processing.