GDSX Manual

DEVICE^HANDLER Example, Running and
Managing
Extended General Device Support (GDSX) Manual–134303
4-6
Binding
TAL /IN USKELEX, MEM 64, OUT $S.#USKELEX/ USCODEE; &
SYMBOLS, INSPECT, NOCODE, NOICODE, NOMAP
CLEAR ALL
EXIT
After creating UBUILD, issue the command OBEY UBUILD to compile the source
code file and produce the object file USCODEE.
The HIGHPIN object-file attribute is not set on, because this example is an unconverted
application that cannot run at a high PIN. If you compile the converted USKELEXC
example program shown in Appendix B, you may set the attribute as follows:
> TAL /IN USKELEXC, MEM 64, OUT $S.#USKELEC/ USCODEC; HIGHPIN
Appendix B has listings of USKELEX and USKELEXC.
Binding
Now use the UBINDE file to bind TSCODE and USCODE. UBINDE contains the
following commands:
add * from tscode
add * from USCODEE, delete
set data 64 pages
set inspect on
set saveabend on
set subtype 30
build GDSE !
The GDSX object file must be named GDSE in this example. TSCODE must be added
before USCODE so that TSCODE is loaded into the first code segment. The SET
SUBTYPE 30 command makes it possible for the GDSX process to receive and respond
to device type requests from other processes. For more information about the BIND
program, see the Binder Manual.
Before using the UBINDE file, depending on the location of the TSCODE file, you may
need to qualify the file name in the first command. To produce the runnable object file,
issue the command:
> BIND /IN UBINDE/
Running the DEVICE^HANDLER Example
At the TACL terminal, use CLEAR ALL if necessary to clear any previously set
parameter values, and then assign 1 to the configuration parameter EXTSUSIZE:
> PARAM EXTSUSIZE 1
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-55.)
Then run your new GDSX process:
> RUN GDSE /NAME $GDS, NOWAIT/