Insufficient storage when starting region in CICS

We are running under CICS TS V3.1. Yesterday we received an error message indicating the region could not start as there was insufficient storage below the 16M line. We had to back out a product to get the region to start. Most of our CICS regions have DSALIM between 6-8M. I don't want to allocate a lot more, as I think it takes the storage from the area above the 16M line. Do you have a rule of thumb?

Answer Wiki

Thanks. We'll let you know when a new response is added.

Unfortunately, I don’t have a rule of thumb. Figuring out the amount of below-the-line DSA has always been a tricky balancing act between CICS and operating system requirements, which is usually established by trial and error.

I would not increase DSALIM unless you think there will be enough storage left over for the operating system. If there isn’t, you’ll put yourself in the position of getting 80A and 40D ABENDs.

You can establish if you have any room to increase DSALIM by watching the available storage between the top of DSA and the bottom of system storage. If you leave your CICS regions up for days, you’ll have to monitor that area for fragmentation. If, after your monitoring, you think you have some cushion you can increase your DSA to take up the slack. Otherwise you may have to follow the classic CICS solution of growing horizontally.

Also, do not specify REGION=0M on the CICS job step. While coding the REGION parameter in this way assures the application has access to every byte of private storage below the line, it does not leave anything for the operating system. Again, you will be vulnerable to 80As and 40Ds.

By the way, increasing the DSA below the line shouldn’t impact EDSA above it. The two are separated by system control blocks, the MVS nucleus and Link Pack Area (LPA) modules.

Discuss This Question: 1  Reply

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Mahmoudcbk
    Hello We have CICS/TS 1.1.1 with operating system VSE/ESA 2.6.0 and we get leaking in GETVIS storage below 16MB over working day. What i did to solve this problem, that only i change and rearrange the files location for LSRPOOL=0 that is location below 16MB to LSRPOOL=1 and LSRPOOL=2 that are over 16MB. As i observe the leaking of storage is stopped. May be this solution will solve your problem. Another solution, i suggest, is to remove any product that is not using from the online production LIBDEF search chain to more GETVIS storagre below 16MB. regards Mahmoud Ashkanani System Specialist Central Bank of Kuwait
    10 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: