Re: The dreaded system full, now what.

Jack

Once the dust settles, do take a long hard look at a tool called DASD Plus - Alert from s4i - it used to be called disk/HUNTER and was bought, I think, from a former employer of mine - I wrote much of it, actually. It is a realtime monitor of disk usage and can warn you far ahead of this kind of disaster - of course, with the speed of things these days, maybe nothing can help! www.s4isystems.com is the link, and I have nothing to do with the company, I just know this has helped a number of people in the past.

HTH
Vern

Jack Kingsley wrote:

I understand that part fine, based on my problem I didn't have all day to
figure out it, now with this information I am sure that I can, thanks.

On Mon, Feb 8, 2010 at 1:40 PM, <rob@xxxxxxxxx> wrote:

I guess prompt the command and read the help is hard for some to
understand but when I type in RTVDSKINF and hit F4 to prompt and then hit
F1 for help I see stuff like
Each time this command is run, existing information in QCURRENT is
written over. To save existing information in member QCURRENT,
rename file QAEZDISK or QAEZDnnnnn, or copy the member to another
file.

So I suppose I could do this:
WRKOBJ QAEZDISK
Object Type Library
QAEZDISK *FILE QSYS
QAEZDISK *FILE QUSRSYS
The one in QSYS is just the template for the one in QUSRSYS. So I could
do this:
CRTDUPOBJ OBJ(QAEZDISK)
FROMLIB(QUSRSYS)
OBJTYPE(*FILE)
TOLIB(MYLIB)
DATA(*YES)
Then I could run comparisons from that if I wanted to.


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





From: Jack Kingsley <iseriesflorida@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 02/08/2010 10:04 AM
Subject: Re: The dreaded system full, now what.
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Rob, here is the drawback, unless you have examined the current one and
somewhat know what is going on the new one will overlay the previous data
and your back at square one in figuring it out.

On Mon, Feb 8, 2010 at 9:45 AM, <rob@xxxxxxxxx> wrote:

"quickly" is they key word. RTVDSKINF is your answer (as you figured)

but

it's not quick. If you read the help on RTVDSKINF it tells you what

files

it creates and how to retain that data to do comparisons.


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





From: Jack Kingsley <iseriesflorida@xxxxxxxxx>
To: Midrange Systems Technical Discussion <MIDRANGE-L@xxxxxxxxxxxx>
Date: 02/08/2010 09:10 AM
Subject: The dreaded system full, now what.
Sent by: midrange-l-bounces@xxxxxxxxxxxx



I recently had a system that had filled up it's disk storage due to a

run

away job and an errant qsysprt printer file set to nomax on records, the
system was basically locked up. Does anyone have specific instructions

on

what they do when a problem such as this comes about. I did a normal

IPL

and did not know what I had at the time until the IPL had completed and

I

was able to gain access to a signon screen. Once signed on I did a

quick

wrksyssts and could see what was going on. At that time I ended all
subsystems to get the box in a restricted state in order to diagnose

what

was going on. I happened to stumble on the spooled file that had the
dreaded +++++ for pages. Once I deleted the spooled file the disk

storage

went down, but then I get bit by the qrclsplstg system value being set

to

*NONE, this caused a massive locking problem on members in QSPL library
and
jobs that could not then run due to qpjoblog locks. If I had not

stumbled

on the spooled file I am not sure how long it would have taken me to
figure
out the(where has mydisk space gone) situation. I don't believe there

is

a
command to quickly diagnose previous rtvdskinf(s) either and or a

command

to
show which reports take up the most disk storage(not at least quckly )
anyways.
--
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.