Changes in the storage group

Consider the consequence of making a specific volume request in a storage group configuration that has changed. Assume that a data set with the GUARANTEED SPACE storage class has been backed up. Sometime later, one or more of the volumes on which the data set has resided are removed from the storage groups that contain GUARANTEED SPACE data sets. A subsequent recover of the data set fails because at least one of the requested volumes is no longer part of a storage group for a GUARANTEED SPACE request. The result is the same for both single-volume data sets and multiple-volume VSAM data sets if the specific volume required is unavailable in the necessary storage group. Use of EAV volumes in mixed environments where the volume cannot be brought online to all systems can also result in problems recalling/recovering data sets that belong to a Storage Class having the Guaranteed Space attribute.

If a storage group is changed to remove volumes that data sets migrated from, you must do one of the following:
  • Change the ACS storage class routine so that a storage class with GUARANTEED SPACE is not assigned to the data set.
  • Change the volume configuration again so the storage group contains the volumes from which the data set was backed up.
  • Change the set of storage groups to which the GUARANTEED SPACE storage class maps to include one that already has the necessary volumes defined. This step applies only if the volumes are already SMS-managed.
  • Use the RECOVER command with the FORCENONSMS and the VOLUME parameters. This RECOVER command causes the data set to be recovered to a non-SMS-managed volume as a non-SMS-managed data set. You can then move, copy, or convert the data set as necessary.
    Note: If the data set was multiple-volume when it was backed up, it is recovered to a single volume.
Parent topic: Problems that can occur