ART IMS Calls Transaction in Z/IMS

In some circumstances, the main transaction has been migrated to ART/IMS on Linux, while some sub-transactions still reside on z/OS, as they are shared by other main transactions residing on z/OS. This solution aims to enable applications in ART/IMS to invoke sub-transactions on z/OS without code changes, e.g. through Alternate PCB, referred to as ALTPCB hereinafter.

You can call an online transaction, referred to as main transaction hereinafter, provided by ARTIMS from 3270 terminal or a Tuxedo client through ARTIGW. To make the main transaction call a sub-transaction on z/OS, you need to follow these steps, which will be elaborated later:

•	Step 1: Configuring Sub-transactions on Z/OS;

•	Step 2: Configuring and Deploying TMA SNA for IMS;

•	Step 3: Generating Buffer Converter Program for Sub-transactions.

Step 1: Configuring Sub-transactions on Z/OS

You can configure sub-transactions on z/OS in the zostrans.desc file at $ART_IMS_CONFIG, all of which should only be called sub-transaction. For instance, in Listing 11‑1:

Listing 11‑1 Sample Sub-transaction Configuration

[zostran]

NAME=SUBTRAN1

CONV=TMAA2Z

[zostran]

NAME=SUBTRAN2

 

NAME is the z/OS transaction name. CONV is the input message’s buffer converter program, which can be generated by the ART Workbench based on a copybook describing the input message/segment structure of the sub-transaction.

Note:

CONV handles the data conversion before calling sub-transactions on z/OS. If it is not specified, ART/IMS only does ASCII to EBCDIC conversion by default, e.g. treating all bytes in the input message as characters.

Step 2: Configuring and Deploying TMA SNA for IMS

1.	Install the Oracle Tuxedo Mainframe Adapter for SNA. For more information, see Oracle Tuxedo Mainframe Adapter for SNA.

2.	Add one line GWSNAX:::: to your $TUXDIR/udataobj/DMTYPE.

3.	Establish a VTAM Configuration:

If you are running your CRM on a mainframe, your mainframe must have a local VTAM configuration that communicates with the CRM.

For more information, see Preparing Mainframe Configurations for CRM Requirements.

4.	Configure the Oracle TMA SNA for IMS:

a.	Configure the UBBCONFIG file. Listing 11‑2 shows an example.

Listing 11‑2 Example of UBBCONFIG Configuration

*RESOURCES

IPCKEY 40036

DOMAINID snax

MASTER SITE1

MAXACCESSERS 400

MAXSERVERS 80

MAXSERVICES 80

MAXCONV 120

MODEL SHM

LDBAL N

SCANUNIT 5

BLOCKTIME 4

DBBLWAIT 1

*MACHINES

DEFAULT:

"HOSTNAME"

LMID=SITE1

TUXDIR="TUXDIR"

APPDIR="APPDIR"

TUXCONFIG="APPDIR/tuxconfig"

TLOGDEVICE="APPDIR/TLOG"

*GROUPS

ADMGRP

LMID=SITE1 GRPNO=1

CRM12200

LMID=SITE1 GRPNO=10

APPGRP

LMID=SITE1 GRPNO=100 TMSCOUNT=2 TMSNAME=TMS

*SERVERS

DEFAULT: CLOPT="-A"

DMADM

SRVGRP=ADMGRP SRVID=1

GWADM

SRVGRP=CRM12200 SRVID=11

GWSNAX

SRVGRP=CRM12200 SRVID=12

RQADDR="GWSNAX"

REPLYQ=N RESTART=N GRACE=0

CLOPT="-A -- -t 1"

*SERVICES

 

b.	Configure the DMCONFIG file. Listing 11‑3 shows an example.

If you are building a new dmconfig, Listing 11‑3 may need to be adjusted to your mainframe connection. If it already exists for the same CRM connection, you only need to merge the relevant entries from the DM_SNASTACKS, DM_SNALINKS, and DM_REMOTE_SERVICES sections into the existing configuration. It is shown in bold typeface where you need to change according to your environment in Listing 11‑3:

