All, I understand why RSVNONR is in a "bit of a fix" <g> in our shop and we're trying to address the problem by getting the problem tasks to shutdown -cleanly- but aren't having much luck so I thought I'd run it up the flag pole (so to speak) and see if any of you have found a solution or might suggest one.
The -offending- address spaces are -all- DB2 regions that get cycled on a regular basis (I still need to talk to the DBA to see why). We've got Landmark and BMC as well as CICS that -touch- DB2 and we've tryed shutting them down in about everyway possible but the IEF352I message won't go away and of course the used RSVNONR keeps increasing with every shutdown and startup of DB2. It's been 2.5 months since an IPL and we plan on increasing RSVNONR from 99 to 2xx but it just urks me to think we might -have- to have planned IPL's over something this silly. Has anyone found a way around it or do you all just plan an IPL on some scheduled basis and call it a day? Bill Mainframe - An obsolete device still used by thousands of obsolete companies, serving billions of obsolete customers, and making huge obsolete profits, for their obsolete shareholders. And this year's run twice fast as last year's. -Phil Payne- ---------------------------------------------------------------------- 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
