GDSX (Extended General Device Support) Manual

DEVICE^HANDLER Example, Running and
Managing
Extended General Device Support (GDSX) Manual—529931-001
4-12
Running a Second Application Process
From the TACL prompt (you may need to use the Break key again to interrupt SCF),
you can enter:
> STATUS *, TERM
to see whether the process has started and what the CPU number and PIN are. The
CPU number and PIN should be the same as the numbers that now appear in the
prompt on the second application terminal.
Then pause the TACL process at the TACL terminal to allow SCF to regain control.
When you see the SCF prompt, enter:
-> STATUS PROCESS $GDS
The display tells you that now there are two TSCODE system tasks, and two USCODE
user tasks, which are both DEVICE^HANDLER tasks.
Enter:
-> INFO #TC2
You should see a display with the task number 4.
If you wish, you can enter strings at the second application terminal and verify that the
strings are reversed. GDSX may serve as a front-end process between multiple
requesters and a number of terminal devices.
At the second application terminal, press CTRL/Y. On the screen you see the
following:
EOF!
APPLICATION STOPPING
Press the Break key to get a TACL prompt at the application terminal.
At the TACL terminal, enter a FC command to repeat the previous SCF command.
(You may need to pause the TACL process to complete the command and see the
response.) You should see the message:
-> GDS E00001 Object name does not exist
This verifies that task number 4, the $GDS process’s DEVICE^HANDLER task that
was mapped to the second application terminal ($TC2), no longer exists.
To see if the $A2 application process has been stopped, enter the following command
at the TACL prompt:
> STATUS *, TERM
Then enter the following to allow SCF to regain control:
> PAUSE