GDSX (Extended General Device Support) Manual

LINE^HANDLER Example, Running and Managing
Extended General Device Support (GDSX) Manual—529931-001
6-2
Running the LINE^HANDLER Example
This section of the tutorial requires three terminals designated the TACL terminal, the
SCF terminal, and the application terminal. It is assumed that the terminals will be
accessed by way of the TERMPROCESS IOP.
Running the LINE^HANDLER Example
This example uses the same APPL and GDSE object files generated in Section 4,
DEVICE^HANDLER Example, Running and Managing. Although the LINE^HANDLER
was not called in the exercises in Section 4, DEVICE^HANDLER Example, Running
and Managing and Section 5, DEVICE^HANDLER Example, Design, a customized
LINE^HANDLER procedure is included in the GDSE object file.
At the TACL terminal, use CLEAR ALL if necessary to clear any previously set
parameter values, and then assign the value 1 to the configuration parameter
MAXLINES:
> PARAM MAXLINES 1
This indicates to the GDSX process that at most one LINE^HANDLER task will be
created. If MAXLINES is set to zero as in Section 4, DEVICE^HANDLER Example,
Running and Managing and Section 5, DEVICE^HANDLER Example, Design, the
LINE^HANDLER cannot be run.
Assign the value 1 to the configuration parameter EXTSUSIZE:
> PARAM EXTSUSIZE 1
This is necessary because of application-specific changes to the device control block
declaration. (See EXTSUSIZE on page 2-59.)
Then run your new GDSX process:
> RUN GDSE /NAME $GDS, NOWAIT/
This GDSX process includes a LINE^HANDLER that allows multiple requesters to
queue for access to a single asynchronous terminal. To see whether the GDSX
process has been started, enter the following:
> STATUS *, TERM
Preconfiguring the LINE and Subdevices
At the SCF terminal, log on and start SCF:
> 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