Problem solve Get help with specific problems with your technologies, process and projects.

What savings can be expected from CICS V4 temp storage tuning changes?

I'm trying get management to support making some CICS V4 temp storage tuning changes. To a couple of us these are...

no-brainers, but where we're having difficulty is to be able to say what savings can we expect to see as the result of these tuning changes. Our non-production regions don't have enough activity to really get any figures to publish. Here's one example of a heavily used CICS V4 region........what we see today.......and what I plan to do:

Note I'm getting the stats from Omegamon CICS:

Please don't chuckle!

CIMACPR7 is the region.
4K CI for temp storage
PUTs > CI size . . . . : 125444
TSGID extensions = 53,477
Unit table compressions = 1,123,098
Total Q's created = 1,666,984
Items in Q (HWM) 29,487
Longest aux item = 32,787
Temp storage buffers/strings are 64,4

What I plan to do:
TSGID=100 (to start)
Temp storage CISIZE 8K to start then
evaluate (also increase the size of the temp storage dataset by 1/3).
Buffers/strings increase to 100,50 and evaluate.

Can you give me any ammunition?

Based on what I have read and seen in test regions, I am going to possibly decrease DSA utilization, increase thruput, and possibly decrease transaction response time for transactions that use temp storage (and possibly on other transactions too). Can I expect to see any cpu savings? Any negative impact to be expected? What do you think........If I make the changes as specified, I can't think of any.

Your opinion and recommendation is appreciated. We've got about 10 CICS V4 regions in this same condition and with similar volume, so I really feel we have an opportunity to effect some savings here.

I am afraid I cannot quantify what any gains might be. The only thing I can say is that the given the current Temporary Storage statistics, the proposed changes are in-line with tuning recommendations. I cannot really see that it would have any negative impact unless you are already severely storage constrained.

This was last published in February 2002

Dig Deeper on IBM system z and mainframe systems

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.