z/OS DFSMShsm Implementation and Customization Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Allowing functions to release ARCENQG and ARCCAT or ARCGPA and ARCCAT for CDS backup to continue

z/OS DFSMShsm Implementation and Customization Guide
SC23-6869-01

Certain functions and modules enqueue ARCENQG and ARCCAT or ARCGPA and ARCCAT resources during processing. When these resources are held, CDS backup cannot continue. Table 1 lists the external interface (patch) that can be enabled or tuned to set an interval at which the function or module is forced to release the resources.

When a patch is used, the function or module is quiesced and the resource is released. After the set interval, a hold on the resource is obtained again. These patches are not applicable for every action of the function or module. For example, the auditing 500 data set interval is not applicable for audit functions that do not process data sets.
Table 1. Functions and the Patch Used to Control the Release Interval to Allow CDS Backup to Continue
Function or module Resource released Default interval External interface (patch)
Recycle ARCGPA, ARCCAT 15 minutes PATCH.YGCB.+CE X'nn'
Audit ARCGPA, ARCCAT 500 data sets PATCH.MCVT.+25C X'nn'
TAPECOPY ARCGPA, ARCCAT 10,000 blocks PATCH.MCVT.+286 BITS(........1.)
Migration (secondary space management) ARCGPA, ARCCAT 5 minutes (TIME default) PATCH.MGCB.+B2 X'nn'
Start of changeMigration (primary space management, interval migration, on-demand migration, and command migration)End of change ARCENQG, ARCCAT 0 minutes (TIME default) PATCH.MGCB.+90 X'nn'
EXPIREBV ARCGPA, ARCCAT 500 data sets PATCH.MCVT.+25C X'nn'
Tape device allocation (migration) ARCGPA, ARCCAT 10 seconds PATCH.MCVT.+194 BIT(.......1)
Note:
  1. These patches to not have an effect on releasing the ARCCAT resource under normal operation of the function or module. However, if an error occurs that prevents the function or module from releasing ARCCAT when a CDS backup is initiated, the patch value will apply.
  2. X'nn' is the hexadecimal representation of the interval (minutes or data sets) for which the resource is released.
  3. For both migration patches (in both a non-RLS and RLS environment), when work is completed on the current data set, a check is performed to determine whether the number of minutes specified in the patch has passed. If the number of minutes has passed, the resource is released so that other functions (such as CDS backup) that need the resource are able to continue.
  4. For both migration patches (in an RLS environment), when work is completed on the current data set, an additional check is performed to determine whether any other host is waiting for the resource to be available before starting a CDS backup. If a host is waiting for the resource, the resource is released.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014