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

516 File Allocation and Naming for Bulk Loading 4 Chapter 163 BL_DB2IN=3 BL_DB2LDCT1=3 BL_DB2LDCT2=3 BL_DB2LDCT3=3 BL_DB2LDEXT=3 BL_DB2MGMTCLAS=3 BL_DB2MAP=3 BL_DB2PRINT=3 BL_DB2PRNLOG=3 BL_DB2REC=3 BL_DB2RECSP=3 BL_DB2RSTRT=3 BL_DB2SPC_PERM=3 BL_DB2SPC_TEMP=3 BL_DB2STORCLAS=3 BL_DB2TBLXST=3 BL_DB2UNITCOUNT=3 BL_DB2UTID=File Allocation and Naming for Bulk LoadingWhen you use bulk loading, these files (data sets) are allocated.3 The DB2 DSNUTILS procedure allocates these as new and catalogs the SysDisc,SysMap, and SysErr file unless BL_DB2LDEXT=USERUN (in which case the datasets are allocated as old and are kept).3 The DB2 interface engine allocates as new and catalogs the files SysIn and SysRecwhen the execution method specifies to generate them.3 The DB2 interface engine allocates as new and catalogs the file SysPrint when theexecution method specifies to run the utility.All allocations of these data sets are reversed by the end of the step. If errors occurbefore generation of the SysRec, any of these data sets that were allocated as new andcataloged are deleted as part of cleanup because they would be empty.The interface engine uses these options when it allocates nonexisting SYS data setnames.3 DSNUTILS uses BL_DB2DEVT_PERM= and BL_DB2SPC_PERM= for SysDisc,SysMap, and SysErr.3 The DB2 interface engine uses BL_DB2DEVT_PERM= for SysIn, SysRec, andSysPrint.3 SysRec uses BL_DB2RECSPC=. BL_DB2RECSPC= is necessary because theengine cannot determine how much space the SysRec requires—it depends on thevolume of data being loaded into the table.3 DSNUTILs uses BL_DB2DEVT_TEMP= and BL_DB2SPC_TEMP= to allocate theother data set names that the LOAD utility requires.This table shows how SysIn and SysRec are allocated based on the values ofBL_DB2LDEXT= and BL_DB2IN=, and BL_DB2REC=.