z/OS DFSMSrmm Managing and Using Removable Media
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Volume retention date

z/OS DFSMSrmm Managing and Using Removable Media
SC23-6873-00

DFSMSrmm uses the latest date for all the data sets on the volume as the retention date for the volume. DFSMSrmm sets the volume retention date in this order:

  1. PERMANENT
  2. CYCL/ccccc
  3. WHILECATLG
  4. A date in the format selected by your installation
  5. CATRETPD

Table 1 and Table 2 describe how DFSMSrmm calculates the retention date.

Table 1. DFSMSrmm retention date calculation by COUNT from 1 through 99998
If you have retention type: RMM calculates retention date as: And displays retention date as:
CYCLES Special cycles date format1 CYCL/ccccc
DAYS COUNT plus the create date1 Date format specified by your installation
EXTRADAYS (XD) COUNT plus the date14 Date format specified by your installation
LASTREF COUNT plus the last reference date1 Date format specified by your installation
CYCLES + WC Special catalog date format2 WHILECATLG
DAYS + WC COUNT plus the create date1 Date format specified by your installation
LASTREF + WC COUNT plus the last reference date1 Date format specified by your installation
CYCLES + UEX Volume expiration date1 Date format specified by your installation
DAYS + UEX Lower of volume expiration date and COUNT plus create date1 Date format specified by your installation
LASTREF + UEX Lower of volume expiration date and COUNT plus date last referenced1 Date format specified by your installation
CYCLES + WC + UEX Volume expiration date1 Date format specified by your installation
DAYS + WC + UEX Lower of volume expiration date and COUNT plus create date1 Date format specified by your installation
LASTREF + WC + UEX Lower of volume expiration date and COUNT plus date last referenced1 Date format specified by your installation
(DSN = UEX) and (MV/MC) Calculates two dates. One date using the primary data set vital record specifications. One date using the secondary MV or MC vital record specification. DFSMSrmm uses the earliest of the two dates.1,3 As determined by the vital record specification retention options.
Notes:
  1. The vital record specification deletion date is used as long as it is not 1999/365 and is lower than the retention date calculated. DFSMSrmm calculates the deletion date by using the earlier of the vital record specification currently retaining the data set or the first vital record specification in the vital record specification chain.
  2. The vital record specification deletion date is used as long as it is not 1999/365 and is lower than the retention date calculated. If a data set is not cataloged and is retained using the parmlib CATRETPD operand, DFSMSrmm sets the CATRETPD retention date. CATRETPD is used when the data set is retained by the catalog retention value and the WHILECATALOG retention type is specified. DFSMSrmm does not retain the data set if DFSMSrmm detected that the data set was cataloged and then uncataloged during the catalog retention period.
  3. The retention date format can be a date or any of the special date formats.
  4. DFSMSrmm uses the date when the subchain started to retain the data set as the retention date.
Legend
  • CYCLES= CYCLES and BYDAYSCYCLE retention types
  • DSN = Matching data set vital record specification
  • LASTREF = LASTREFERENCE (LASTREF date is the last referenced date in the data set record and is checked each time DFSMSrmm vital record processing is run.)
  • MC = Management class
  • MV = Management value
  • UEX = UNTILEXPIRED
  • WC = WHILECATALOG
  • XD = EXTRADAYS

Table 2 shows how DFSMSrmm calculates retention date for various retention types when you specify a COUNT(99999) on the DFSMSrmm ADDVRS subcommand. The COUNT(99999) on the DFSMSrmm ADDVRS subcommand indicates that DFSMSrmm retains all cycles of a data set.

Table 2. DFSMSrmm retention date calculation by COUNT(99999)
If you have retention type: RMM calculates retention date as: And displays retention date as:
CYCLES vital record specification delete date OR cycles date format1 Date format specified by your installation or CYCL/nnnnn
DAYS vital record specification delete date Date format specified by your installation or PERMANENT if the VRS delete date is 1999/365
EXTRADAYS (XD) vital record specification delete date Date format specified by your installation or PERMANENT if the VRS delete date is 1999/365
LASTREF vital record specification delete date Date format specified by your installation or PERMANENT if the VRS delete date is 1999/365
CYCLES + WC vital record specification delete date OR catalog date format2 Date format specified by your installation or WHILECATLG if WHILECATALOG is specified.
DAYS + WC vital record specification delete date OR catalog date format2 Date format specified by your installation or WHILECATLG if WHILECATALOG is specified.
LASTREF + WC vital record specification delete date OR catalog date format2 Date format specified by your installation or WHILECATLG if WHILECATALOG is specified.
CYCLES + UEX Volume expiration date3 Date format specified by your installation
DAYS + UEX Volume expiration date3 Date format specified by your installation
LASTREF + UEX Volume expiration date3 Date format specified by your installation
CYCLES + WC + UEX Volume expiration date3 Date format specified by your installation
DAYS + WC + UEX Volume expiration date3 Date format specified by your installation
LASTREF + WC + UEX Volume expiration date3 Date format specified by your installation
(DSN = UEX) and (MV/MC) Calculates two dates. One date using the primary data set vital record specifications. One date using the secondary MV or MC vital record specification. DFSMSrmm uses the earliest of the two dates.2,4 As determined by the vital record specification retention options.
Notes:
  1. The vital record specification deletion date is used as long as it is not 1999/365. The special cycles date format is used when the vital record specification deletion date is 1999/365. The deletion date used is the earlier of the current vital record specification and the first vital record specification in the vital record specification chain.
  2. The vital record specification deletion date is used as long as it is not 1999/365. The special catalog date format is used when the vital record specification deletion date is 1999/365. The deletion date used is the earlier of the current vital record specification and the first vital record specification in the vital record specification chain. If the data set is not cataloged and CATRETPD retains the data set, DFSMSrmm uses the CATRETPD retention date. CATRETPD is used when the data set is retained by the catalog retention value and the WHILECATALOG retention type is specified. DFSMSrmm does not retain the data set if DFSMSrmm detected that the data set was cataloged and then uncataloged during the catalog retention period.
  3. The vital record specification deletion date is used as long as it is not 1999/365. The deletion date used is the earlier of the current vital record specification and the first vital record specification in the vital record specification chain.
  4. DFSMSrmm calculates retention date based on both vital record specifications and information in this table.
Legend
  • CYCLES= CYCLES and BYDAYSCYCLE retention types
  • DSN = Matching data set vital record specification
  • LASTREF = LASTREFERENCE

    LASTREF date is the last referenced date in the data set record and is checked each time DFSMSrmm vital record processing is run.

  • MC = Management class
  • MV = Management value
  • UEX = UNTILEXPIRED
  • WC = WHILECATALOG
  • XD = EXTRADAYS
Parent topic: How DFSMSrmm calculates the retention date

Go to the previous page Go to the next page

Notices | Terms of use | Support | Contact z/OS | zFavorites



Copyright IBM Corporation 1990, 2014