GDSX Manual

Using Pseudo Procedures in a NonStop TS/MP
Environment
Extended General Device Support (GDSX) Manual–134303
D-5
Running the GDSX Application
At the TACL prompt the following commands are entered to start the NonStop TS/MP
and Pathway/TS 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/TS
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
DEVICETYPE 6, DEVICESUBTYPE 4, PHYSRECLEN 80
-> ADD SU $GDSX.#TERM2, ACCESSNAME $STAR.#PTY10
DEVICETYPE 6, DEVICESUBTYPE 4, PHYSRECLEN 80
-> START SU $GDSX.#TERM1
-> START SU $GDSX.#TERM2
USAMPLE1 Listing
1.
!******************************************************************************
2. ! GDSX USCODE Generic DEVICE^HANDLER
!
3. ! Sample program
!
4. !
!
5. ! Writing or deleting records in a database using IDS