Re: Large Objects created on AS400 consuming huge disk space

[Luis Rodriguez <luisro58@xxxxxxxxx>]

Rob,

You are right, of course. As I explained before, I did wrongly assume that
you were referring only to QSYS. Don't know why I fell into that mistake, as
trying to explain to my coworkers about why the IBM i is more than RPG is
one of my hobbies (and I do work a lot with stream files).

That said, my only excuse was that yesterday was a very complicated day
(aren't they all? ) and my English wasn't up to the task.

My apologies for the confusion...

Regards,

Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries


On Tue, Feb 2, 2010 at 9:33 AM, <rob@xxxxxxxxx> wrote:

> QUALITY is not a "library" it is a directory on my i.  QSYS.LIB is both a
> library and a directory.  Do this
>
> WRKLNK '/*'
>
> See all that stuff?  Now, if you scroll down to /QSYS.LIB the contents of
> that is everything you see in the library QSYS on your system.  So, yes,
> it's technically feasible to do
> WRKLNK '/QSYS.LIB/MYLIB.LIB/MYFILE.FILE/MYMBR.MBR'
> It's called the "Integrated File System" or IFS for short.  EVERYTHING is
> in the IFS.  Some people refer to only stuff outside of /QSYS.LIB as the
> IFS.  I prefer to lump all that into "stream files".  Why that?  Well, if
> you look into something other than /QSYS.LIB with WRKLNK you will see they
> are "generally" either STMF for stream files, or DIR for directories.
>
> So in summary, DSPOBJD is limited to just the stuff you see in
> WRKLNK '/QSYS.LIB/*'
> There's a whole world outside of your neighborhood block.
>
> Hence:  This is not an AS/400, this is a system i.
>
>
> Rob Berendt
> --
> Group Dekko Services, LLC
> Dept 01.073
> Dock 108
> 6928N 400E
> Kendallville, IN 46755
> http://www.dekko.com
>
>
>
>
>
> From:   Luis Rodriguez <luisro58@xxxxxxxxx>
> To:     Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> Date:   02/01/2010 04:31 PM
>  Subject:        Re: Large Objects created on AS400 consuming huge disk
> space
> Sent by:        midrange-l-bounces@xxxxxxxxxxxx
>
>
>
> Rob,
>
> Although I agree with your point of view about RTVDSKINF, I'm a little
> mystified regarding your statement about DSPOBJD getting only QSYS.LIB.
> Would you like  to clarify? Also, I see in your list a library called
> "QUALITY". Is that a system lib?
>
> Regards,
>
> Luis Rodriguez
> IBM Certified Systems Expert — eServer i5 iSeries
>
>
> On Mon, Feb 1, 2010 at 3:02 PM, <rob@xxxxxxxxx> wrote:
>
> > This is no longer an AS/400.  This is a system i.  Continuing to use old
> > methods like that will not show you what's been consumed by stream
> files,
> > temporary space and other stuff outside of the /QSYS.LIB file system.
> > Use RTVDSKINF and PRTDSKINF *SYS.
> > On my system using DSPOBJD would be ignoring 1.2TB of stuff consumed by
> > other stuff.  If 1.2TB is insignificant to you then, by all means,
> > continue to use DSPOBJD.
> > If you did a "directory" on your PC would you feel that just adding up
> the
> > size of one directory show you how much stuff is used on your system?
> > After all DSPOBJD only adds up one directory out of 96 on my system.
> > Sample:
> > Object link
> > ...
> > QFPNWSSTG
> > QIBM
> > QNTC
> > QOpenSys
> > QOPT
> > QPWXCGA
> > QPWXCGY
> > QPWXCPC
> > QPWXCRB
> > QPWXCSO
> > QPWXCWN
> > QReclaim
> > QSR
> > QSYS.LIB
> > QTCPTMM
> > QUALITY
> > ...
> > And DSPOBJD only gets QSYS.LIB.
> > I've freed up workfiles outside of /QSYS.LIB that's freed up over 30% of
> > my disk used.  I know of another company that cleared up 18% easily with
> > that same workfile directory.
> >
> > Rob Berendt
> > --
> > Group Dekko Services, LLC
> > Dept 01.073
> > Dock 108
> > 6928N 400E
> > Kendallville, IN 46755
> > http://www.dekko.com
> >
> >
> >
> >
> >
> > From:   "Dave Snyder" <DSnyder@xxxxxxxx>
> > To:     Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> > Date:   02/01/2010 01:55 PM
> > Subject:        Re: Large Objects created on AS400 consuming huge disk
> >  space
> > Sent by:        midrange-l-bounces@xxxxxxxxxxxx
> >
> >
> >
> > I use the following command weekly:
> >
> > DSPOBJD    OBJ(*ALL/*ALL) OBJTYPE(*ALL) +
> >             OUTPUT(*OUTFILE) OUTFILE(QTEMP/OBJECTS)
> >
> > Then create a query to read in the QTEMP/OBJECTS file and sort by size.
> > That will at least tell you which ones are large and when they were
> > created/updated.
> >
> > Dave
> >
> > From:
> > sneha verma <snehaverma001@xxxxxxxxxxxxxx>
> > To:
> > midrange-l@xxxxxxxxxxxx
> > Date:
> > 02/01/2010 12:13 PM
> > Subject:
> > Large Objects created on AS400 consuming huge disk space
> > Sent by:
> > midrange-l-bounces@xxxxxxxxxxxx
> >
> >
> >
> > Hi,
> >
> > I am on V5R4.I have seen a substatntial increase in the DASD since last
> 4
> > days almost 4%.
> >
> > There are no Object Management tools installed (eg OS Director) thru
> which
> > I
> > can actually find about the big files/libs created in the last 4 days
> and
> > chase the user.
> >
> > Is there a way on AS400(thru AS400 commands) thru which I can find about
> > the
> > big files and objects created in the last 4 days.
> >
> > Regards
> > Sneha
> >
> >
> >
> > NOTICE - This e-mail message is intended only for use by the
> addressee(s)
> > named herein and may contain legally privileged and/or confidential
> > information. If you are not the intended recipient of this message, you
> > are hereby notified that any dissemination, distribution or copying of
> > this message is strictly prohibited. If you have received this message
> in
> > error, please notify the sender by e-mail or telephone and delete the
> > original and all copies of this message immediately.
> >
> > www.ephratanationalbank.com
> > --
> > 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.