Updating DBCDLT - Teradata Tools and Utilities

Teradata Tools and Utilities for IBM z/OS Installation Guide

Product
Teradata Tools and Utilities
Release Number
15.10
Published
August 2016
Language
English (United States)
Last Update
2018-06-05
dita:mapPath
PDF_Installation_ZOS_1600.ditamap
dita:ditavalPath
ft:empty
dita:id
B035-3128
lifecycle
previous
Product Category
Teradata Tools and Utilities
The release media contains macros used to create the DBCDLT. When using the DBCDLT macro that is distributed in dbcpfx.TDPMAC, you must define each Teradata Director Program associated with a server that needs to communicate with applications in 2PC mode. The USERMOD sample for the DBC List Table (DBCDLT) is TDU0011 in dbcpfx.SAMPLIB. The macro operands are as follows:
DBCDLT TYPE=ENTRY,TDPID=TDPx,START=zzz
.
.
.
DBCDLT TYPE=FINAL
END,
  1. If your site is using 2PC processing, create the DBC List Table (DBCDLT) to define 2PC participants.where:
    Macro element x
    a single alphanumeric character (0 through 9, A through Z, $, #, or @) that identifies the actual tdpid.
    Macro element zzz
    YES or NO, indicating whether the interface to TDP is to be started automatically during initialization of the DBC CICS Attachment Facility
    You must have one TYPE=ENTRY specification for each Teradata Director Program that you are defining. The last macro in the source must be TYPE=FINAL.
    The assembler statement END is required. Any valid load module addressing and residency are supported and may be specified using Assembler, Linkage Editor, or Binder control statements. None are included in DBCDLT so that assemblers lacking such support may be used. The source is then assembled and link-edited into dbcpfx.CXILOAD. This is the CICS run-time load library that is added to the DFHRPL concatenation in the CICS procedure.