Requirements for existing output data sets

If an existing output data set does not meet the requirements described in this section, IMS displays an error message and the online reorganization for the HALDB partition does not begin.

An OSAM output data set has the following requirements:
  • Must be cataloged
  • Must be a DASD data set
  • Must not be a VSAM data set, except for the primary index data set of a PHIDAM database
  • Must not be a PDS, PDSE, or a member of a PDS or PDSE
A VSAM output data set has the following requirements:
  • Must be a VSAM entry-sequenced data set (ESDS), except for the primary index data set of a PHIDAM database
  • Must have the REUSE attribute
  • Must have a fixed-length record length that is identical to that of the corresponding input data set
  • Must have a control interval size that is identical to that of the corresponding input data set
  • Must have a SHAREOPTIONS attribute value that is at least as high as that of the corresponding input data set if the database is defined to DBRC with a SHARELVL attribute value of 2 or 3

For both OSAM and VSAM data sets, if you are increasing the block or CI size when you are altering the structure of the database by using the INIT OLREORG OPTION(ALTER) command, you cannot use existing data sets from a previous online reorganization. If you manually allocate the output data sets when the ALTER option is specified, you must ensure that the new data sets can accommodate any increase to the block or CI size that you have specified in the RECON data set for the alter operation.

A primary index data set has the following requirements:
  • Must be a VSAM key-sequenced data set (KSDS)
  • Must have the same key offset and length as the corresponding input KSDS
  • Must have the other required characteristics listed for VSAM output data sets