GDSX Manual

Design and Development
Extended General Device Support (GDSX) Manual–134303
2-42
Binding
Binding
Next you use the UBIND file to bind TSCODE and USCODE. UBIND contains the
following commands:
add * from tscode
add * from USCODE, delete
set data 64 pages
set inspect on
set saveabend on
set subtype 30
build OGDS !
The UBINDHI file is the same as the UBIND file, except that it includes the SET
HIGHPIN ON command used to set the HIGHPIN object-file attribute at bind time.
For this example, the resulting GDSX object file is called OGDS. TSCODE should 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 UBIND file, depending on the location of the TSCODE file, you may
need to qualify the TSCODE file name in the first command. To produce the runnable
object file, issue the command:
> BIND /IN UBIND/
You may want to include an OUT file in this command in order to capture binding
process information or to speed up the binding process.
GDSX Configuration Parameters
GDSX uses configuration parameters to control memory allocation and numerous
aspects of the run-time environment (RTE). Some configuration parameters are called
static, because once their values are determined at process creation time. They cannot
be changed for that process. The other configuration parameters are called dynamic,
because their values can be changed after the process has been initialized.
Table 2-2 and Table 2-3 contain information about the static and dynamic configuration
parameters for GDSX. The first column of the tables gives the external parameter
names used when setting parameter values by means of an SCF or TACL PARAM
command.
The second column lists the internal DEFINE names used when setting parameter values
in USCODE (usually within the USER^INIT^CONFIG^PARAMS user exit). These
globals are defined in the config^params^template STRUCT of the config^templates
section of DCCBDECS (see Appendix C).
Each internal parameter name listed in the third column is defined in terms of a
STRUCT variable. For example,
CONFIG^PARAMS.term^data