Specifies how many hours to attempt to acquire a Teradata utility slot.
| Valid in: | DATA and PROC steps (when creating and appending to DBMS tables using SAS/ACCESS software) |
|---|---|
| Category: | Bulk Loading |
| Default: | 0 (FastLoad) |
| 4 (FastExport, MultiLoad) | |
| Data source: | Teradata |
| Tip: | The data set option has precedence over the LIBNAME option. |
| See: | DBSLICEPARM= LIBNAME option, DBSLICEPARM= data set option, DBSLICEPARM= system option, FASTEXPORT= LIBNAME option, Maximizing Teradata Load Performance, MULTILOAD= data set option, SLEEP= LIBNAME option, SLEEP= data set option, Using the TPT API |
Table of Contents
specifies the number of hours to continue to try again to log on to Teradata.
Use this option to indicate to TPT FastExport, FastLoad, or MultiLoad how long to continue retrying a logon operation when the maximum number of utilities are already running. The maximum number of Teradata utilities that can run concurrently varies from 5 to 15, depending on the database server value. The default value for TENACITY= is four hours. The value specified for TENACITY= must be greater than zero.
Use TENACITY= with SLEEP= , which specifies the number of minutes that TPT FastExport, FastLoad, or MultiLoad waits before it retries logging on to Teradata. SLEEP= and TENACITY= function very much like the SLEEP and TENACITY run-time options of the native Teradata FastExport, FastLoad, or MultiLoad utility.
Here is an example of the message that is written to the SAS log if the time period that TENACITY= specifies is exceeded.
ERROR: MultiLoad failed unexpectedly with returncode 12
Check the TPT FastExport, FastLoad, or MultiLoad log for more information about the cause of the FastExport, FastLoad, or MultiLoad failure. SAS does not receive any informational messages from Teradata in either of these situations:
The native Teradata FastExport, FastLoad, or MultiLoad utility sends messages associated with SLEEP= and TENACITY= only to the TPT FastExport, FastLoad, or MultiLoad log. So nothing is written to the SAS log.