GDSX (Extended General Device Support) Manual

Design and Development
Extended General Device Support (GDSX) Manual—529931-001
2-41
Installed Subvolume Files
supplied declarations may also be sourced in from ULHDECS, ULHDECSE,
USKELDEC, or a user-supplied declaration file with a different name. See User Code
Declarations on page 2-17 for more information on files used during source code
compilation.
The object code file resulting from the compilation, named USCODE in Figure 2-3 on
page 2-42, is then bound with TSCODE, the object code file supplied by HP. A
BINDER IN file is commonly used for this step. The result of binding USCODE with
TSCODE is a runnable GDSX object file.
Installed Subvolume Files
When generating a GDSX process, you normally use the following files from a GDSX
installed subvolume:
File Description
DCCBDECS Source file containing global variables and other common declarations
DCCBDEC2 Source file containing global variables and other common declarations to
support access to a file of size greater than 4 GB
PEXTGDS Another source file, containing external declarations for procedures within
TSCODE
PEXTGDS2 Another source file, containing external declarations for procedures within
TSCODE2
UBUILD Command (OBEY) file used to compile your program
TSCODE Object code supplied by HP; you cannot modify this file
TSCODE2 Object code supplied by HP provides support for accessing file of size
greater than 4 GB
ubind BINDER IN file used to bind TSCODE with USCODE, producing a
runnable GDSX object file named OGDS
UBINDHI Same as the UBIND file, except that it includes the SET HIGHPIN ON
command