Re: 'Serious storage condition may exist'

RTVMBRD FILE(X) NBRCURRCD(&CURRENT) NBRDLTRCD(&DELETED)
RTVOBJD OBJ(X) SIZE(&SIZE)
jim
----- Original Message ----- 
From: "James H H Lampert" <jamesl@xxxxxxxxxxx>
To: <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, November 11, 2004 2:46 PM
Subject: Re: 'Serious storage condition may exist'


> > What is your percentage of storage used from DSPSYSSTS, and what is the
> > system value QSTGLOWLMT.  You may be forced to clean up stuff, or
> > execute the SPENDMONEY command.
>
> Wouldn't that be "SPDMNY"?
>
> I found the 3,700,000,000-lb gorilla. It seems that a diagnostic logging
> function was left enabled, and nobody had bothered to clear out the log
> file therefrom had been allowed to grow to over 3GB (out of a 16GB system
> ASP) without being CLRPFMed.
>
> We're back down to a nice, healthy 67+%
>
> Thanks to all who came up with suggestions.
>
> Just out of curiosity (and I haven't bothered to RTFM about it yet), is
> there a quick and easy way to retrieve the size in bytes of a physical
> file in a CL program? I'm getting this idea of checking the aforementioned
> log file automatically whenever the associated server is started, and
> issuing a QSYSOPR message if it's grown beyond a certain threshold.
>
> --
> JHHL
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>