GDSX Manual

Overview of GDSX
Extended General Device Support (GDSX) Manual–134303
1-13
Starting SU/Line With accessname NONE
When the I/O operation(s) completes, the data is picked up by the LINE^HANDLER
task, sent through TSCODE to the DEVICE^HANDLER task, and then passed back to
the requester.
Starting SU/Line With accessname NONE
This feature provides support for preconfigured SUs and LINEs without the need for an
associated file as accessname. TSCODE will not open any device for a task configured
with accessname NONE. The Device^Handler/Line^Handler procedure gets called with
term^file^num/line^file^num set to -1.
The example below shows two SUs configured through SCF under the GDSX process
$gds:
-> add su $gds.#t1, accessname NONE
-> add su $gds.#t2, accessname $LT1
-> start su $gds.#t1
-> start su $gds.#t2
SU T1 has no associated IOP and is configured with accessname NONE (instead of
using a dummy $NULL process). SU T2 communicates through $gds to $LT1.
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 NonStop TS/MP pseudo procedure
^SERVERCLASS_SEND_ to send terminal data from GDSX directly to a NonStop
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_.
Figure 1-8. GDSX With a LINE^HANDLER
Requester
D^H Task
D^H Task
Requester
Requester
CDT022
D^H Task
L^H Task
IN^QUEUE^
FILE^NUM
LINE^
FILE^
NUM
TSCODE
$GDS
$RECEIVE IOP