GDSX Manual

Using Pseudo Procedures in a NonStop TS/MP
Environment
Extended General Device Support (GDSX) Manual–134303
D-2
Compiling USAMPLE1
The following subsections step you through the process of compiling, binding,
configuring, and starting the GDSX and Pathway/TS applications.
Compiling USAMPLE1
The first step is compiling the user code USAMPLE1. In the following example, the
commands to compile USAMPLE1 were entered in an OBEY file called COMP1:
CLEAR All
PARAM WORKFILE $CRASH
COMMENT Assign SSV0 to the volume and subvolume for
COMMENT the GDSX installation subvolume
ASSIGN SSV0, $SKY.LINZ
ASSIGN ZSPITACL, $SKY.ZSPIDEF.ZSPITACL
ASSIGN ZEMSTACL, $SKY.ZSPIDEF.ZEMSTACL
ASSIGN ZGDXTAL, $SKY.LINZ.ZGDXTAL
ASSIGN COPYTAL, $SYSTEM.SYSTEM.COPYTAL
ASSIGN SSV1, $SKY.ZSPIDEF
ASSIGN SSV2, $SYSTEM.SYSTEM
TAL /IN USAMPLE1, SWAP $CRASH, OUT $S.#USAMPL1, MEM 64,&
NOWAIT, CPU 4/ USCODE1; NOMAP, NOCODE, NOICODE
The user code is compiled when this command is entered at the TACL prompt:
> OBEY COMP1
Binding
The second step is binding TSCODE and USCODE1 together into a GDSX object file
named OGDS1. In the following example, the commands to do this were entered in a
file called BIND1:
ADD * FROM $SKY.LINZ.TSCODE
ADD * FROM USCODE1, DELETE
SET DATA 64 PAGES
Figure D-1. GDSX Application Without Pathway/TS and TMF Pseudo Procedures
USCODE1
TSCODE
USCODE
Pathway/TS
TCP
SCOBGDSX WRITERO
TERM1
TERM2
$SKY.LINZ.TSTDAT
DELETERO
NonStop TS/MP
SERVERS
$PWGDS$GDSX