Candidates for exploitation of the EXPDT retention method

Any volume that is externally managed by an application such as DFSMShsm, DFSMS OAM, or Tivoli® Storage Manager that is assigned an expiration date such as 1999/365. When the volume is no longer required, the application exploits the EDGTVEXT program interface to expire or release the volume.
"Archive" tape data that, once created, is retained by the same, simple policy until it should be expired, such as by using a retention period.
Any volume currently managed using a data set or volume VRS with DAYS COUNT(nnnn).
Any volume currently managed using a VRS with UNTILEXPIRED causing retention by the volume EXPDT.
Any volume currently managed using a data set VRS or a name VRS with LASTREFERENCEDAYS COUNT(nnnn).
Any volume that can be managed based on the expiration date of the first file.

Changing existing DFSMShsm managed volumes: You can use the CHANGEVOLUME subcommand with RETENTIONMETHOD and RETAINBY operands on single volumes and the first volumes in a multivolume set. DFSMSrmm will apply the specified retention method to all volumes in the multivolume set. All EXPDT retention method managed volumes must have a valid expiration date. For multivolume sets that use the EXPDT retention method and retain by VOLUME the desired expiration date must be specified for each volume in a multivolume set.

Identify your DFSMShsm managed single volumes, build and execute CLIST command for changing retention method, RETAINBY value, and expiration date:
```
RMM SV OWNER(hsm) INSET(NO) LIMIT(*) ... CLIST(’RMM CV ’,’ RM(EXPDT) RETAINBY(VOLUME) EXPDT(99365)’)
EXEC EXEC.RMM.CLIST
```
Identify your DFSMShsm managed first volumes in multivolume sets, build and execute CLIST command for changing retention method:
```
RMM SV OWNER(hsm) INSET(FIRST) LIMIT(*) ... CLIST('RMM CV ',' RM(EXPDT)')
EXEC EXEC.RMM.CLIST
```
Identify your DFSMShsm managed multivolume sets, build and execute CLIST command for changing expiration date:
```
RMM SV OWNER(hsm) INSET(YES) LIMIT(*) ... CLIST('RMM CV ',' EXPDT(99365)')
EXEC EXEC.RMM.CLIST
```

For single volumes and first volumes in each multivolume set that you want to retain by SET, issue the following:

RMM SV OWNER(id) INSET(NO) LIMIT(*) ... CLIST(’RMM CV ’,’ RM(EXPDT) RETAINBY(SET) EXPDT(99365)’) 
EXEC EXEC.RMM.CLIST

RMM SV OWNER(id) INSET(FIRST) LIMIT(*) ... CLIST(’RMM CV ’,’ RM(EXPDT) RETAINBY(SET) EXPDT(99365) ’)
EXEC EXEC.RMM.CLIST

DFSMSrmm processing sets the expiration date for all volumes in the set to the expiration date specified for the first volume.

For single volumes and first volumes in each multivolume set that you want to retain by FIRSTFILE, issue the following :

RMM SV OWNER(id) INSET(NO) LIMIT(*) ... CLIST(’RMM CV ’,’ RM(EXPDT) RETAINBY(FIRSTFILE) ’) 
EXEC EXEC.RMM.CLIST

RMM SV OWNER(id) INSET(FIRST) LIMIT(*) ... CLIST(’RMM CV ’,’ RM(EXPDT) RETAINBY(FIRSTFILE) ’)
EXEC EXEC.RMM.CLIST

You cannot set the volume expiration date in this case, the expiration date from the first file is applied. You can change the expiration date using RMM CHANGEDATASET command on the first file. DFSMSrmm processing sets the expiration date for all volumes in the set to the expiration date specified for the first file.