REDEFINE
This option controls whether LOADPLUS deletes and redefines the VSAM data sets for the table space and index spaces that are participating in the load.
LOADPLUS can redefine both user-defined (VCAT-defined) data sets and data sets that are defined in DB2 storage groups (STOGROUP-defined).
Additional considerations
Note the following additional information about the REDEFINE option:
- For an SQLAPPLY load, LOADPLUS ignores this option.
- If you are loading a large number of partitions, BMC recommends that you specify REDEFINE NO.
- If you have altered the COMPRESS definition of a participating index, specify REDEFINE YES to enable LOADPLUS to redefine the index.
Specifying the default
You can specify the default for the REDEFINE command option in your installation options module by using the REDEFINE installation option. LOADPLUS was shipped with a default value of YES for this option. The command option overrides the default that is in the installation options module.
YES
The REDEFINE YES option tells LOADPLUS to delete and redefine the VSAM data set for each Db2 object before loading it. LOADPLUS also defines any additional VSAM data sets that might be required. The following table describes which Db2 objects that LOADPLUS redefines:
Command issued | Objects redefined |
---|---|
LOAD REPLACE |
|
LOAD RESUME YES SHRLEVEL NONE | If you specify or default to INDEX BUILD, all participating indexes |
LOAD RESUME YES PART n | If you specify or default to INDEX BUILD, the corresponding partition of any partitioned index and participating nonpartitioned indexes |
LOAD RESUME YES PART n REPLACE |
|
LOAD RESUME YES INTO TABLE tableName REPLACE | All participating indexes If you replace all tables in a table space, LOADPLUS also redefines the table space. |
SHRLEVEL CHANGE (except SQLAPPLY load) or SHRLEVEL REFERENCE | Staging data sets If you are loading VCAT-defined objects, you must provide the IDCAMS statements in the SYSIDCIN data set to delete and define the staging data sets. See Staging-data-sets for information about naming the staging data sets. |
Restriction
When invoking DSNUTILB, LOADPLUS ignores this option.
VCAT considerations
For VCAT-defined objects, consider the following information:
- When you specify PRELOAD PAUSE, you still have the option of deleting and redefining VCAT-defined data sets.
When you specify PRELOAD CONTINUE or PRELOAD LOAD, the only way to delete and redefine VCAT-defined data sets as part of the load is to use this option and provide the SYSIDCIN data set that contains the necessary IDCAMS control statements. Otherwise, LOADPLUS issues message BMC50391E and resets the high-used RBA.
For detailed information about using the SYSIDCIN data set in LOADPLUS, see SYSIDCIN-data-set-in-LOADPLUS.
STOGROUP considerations
For STOGROUP-defined objects, consider the following information:
- When you specify this option for STOGROUP-defined data sets, do not provide a SYSIDCIN data set.
- For a STOGROUP-defined table space or index space with multiple volumes defined in the storage group, LOADPLUS attempts to reallocate the data set on the volume on which it currently resides if that volume is still defined in the storage group. The order in which LOADPLUS retrieves subsequent volumes from the storage group for the purpose of allocating VSAM data sets is not predictable.
- The redefined table space data sets will have a control interval (CI) size that corresponds with the page size of the assigned buffer pool if the value of your DSVCI system parameter is set to YES.
NO
The REDEFINE NO option tells LOADPLUS not to delete and redefine the existing VSAM data sets for the table space and index spaces that are participating in the load. Instead, LOADPLUS issues message BMC50391I, reuses the existing data sets, and resets the high-used RBA.
When invoking DSNUTILB, LOADPLUS passes this option to the IBM Db2 LOAD utility as REUSE.
VCAT considerations
For VCAT-defined objects, LOADPLUS:
- Extends to another data set, if needed, as long as that data set is already defined
- Does not define any additional data sets
If you specify REDEFINE NO with any load job that uses staging data sets, you must preallocate the staging data sets for VCAT-defined objects. For more information, see Staging-data-sets.
STOGROUP considerations
For STOGROUP-defined objects, LOADPLUS provides the following functionality:
- For load jobs that use staging data sets, LOADPLUS creates any staging data sets that you do not preallocate and reuses any staging data sets that you do preallocate.
- For multi-data-set objects, LOADPLUS extends to another data set if needed, and creates the data set if it does not exist. When the load completes, LOADPLUS deletes any data set that it did not use.
- The control interval (CI) size for any additional data sets that LOADPLUS creates is based on the value of your DSVCI Db2 system parameter and the page size that is defined in the table space that you are loading.
Related topics