GDSX Manual

Design and Development
Extended General Device Support (GDSX) Manual–134303
2-39
The GDSX Generation Process
open the disk file and initialize a semaphore for the file. See the example in the
considerations for the ^OPEN procedure in Section 8.
The GDSX Generation Process
Every runnable GDSX process is a combination of code supplied by Tandem and user-
supplied code. The user-supplied code is typically written in TAL. (Only USCODE
written in TAL has been tested; although USCODE may be written in other languages,
GDSX has not been tested with other languages.) When the your source code file is
compiled, declarations contained in files supplied by Tandem (DCCBDECS and
PEXTGDS) are sourced in (see Figure 2-3 on page 2-40); depending on the application,
user-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-16 for more information on files used during source code
compilation.
The object code file resulting from the compilation, named USCODE in Figure 2-3, is
then bound with TSCODE, the object code file supplied by Tandem. 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
PEXTGDS
Another source file, containing external declarations for procedures
within TSCODE
UBUILD Command (OBEY) file used to compile your program
TSCODE
Object code supplied by Tandem; you cannot modify this file
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