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

Data Set Options for Relational Databases 4 BL_CONTROL= Data Set Option 215Syntax Descriptionpath-and-control-filename [Oracle]specifies the SQL*Loader file to which SQLLDR control statements are written thatdescribe the data to include in bulk load.path-and-data-filename [Teradata]specifies the name of the control file to generate for extracting data withSAS/ACCESS Interface to Teradata using FastExport multithreaded read.On most platforms, the default filename is BL__.ctl [Oracle,Teradata]:tableunique-IDDetailsspecifies the table namespecifies a number that is used to prevent collisions in the event oftwo or more simultaneous bulk loads of a particular table. TheSAS/ACCESS engine generates the number.To specify this option, you must first set BULKLOAD=YES.Oracle: The Oracle interface creates the control file by using information from theinput data and SAS/ACCESS options. The file contains Data Definition Language(DDL) definitions that specify the location of the data and how the data corresponds tothe database table. It is used to specify exactly how the loader should interpret thedata that you are loading from the DATA file (.DAT file). By default it creates a controlfile in the current directory or with the default file specifications. If you do not specifythis option and a control file does not already exist, a file is created in the currentdirectory or with the default file specifications. If you do not specify this option and acontrol file already exists, the Oracle interface reuses the file and replaces the contentswith the new control statements.Teradata: To specify this option, you must first set DBSLICEPARM=ALL as aLIBNAME or data set option for threaded reads. By default SAS creates a data file inthe current directory or with a platform-specific name. If you do not specify this optionand a control file does not exist, SAS creates a script file in the current directory orwith the default file specifications. If you do not specify this option and a control filealready exists, the DATA step. SAS/ACCESS Interface to Teradata creates the controlfile by using information from the input data and SAS/ACCESS options. The filecontains FastExport Language definitions that specify the location of the data and howthe data corresponds to the database table. It is used to specify exactly how theFastExport should interpret the data that you are loading from the DATA (.DAT) file.Because the script file that SAS generates for FastExport must contain logininformation in clear text, it is recommended that you secure the script file by specifyinga directory path that is protected.ExamplesThis example generates a Teradata script file, C:\protdir\fe.ctl on Windows.DATA test;SET teralib.mydata(DBSLICEPARM=ALL BL_CONTROL="C:\protdir\fe.ctl");run;This example generates a Teradata script file, /tmp/fe.ctl, on UNIX.