Daily limit not reached

If all DASD daily backup volumes are full or in use before the daily limit is reached, DFSMShsm does the following processing:

1. It assigns another DASD daily backup volume. When DFSMShsm assigns another DASD daily backup volume, it tries to select volumes in the following order:
   1. Unassigned DASD daily backup volume. DFSMShsm then assigns it to the current day in the backup cycle.
   2. Unassigned DASD backup volume. DFSMShsm then assigns it as a daily backup volume and to the current day in the backup cycle.
2. It reuses a full DASD daily backup volume. When no unassigned DASD backup volumes are available, DFSMShsm either spills or cleans up the full, unallocated, DASD daily backup volumes. DFSMShsm uses the first volume that falls below the threshold of occupancy that you specified with the THRESHOLD parameter of the ADDVOL command.
3. It waits for a DASD daily backup volume that is in use to become available. If the spill or cleanup process does not result in a usable DASD daily backup volume and another volume backup task is currently using a DASD daily backup volume, this volume backup task waits for a DASD daily backup volume to become available.

   In a multiple DFSMShsm-host environment, before a volume backup task enters the wait state, a five-minute timer is set. When the timer expires, the volume backup task is dispatched, and DFSMShsm tries to select another DASD daily backup volume. If the DASD daily backup volume is still not available, the volume backup task resets the timer and reenters a wait state. If another volume backup task dispatches the volume backup task in the same host before the timer expires, the timer is canceled, and DFSMShsm tries to select the DASD daily backup volume again.

4. It stops backup processing. If DFSMShsm cannot find a DASD daily backup volume and no other volume backup task is using a DASD daily backup volume, the current volume backup task ends because no DASD daily backup volume is available.