Hello Lizette,
To summarize what we have already discussed in the open case we are working together it is normal to be impacted by an increase of storage after an upgrade to release 12.3 and it is caused mainly for the expansion of the OPMO Control Block. I have recently added in the Introduction section of the KD TEC1037203 most of our clients have already looked at, what is the delta in bytes for the Control Block in question.
This is a direct URL to the KD:
http://www.ca.com/us/services-support/ca-support/ca-support-online/knowledge-base-articles.tec1037203.html
A tool to help estimate an appropriate REGION= size based on current storage impacting related parameters for the OPSMAIN region will be the use of the OPSVIEW option 4.1.6 'CA OPS/MVS Storage Simulator'.
Recommendation will be that for starters you should use REGION=256M as the smallest size for a OPSMAIN region.
This is a list of what we currently shipped our sample PROCs at this time:
CCLXCNTL(OPSMAIN) => REGION=4M
CCLXCNTL(OPSOSF) => REGION=4M
CCLXCNTL(OPSECF) => REGION=4M
CCLXCNTL(OPSUSS) => REGION=0M
CCLXCNTL(OPSLOGSV) => REGION=0M
CCLXCNTL(OPSWS) => REGION=0M
CCLXCNTL(OPSOFSRV) => No REGION= coded
CCLXCNTL(ARCHPROC) => No REGION= coded
Hope this helps start a discussion with the rest of the Community and how you would like to have this documented in our online product manuals in addition of what we have already out there.
Thanks Lizette for starting this discussion today.
Regards,Cesar