DFSMSrmm enhancements for z/OS V2R2
- DFSMSrmm operational enhancements
Specify expiration time for volumes and data sets: DFSMSrmm
now specifies an expiration time, in addition to an expiration date,
for volumes and data sets, thus allowing greater control of exactly
when a volume or data set is to expire. The expiration time will be set to the current time whenever RETPD is used in the JCL, as a default, or in ADDDATASET, ADDVOLUME, CHANGEDATASET, or CHANGEVOLUME subcommands. When EXPDT is used instead of RETPD (in JCL or on a DFSMSrmm subcommand), the expiration time will be set to midnight.
In addition, the CHANGEDATASET and CHANGEVOLUME commands have been enhanced to enable the user to specify the time (in hhmmss format) that should be used, in addition to the date, when deciding when to expire volumes and data sets.
The ability to specify both the expiration time and date will be helpful to customers using the EXPDT retention method. For example, you might have data sets created shortly before midnight with a default retention period of one day. This new function will allow you to ensure these data sets do not expire in a few minutes and are kept at least for 24 hours.
- Search volumes and data sets by date/time ranges: The
SEARCHDATASET and SEARCHVOLUME commands have been enhanced to enable
the user to specify the time (in hhmmss format)
in addition to the date when searching for volumes and data sets by
the creation date.
The ability to select records by both the creation time and date will be helpful to customers using the EXPDT retention method. For example, the daily night batch processing might create tapes starting from 8 PM and until 5 AM on the next day. This new function will allow you to assign the same expiration date to all of these volumes, even though they were created on different calendar days.
- Specify that a data set not expire while cataloged: A
new WHILECATALOG option has been added to the EDGRMMxx parmlib member
OPTION command and to the CHANGEDATASET TSO subcommand to enable the
user to specify either that:
- the dataset will be kept as long as it is cataloged. If the dataset is uncataloged, it will still be kept if the expiration date has not been reached yet.
- the dataset will be kept as long as it is cataloged, but no later than the expiration date.