Recommended primary GDIF control file size: n KB Peak: Number of Global Resources.: n Average RNAME length.......: n Number of GCBs.............: n Number of GHBs.............: n Number of MIMQNAME QNAMEs..: n Number of ALLSYS QNAMEs……..: n Number of Dynamic QNAMEs…..: n Required control file size.: n KB Current: Number of Global Resources.: n Average RNAME length.......: n Number of GCBs.............: n Number of GHBs.............: n Number of MIMQNAME QNAMEs..: n Number of ALLSYS QNAMEs....: n Number of Dynamic QNAMEs...: n Required control file size.: n KB
Reason:
This message is issued in response to the DISPLAY GDIF CFSIZE command. It displays a control file size recommendation based on your peak workload observed since product startup. If the DETAIL option is specified, then it also displays both peak and current values for the following various metrics used to calculate the size recommendation:
The recommended size, in KB, recommended for your primary control file.
The number of managed global ENQ resources concurrently held across the complex.
The mean of the length of the RNAME described in the Number of Global Resources.
The number of GCB control blocks, which represent interest for or ownership of an ENQ resource by the local system, on the local system. Only a small subset of these requires control file space on a global copy in practice. However, all are included in the size calculation so that the size estimate errs on the conservative side.
The number of GHB control blocks, representing desire for an ENQ resource by an external system, on the local system.
The number of control blocks representing managed QNAMEs built from the MIMQNAME member or from an internal list of QNAMEs hard-coded in the product.
The number of control blocks representing managed QNAMEs that originated from GDIINIT PROCESS=ALLSYSTEMS additions.
The number of control blocks representing managed QNAMEs that originated from ADDQNAME or DELQNAME commands.
The total control file size, in KB, that would be required to perform a global copy (typically done at migration/VCF recovery or product startup).
Action:
Ensure that your control files are adequately allocated given the displayed information.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |