GDSX Manual

Intertask Communication Example
Extended General Device Support (GDSX) Manual–134303
E-2
Binding
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 USAMPLE3, SWAP $CRASH, OUT $S.#USAMPL3, MEM 64,&
NOWAIT, CPU 4/ USCODE3; NOMAP, NOCODE, NOICODE
The user code is compiled when this command is entered at the TACL prompt:
> OBEY COMP3
Binding
The second step is binding TSCODE and USCODE3 together into a GDSX object file
named OGDS3. The commands are entered in a file called BIND3:
ADD * FROM $SKY.LINZ.TSCODE
ADD * FROM USCODE3, DELETE
SET DATA 64 PAGES
SET INSPECT ON
SET SAVEABEND ON
SET SUBTYPE 30
BUILD OGDS3 !
CHANGE HIGHPIN ON IN OGDS3
The binding process occurs when a BIND command is entered at the TACL prompt,
specifying the BIND3 file with an IN option:
> BIND /IN BIND3/
Running the GDSX Application
In this step the GDSX object file is run and given the name $GDSX. The commands to
do this and set some GDSX configuration parameters are entered in the TACL macro file
named RUN3:
?TACL MACRO
STOP $GDSX
STOP $GDSX
CLEAR All
PARAM MAXLINES 0
Run DEVICE^HANDLER task only
PARAM CONTROLFLAGS 9 Run as high PIN and send system
message to USCODE
PARAM MAXBUFPOOL 50000 Make pool 10 larger
PARAM TASKSIZE 2048 Increase the task size
PARAM MAXITC 2 Account for two additional ITC files
RUN OGDS3 /NAME $GDSX/
The GDSX application is started when the macro name is entered at the TACL prompt:
> RUN RUN3