Scratching non-SMS generation data sets at roll-off time regardless of expiration dates

The MCVTFGDG patch only applies to non-SMS generation data sets. The management class controls SMS generation data sets. For more information about specifying GDG management attributes and deleting expired data sets, see the chapter on space management of SMS-managed storage in z/OS DFSMShsm Storage Administration.

When the MCVTFGDG bit is set to 1, DFSMShsm ignores the expiration date of a migrated generation data set at roll-off time, and immediately scratches the data set. To set this bit to 1, enter the following command:

PATCH .MCVT.+53 BITS(1.......) /* ignore expiration date at GDS roll-off    */
                               /* and scratch the data set.                 */

When this command is issued, migrated, date-protected, and rolled-off generation data sets defined with the SCRATCH option are scratched as the generation rolls off.

To allow both the migration of password-protected GDSs with their deletion at roll off without password checking, and the deletion of unexpired, date-protected GDSs at roll-off time, issue the following command:

PATCH .MCVT.+53 BITS(11......) /* allow pswd protected GDS to migrate then  */
                               /* scratch without checking pswd at roll off */
                               /*                    and                    */
                               /* ignore expiration date at GDS roll off    */
                               /* and scratch the data set.                 */