GDSX Manual

DEVICE^HANDLER Example, Running and

Managing

Extended General Device Support (GDSX) Manual–134303

4-4

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.

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 Tandem; you cannot modify this file

UBINDE BINDER IN file used to bind TSCODE with USCODE, producing a

runnable GDSX object file named GDSE.

File Description