Mike, if your application is not very well behaved when it comes to allocating working storage, I have had occasion in the past to override the default LE runtime parameters. The programs I was working with needed large (and hugely variable in size) amounts of working storage. Despite REGION=0M, eventually, after the programs ran to near-completion, they'd die on abend S878 trying to close some files. The default small values used by LE for working storage allocation caused all available storage below the 16m-line to be used up. The following LE-runtime parm prevented that: HEAP(...) because it forced working storage to be allocated above the line first. e.g.: PARM='/RPTSTG(ON),RPTOPTS(ON),HEAP(16M,1M)' If you also use the RPTSTG and RPTOPTS options, you'll get some info written to //SYSOUT DD about LE options in effect and storage use. Please see the LE manuals for more details. I hope that'll help solve your problem.
Regards, Ulrich Krueger Mainframe Systems Services National Semiconductor Corp. Santa Clara, CA 95051 Tel: (408) 721-8071 Email: [EMAIL PROTECTED] "IBM Mainframe Discussion List" <[email protected]> wrote on 06/28/2006 12:53:10 AM: > >The virtual 8304K looks suspicious. normally that means some 24bit code > >because there isn't as much usage of EXT (above the line private). > > But all my modules are AMODE=31 RMODE=ANY..... > > Maybe something I could force using LE parameters on the JCL PARM- > Statement?!?!? > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
