11 Configuring the OLTP

Configuring CICS Transaction Server for z/OS

If your OLTP is CICS Transaction Server for z/OS, then perform the following steps to configure it for communication with the gateway:

1. Configure MVS VTAM for the SNA communication package that will make the APPC connection to your system. At least one independent LU must be available to the gateway.

2. Check the VTAM logmode table used by the CICS Transaction Server for z/OS. (The table name is specified in the MODETAB parameter in the VTAM APPL definition for CICS.) Ensure that an entry exists for APPC sessions with parallel session and sync-level support.

   The oraplu62.asm file in the $ORACLE_HOME/pg4appc/sna directory contains a sample mode entry, including comments that indicate the required values in the mode entry.

3. Using a file transfer facility, transfer the following files from the $ORACLE_HOME/pg4appc/demo/CICS directory to the z/OS system on which you run CICS Transaction Server for z/OS:

   • dfhcsdup.jcl: JCL to run the CICS DFHCSDUP utility

   • pgaflip.asm: Assembler source for the CICS FLIP transaction

   • pgaflip.jcl: JCL to assemble and linkedit the CICS FLIP transaction

4. Using the comments in the dfhcsdup.jcl file, tailor the JCL and input statements to match your system setup, and submit it for batch execution. Performing this step updates your Transaction Server for z/OS system definitions.

5. Using the instructions in the pgaflip.jcl file comments, tailor the JCL to match your system setup, and submit it for batch execution. Performing this step assembles and linkedits the pgaflip.asm file into a load module library accessible to your Transaction Server for z/OS through the DFHRPL DD statement in the CICS startup procedure.

6. Log on to your CICS Transaction Server for z/OS and enter the following transaction:

   CEDA INSTALL GROUP(ORAPGA)
   
   

   This transaction installs the CICS connection and session definitions for APPC communication with the gateway on UNIX. It also installs definitions for the sample CICS programs and transactions provided with the gateway.

Your CICS Transaction Server for z/OS configuration is now complete.

Configuring IDMS-DC

If your OLTP is IDMS-DC, perform the following steps to configure IDMS-DC and z/OS for communication with the gateway:

1. Configure MVS VTAM for the communication interface APPC connection to HP-UX. At least one independent LU must be available for use by the gateway.

2. If your IDMS-DC system does not have APPC support, then set up a separate MVS VTAM APPL definition for use by the IDMS-DC LU6.2 interface. IDMS-DC cannot use the same VTAM APPL for both VTAM terminal and VTAM APPC support.

   For more information, refer to vendor documentation.

3. Check the VTAM logmode table used by IDMS-DC. (The table name is specified in the MODETAB parameter in the VTAM APPL definition for IDMS-DC.) Ensure that an entry exists for APPC sessions with parallel session and sync level support. The oraplu62.asm file in the $ORACLE_HOME/pg4appc/sna directory contains a sample mode entry, including comments that indicate the required values in the mode entry.

4. Modify the Mode Profile to be used for your IDMS-DC connections.

   To bypass a bug in IDMS-DC, set the Auto ACTIVATIONS Limit field to the same value as the Maximum Number of SESSIONS field. Without this setting, IDMS-DC rejects the first data packet received from HP-UX on each conversation, making it impossible for the gateway to communicate with an IDMS-DC transaction.

5. Using CA-IDMS System Generation as a guide, perform the following IDMS tasks:

   1. Enable the IDMS-DC multiple session service manager, RHDCCNOS.

   2. Define a VTAM line for APPC use if one is not already defined.

   3. Define PTERMs and LTERMs for communications with the HP-UX independent LU, as defined to VTAM on z/OS.

      Set up two PTERM/LTERM definitions to use the SNASVCMG mode entry for communications between the SNA Service Managers on MVS and HP-UX. Set up one of these definitions as a contention winner and set up the other one as a contention loser. Set up additional PTERM/LTERM definitions to use the mode entry defined in the SNA communication package. Profile DEFINE/MODE entry for use by the gateway sessions. One PTERM/LTERM definition is required for each concurrent session with the gateway. Set up these definitions with contention off.

      In the $ORACLE_HOME/pg4appc/demo/IDMS directory, the appcdef.doc file provides sample IDMS-DC definitions for a VTAM line with PTERMs and LTERMs.

   4. Define the IVP and sample programs and transactions to IDMS-DC.

      In the $ORACLE_HOME/pg4appc/demo/IDMS directory, the trandef.doc file provides sample IDMS-DC definitions for the IVP and sample programs and transactions. These definitions should not be modified.

