GDSX (Extended General Device Support) Manual

Using Pseudo Procedures in a TS/MP Environment
Extended General Device Support (GDSX) Manual—529931-001
D-5
Running the GDSX Application
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
START TCP *
At the TACL prompt the following commands are entered to start the TS/MP and
Pathway/iTS 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 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 named RUN1:
?TACL MACRO
STOP $GDSX
STOP $GDSX
CLEAR All
PARAM MAXLINES 0
Run DEVICE^HANDLER only
PARAM CONTROLFLAGS 8 Run as high PIN
PARAM MAXBUFPOOL 50000 Make pool 10 larger
PARAM DEVICEINFO 1 Support DEVICEINFO calls from Pathway/iTS
RUN OGDS1 /NAME $GDSX/
The GDSX application is started when the macro name is entered at the TACL prompt:
> RUN RUN1
Configuring and Starting the Terminal Tasks
The last step is configuring the two tasks for the terminals, TERM1 and TERM2, and
starting them with SCF commands. In the following example, TERM1 and TERM2 are
configured with terminals that have access names of $STAR.#PTY9 and
$STAR.#PTY10.
> SCF
-> ADD SU $GDSX.#TERM1, ACCESSNAME $STAR.#PTY9