GDSX Manual

Extended General Device Support (GDSX) Manual–134303

D-1

Using Pseudo Procedures in a NonStop

TS/MP Environment

This appendix contains an example of converting a GDSX application that

communicates with a NonStop TS/MP server through a Pathway/TS SCREEN COBOL

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

server. The converted program also uses the TMF component of NonStop TM/MP 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/TS

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

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

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

protect transactions originating in the user code.

GDSX Without Pathway/TS 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/TS application through a SCREEN COBOL program named SCOBGDSX.

The Pathway/TS application is named $PWGDS.

•

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

the database for the Pathway/TS 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/TS application.

See Figure D-1 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.