Specifies the name of a temporary table that non-TPT MultiLoad uses to track checkpoint information.
| Valid in: | DATA and PROC steps (when creating and appending to DBMS tables using SAS/ACCESS software) |
|---|---|
| Category: | Data Set Control |
| Default: | none |
| Restrictions: | Starting in SAS 9.4M9, this option is no longer used. |
| Do not use ML_RESTART= with ML_LOG=, which provides a common prefix for all temporary tables that the non-TPT MultiLoad utility uses. | |
| Requirements: | To specify this option, you must first specify MULTILOAD=YES. |
| When you restart a failed MultiLoad job, you must specify the same application table from the earlier run so that the MultiLoad job can restart correctly. Using ML_RESTART=, ML_ERROR1=, and ML_WORK=, you must also specify the same log table, acquisition error table, and work table upon restarting. | |
| Data source: | Teradata |
| See: | ML_ERROR1= data set option, ML_ERROR2 data set option, ML_LOG= data set option, ML_WORK= data set option, MULTILOAD= data set option, Teradata MultiLoad documentation, TPT_LOG_TABLE= data set option, Using MultiLoad |
Table of Contents
specifies the name of the temporary table that the non-TPT MultiLoad utility uses to track checkpoint information.
This option pertains only to non-TPT MultiLoad. To work with TPT MultiLoad, use the TPT_LOG_TABLE= data set option.
Use the ML_RESTART= option to specify the name of a table to store checkpoint information. Upon restart, ML_RESTART= is used to specify the name of the log table that you used for tracking checkpoint information in an earlier failed run.