GDSX (Extended General Device Support) Manual

LINE^HANDLER Example, Running and Managing
Extended General Device Support (GDSX) Manual—529931-001
6-3
Preconfiguring the LINE and Subdevices
After the ASSUME command executes, the SCF prompt includes the object type and
process name. Now enter a STATUS command:
PROCESS $GDS # -> STATUS
The STATUS command tells you that there are two TSCODE system tasks running,
and no USCODE user tasks running.
Now ADD a LINE object (a logical LINE) called $GDS.#LX with an access name of the
device name of your application terminal. The ACCESSNAME attribute tells TSCODE
what device to open when it starts the LINE $GDS.#LX. To add the LINE, enter:
PROCESS $GDS # -> ASSUME LINE #LX
PROCESS $GDS # -> ADD, ACCESSNAME $TC1
This defines a LINE object to TSCODE. Now enter:
PROCESS $GDS # -> INFO, DETAIL
Note the access name. Then enter:
PROCESS $GDS # -> STATUS, DETAIL
Note that the state of the LINE is stopped. The LINE task number is 0, indicating that a
LINE^HANDLER task has not yet been created to manage the LINE object configured.
Now define three SU objects with names T1, T2, and T3, such that each subdevice is
under the LINE $GDS.#LX:
PROCESS $GDS # -> ADD SU T1
PROCESS $GDS # -> ADD SU T2
PROCESS $GDS # -> ADD SU T3
Check their state and the state of the LINE with:
PROCESS $GDS # -> STATUS, SUB ALL
PROCESS $GDS # -> INFO, DETAIL
The state of the SU objects is stopped, meaning that although the SU objects have
been configured, there are no corresponding DEVICE^HANDLER tasks. All SU
objects are defined under the LINE object, and therefore are accessed by way of $TC1
(the LINE object access name).
Now START the LINE object and check its status:
PROCESS $GDS # -> START
PROCESS $GDS # -> STATUS, DETAIL
The state is started. The task number is 3, indicating that a LINE^HANDLER task was
created when the LINE object was STARTed. (In addition to starting the LINE object,
TSCODE opened the $TC1 device specified by the LINE object access name.)
Enter:
PROCESS $GDS # -> STATUS PROCESS $GDS