Hi Reza, it seems you're asking about ISGLOCK. Although the formula in the GRS Planning manual claims this structure is independent of connector count, and only depends on the peak resource count, playing around with various different connector counts in CFSIZER seems to indicate otherwise, so I'd go with the CFSIZER output, but maybe use the formula as a comparison.
A bit more from the CFSIZER help page I had to use when checking this elsewhere a while ago: -- start extract The IGSLOCK structure size is dependent upon the following factors: - The size and type of systems in the sysplex - The type of workload being performed. Global resource serialization requires that the lock structure contains at least 32767 (32k) locks. Typically, a small sysplex, made up of smaller processors, running a transaction processing workload will use a smaller structure size than a larger sysplex, composed of large processors, running a batch/TSO workload combination. Peak Number of Global Resources The number of peak global resources equals the number of unique globally managed resources (SYSTEMS ENQs and converted RESERVEs) outstanding, measured at a peak load time. The utility program ISGCGRS, available in SYS1.LINKLIB, can be used to obtain the number of outstanding global requests. The number of outstanding requests is shown in the third column of the report. To execute the utility, use the sample JCL found in SYS1.SAMPLIB member ISGCGRS. -- end extract Thx Peter Bishop On Mon, 8 Apr 2013 17:31:14 -0500, R Hey <[email protected]> wrote: >Thanks Lizette. > >Yes, seen it. > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
