GDSX (Extended General Device Support) Manual

DEVICE^HANDLER Example, Running and
Managing
Extended General Device Support (GDSX) Manual—529931-001
4-4
Compiling
LINE^HANDLER Example, Running and Managing and Section 7, LINE^HANDLER
Example, Design), use the following files from a GDSX installed subvolume:
Compiling
To facilitate the compiling and binding procedures, you use UBUILD and UBINDE files.
At the TACL terminal, while in the subvolume where you wish to work, copy the
UBUILD and UBINDE files from the installed subvolume. Edit UBUILD to assign SSV1
to the installed subvolume, assign SSV2 to $SYSTEM.SYSTEM, and assign SSV3 to
the SPI subvolume. The IN file for the TAL compiler is USKELEX, and the object file is
named USCODEE. You might want to use an OUT file to capture the compile listing.
File Description
DCCBDECS
Source file containing global variables and other common
declarations
ULHDECSE
Source file containing declarations specific to the example
program
PEXTGDS
Another source file containing external declarations for
procedures within TSCODE
USKELEX
User source code file containing all the user exits (procedures)
called by TSCODE. USKELEX—the name is derived from
“USKEL Example for GDSX”—was prepared from USKEL, the
user code skeleton file supplied in the GDSX installed
subvolume, by replacing the three procedure stubs for
DEVICE^HANDLER, USER^STOP, and LINE^HANDLER with
user-customized procedures.
UBUILD Command (OBEY) file used to compile the example program.
When you use an edited version of UBUILD to compile
USKELEX, the ULHDECSE and PEXTGDS files and sections
of the DCCBDECS file are sourced in, and the resulting object
code is named USCODEE.
TSCODE
Object code supplied by HP; you cannot modify this file
UBINDE BINDER IN file used to bind TSCODE with USCODE,
producing a runnable GDSX object file named GDSE.