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.

Data Set Options <strong>for</strong> <strong>Relational</strong> <strong>Databases</strong> 4 BL_REMOTE_FILE= Data Set Option 277DetailsTo specify this option, you must first set BULKLOAD=YES.See Also“BL_REJECT_LIMIT= Data Set Option” on page 275“BULKLOAD= Data Set Option” on page 290BL_REMOTE_FILE= Data Set OptionSpecifies the base filename and location of DB2 LOAD temporary files.Default value: noneValid in: DATA and PROC steps (when accessing DBMS data using <strong>SAS</strong>/<strong>ACCESS</strong>software)DBMS support: DB2 under UNIX and PC HostsSyntaxBL_REMOTE_FILE=pathname-and-base-filenameSyntax Descriptionpathname-and-base-filenameis the full pathname and base filename to which DB2 appends extensions (such as.log, .msg, and .dat files) to create temporary files during load operations. By default,the base filename takes the <strong>for</strong>m BL__:tableunique-IDspecifies the table name.specifies a number that is used to prevent collisions in the eventof two or more simultaneous bulk loads of a particular table. The<strong>SAS</strong>/<strong>ACCESS</strong> engine generates the number.DetailsTo specify this option, you must first set BULKLOAD=YES.Do not use BL_REMOTE_FILE= unless you have <strong>SAS</strong> Release 6.1 or later <strong>for</strong> boththe DB2 client and server. Using the LOAD facility with a DB2 client or server be<strong>for</strong>eRelease 6.1 might cause the tablespace to become unusable in the event of a load error.A load error might affect tables other than the table being loaded.When you specify this option, the DB2 LOAD command is used (instead of theIMPORT command). For more in<strong>for</strong>mation about these commands, see the bulk-loadtopic in the DB2 under z/OS section.For pathname, specify a location on a DB2 server that is accessed exclusively by asingle DB2 server instance, and <strong>for</strong> which the instance owner has read and writepermissions. Make sure that each LOAD command is associated with a uniquepathname-and-base-filename value.

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

Saved successfully!

Ooh no, something went wrong!