We would need to see the entire map: Nucleus, SQA, xLPA, and CSA along with the size specifications for SQA and CSA and the IPL syslog to see if there were any overflow messages for both production and DR to begin to determine where the storage went.
Dennis Roach, CISSP, PMP IAM Access Administration – Consumer – Senior Analyst 2929 Allen Parkway, America Building, 3rd Floor, Houston, TX 77019 Work: 713-831-8799 Cell: 713-591-1059 Email: [email protected] All opinions expressed by me are mine and may not agree with my employer or any person, company, or thing, living or dead, on or near this or any other planet, moon, asteroid, or other spatial object, natural or manufactured, since the beginning of time. -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of phil yogendran Sent: Thursday, May 05, 2016 3:12 PM To: [email protected] Subject: Re: CSA Shrank in DR I did think it was a bigger IODF but in my case SQA in DR has gone down implying a smaller IODF. However, CSA has also gone down. Here's some inform from DR and Prod; DR: SQA 988K CSA 3.43M Prod: SQA 1.11M CSA 4.28M On Thu, May 5, 2016 at 3:25 PM, Bob Rutledge <[email protected]> wrote: > On 5/5/2016 3:07 PM, phil yogendran wrote: > >> Hello, >> >> We recently performed a DR exercise and on one of the LPAR's, the CSA >> was smaller by about 800k. Parmlib specification in DR and production >> were identical. The LPAR affected is our designated 'network' box so >> there are no apps or subsystems like CICS or IMS running on it. >> >> Any thoughts on what could make CSA shrink at IPL, particularly when >> parmlib was not changed? The IODF in DR would have been different but >> I can't see that affecting CSA. >> > > If your production CSA size is considerably larger than the > specification in parmlib, the DR IODF could be scarfing more SQA which > would affect the size of CSA. > > Bob > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
