Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Specifying whether to suspend system activity for device allocations z/OS DFSMShsm Implementation and Customization Guide SC23-6869-01 |
|
Sometimes DFSMShsm requests a device allocation and that request cannot be met because all tape devices are temporarily unavailable. When no tape devices are immediately available, dynamic allocation can wait for a tape device to become available before it returns to DFSMShsm or it can retry the request at a later time. If dynamic allocation waits for a device, all DFSMShsm processing soon stops until a device is allocated. If dynamic allocation does not wait and DFSMShsm retries the request later, other DFSMShsm functions can continue processing. The WAIT and NOWAIT options of the tape device-allocation parameters
(INPUTTAPEALLOCATION, OUTPUTTAPEALLOCATION, and RECYCLETAPEALLOCATION)
control whether all DFSMShsm processing is suspended for a device allocation
or not. The options you should use depend on:
Note: The WAIT|NOWAIT option does not apply to the aggregate-backup-and-recovery
support (ABARS) secondary address space. For information about specifying
a wait option for ABARS, see Enabling ABARS ABACKUP and ARECOVER to wait for a tape unit allocation.
|
Copyright IBM Corporation 1990, 2014
|