13.07.2015 Views

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

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

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

372 TENACITY= Data Set Option 4 Chapter 11TENACITY= Data Set OptionSpecifies how many hours MultiLoad continues to retry logging on to Teradata if the maximumnumber of Teradata utilities are already running.Default value: 4Valid in: DATA and PROC steps (when creating and appending to DBMS tables using<strong>SAS</strong>/<strong>ACCESS</strong> software)DBMS support: TeradataSyntaxTENACITY=number-of-hoursSyntax Descriptionnumber-of-hoursthe number of hours to continue to retry logging on to Teradata.DetailsUse the TENACITY= data set option to indicate to MultiLoad how long to continueretrying 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 to15, depending upon the database server setting.) The default value <strong>for</strong> TENACITY= isfour hours. The value specified <strong>for</strong> TENACITY must be greater than zero.Use TENACITY= with SLEEP=, which specifies the number of minutes thatMultiLoad waits be<strong>for</strong>e it retries logging on to Teradata. SLEEP= and TENACITY=function very much like the SLEEP and TENACITY run-time options of the nativeTeradata MultiLoad utility.This message is written to the <strong>SAS</strong> log if the time period that TENACITY= specifiesis exceeded.ERROR: MultiLoad failed unexpectedly with returncode 12Note: Check the MultiLoad log <strong>for</strong> more in<strong>for</strong>mation about the cause of theMultiLoad failure. <strong>SAS</strong> does not receive any in<strong>for</strong>mational messages from Teradata ineither of these situations:3 when the currently run MultiLoad process waits because the maximum number ofutilities are already running3 if MultiLoad is terminated because the time limit that TENACITY= specifies hasbeen exceededThe native Teradata MultiLoad utility sends messages associated with SLEEP= andTENACITY= only to the MultiLoad log. So nothing is written to the <strong>SAS</strong> log. 4

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!