RE: Oh where has my disk space gone?

Steve,

I'm going to do the RTVDSKINF tonight, but the DSPOBJD did find
the offending file (the 12G APPLOG file). Now that I know about
the DISKTASKS options, I will be using these to monitor things
going forward so I don't end up in the position I'm in now.

Rebecca

-----Original Message-----
From: midrange-l-admin@midrange.com
[mailto:midrange-l-admin@midrange.com]On Behalf Of Steve Richter
Sent: Thursday, November 15, 2001 2:11 PM
To: midrange-l@midrange.com
Subject: Re: Oh where has my disk space gone?


Rebecca,

I have changed my recomendation.

Looks like RTVDSKINF and PRTDSKINF, like jt and others say, is the way to
go.  PRTDSKINF looks like it has some options that are exactly what you
need.

Thank you for posting.  I would not have known about this otherwise.

Steve Richter


----- Original Message -----
From: "jt" <jt@ee.net>
To: <midrange-l@midrange.com>
Sent: Thursday, November 15, 2001 11:45 AM
Subject: RE: Oh where has my disk space gone?


> Rebecca, Steve
>
> It is my understanding that RTVDSKINF essentially IS a DSPOBJD *ALL...  In
> emergencies, I've run it without undue impact, during the day.  I used to
> run queries, but found the PRTDSKINF to be more informative.  Same daggone
> headers on each printout, so just skip to page 4 to see the details each
> report is showing.
>
> jt
>
>
> "Have a GREAT day...!  And a BETTER ONE TOMORROW~~~:-)" (sm)
>
>
> > -----Original Message-----
> > From: midrange-l-admin@midrange.com
> > [mailto:midrange-l-admin@midrange.com]On Behalf Of Steve Richter
> > Sent: Thursday, November 15, 2001 11:30 AM
> > To: midrange-l@midrange.com
> > Subject: Re: Oh where has my disk space gone?
> >
> >
> > Rebecca,
> >
> > To get answers now, if at all possible,  instead of waiting for
> > RTVDSKINF to
> > run later, you should run Dspobjd *all/*all *all to an outfile as
> > suggested
> > in an earlier reply.
> >
> > Use WRKQRY to create two queries, one by object size descending,
> > the other a
> > library summary with an object size total.  The guilty parties then show
> > themselves:  too many objects in qrplobj ( need to ipl ), library
> > qspl has a
> > lot of space used ( too many spooled files, need to rplsplstg ),
> > save files
> > have not been cleared ( need to get tough and break some arms ), ....
> >
> > Dspobjd may run for a while ( 30 minutes ). You should run it in batch
as
> > qsecofr. Also the outfile might reach its default capacity.  I get
around
> > that by running DSPOBJD to an outfile on a single object.  Call
> > the outfile
> > "qgpl/dspobjd". After running the dspobjd on the single object, CHGPF
> > QGPL/DSPOBJD Size(*NoMax).
> >
> > Good luck,
> >
> > Steve Richter
> >
> > ----- Original Message -----
> > From: "Rebecca Snyder" <rsnyder@atlasdie.com>
> > To: <midrange-l@midrange.com>
> > Sent: Thursday, November 15, 2001 10:38 AM
> > Subject: RE: Oh where has my disk space gone?
> >
> >
> > > Thanks everyone for all the suggestions. I've set RTVDSKINF to
> > > run tonight at 8pm. I've never run it before so I won't have
> > > anything to compare it to, but maybe something will stick out.
> > >
> > > We only save 4 days of performance data, which when I deleted
> > > 3 days worth it got me .1% of space back.
> > >
> > > We do run cleanup and keep the following:
> > >
> > > Number of days to keep:
> > >   User messages . . . . . . . . . . . . . . . . .   15
1-366,
> > > *KEEP
> > >   System and workstation messages . . . . . . . .   15
1-366,
> > > *KEEP
> > >   Job logs and other system output  . . . . . . .   30
1-366,
> > > *KEEP
> > >   System journals and system logs . . . . . . . .   30
1-366,
> > > *KEEP
> > >   OfficeVision for AS/400 calendar items  . . . .   0
1-366,
> > > *KEEP
> > >        (we don't use office vision)
> > >
> > > Are we saving too much? What do you suggest for these options?
> > >
> > > We also do a monthly IPL. In fact we just did one this Saturday.
> > > I've never run RCLRSC or RCLSTG for that matter. We've had our
> > > AS/400 (iSeries) since June 1999, and this is our first one.
> > > We only use Mapics for our carbon paper business. Our steel rule
> > > die business still runs our home-grown system on our VAX. Our
> > > computer room did not implode when we put an AS/400 next to our
> > > VAX!! I'm planning on doing a RCLSTG on some weekend in December.
> > > Would it be better to do RCLRSC or RCLSTG? Or maybe both?
> > >
> > > So needless to say I was kind of thrown on the thing without any
> > > training (except in mapics) and everything I've learned over the
> > > past 2 1/2 years has been out of necessity or from reading
> > > the messages posted here. I did manage to get copies of "Control
> > > Language Programming for the AS/400" and "Mastering the AS/400",
> > > both which has been very helpful although I haven't had the time
> > > to read through either of them. I've just picked out what I've
> > > needed at the time I needed it. One of these days I'm going to
> > > see if one of our local colleges has classes that I can take
> > > after hours...
> > >
> > > I'll stop rambling now & thanks again for all the help!
> > >
> > > Rebecca Snyder
> > >
> > >
> > > > -----Original Message-----
> > > > From: Rebecca Snyder [SMTP:rsnyder@atlasdie.com]
> > > > Sent: Thursday, November 15, 2001 4:16 PM
> > > > To: midrange-l@midrange.com
> > > > Subject: Oh where has my disk space gone?
> > > >
> > > > In the past 2 months my disk space has gone from
> > > > 45% used to 75% used... and I've got 50G of space!
> > > >
> > > > How can I tell what's using up my disk space? Because
> > > > we couldn't possibly be selling that much carbon paper!
> > > >
> > > >
> > > > Rebecca Snyder
> > > > Atlas Companies, Inc
> > > > 219-295-0050 ext 242
> > > > mailto:rsnyder@atlasdie.com
> > > >
> > > > _______________________________________________
> > > > This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
> > > > list
> > > > To post a message email: MIDRANGE-L@midrange.com
> > > > To subscribe, unsubscribe, or change list options,
> > > > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > > > or email: MIDRANGE-L-request@midrange.com
> > > > Before posting, please take a moment to review the archives
> > > > at http://archive.midrange.com/midrange-l.
> > > >
> > > >
> > >
> > > ---------------------------------------------------------
> > >
> > > "The content of this e-mail message and all attachments thereto ("this
> > > message") does not necessarily reflect the views of Fraser
> > Alexander Group
> > > of Companies (FAGC). Before acting on the contents thereof, the
> > recipient
> > > should verify that the originator has the appropriate delegated
> > authority.
> > > In the event that this message has not been appropriately authorised
in
> > > terms of FAGC delegation of authority, or in the event of the personal
> > usage
> > > of FAGC 's e-mail facility, FAGC will not be liable for the contents
of
> > the
> > > message.
> > >
> > > _______________________________________________
> > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> > list
> > > To post a message email: MIDRANGE-L@midrange.com
> > > To subscribe, unsubscribe, or change list options,
> > > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > > or email: MIDRANGE-L-request@midrange.com
> > > 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@midrange.com
> > > To subscribe, unsubscribe, or change list options,
> > > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > > or email: MIDRANGE-L-request@midrange.com
> > > 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@midrange.com
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > or email: MIDRANGE-L-request@midrange.com
> > 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@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> 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@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.