Posted: Thu Jan 23, 2020 3:21 pm Post subject: Large'ish Working Storage and SOS issues
Firstly- I did post this in "another" forum too, so I hope I'm not flouting some regulations!
Hi all- I have been doing CICS programming for many years and believe it or not heard this term SOS for the first time today. I guess I have been lucky.
Anyway we were performance testing a CICS web service and the region just became unresponsive and had to be recycled. And the CICS admin said it was an SOS issue.
The program had performed well in the prior environments.
I was just wondering if it could be because the program underpinning the web service has a large-ish WS, just over 2.5MB. I say it is large because I looked a a number of our existing regular CICS transactions and none come even close.
The stress testing team were simulating a scenario with 25 active users submitting enough requests to mimic a peak production load of about 40K requests an hour- would it have caused this SOS scenario?
FWW we're on CICS 3.2 and the region under consideration has 130MB in 31bit storage
Joined: 26 Nov 2002 Posts: 12376 Topics: 75 Location: San Jose
Posted: Thu Jan 23, 2020 9:44 pm Post subject:
sumithar,
I usually don't honor cross posting, however since you came clean about it, I will let it go.
My CICS knowledge is rusty, so here are my thoughts
1. What is the AMODE of the offending transaction ? 24 ?
2. If the AMODE is not 24 , then did your program compile with Data(31). DATA(31) is a compile option, which specifies that working-storage will be acquired above the line. If your program amode is 24 then even if you had Data(31), it would be ignored under CICS
Joined: 01 Feb 2007 Posts: 1075 Topics: 7 Location: At Home
Posted: Fri Jan 24, 2020 7:51 am Post subject:
It's OK about the cross-posting in this case as the original was a week ago and with no responses. _________________ Utility and Program control cards are NOT, repeat NOT, JCL.
I usually don't honor cross posting, however since you came clean about it, I will let it go.
My CICS knowledge is rusty, so here are my thoughts
1. What is the AMODE of the offending transaction ? 24 ?
2. If the AMODE is not 24 , then did your program compile with Data(31). DATA(31) is a compile option, which specifies that working-storage will be acquired above the line. If your program amode is 24 then even if you had Data(31), it would be ignored under CICS
Hi Kolusu,
Thanks for the response.
It's AMODE(31)
It's compiled with DATA(31)
I had downloaded that presentation and have been making my way thru it.
But the update at this point is that the CICS Admin increased the EDSALIM from 130 to 640M and on DFHSIP changed the value to REGION=0K from REGION=200M.
After these two changes, we didn't encounter any SOS issues.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
FAQ
Search
Quick Manuals
Register
Profile
Log in to check your private messages
Log in
