I have to do this for all compilers from V3 through V6 Oh the joy of compiler debugging
Lizette > -----Original Message----- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of > Alan Young > Sent: Sunday, January 27, 2019 1:08 PM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: Cobol Working Storage size in Dump > > You did not specify which compiler version or if the dump is from batch or > CICS, but... This link is CICS orientated and was published in 2009, so it > may not apply to the "newer" compilers: > http://www-01.ibm.com/support/docview.wss?uid=swg27017236 . I think the key > in either environment is to find the LE CAA. If the LE CAA is in the dump, > slide 8 has the pointer links to the COBOL TGT and the offset to WS length. > > Alan > > Lizette Koehler wrote: > > Yep, another question > > > > Is there a way in a SVC Dump or SYSUDUMP to determine the size of the > working > > storage section? > > > > My original issue looks to be caused by two things, > > > > 1) The working storage size increased > > 2) There is one 24bit module linked with all the 31bit modules, > thereby > > forcing it below the line > > > > Any guidance appreciated > > > > > > > > Lizette Koehler > > statistics: A precise and logical method for stating a half-truth > inaccurately > > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
