Db2 batch load utility load job steps

This section describes the steps in the load job when you select the Db2 Batch Load Utility option and your load includes Db2 tables.

Important

Which of the steps described below File-AID/RDX includes in the load job depends on:

  • The processing options specified.
  • The type or state of the tablespaces.
  • Whether referential integrity relationships exist.

Related topics

Db2 environment

The-load-process

  1. CREATE—Create New Tables and Indexes (XFREXEC)This step creates any new tables and indexes that did not exist at the time of the interactive phase of the Load function. The extract file being used must contain DDL for the tables and indexes to be created.

    For more information about how File-AID/RDX creates new tables, see Generating-CREATE-DDL.

  2. CLEAN1ST—File Cleanup (IDCAMS)

    This step deletes any existing files that are to be created in this job. This enables you to keep and rerun a JCL stream.

  3. LDDRV—Load Driver (XFREXEC)

    This step checks user authorizations for subsequent steps and separates the extract file into multiple files, one file per table to be loaded.

    Steps 4 through 7 are generated and executed for each table to be loaded.

  4. DELTEnnn—Delete Rows (XFREXEC)This step is generated when you request that data be deleted from a table before the load on the Load Options screen and the table resides in a tablespace that contains multiple tables. If the table to be loaded is the only table in the tablespace, the LOAD Utility parameter, REPLACE, is used to delete rows from the table. This step deletes rows from a table before data is loaded.

    If the table exists in a tablespace with multiple tables and the table has any dependents, File-AID/RDX generates and executes an ALTER statement to drop foreign keys from dependent tables prior to deleting rows. After deleting rows, File-AID/RDX generates and executes another ALTER statement to recreate the foreign keys.

  5. FIXDLnnn—IBM Db2 REPAIR Utility (DSNUTILB)This step executes the REPAIR utility for tablespaces after all data has been deleted from tables in a previous step.

    A tablespace will be placed in copy pending status when a table is loaded with the LOG Option parameter set to 3 (repair).

    For more information about this Db2 utility, see the IBM Db2 Command and Utility Reference.

  6. SORTnnn—File Sort Utility (SORT) or ICETOOL Multiple File SortThis step sorts a file containing the data to be loaded in the associated LOADnnn step.

    The sort sequence is based on the clustering index for that table. If no clustering index exists, sort sequence is based on the first defined unique index for that table. If no unique index exists, sort sequence is based on the first-defined index for that table.

    This step

    is generated and executed for each table to be loaded (SORT), or once for all files to be loaded (ICETOOL).

  7. LOADnnn—IBM Db2 LOAD Utility (DSNUTILB/NGTUTIL)(BMC AMI Load Utility must be configured in PARMLIB FADEXXXX)

    This step loads the data into a table from the sorted file generated in the SORT step 4. The RESUME NO parameter is used when rows are to be deleted from a table. The RESUME YES parameter is used when rows are not to be deleted from a table. The REPLACE parameter is used when rows are to be deleted from a table and no other tables exist in the tablespace.

    A return code of 4 may be acceptable. However, it is advisable to check any return code not equal to 0. Any return code greater than 4 will stop subsequent steps from running.

    For more information about this Db2 utility, see the IBM Db2 Command and Utility Reference.

    For more Information BMC AMI Load, see BMC AMI Load for Db2.

  8. RPAIRnnn—IBM Db2 REPAIR Utility (DSNUTILB)This step executes the REPAIR utility for required tablespaces. Required tablespaces are those tablespaces that will be placed in copy pending or checking pending status by either the load or delete steps and will be used by subsequent DELTE steps.

    A tablespace containing a dependent table will be placed in check pending status when the dependent table is loaded.

    A dependent table’s tablespace will be placed in check pending status when the dependent table’s parent rows are deleted.

    A tablespace will be placed in copy pending status when a table is loaded with the LOG Option parameter set to 3 (repair).

    For more information about this Db2 utility, see the IBM Db2 Command and Utility Reference.

  9. CHCKDATA—IBM Db2 CHECK Utility (DSNUTILB)This step executes the CHECK DATA utility for all tablespaces that could possibly have a CHECK PENDING restriction set by the IBM Db2 LOAD utility.

    A return code of 4 may be acceptable. However, it may also indicate tablespaces are left in a CHECK PENDING status. It is advisable to check the output from any return code not equal to 0.

    For more information about this Db2 utility, see the IBM Db2 Command and Utility Reference.

  10. IMAGECPY—IBM Db2 COPY Utility (COPY)This step invokes the COPY utility for all tablespaces included in the load if Log Option 1 (see Specify Db2 Load Utility Options) is not specified in the Load Utility control cards.

    For more information about this Db2 utility, see the IBM Db2 Command and Utility Reference.

  11. CLEANLST—File Cleanup (IDCAMS)This step deletes all File-AID/RDX

     temporary files used in this job. Keeping these files until all steps run successfully allows for the restarting of the JCL at any step.

  12. CLEANCTL—File Cleanup (IEFBR14) - OptionalThis step deletes the File-AID/RDX control card PDSEs. Whether step CLEANCTL is commented out or executed is determined by the global job option Delete in-stream data data sets at EOJ. If the job option is set to NO, File-AID/RDX

     control card PDSEs created in the load and delete jobs will NOT be deleted. Keeping the data sets until all steps run successfully allows for the restarting of the JCL at any step.

  13. CLEANEXT—File Cleanup (IDCAMS) - Optional

    This step deletes the File-AID/RDX EXTPARMS parameter file. Whether step CLEANEXT is commented out or executed is determined by the global job option Delete in-stream data data sets at EOJ. If the job option is set to NO, File-AID/RDX EXTPARMS files created in the load and delete jobs will NOT be deleted. Keeping the data sets until all steps run successfully allows for the restarting of the JCL at any step.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*