If availability field is blank

Check when the DFSMSrmm EDGHSKP inventory management utility was last run. For volumes managed by the VRSEL retention method, DFSMSrmm does not mark a volume pending release if the last change date is more recent than the time of the last VRSEL processing. The last change date might have changed for one of these reasons.
- The volume is used or updated outside of EDGHSKP processing
- A move is confirmed since the last VRSEL processing
Check the volume expiration date, the volume retention method, and if you have specified that DFSMSrmm should ignore the expiration date for the volume. Look at the volume Action on Release: Expiry date ignore setting. If the expiration date is not ignored based on the retention policies you defined, DFSMSrmm keeps the volume until the expiration date is reached, even though the volume is no longer covered by a vital record specification.
The default expiration date set by DFSMSrmm is the creation date plus the EDGRMMxx PARMLIB member RETPD value. You can override the default by using the RMM CHANGEVOLUME subcommand with the EXPDT or RETPD operands.
A very common error occurs when you are using expiration dates that have special meaning. Examples of these dates include EXPDT=99000 and EXPDT=98001. DFSMSrmm requires the use of the DFSMSrmm EDG_EXIT100 exit to clear the expiration date field in the JFCB (JFCBXPDT) and assign a vital record specification management value for these dates. With the DFSMSrmm EDG_EXIT100 exit, the volume expiration date is set to the creation date plus the EDGRMMxx parmlib member RETPD operand value. If EDG_EXIT100 does not clear JFCBXPDT, the EXPDT date is passed to DFSMSrmm. DFSMSrmm translates EXPDT=99000 to an expiration date of 1999/000, which causes DFSMSrmm to consider the volume to be already expired. The same result occurs if EXPDT=98001 is used. To avoid premature expiration of volumes, check the EDG_EXIT100 exit to ensure that it correctly clears the expiration date field. If you did not intend to use an expiration date that has a special meaning, use the RMM CHANGEVOLUME subcommand to specify the correct expiration date.
When the RETAINBY(SET) option is used for VRSEL managed volumes, a volume that is not VRS retained and whose volume expiration date has been reached can be retained because another volume in the set is still required to be retained.

You can use the DFSMSrmm dialog to view the vital record status for volumes and data sets. Volume search results lists include 'VRS' in the status column and set retention state in the 'S R' column. Data set search results lists show the vital record state in the 'V R' column. Select/display the data set details to view the matching VRS information and the VRS retention date. Move the cursor to the 'VRS name' and press enter to see a list of the VRSes, enabling you to look at the matching VRS details. You can also use the RMM LISTDATASET command or the Vital Records Retention Report produced by EDGHSKP VRSEL processing to determine which data set and vital record specification are involved.

Related Reading: For information on the EDGUX100 exit, see z/OS DFSMSrmm Implementation and Customization Guide.