15.10 - Installing IMS/DC Interface for 2PC Protocol - Teradata Tools and Utilities

Teradata Tools and Utilities for IBM z/OS Installation Guide

Teradata Tools and Utilities
August 2016
Substitute the DBC prefix in place of dbcpfx for all library names.
If your site runs applications with the 2PC protocol using IMS as a coordinator, you must install the IMS/DC Interface using one of the methods already described and then complete the steps below. Two-phase commit is described in Teradata Director Program Reference, B035-2416.
  1. Ensure that the dbcpfx.AUTHLOAD library is authorized by APF.The AUTHLOAD library contains the DBCHCPI module, which implements the interface between the IMS coordinator and the Teradata server. The DBCHCPI module has one alias named DBCHCPI0.
  2. Add the AUTHLOAD library to the startup JCL for the control region. In the startup JCL for the control region, you must add a DFSESL statement pointing to dbcpfx.AUTHLOAD. The following is a sample control region DFSESL statement:
  3. Define the AUTHLOAD library in the dependent regions.For each dependent region that will use the IMS/DC Interface with 2PC processing, add a DFSESL statement to the IMSMSG JCL to define dbcpfx.AUTHLOAD. The following is a sample dependent region DFSESL:
  4. Specify the SSM (Subsystem Member) and IMSID values in the startup JCL for both the control region and appropriate dependent regions.

    In the JCL for the control region and the dependent regions that use 2PC, you must specify the following values:

    IMSID=xxxx (typically begins with IMS) 


    xxxx and yyyy are allowed a maximum of four characters each. The xxxx and yyyy values are combined to form the name of the corresponding SSM (subsystem member) in the IMSVS.PROCLIB.

    For example, if the region JCL specifies the IMSID value as IMSA and the SSM value as TDP4, the SSM member name in IMSVS.PROCLIB is IMSATDP4.

  5. Define an SSM entry in IMSVS.PROCLIB for the control region and appropriate dependent regions.All TDPs destined to operate in 2PC mode must be defined as external subsystems to the IMS control region and any dependent regions that support application transactions on the server. This is ensured by using SSM entries.

    One SSM can be defined for all regions (control and dependent). You can optionally define multiple SSMs. For multiple SSMs, you must define one for each dependent region where the dependent region for each SM defines the TDPs accessible to that region. In addition, the SSM for the control region defines all TDPs used in that system. The SSM entry in IMSVS.PROCLIB must be in the following form: TDPx,TDPx,DBCHCPI,,, where:

    TDPx is the tdpid for the Teradata server you are defining.

    IMS requires the comma characters to indicate omitted subparameters that are not used for the IMS/DC Interface.

    The syntax of the SSM entry is as follows: ssn,lit,esmt,,


    ssn is the Subsystem Name. For the Teradata Attachment Facility, this field specifies tdpid (subsystem name).

    lit is the Language Interface Token. This token, which is passed to the IMS external system support with the application call, identifies the external system with which the application is to communicate.

    For the Teradata Attachment Facility, this field must be the same as the subsystem name (ssn). esmt Attachment Facility Initialization Module name. This module specifies which Attachment Facility modules must be loaded by IMS. For the Teradata Attachment Facility, this field must contain DBCHCPI. The release media includes a load module of this name to be placed in the AUTHLOAD library.

  6. Authorize IMS to TDP in the TDPPARM data set and then create new entries in the TDPPARM data set (described in TDPPARM Settings for 2PC Processing) for each IMS control region that uses 2PC protocol. The entries authorize each control region to TDP and are in the following form:

    imsjob is the job name for the IMS control region.

  7. Delete or comment out the TDP command, DISABLE IRF, in the TDPPARM data set.After the DISABLE IRF command is eliminated, the two TDP-internal sessions necessary for 2PC processing are logged on automatically during TDP startup.