GDSX (Extended General Device Support) Manual

Extended General Device Support (GDSX) Manual—529931-001

D-1

Using Pseudo Procedures in a

TS/MP Environment

This appendix contains an example of converting a GDSX application that

communicates with a TS/MP server through a Pathway/iTS SCREEN COBOL program

and an example of a GDSX application that communicates directly with the server.

The converted program also uses the TMF to protect transactions originating in the

user code portion of GDSX.

The first half of the appendix shows the various steps required to compile, bind,

configure, and start the GDSX application as it was designed without the Pathway/iTS

and TMF pseudo procedures. The second half uses the same GDSX application but

illustrates how it was changed to use the TS/MP and Pathway/iTS procedures to

communicate directly with TS/MP servers and the TMF pseudo procedures to protect

transactions originating in the user code.

GDSX Without Pathway/iTS and TMF

Procedures

The example applications have the following configuration:

•

Two terminals send transaction data to the GDSX application named $GDSX. The

terminals are named TERM1 and TERM2.

•

The GDSX application (TSCODE and USCODE1) sends its transactions to a

Pathway/iTS application through a SCREEN COBOL program named

SCOBGDSX. The Pathway/iTS application is named $PWGDS.

•

SCOBGDSX uses two TS/MP server processes to write and delete data in the

database for the Pathway/iTS application. The two servers are named WRITERO

and DELETERO. The database has a file name of $SKY.LINZ.TSTDAT and is

protected by TMF using TMF procedures called by the Pathway/iTS application.

See Figure D-1 on page 2 for a picture of this configuration and the flow of transactions

from the terminals to the database. Source code listings of SCOBGDSX, WRITER,

DELETER, and the user code USAMPLE1 are given at the end of this subsection.