GDSX Manual

Using Pseudo Procedures in a NonStop TS/MP
Environment
Extended General Device Support (GDSX) Manual–134303
D-22
Running the GDSX Application
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
PARAM MAXBUFPOOL 50000 Make pool 10 larger
PARAM TASKSIZE 2048 Increase the task size
PARAM DEVICEINFO 1 Support DEVICEINFO calls from Pathway
PARAM TMF 2 Use TMF product in user task
PARAM PROCNOWAIT 1 Have ^SERVERCLASS_SEND_ run in
nowait mode
RUN OGDS2 /NAME $GDSX, LIB SCPROCS/
The GDSX application is started when the macro name is entered at the TACL prompt:
> RUN RUN2
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
USAMPLE2 Listing
2. ! GDSX USCODE
!
3. ! Sample program
!
4. ! Writing or deleting records in a database using Pathsend and TMF
!
5.
!******************************************************************************
7 ?NOMAP, NOLMAP, NOCODE, SYMBOLS, CPU TNS/II
8.
9. Name Uscode;
10.
11. Block Common^Templates;
12. ?NOLIST, Source DCCBDECS (ERRORS)
14. ?NOLIST, Source DCCBDECS (EVENTS)
16. ?NOLIST, Source DCCBDECS (TCB^LAYOUT)
18. ?NOLIST, Source DCCBDECS (IOCB^LAYOUT)