GDSX (Extended General Device Support) Manual

Design and Development

Extended General Device Support (GDSX) Manual—529931-001

2-45

Binding

Next you use the UBIND file to bind TSCODE and USCODE and TSCODE2 with

USCODE2. UBIND contains the following commands

COMMENT -- Make sure current default volume contains tscode and

uscode obje

cts

add * from tscode

add * from uscode , delete

set data 64 pages

set inspect on

set saveabend on

set subtype 30

build OGDS !

COMMENT -- Make sure current default volume contains TSCOD2 &

USCODE2 objects

add * from tscode2

add * from uscode2 , delete

set data 64 pages

set inspect on

set saveabend on

set subtype 30

build GDS2 !"

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.