The RELEASE command releases for processing all or part of the DFSMShsm functions that have been held. You cannot release the processing of a subfunction while the processing of its main function is being held. For example, you cannot release the subfunction BACKUP(AUTO) if the main function BACKUP is held. When you release a main function, the held main function processing and its associated subfunctions processing are released. Commands that failed after you issued the HOLD command are not restarted.
If a journal becomes full, processing is held for all migration, backup, and dump functions. To resume journaling and other DFSMShsm functions, enter the BACKVOL CDS command to null the journal. If multiple systems share the journal, enter the BACKVOL CDS command on one of the systems, and then enter the RELEASE ALL command on all of the systems that share the journal.
If DFSMShsm functions are held because of a full journal, the RELEASE command will not appear to be effective until the control data sets are backed up. For more information, seeData recovery scenarios.
The RELEASE command allows migration target levels (ML1 or ML2 tape) that have become unavailable as targets because of some error condition to become available for retry. For more information, see Managing DFSMShsm media.
In addition, you can also decide to print the activity logs or you can enable the EDGTVEXT interface again after it was disabled because of an ABEND in DFSMSrmm.