Creating Your Own TDPPARM - 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

If the examples on the release tape are insufficient, create a custom TDPPARM data set. It can be any data set that contains fixed, 80 byte records consisting of EBCDIC characters and is accessible to IBM SAM (Queued Sequential Access Method). Columns 73 through 80 are reserved for traditional sequence numbers and are ignored. Records containing only blanks are ignored. If the first non-blank characters of a record are /*, the record is considered a comment and ignored.

Messages that result from executing commands in the TDPPARM data set are routed to the z/OS console at which TDP was started. The records can be maintained by any text editor or utility that honors these attributes. If TDP was started as a batch job, messages are routed to the master console route code.

If execution of any TDPPARM command results in an error, TDP displays:

TDP0113 INITIALIZATION ERRORS -- ENTER GO OR CANCEL

If you enter “GO”,TDP continues to run. “CANCEL” stops TDP. The source of the error(s) can be determined either from the responses displayed at the console or from the dump.

TDPPARM is read only when TDP is started. Once all records have been processed, TDPPARM is not read again.