GDSX Manual

Using Pseudo Procedures in a NonStop TS/MP
Environment
Extended General Device Support (GDSX) Manual–134303
D-19
GDSX With NonStop TS/MP and TMF Procedures
GDSX With NonStop TS/MP and TMF Procedures
The sample GDSX application described in the first part of this appendix communicated
with a Pathway/TS application through a SCREEN COBOL program. Also, the
transactions originating from the GDSX application were protected by TMF only after
they entered the NonStop TS/MP environment.
In this section, the GDSX application is changed in the following ways:
•
The GDSX application (TSCODE and USCODE2) uses the
^SERVERCLASS_SEND_ and ^SERVERCLASS_SEND_INFO_ pseudo
procedures to send its transactions directly to the NonStop TS/MP servers
WRITERO and DELETEO. The SCREEN COBOL program SCOBGDSX is no
longer necessary.
•
The user code portion of the GDSX application uses the pseudo TMF procedures to
protect the transactions it sends to the NonStop TS/MP application.
See Figure D-2 for a picture of this configuration and the flow of transactions from the
terminals to the database. The source code listing of the user code USAMPLE2 is given
at the end of this subsection. The code listings for WRITER and DELETER remain the
same; see the previous subsection for their listings.
The following subsections step you through the process of compiling, binding,
configuring, and starting the GDSX and NonStop TS/MP applications.
Compiling USAMPLE2
The first step is compiling the user code USAMPLE2. In the following example, the
commands to compile USAMPLE2 were entered in an OBEY file called COMP2:
CLEAR All
PARAM WORKFILE $CRASH
Figure D-2. GDSX Application With NonStop TS/MP and TMF Pseudo
Procedures
CDT026
USCODE2
TSCODE
USCODE
WRITERO
TERM1
TERM2
$SKY.LINZ.TSTDAT
DELETERO
NonStop TS/MP
SERVERS
$PWGDS$GDSX