Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
Changing the default number of recall retries for a data set residing on a volume in use by RECYCLE or TAPECOPY processing z/OS DFSMShsm Implementation and Customization Guide SC23-6869-01 |
|
RECYCLE— When a DFSMShsm user needs a data set residing on a volume that is being processed by RECYCLE processing, the recall function requests the volume and then retries the recall request approximately every two minutes for up to 30 minutes (15 retries). After 15 retries, DFSMShsm issues message ARC0380A, which requires the operator to respond with a WAIT, CANCEL, or MOUNT command. TAPECOPY— By default, when a DFSMShsm user needs a data set that resides on a volume that is being read by TAPECOPY processing, that data set cannot be recalled until TAPECOPY processing has completed. By default, DFSMShsm retries the recall request approximately every two minutes for up to 30 minutes (15 retries). After 15 retries, DFSMShsm issues message ARC0380A, which requires the operator to respond with a WAIT, CANCEL, or MOUNT command. For more information about enabling the takeaway function during TAPECOPY, see Enabling the takeaway function during TAPECOPY processing. For both RECYCLE and TAPECOPY, you can increase or decrease the
number of recall request retries by modifying a patchable field in
the MCVT. For example, the following patch resets the number of recall
request retries to zero.
Although 15 is the default for the number of times a recall is
retried when the volume is in use by RECYCLE or TAPECOPY (retries
occur approximately every 2 minutes for a total of 30 minutes), you
can use the following patch to change the number of RECALL request
retries to, for example, 30 for a total of one hour.
|
Copyright IBM Corporation 1990, 2014
|