GDSX (Extended General Device Support) Manual

Using Pseudo Procedures in a TS/MP Environment
Extended General Device Support (GDSX) Manual—529931-001
D-19
GDSX With NonStop TS/MP and TMF Procedures
183 If Not-Found
184 Next Sentence
185 Else
186 Move I to Ok-Nmbr
187 Move 9999 to I
188 Move File-Stat-N to Out-Message-Loop
189 Move "Error reading tstdat" to Out-Message-Text
190 Else
191 Delete Tstdat
192 If File-Error
193 Move I to Ok-Nmbr
194 Move 9999 to I
195 Move File-Stat-N to Out-Message-Loop
196 Move "Error deleting tstdat" to Out-Message-Text.
197 *
198
***Eof**************************************************************************
GDSX With NonStop TS/MP and TMF
Procedures
The sample GDSX application described in the first part of this appendix
communicated with a Pathway/iTS application through a SCREEN COBOL program.
Also, the transactions originating from the GDSX application were protected by TMF
only after they entered the 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 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 TS/MP application.
See Figure D-2 on page 20 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.