Skip to Content
Information
Space announcement: BMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.

Tablespaces

Tablespaces are affected during the File-AID/RDX Db2 load processing by the following:

  • The Target Environment screen;
  • Whether a tablespace contains one or several tables (Db2 Load Utility only); and
  • Whether a tablespace may or may not have been placed in CHECK PENDING or COPY PENDING status by the Db2 Load Utility or the Delete step.

Target Environment Screen

If you specify a tablespace in the Target Environment screen, the tablespace must exist in the specified database or the extract file must contain the DDL for the tablespace. File-AID/RDX generates DDL to create the table in this tablespace.

If you leave the Tablespace field on the Target Environment screen blank, File-AID/RDX generates DDL to create the tablespace implicitly. Implicit tablespace is not valid for multi-table or partitioned tablespaces. The current SQLID must have the proper Db2 authority to create the tablespace in the execution phase.

Single-Table and Multi-Table Tablespaces

When you select the Db2 Load Utility, File-AID/RDX processes tablespaces with a single table and those with multiple tables differently.

Single-Table Tablespaces

When rows are to be deleted before loading a table in a tablespace with only one table, the LOAD utility with the REPLACE parameter is used. Such a tablespace, therefore, does not require a separate DELETE step or a RPAIRnnn step to reset the CHECK PENDING status.

Multi-Table Tablespaces

When rows are to be deleted before loading a table in a tablespace with more than one table, File-AID/RDX generates a separate DELETE step. This DELETE step deletes rows only from the table you specified for load.It does not affect other tables in the tablespace.

Some tablespaces may have been placed in CHECK PENDING status by the load or delete step. Because tablespaces might be used in subsequent steps and cannot be in CHECK PENDING status, the RPAIRnnn step generated by File-AID/RDX resets the CHECK PENDING status.

CHECK PENDING Status

The Load job ensures that all tablespaces that have had the CHECK PENDING status set are included in the CHCKDATA step.

The CHECK utility step is generated as a step in the load JCL only if File-AID/RDX determines that one or more tablespaces to be loaded might be given the CHECK PENDING restriction. The CHECK utility control cards are generated in the LDDRV step of the load process. The SCOPE ALL parameter is also used in this step.

COPY PENDING Status

The Load job ensures that all tablespaces with COPY PENDING status are included in the IMAGECPY step.

It is possible for a table to be left in a COPY PENDING status if LOG OPTION 2 was used in the LOAD utility. A Db2 Copy utility step is generated in the load JCL if you specified 2 in the Log Option field on the Db2 Load Utility Load Options screen. The Copy utility control cards are generated in the LDDRV step of the load process.

 

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

BMC Compuware File-AID/RDX 21.01