|
>From: Leif Svalgaard [mailto:leif@leif.org] >It is not clear that that will run any faster than RCLDLO *ALL. In total time from start to finish I'd almost guarantee that it would run slower. However, I would have more control over how/when it ran. I could run it for x number of docs and then stop, or x minutes of time, etc. My concern with RCLDLO is I have to start it and hope it ends some day. -Walden ------------ Walden H Leverich III President Tech Software (516) 627-3800 x11 (208) 692-3308 eFax WaldenL@TechSoftInc.com http://www.TechSoftInc.com Quiquid latine dictum sit altum viditur. (Whatever is said in Latin seems profound.) -----Original Message----- From: Leif Svalgaard [mailto:leif@leif.org] Sent: Monday, June 03, 2002 12:05 To: mi400@midrange.com Subject: Re: [MI400] QDLS/QDOC internals From: Walden H. Leverich <WaldenL@TechSoftInc.com> > Does anyone have/know of documentation on the internal structure of > *FLR and > *DOC objects? We have a client with > 1 million (yes million) doc and folder > objects in QDOC. A number of these objects are orphaned and we are > trying to > clean up the library w/o doing a RCLDLO *ALL since that will take > *FOREVER. If you knew the structure, you would have to write a program that checks for orphans (i.e. does what RCLDLLO does). It is not clear that that will run any faster than RCLDLO *ALL. _______________________________________________ This is the MI Programming on the AS400 / iSeries (MI400) mailing list To post a message email: MI400@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/mi400 or email: MI400-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/mi400.
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.