Starting a TDP Under z/OS - Teradata Director Program

Teradata® Director Program Reference - 17.20

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Teradata Director Program
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-11-17
dita:mapPath
cki1641301536147.ditamap
dita:ditavalPath
obe1474387269547.ditaval
dita:id
frc1470439950465
Product Category
Teradata Tools and Utilities

To start a TDP, use the following general steps:

  1. Check that the <dbcpfx>.TDPLOAD library at your site is APF-authorized.
  2. Check that the TDPISSI module was run and completed at IPL time.
  3. [Optional] Customize the TDPPARM data set, if necessary.

    For example, you might want to customize the TDPPARM data set if you have installed a new TDP or if you want to make a change in the initialization options.

  4. Start the TDP task, typically with the same name as the tdpid.

    Examples of TDP startup JCL are included in <dbcpfx>.PROCLIB, with the member names of TDP0 and TDP1.

    On z/OS systems, TDP establishes the following exclusive system-wide serialization during its execution:

    Major Name Minor Name Purpose
    TERADATA 4byte EBCDIC tdpid Prevents multiple TDPs with the same id.
    TERADATA 8byte EBCDIC HOSTxxxx, 
where 'xxxx' is the hexadecimal Logical-host id converted to EBCDIC Prevents multiple TDPs from using the same database Logical-host.

    On z/OS, TDP does not inhibit use of Resource Name Lists (RNLs) to alter the scope of the serialization. So if the mainframe configuration consists of a sysplex capable of accessing the same database Logical-hosts, z/OS Global Resource Serialization can be used to extend the local TDP serialization to all system images by including the major and minor names into the System Inclusion RNL.

For more information on starting a TDP, see Teradata® Tools and Utilities for IBM z/OS Installation Guide (B035-3128).