However, the GRS ISGLOCK structure does not support alter, and there is
therefore no need to specify an INITSIZE. Just specify SIZE for ISGLOCK.
Bill Neiman
Parallel Sysplex Development
IBM Poughkeepsie
--
For IBM-MAIN
You should use the size that corresponds to your actual workload and
configuration. If you use a structure that's too small, you'll get fewer lock
table entries and may encounter more false contention (when distinct resources
hash to the same lock table entry) and degraded performance. If you
, MN. 55121-1346
p. 612.266.3150
m. 651.274.5819
f. 612.266.3196
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Bill Neiman
Sent: Friday, April 12, 2013 11:32 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: CFRM policy size
You should
Hi,
Used the CFsizer site for GRS got:
peak-res# , #con --- SIZE
60 ,2 -- 133120
40 ,2 -- 133120
35 ,2 -- 133120
33 ,2 -- 66560
30 ,2 -- 66560
20 ,2 -- 66560
10 ,2 -- 33792
5 ,2 -- 17408
4 ,2 -- 9216
3 ,2 -- 9216
2 ,2 -- 5120
The formula documented in the pub assumes that each lock table entry is 8 bytes
wide. In many cases, that's bigger than it needs to be. The number of
connectors determines the actual required lock table entry width.
Note that CFSizer and the Sizer utility (the documentation for which you are
Thanks Bill
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
@LISTSERV.UA.EDU
Subject: CFRM policy size
Hi,
Book says:
Figure 49. Formula for Determining SIZE Parameter for the CFRM Policy
# lock table entries = peak # resources * 100 Round # lock table entries up
to next
power of 2 Lock table size (in bytes) = # lock table entries * 8 Structure
Thanks Lizette.
Yes, seen it.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
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,
Thanks Peter.
I've heard:
a- formula uses the default 32 systems/connectors.
b- if I only have 2 systems, then the size from formula can be reduced
So, if b is correct, I'd like to know where the #systems fit in the formula.
As for CFSIZER, the doco says:
3. With the structures in the
Hi,
Book says:
Figure 49. Formula for Determining SIZE Parameter for the CFRM Policy
# lock table entries = peak # resources * 100
Round # lock table entries up to next power of 2
Lock table size (in bytes) = # lock table entries * 8
Structure Size (in K bytes) = (lock table size/1024) +
11 matches
Mail list logo
