GDSX (Extended General Device Support) Manual

Using Pseudo Procedures in a TS/MP Environment
Extended General Device Support (GDSX) Manual—529931-001
D-22
Running the GDSX Application
LOG1 PATHLOG, STATUS
RESET SERVER
SET SERVER
SET SERVER PROGRAM DELETERO
SET SERVER PROCESS $GDS1
SET SERVER PROCESS $GDS2
SET SERVER CPUS (1:0, 0:1)
SET SERVER MAXSERVERS 2
SET SERVER CREATEDELAY 1 SECS
SET SERVER DELETEDELAY 30 MINS
SET SERVER NUMSTATIC 1
SET SERVER SECURITY "N"
SET SERVER TMF ON
SET SERVER (ASSIGN TSTDAT, $SKY.LINZ,TSTDAT, SHARED)
ADD SERVER DELETER
RESET SERVER
SET SERVER
SET SERVER PROGRAM WRITERO
SET SERVER PROCESS $GDS3
SET SERVER PROCESS $GDS4
SET SERVER CPUS (0:1, 1:0)
SET SERVER MAXSERVERS 2
SET SERVER CREATEDELAY 1 SECS
SET SERVER DELETEDELAY 20 MINS
SET SERVER NUMSTATIC 1
SET SERVER SECURITY "N"
SET SERVER TMF ON
SET SERVER (ASSIGN TSTDAT, $SKY.LINZ.TSTDAT, SHARED)
ADD SERVER WRITER
At the TACL prompt the following commands are entered to start the TS/MP
application:
> FUP PURGEDATA PATHLOG
> ASSIGN PATHCTL, \SKY.LINZ.PATHCTL
> PATHMON /NAME $PWGDS, NOWAIT, PRI 150, MEM 64, CPU 0/
> PATHCOM /IN PATHIN/ $PWGDS
At this point the TS/MP application named $PWGDS is configured and started, but the
GDSX application is not running.
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 were entered in the TACL macro
file RUN2:
?TACL MACRO
STOP $GDSX
STOP $GDSX
CLEAR All
PARAM MAXLINES 0 Run DEVICE^HANDLER only
PARAM CONTROLFLAGS 8 Run as high PIN