Listing 11‑3 Example of DMCONFIG Configuration

*DM_LOCAL_DOMAINS

SNAXDOM

GWGRP=CRM12200 // Same as GWSNAX group name

TYPE=SNAX

DOMAINID="SNAXDOM"

DMTLOGDEV="APPDIR/DMLOG"

*DM_REMOTE_DOMAINS

MVSDOM

TYPE=SNAX

DOMAINID="MVSDOM"

*DM_SNACRM

SIMPCRM

SNACRMADDR="//hostname:port" // The port must be same as listening port of CRM

NWDEVICE="/dev/tcp"

LDOM="SNAXDOM"

*DM_SNASTACKS

SIMPSTK

SNACRM="SIMPCRM"

STACKTYPE="VT210" // Do not change if CRM is deployed on Mainframe

LOCALLU="CRMLU74" //LU name defined in VTAM

LTPNAME="*"

STACKPARMS="wasa"

*DM_SNALINKS

SIMPLK

STACKREF="SIMPSTK"

RDOM="MVSDOM"

LSYSID="CR63" // VTAM Connection name for this link

RSYSID="IMSD"

RLUNAME="IMSDAPPC" // VTAM netname

MODENAME="SMSNA100"

SECURITY="LOCAL"

STARTTYPE="COLD"

MAXSESS=8

MINWIN=4

MAXSYNCLVL=2

*DM_LOCAL_SERVICES

*DM_REMOTE_SERVICES

TSTNCON1

LDOM="SNAXDOM" //Reference to DOMAINID in DM_LOCAL_DOMAINS

RDOM="MVSDOM" //Reference to DOMAINID in DM_REMOTE_DOMAINS

AUTOTRAN=N

CONV=N

RNAME="TSTNCON1" //Reference to program name defined in remote CICS region

INBUFTYPE="CARRAY"

OUTBUFTYPE="CARRAY"

FUNCTION="APPC"

*DM_ROUTING

 

5.	Perform a tmloadcf and dmloadcf to load the UBBCONFIG and the DMCONFIG files.

6.	Use the following command to start CRM on mainframe:

CRM [ -t 0|1|2|3 ] [-p<nbr>] [-s] [-n <type>:#:#] [-u <keyfile>] [-V] [-P [interval]] [-R [interval]] [-F [trcsz]] <addr> <group>

The port number of addr must be same as that of SNACRMADDR configured in DMCONFIG; the group name must be same as that of GWSNAX configured in UBBCONFIG, which is CRM12200 in the example of UBBCONFIG.

For more information, see CRM.

7.	Start the GWSNAX tmboot to start all ATMI servers including GWSNAX.

Step 3: Generating Buffer Converter Program for Sub-transactions

To enable this functionality in ART Workbench, you need to build a workbench project to convert files. Then, based on the project, you need to follow these steps to generate the buffer converter program:

1.	Configure enable-buffer-converter in the system.desc file (special option).

2.	Put the input copybook file at the source/COPY directory.

3.	Add the following lines to the param/file/Datamap-xxx.re file:

file A.FILE1

organization Sequential

4.	Add the following lines to the param/file/mapper-xxx.re file:

file A.FILE1 transferred

include "COPY/ODCSF0.cpy"

map record RECORD defined in "COPY/ODCSF0.cpy"

source record RECORD defined in "COPY/ODCSF0.cpy"

logical name ODCSF0Q

converter name ODCSF0Q

5.	Run the Workbench file converter project again:

Two output files are generated and only the first one is the needed converter program:

trf/reload/file/STFILEORA/ODCSF0Q1.cbl (ASCII to EBCDIC)

trf/reload/file/STFILEORA/ODCSF0Q2.cbl (EBCDIR to ASCII)

For more information, see Oracle Tuxedo Rehosting Workbench Users Guide.

After all preceding steps performed, configure and setup ARTIMS with TMA gateway environment. Boot the ARTIMS domain and make a call to the online transaction to invoke the sub-transaction on z/OS.