Teradata MultiLoad Configuration File
Use a Teradata MultiLoad configuration file to set the initial default values for the following operating parameters when invoking Teradata MultiLoad:
AMPCHECK |
MAXSESS |
BRIEF |
MINSESS |
OFORMAT |
DATAENCRYPTION=ON or OFF |
IFORMAT |
CONFIGERRORS |
CHARSET |
RETRYFIRSTCONNECT |
ERRLOG |
RETRYOTHERCONNECT |
MATCHLEN |
RETRYCONNECTINTERVAL |
Note: RETRYFIRSTCONNECT, RETRYOTHERCONNECT and RETRYCONNECTINTERVAL can only be specified in the configuration file for network-attached platforms. There are no corresponding command line options.
The values specified in the Teradata MultiLoad configuration file override the internal utility default values for these parameters.
The configuration file parameters can themselves be overridden by the corresponding run‑time parameters, shown earlier in this chapter. (There is no MATCHLEN run‑time parameter.) The order of preference for these parameters, from highest to lowest, is:
1 – Run‑time parameters
2 – Teradata MultiLoad script
3 – Teradata MultiLoad configuration file specifications
4 – Teradata MultiLoad default values
Configuration File Name and Location
On network-attached systems, the Teradata MultiLoad configuration file must be named mloadcfg.dat and it must be located in either:
or
On mainframe-attached systems, the DD statement for the Teradata MultiLoad configuration file must be labeled MLOADCFG.
Configuration File Contents
The Teradata MultiLoad configuration file can have up to eleven entries, one for each parameter:
AMPCHECK=none/all/apply
BRIEF=on/off
OFORMAT=outputencoding
IFORMAT=scriptencoding
CHARSET=character-set-name
ERRLOG=filename
MATCHLEN=on/off
MAXSESS=max-sessions
MINSESS=min-sessions
DATAENCRYPTION=ON/OFF
CONFIGERRORS=IGNORE/TERMINATE
RETRYFIRSTCONNECT=n
RETRYOTHERCONNECT=n
RETRYCONNECTINTERVAL=s
where:
The Teradata MultiLoad configuration file can also have comment statements preceded by a number sign (#) character. For detailed descriptions of the specifications listed here, see “Run‑time Parameters” on page 33.
Configuration File Processing
The utility automatically checks for a configuration file each time the invocation command is entered. Upon locating a configuration file, the utility sets the defaults as specified, produces the appropriate output messages, and begins processing the job.
By default, any invalid configuration file entry or syntax error will abort the Teradata MultiLoad job immediately. The first invalid parameter will be reported, the rest of the config parameters will not be checked.
Note: The config file must be in the platform-appropriate single-byte character set, like ASCII or EBCDIC.