Mainframe-Attached Runtime Parameters | Teradata FastLoad - Mainframe-Attached Runtime Parameters - FastLoad

Teradata® FastLoad Reference

Release Number
June 2020
English (United States)
Last Update
Product Category
Teradata Tools and Utilities

The following table describes the runtime parameters used by Teradata FastLoad.

Using these Teradata FastLoad runtime parameters will override configuration parameter settings.

Runtime Parameters (Mainframe-Attached Systems)
Parameter Description
BUFSIZE=kilobytes Output buffer size specification, where kilobytes is the size of the output buffer, in kilobytes, that will be used for Teradata FastLoad messages to the database.

The output buffer size and the size of the rows in the Teradata FastLoad table determine the maximum number of rows that can be included in each message to the database. A larger buffer size reduces processing overhead by including more data in each message.

The default buffer size is also the maximum size allowed, 63 KB. If a value greater than 63 KB is specified, Teradata FastLoad:
  • Responds with a warning message
  • Resets the buffer size back to the default value
  • Continues with the Teradata FastLoad job
CHARSET=character-set-name A character set specification remains in effect for the entire Teradata FastLoad job, even if the database server resets, causing the Teradata FastLoad job to be restarted.

The character set specification does not remain in effect if the client system fails, or if the Teradata FastLoad job is canceled. In these cases, when the job is resubmitted, he same character set specification that was used on the initial job must be used. If a different character set specification is used when such a job is resubmitted, the data loaded by the restarted job will not appear the same as the data loaded by the initial job.

When a particular character set is specified, the identifiers and data in that character set can be specified, thus affecting how the data is loaded into the Teradata FastLoad table.

If a character set specification is not entered, the default is whatever character set that is specified for the database whenever Teradata FastLoad was invoked.

The order in which the character set is determined for a Teradata FastLoad job is as follows:
  • User-specified by either a runtime parameter on mainframe-attached systems or a SET SESSION CHARSET command on workstation-attached systems
  • When using UTF-8 client character set on the mainframe, the client character set name needs to be specified by the runtime parameter (for example, CHARSET=UTF-8). UTF8 is also a valid value.
  • System Parameter Block (SPB) specified by either the HSHSPB on mainframe-attached systems or the clispb.dat file on workstation-attached systems
  • Database default, determined by a query from Teradata FastLoad
On IBM z/OS, the job script must be in Teradata EBCDIC when using UTF-8 client character set. Teradata FastLoad translates commands in the job script from Teradata EBCDIC to UTF-8 during the load. Be sure to examine the definition in Teradata Vantage™ - Advanced SQL Engine International Character Set Support, B035-1125 to determine the code points of any special characters required. Different versions of EBCDIC do not always agree as to the placement of these characters. The mappings between Teradata EBCDIC and Unicode can be referred in Teradata Vantage™ - Advanced SQL Engine International Character Set Support, B035-1125.
DEBUG Used to display FastLoad execution debugging information to the standard output.
ERRORLOG= filename Alternate file specification for Teradata FastLoad error messages

Specifying an alternate file name produces a duplicate record of all Teradata FastLoad error messages.

The alternate file specification is limited to eight characters and, on z/OS, it must be to a DD name defined in the JCL.

There is no default filename specification.

MAXSESS = max-sessions Maximum number of Teradata FastLoad sessions logged on to the database.

Maximum specification must be greater than zero and no more than the total number of AMPs on the system.

Default is one session for each AMP.

MINSESS = min-sessions Minimum number of Teradata FastLoad sessions required to run the job.

Minimum specification must be greater than zero and it must be less than the value given for MAXSESS.

Default is 1.

RATE=outputrate The rate for displaying progress messages to standard output for rows successfully loaded to the database.

If not specified, FastLoad defaults to writing a message every 100000 rows. Standard output for the default looks similar to the following:

**** 22:00:06 Starting row 400000
**** 22:00:11 Starting row 500000
**** 22:00:15 starting row 600000

outputrate must be specified as an integer between 1 and 4294967295. Integers outside this range or float values are invalid. If an invalid value is specified, FastLoad displays a message stating that an invalid outputrate value has been specified and the default value is used to process the Teradata FastLoad job.

RVERSION Display version number and stop.

This option must be run alone. Running the -V option with other run time options will produce invalid results.

SLEEP= minutes Specification of the sleep option in which minutes is the number of minutes that Teradata FastLoad pauses before retrying the logon operation.

For more information, see SLEEP.

The Teradata FastLoad default value is 6 minutes.

TENACITY= hours Specification of the tenacity option in which hours is the number of hours that Teradata FastLoad continues trying to log on when the maximum number of load jobs are already running on the database.

For more information, see TENACITY.

The Teradata FastLoad default is no tenacity. Either a Teradata FastLoad configuration file entry, the runtime parameter, or a TENACITY command in your Teradata FastLoad job script must be used to enable the tenacity feature for the Teradata FastLoad logon operation.

VERBOSE Allows every request sent to the database to be printed.