GDSX (Extended General Device Support) Manual

Operations and Support
Extended General Device Support (GDSX) Manual—529931-001
3-9
Running a Pathway/iTS Application
When requester $A1 starts up, the file $IOP1.#DEV1 will be accessed on node \NY.
Running a Pathway/iTS Application
When starting an application using Pathway/iTS (and its parent product, TS/MP) and
GDSX, the GDSX process is started first. For example, the following command may
be issued to run a GDSX object named $GDSX:
> RUN GDSE /NAME $GDSX, NOWAIT/
The configuration either involves a LINE or does not involve a LINE. Suppose that the
application has no LINE. Then, if SUs are to be preconfigured, SCF is used to
configure them before TS/MP (and Pathway/iTS) is started. Otherwise, SCF is simply
started.
If a GDSX application is designed to use SCF to preconfigure SUs T1 and T2 using
devices $T1 and $T2, the following commands could be issued:
-> SCF
-> ADD SU $GDSX.#T1
-> ADD SU $GDSX.#T2
Note how the device names $T1 and $T2 become #T1 and #T2, respectively, when
combined with the GDSX process name in these commands. When GDSX receives
these commands, it derives the proper device names, but does not open the files until
it receives an open message from Pathway/iTS.
In PATHCOM, you configure terminals to be opened through GDSX. If a Pathway/iTS
requester is to communicate through a GDSX process named $GDSX with a device
$T2, the file name $GDSX.#T2 is used in a series of PATHCOM commands like the
following:
= SET TERM TCP TCP-X
= SET TERM TYPE T16-6530:0
= SET TERM INITIAL LOGON-SCREEN
= SET TERM FILE $GDSX.#T2
= ADD TERM TX-2
Term type specifies the type of terminal that the GDSX process is simulating for
Pathway/iTS.
A session or thread is established when you issue the following PATHCOM command:
= START TERM TX-2
Then the TCP opens the file specified in the configuration commands, $GDSX.#T2 in
this example. Within the GDSX process, TSCODE receives the open message,
derives the device name $T2 from the message, and opens the device. A thread is
established from the TCP requester through $GDSX to $T2.