|
A piercing glance at the obvious - I've been at a company where we desperately needed to RCLSTG, but it was very difficult to justify the time. Of course, you CAN do it in stages, right? It starts up where it left off, I believe, if interrupted. At 09:31 AM 3/21/02 -0500, you wrote: >Al, > > This file can not be reorged by regular means because it is always >locked by QDBSRVXR or QDBSRVXR2. The only way to clean up the deleted >records is to do a RCLSTG. You can either do a full RCLSTG, or just >reorg the Database Xref files. If you run this, it will reorg all the >QABD* files, which is what you want. This file tends to get huge on >test/development systems where you are creating/deleting, restoring, >files onto your system. There is also a program in QSYS called >QDBRCLXR which will also reorg the QADB files. In any case, you Must be >in a restricted state to do the reorgs on these QADB files. > > We recommend that people do a RCLSTG at least once a year, and >preferably every 6 months, but that comment will probably create as many >replies as which religion is better :) > > Pete Massiello > >MacWheel99@aol.com wrote: > >>This has probably come up before & possibly even I brought it up. >>Seems to me there are objects in QSYS like this one that manage to amass a >>large number of deleted records of significant size. >> >>What I desire is >> >>1. Some IBM menu option that I ought to run periodically to clean up these >>QSYS objects, like I have in my application management to clean up >>application objects. It would be even better if GO CLEANUP or WRKSYSVAL >>could set some standard for cleaning them up regularly. >> >>2. Reminder what the heck this is for ... is there some way to adjust values >>of what it includes ... I am having trouble believing that any object needs >>to be that large ... to make it smaller, is that an application design issue? >> >>Our QADBIFLD in QSYS is currently >>188,890 good records >>22,407 deleted records >>record length 4,876 >>meaning 110 meg bytes wasted by deleted records >>and 1 gig bytes total size of the file >>Am I estimating that math right? >>Our entire 400 is only 12 gig >> >>MacWheel99@aol.com (Alister Wm Macintyre) (Al Mac) >>_______________________________________________ >>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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
