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

Data Set Options for Relational Databases 4 BL_DATAFILE= Data Set Option 219Default value: DBMS-specificValid in: DATA and PROC steps (when accessing data using SAS/ACCESS software)DBMS support: Aster nCluster, DB2 under UNIX and PC Hosts, Greenplum, HP Neoview,Netezza, Oracle, Sybase IQSyntaxBL_DATAFILE=path-and-data-filenameSyntax Descriptionpath-and-data-filenamespecifies the file that contains the rows of data to load or append into a DBMS tableduring bulk load. On most platforms, the default filename takes the formBL__.ext:tablespecifies the table name.unique-IDextDetailsspecifies a number that is used to prevent collisions in the eventof two or more simultaneous bulk loads of a particular table. TheSAS/ACCESS engine generates the number.specifies the file extension (.DAT or .IXF) for the data file.To specify this option, you must first set BULKLOAD=YES or BULKEXTRACT=YES.DB2 under UNIX and PC Hosts: The default is the current directory.Greenplum: This option specifies the name of the external file to load. It ismeaningful only when BL_PROTOCOL= is set to gpfdist or file. If you do not specifythis option, the filename is generated automatically. When you specify the filenamewith a full path, the path overrides the value of the GPLOAD_HOME environmentvariable. However, bulk load might fail if the path does not match the base directorythat the gpfdist utility used.HP Neoview, Netezza: You can use this option only when BL_USE_PIPE=NO. Thedefault is that the SAS/ACCESS engine creates a data file from the input SAS data setin the current directory or with the default file specifications before calling the bulkloader. The data file contains SAS data that is ready to load into the DBMS. By default,the data file is deleted after the load is completed. To override this behavior, specifyBL_DELETE_DATAFILE=NO.Oracle: The SAS/ACCESS engine creates this data file from the input SAS data setbefore calling the bulk loader. The data file contains SAS data that is ready to load intothe DBMS. By default, the data file is deleted after the load is completed. To overridethis behavior, specify BL_DELETE_DATAFILE=NO. If you do not specify this optionand a data file does not exist, the file is created in the current directory or with thedefault file specifications. If you do not specify this option and a data file already exists,SAS/ACCESS reuses the file, replacing the contents with the new data. SAS/ACCESSInterface to Oracle on z/OS is the exception: The data file is never reused because theinterface causes bulk load to fail instead of reusing a data file.Sybase IQ: By default, the SAS/ACCESS engine creates a data file with a .DAT fileextension in the current directory or with the default file specifications. Also by default,the data file is deleted after the load is completed. To override this behavior, specifyBL_DELETE_DATAFILE=NO.