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

380 TPT_ERROR_TABLE_1= Data Set Option 4 Chapter 11NOspecifies that all communication between the Teradata client and server is notencrypted when using the TPT API.DetailsTo use this option, you must first set TPT=YES.You can ensure that SQL requests, responses, and data that is transferred betweenthe Teradata client and server is encrypted when using the TPT API. See your Teradatadocumentation for details.See Also“Maximizing Teradata Load Performance” on page 804“Using the TPT API” on page 807“BULKLOAD= LIBNAME Option” on page 102“BULKLOAD= Data Set Option” on page 290“MULTILOAD= Data Set Option” on page 342“MULTISTMT= Data Set Option” on page 348“TPT= LIBNAME Option” on page 192“TPT= Data Set Option” on page 373TPT_ERROR_TABLE_1= Data Set OptionSpecifies the name of the first error table for SAS to use when using the TPT API with Fastload orMultiLoad.Default value: table_name_ETValid in: DATA and PROC steps (when accessing DBMS data using SAS/ACCESSsoftware)DBMS support: TeradataSyntaxTPT_ERROR_TABLE_1=valid_teradata_table_nameSyntax Descriptionvalid_teradata_table_namespecifies the name of the first error table for SAS to use when using the TPT API toload data with Fastload or MultiLoad.DetailsTo use this option, you must first set TPT=YES. This option is valid only when usingthe TPT API.Fastload and MultiLoad require an error table to hold records that were rejectedduring the acquisition phase. If you do not specify an error table, Teradata appends"_ET" to the name of the target table to load and uses it as the first error table by