DFSMSrmm uses the EDGDFHSM programming interface to release DFSMShsm tape volumes. The interface between DFSMShsm and DFSMSrmm is automatically in place when you install DFSMS, so you do not need to take any action to activate it or to call it.

Any caller of EDGDFHSM must be defined to RACF. If the caller is a started task, define the user ID with the STARTED class. Authorize your application to release its own tape volumes.

You must also consider how volumes are retained until the application calls the EDGDFHSM exit to release the volumes. You can use this program interface from programs other than DFSMShsm to release tape volumes. Refer to Running DFSMSrmm with DFSMShsm for information about setting up DFSMShsm with DFSMSrmm. You can use this information as an example for setting other applications that manage tape. You could retain tapes by defining vital record specifications like the ones shown in this example.

RMM ADDVRS DSN('**') JOBNAME(jobname) LOCATION(CURRENT) DAYS COUNT(99999)
RMM ADDVRS DSN('ABEND') JOBNAME(jobname) LOCATION(CURRENT) DAYS COUNT(99999)
RMM ADDVRS DSN('DELETED') JOBNAME(jobname) LOCATION(CURRENT) DAYS COUNT(99999)
RMM ADDVRS DSN('OPEN') JOBNAME(jobname) LOCATION(CURRENT) DAYS COUNT(99999)

Another way to retain tapes is with the EXPDT retention method.

You can use DFSMSrmm parmlib OPTION TVEXTPURGE operand to control the processing that EDGDFHSM performs. You can release volumes or set the volume expiration date either to the current date or based on a number of days from the current date. The effect of setting the expiration date depends on the retention method (EXPDT or VRSEL) already specified for the volume. Refer to TVEXTPURGE described in Defining system options: OPTION.

Callers of EDGDFHSM can request the processing of volumes only when their RACF user ID is authorized as defined by the RACF FACILITY class profiles for DFSMSrmm.