RE: "Serious storage condition may exist"

[pnelson@xxxxxxxxxx]

Nada


Paul Nelson
Arbor Solutions, Inc.
708-670-6978  Cell
pnelson@xxxxxxxxxx





rob@xxxxxxxxx
Sent by: midrange-l-bounces@xxxxxxxxxxxx
11/11/2004 04:08 PM
Please respond to Midrange Systems Technical Discussion
 
        To:     Midrange Systems Technical Discussion 
<midrange-l@xxxxxxxxxxxx>
        cc: 
        Subject:        RE: "Serious storage condition may exist"


>From the joblog:

Message id
>From program
To program

Then search for the message at
http://www-912.ibm.com/a_dir/as4ptf.nsf/as4ptfhome
Maybe that will list the ptf you are missing.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





pnelson@xxxxxxxxxx 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
11/11/2004 04:10 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
cc

Fax to

Subject
RE: "Serious storage condition may exist"






On a V5R2 machine, I did a rtvdskinf, and when I do the prtdskinf, I get a 


message stating "Receiver value too small". What gives? I'm up to the 
April cumulative PTF.


Paul Nelson
Arbor Solutions, Inc.
708-670-6978  Cell
pnelson@xxxxxxxxxx





rob@xxxxxxxxx
Sent by: midrange-l-bounces@xxxxxxxxxxxx
11/11/2004 02:57 PM
Please respond to Midrange Systems Technical Discussion
 
        To:     Midrange Systems Technical Discussion 
<midrange-l@xxxxxxxxxxxx>
        cc: 
        Subject:        RE: "Serious storage condition may exist"


RTVDSKINF / PRTDSKINF beats DSPOBJD...
On our i5-570's (with 3TB of disk) largest partition only 9% of our data 
is in "User Libraries".  Therefore the DSPOBJD would do jack for us.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
11/11/2004 12:08 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc

Fax to

Subject
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?

--
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.


--
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.


--
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.


--
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.