GDSX (Extended General Device Support) Manual

DEVICE^HANDLER Example, Running and
Managing
Extended General Device Support (GDSX) Manual—529931-001
4-7
Using SCF
This is necessary because of example-specific changes made to the device control
block declaration. (For more information, see the description for EXTSUSIZE on
page 2-59.)
Then run your new GDSX process:
> RUN GDSE /NAME $GDS, NOWAIT/
This GDSX process includes a DEVICE^HANDLER that does datastream conversion
on messages passed from multiple requesters to different asynchronous terminals.
You can enter:
> STATUS *, TERM
to see whether the GDSX process has been started.
Using SCF
The operator interface to running GDSX processes is the Subsystem Control Facility
(SCF). SCF provides a set of commands used to manage GDSX processes and the
devices (SUs) and lines (LINEs) used by the GDSX processes. For general
information about SCF functions and command formats, see the Subsystem Control
Facility (SCF) Reference Manual. For information on running SCF specifically to
manage GDSX, see the SCF Reference Manual for GDSX.
TSCODE supports the SCF commands listed in Table 3-1, “GDSX Subsystem-Specific
SCF Commands,” on page 3-15.
At the TACL terminal, start SCF by entering:
> SCF
If SCF does not reside in $SYSTEM.SYSTEM.*, you must enter:
> RUN SCF
Then enter a SETPROMPT command to cause SCF to display, as part of the prompt,
any object type and name currently being assumed:
-> SETPROMPT OBJECT
Now enter an ASSUME command to define the object type and name:
-> ASSUME PROCESS $GDS
After the ASSUME command executes, the SCF prompt includes the process name.
Now enter a STATUS command:
PROCESS $GDS # -> STATUS
The STATUS command tells you there are two TSCODE system tasks running, and no
USCODE user tasks running.
Enter:
PROCESS $GDS # -> VERSION, DETAIL