6. Using a file transfer facility, transfer the following files from the $ORACLE_HOME/pg4appc/demo/IDMS directory to the z/OS system on which you run IDMS-DC:

   • pgaflip.asm: The assembler source for the IDMS-DC FLIP program

   • pgaflip.jcl: JCL to assemble and linkedit the IDMS-DC FLIP program

7. Using the comments in the pgaflip.jcl file, tailor the JCL to match your system setup and submit it for batch execution. Performing this step assembles and linkedits the pgaflip.asm file into a load module library accessible to your IDMS-DC system through the CDMSLIB DD statement in the IDMS-DC startup procedure.

The IDMS-DC configuration is now complete.

Configuring IMS/TM

If your OLTP is IMS/TM, then perform the following steps to configure IMS/TM and z/OS for communication with the gateway:

1. Configure your IMS system for the APPC.

2. Configure MVS VTAM for the SNA APPC connection to UNIX. At least one independent LU must be available for use by the gateway, unless you are using the IMS LU6.1 Adapter for LU6.2 applications. In this case, you must have one dependent LU defined for each concurrent session. For example, if you want to support 10 concurrent sessions, then you must have 10 dependent LUs defined.

3. Check the VTAM logmode table used by IMS/TM. The table name is specified by the MODETAB parameter in the VTAM APPL definition. For APPC/IMS, ensure that an entry exists for APPC sessions with sync-level support and parallel session support. The oralu62.asm and oraplu62.asm files in the $ORACLE_HOME/pg4appc/sna directory contain sample mode entries for single session and parallel session support, respectively. The samples include comments that indicate the required values in the mode entries.

4. Using your file transfer facility, transfer the following files from the $ORACLE_HOME/pg4appc/demo/IMS directory to the z/OS system on which you run IMS/TM:

   • pgaflip.asm is assembler source for IMS FLIP transaction

   • pgaflip.jcl is JCL to assemble and linkedit IMS FLIP transaction

   • imsgen.asm is IMS stage 1 gen definitions for the IMS FLIP transaction

5. Add the statements in the imsgen.asm file to your IMS stage 1 gen and run your IMS stage 1 and stage 2 gens. Use the online change utility to enable the new transaction definition.

6. Using the comments in the pgaflip.jcl file, tailor the JCL to match your system setup and submit it for batch execution. This assembles and linkedits the pgaflip.asm file into a load module library that is accessible to your IMS/TM system and creates an PSB and an ACB for the FLIP transaction.

7. Perform the tasks necessary on your system to make the new transaction available to IMS/TM. Depending on your system setup, you might have to restart IMS.

The IMS/TM configuration is now complete.

Configuring APPC/MVS

If your OLTP is APPC/MVS, then perform the following steps to configure APPC/MVS for communication with the gateway:

1. Configure MVS VTAM for the SNA APPC connection to HP-UX. At least one independent LU must be available for use by the gateway.

2. Check the VTAM logmode table used by APPC/MVS. (The table name is specified by the MODETAB parameter in the VTAM APPL definition for APPC/MVS.) Ensure that an entry exists for APPC sessions with sync level and parallel session support. The oraplu62.asm file in the $ORACLE_HOME/pg4appc/sna directory contains a sample mode entry, including comments that indicate the required values in the mode entry.

3. Allocate a partitioned data set (PDS) on your z/OS system where the sample files are placed. The PDS should be allocated with RECFM=FB, LRECL=80, and a BLKSIZE appropriate for the device type on which it is located. Approximately two tracks of 3390 disk space are required with one directory block. Oracle suggests naming this partitioned data set (PDS) ORAPGA.APPCMVS.SAMPLIB.

4. Using a file transfer facility, transfer the following files from the $ORACLE_HOME/pg4appc/demo/MVS directory to the z/OS PDS you allocated in the previous step, using the following specified member names:

   • pgaflip.jcl: JCL to add an APPC/MVS TP profile and to define the execution environment for the transaction. Store this file in your z/OS PDS as member PGAFLIPJ.

   • pgaflip.rex: The REXX source for the APPC/MVS PGAFLIP transaction. Store this file in your z/OS PDS as member PGAFLIP.

5. Using the comments in the pgaflip.jcl file, tailor the JCL to match your system setup and submit it for batch execution. Performing this step defines the APPC/MVS TP profile for the PGAFLIP transaction and stores it in the APPC/MVS profile data set. Ensure that you change the data set name in the JCL to match the name of the z/OS PDS allocated in Step 3.

The APPC/MVS configuration is now complete.

Now that you have completed configuration of the network on a gateway using the SNA protocol, refer to Chapter 12, "Gateway Configuration Using SNA Communication Protocol". Refer to Chapter12, "Configuring Commit-Confirm" for more information on configuring commit-confirm.