Skip to Content
Information
Limited support 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.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see REORG PLUS for DB2 13.1.

Reorganizing multi-data-set Db2 objects

You can reorganize multi-data-set Db2 objects. However, the following requirements and considerations apply when reorganizing these objects:

  • For multi-data-set table spaces and index spaces that are VCAT-defined, you must perform one of the following tasks to prevent REORG PLUS from terminating:
    • Predefine all required data sets.
    • Specify REDEFINE YES and include a SYSIDCIN data set that defines the required data sets.
  • For storage-group-defined multi-data-set objects, REORG PLUS defines additional data sets if needed for expansion, even if REDEFINE NO is in effect.

  • If you are using Instant Snapshot technology to copy nonpartitioned indexes and the copy of one component of the multi-data-set object fails, the copy for the entire index fails.

    • If the value of the SIXSNAP command or installation option is YES, REORG PLUS terminates.
    • If the value of the SIXSNAP command is AUTO, REORG PLUS changes SIXSNAP to NO and recopies all components in the multi-data-set index, using the software-based copy method.

    For possible timeout considerations when using the SIXSNAP function, see Considerations for SIXSNAP use.

  • You can use the DSRSEXIT user exit to redefine a multi-data-set object. For more information, see Using-DSRSEXIT-to-manage-VSAM-data-set-redefinition.

Related topics

Getting-started

Operational-considerations

 

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

REORG PLUS for DB2 11.2