SAS/ACCESS 9.2 for Relational Databases: Reference, Fourth Edition

806 Using MultiLoad 4 Chapter 283 unique secondary indexes3 foreign key references3 join indexesBoth the Teradata MultiLoad utility and the SAS/ACCESS MultiLoad facility logdata errors to tables. Error recovery can be difficult, but the ability to restart from thelast checkpoint is possible. To find the error that corresponds to the code that is storedin the error table, see the Teradata MultiLoad documentation.MultiLoad SetupHere are the requirements for using the MultiLoad bulk-load capability in SAS.3 The native Teradata MultiLoad utility must be present on your system. If you donot have the Teradata MultiLoad utility and you want to use it with SAS, contactTeradata to obtain the utility.3 SAS must be able to locate the Teradata MultiLoad utility on your system.3 The Teradata MultiLoad utility must be able to locate the SASMlam accessmodule and the SasMlne exit routine. They are supplied with SAS/ACCESSInterface to Teradata.3 SAS MultiLoad requires Teradata client TTU 8.2 or later.If it has not been done so already as part of the post-installation configuration process,see the SAS configuration documentation for your system for information about how toconfigure SAS to work with MultiLoad.MultiLoad Data Set OptionsCall the SAS/ACCESS MultiLoad facility by specifying MULTILOAD=YES. See theMULTILOAD= data set option for detailed information and examples on loading dataand recovering from errors during the load process.Here are the data set options that are available for use with the MultiLoad facility.For detailed information about these options, see Chapter 11, “Data Set Options forRelational Databases,” on page 203.3 MBUFSIZE=3 ML_CHECKPOINT=3 ML_ERROR1= lets the user name the error table that MultiLoad uses for trackingerrors from the acquisition phase. See the Teradata MultiLoad reference for moreinformation about what is stored in this table. By default, the acquisition errortable is named SAS_ML_ET_randnum where randnum is a random number.When restarting a failed MultiLoad job, you need to specify the same acquisitiontable from the earlier run so that the MultiLoad job can restart correctly. Notethat the same log table, application error table, and work table must also bespecified upon restarting, using ML_RESTART, ML_ERROR2, and ML_WORKdata set options. ML_ERROR1 and ML_LOG are mutually exclusive and cannotbe specified together.3 ML_ERROR2=3 ML_LOG= specifies a prefix for the temporary tables that the Teradata MultiLoadutility uses during the load process. The MultiLoad utility uses a log table, twoerror tables, and a work table while loading data to the target table. These tablesare named by default as SAS_ML_RS_randnum, SAS_ML_ET_randnum,SAS_ML_UT_randnum, and SAS_ML_WT_randnum where randnum is arandomly generated number. ML_LOG= is used to override the default namesused. For example, if you specify ML_LOG=MY_LOAD the log table is named