GDSX Manual

DEVICE^HANDLER Example, Running and
Managing
Extended General Device Support (GDSX) Manual–134303
4-11
Running a Second Application Process
Enter an INFO command:
SU $GDS.#TC1 -> INFO
The INFO command gives information about the SU created and mapped to device
$TC1 when APPL was run.
Enter:
SU $GDS.#TC1 -> INFO, DETAIL
The INFO, DETAIL command gives even more information about the SU.
Enter another ASSUME command, followed by an INFO command:
SU $GDS.#TC1 -> ASSUME TASK
TASK $GDS #TC1 -> INFO
The prompt changes; then you see a display with the task number (3) and other
information. GDSX identifies a task externally by its task number and internally by a
task control block address.
Enter an INFO, DETAIL command:
TASK $GDS.#TC1 -> INFO, DETAIL
More detailed information is displayed. Note that the state of the SU is STARTED.
This is the normal state of a LINE or SU, when it is not faulted, stopped, or in the
process of being stopped.
Running a Second Application Process
If you have a second application terminal available, you can start a second application
process and direct I/O to the second application terminal. The second application
process uses the same object file APPL.
At the second application terminal, log on and enter a WHO command to identify the
terminal device name. Suppose for this example that it is $TC2. Pause the TACL
process with the PAUSE command.
At the TACL terminal, use the Break key to interrupt SCF and return to the TACL
prompt. Start the second application process, to be named $A2:
> RUN APPL /NAME $A2, OUT $GDS.#TC2, NOWAIT/
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.