|
First try RCLDLO? V3R2 is a bit back but I think you should stop using the QDOC library, aka as the QDLS directory, aka WRKFLR. See WRKLNK OBJ('/*') If you see QDLS under there then you can probably not use that. :-). Don't remember when NetServer came along as a way of accessing shares on the 400 versus being limited to Client Access and shared folder support. Every 8 weeks we do RCLDLO DLO(*ALL) run it once like that, and maybe run it again with any particular options pointed out to you in the joblogs you saw where you had damaged objects in QDOC. RGZDLO DLO(*ALL) FLR(*ANY) MAIL(*YES) RCLSTG Can't hurt. What the heck. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com daparnin@xxxxxxxxxxxxxxxxxx Sent by: midrange-l-bounces@xxxxxxxxxxxx 11/08/2004 04:35 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To midrange-l@xxxxxxxxxxxx cc Fax to Subject Damaged QDOC objects The other day my home system crashed after a power outage. Now I've got some damaged objects in the QDOC library. From what I've read at the Infocenter these seem to pertain to DLO objects. I haven't done much with the system lately can I simply restore them from the last backup or could it contain system objects that can't be directly restored? I'm at V3R2. Thanks. Dave Parnin Nishikawa Standard Company Topeka, IN 46571 daparnin@xxxxxxxxxxxxxxxxxx -- 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.
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.