Yeah, it might be a good idea to do a Q RECORDING before any drastic action is taken. Either that or ask the operator if the system has been flooding the console with records accumulating messages. A RECORDING ALL OFF PURGE followed by restarting the recording machines might be what is needed. And if that is it, investigate what is happening in the one or more recorders that is causing the build-up.
We recently had a situation wherein a new device was causing EREP to fill memory. I had to shut EREP down because of the volume of messages going to OPERATOR's console until the device was fixed. The RECORDING limit, which only governs the number of records that will cause a message to be sent to OPERATOR and is not a limit to the number of records that can accumulate, hit well before we ran out of storage, but we were headed in that direction. Regards, Richard Schuh > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:ib...@listserv.uark.edu] On Behalf Of Rob van der Heij > Sent: Wednesday, December 16, 2009 12:54 PM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: System Free Storage > > On Wed, Dec 16, 2009 at 7:57 PM, Bill Holder > <hold...@us.ibm.com> wrote: > > Correct, though redefining virtual machine storage to a > different size > > performs a reset clear function on the virtual machine, which could > > well help clear up the problem. > > Just wagging, but the fair share before CP gets annoyed was > calculated as a part of available storage. If the available > storage gets very low, even fairly normal usage is considered > outrageous by CP. The case that I had was where pending > account or EREP records were filling up available memory and > CP even felt that OPERATOR doing an IPL CMS was enough to > kick him off... > > This was in the old days, so I don't know what all resides in > CP free storage address space. > > Rob >
