RE: "Serious storage condition may exist"

What's your QSTGLOWLMT set at?  Hopefully you still have a little room.

Next, see if it's memory or disk.  Do a WRKSYSSTS and check your current
unprotected storage used (on the right side, about row six).  This
number can get very big under certain circumstances.  On my machine, I
use about 4GB of unprotected storage, which is a significant percentage
of my overall disk.

The next trick is to analyze your disk space.  The quickest way I've
found is to do a DSPOBJD *ALL/*ALL OUTPUT(*OUTFILE) OUTFILE(QTEMP/OBJS).
Then you can run an SQL over that file to get some idea of which
libraries are taking up space.  Use *ALLUSR/*ALL if you want to skip IBM
supplied objects.

If after all this you still don't see the issue, check the IFS.  If
somebody is using your IFS as a repository for MP3 files (or images or
PDFs or whatever), then you could have problems there.  The easiest way
I've found to view the IFS is to map a drive to the root and then use
Windows to check the properties.  This will cause a scan of the entire
IFS and tell you the total size.  From that point, you can check the
size of individual folders to get an idea of who is hogging storage.

Joe


> From: James H H Lampert
> 
> We've suddenly started getting "serious storage" and "critical
storage"
> QSYSOPR messages on our production box, and so far, we're unable to
> determine the cause. We've got very few spool files, and very little
in
> QRPLOBJ. Any other suggestions on where to look?