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

Data Set Options for Relational Databases 4 BL_DB2TBLXST= Data Set Option 235Default value: NOValid in: DATA and PROC steps (when accessing DBMS data using SAS/ACCESSsoftware)DBMS Support: DB2 under z/OSSyntaxBL_DB2TBLXST=YES | NOSyntax DescriptionYESspecifies that the LOAD utility runs against an existing table. This is not areplacement operation. (See “Details.”)NOspecifies that the LOAD utility does not run against an existing table.DetailsTo specify this option, you must first set BULKLOAD=YES.SAS/ACCESS does not currently support table replacement. You cannot simplycreate a new copy of an existing table, replacing the original table. Instead, you mustdelete the table and then create a new version of it.The DB2 LOAD utility does not create tables—it loads data into existing tables. TheDB2 under z/OS interface creates a table before loading data into it whether you useSQL INSERT statements or start the LOAD utility) You might want to start the utilityfor an existing table that the DB2 engine did not create. If so, specifyBL_DB2TBLXST=YES to tell the engine that the table already exists. WhenBL_DB2TBLXST=YES, the engine neither verifies that the table does not already exist,which eliminates the NO REPLACE error, nor creates the table. Because BULKLOAD=is not valid for update opening of tables, which include appending to an existing table,use BL_DB2TBLXST= with an output open, which would normally create the table, toaccomplish appending, or use the LOAD utility against a previously created table. Youcan also use BL_DB2TBLXST= with BL_DB2LDEXT=GENONLY if the table does notyet exist and you do not want to create or load it yet. In this case the control and datafiles are generated but the table is neither created nor loaded.Because the table might be empty or might contain rows, specify the appropriateLOAD utility control statement values for REPLACE, RESUME, or both by usingBL_DB2LDCT1, BL_DB2LDCT2 , or both.The data to be loaded into the existing table must match the table column types. Theengine does not try to verify input data with the table definition. The LOAC utilityflags any incompatible differences.See Also“BULKLOAD= Data Set Option” on page 290