Mark Pace wrote: >>I have an SE that has job running out of memory. The error message says that he ran out of storage at 1792MB.
and >>There is not a dump. The program ends nicely with an error message, not an IBM message, that it is out of memory. >>It's batch utility to massage SMF data and was not written inhouse. The SE is talking with them now. There suggestion was to process less data. :-D Why not selecting shorter intervals of SMF data? Or process one LPAR at a stage? Or try massage the SMF data in two stages using work datasets as temporary storage? Peter Relson wrote: >In my opinion, the odds are that this program has an error and it is running out of memory because of that error. Even if you were to increase the region size, it would still run out of memory. Of course. Since it ends 'nicely with an error message'. >And then if it truly is not an error and truly needs this much memory, the program needs to be re-written to use data spaces or above-2G storage. Or use disk/tape as storage. To Mark: I am suspecting that the program may needs to be re-assembled to pickup the correct SMF record layout. Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- 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
