Background:
We run Top Secret release 5.3 at Service Level 5302 in
6 z/OS 1.5 images sharing a SECFILE structure with
OPTIONS(61) to move the SECFILE locking function into
the structure. The default TIMELOCK wait value (250
milliseconds) causes CICS response time spikes in the
10+ second range. The vendor (Computer Associates)
recommends 100 milliseconds for TIMELOCK, but our
experimentation (SYSPLEX(TRACE)) shows the SECFILE
lock can be gotten and released in less than 10
milliseconds.
The basic question is this:
If you're using Computer Associates' Top Secret
product in a parallel sysplex, and have implemented a
coupling facility structure for the SECFILE with
OPTIONS(61) in effect, what value do you use for the
TIMELOCK "wait" parameter (1st value)?
Extended questions:
We are very interested in any experience modifying the
TIMELOCK value when structures are used for Top Secret
SECFILE locking. If you use the default TIMELOCK wait
value (50 for release 5.2, 25 for release 5.3), how
many images share the structure? If you have modified
the default, how did you determine the correct value?
Are you confident that the value you use is optimum
(e.g. a lower value would be detrimental to
performance)? Do all sharing instances of Top Secret
use the same TIMELOCK value or is each assigned a
value based on the performance characteristics of the
hosting z/OS image?
Thanks,
__________________________________
Discover Yahoo!
Find restaurants, movies, travel and more fun for the weekend. Check it out!
http://discover.yahoo.com/weekend.html
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
