|
If all the files are set to *IMMED, then you shouldn't have to open them. Copying the data into the physical file using *REPLACE should invalidate all indexes then rebuild them when the copy completes. If you have to open them before they rebuild then they aren't set to *IMMED or you are doing something else clever that is preventing the ordinary stuff from working. Based on my V4R3 manuals, MAINT appears to be a file attribute for PF and LF, not a member attribute. If you must rebuild access paths, look at the FRCRBDAP parameter on CHGLF. Instead of thrashing around, figure out why it doesn't work the way you want then fix it. Richard Jackson mailto:richardjackson@richardjackson.net http://www.richardjacksonltd.com Voice: 1 (303) 808-8058 Fax: 1 (303) 663-4325 -----Original Message----- From: owner-midrange-l@midrange.com [mailto:owner-midrange-l@midrange.com]On Behalf Of Mike Naughton Sent: Wednesday, September 13, 2000 10:01 AM To: MIDRANGE-L@midrange.com Subject: Re: RE: RE: Rebuild Access Paths I'm not sure this is true. . . . -- I checked some LFs, and they're all set to *IMMED, but nothing showed up on the EDTRDBAP screen. OTOH, I liked Dave's suggestion of building a list of LFs and running it through a CL using OPNDBF and CLOF to rebuild the paths. Question: a lot of these files have multiple members (yes, it's BPCS!). Should I open each member, or can I get away with just opening the first one? MIDRANGE-L@midrange.com writes: >Check: > Access path maintenance . . . . *IMMED > *SAME > *IMMED > *REBLD > *DLY >on your files. If they are set to *REBLD or *DLY they will not get >rebuilt >or updated until you open the files. Change them to *IMMED and they >should >either start rebuilding whilst your executing the CHGLF command or show up >on the EDTRBDAP screen. > >Christopher K. Bipes mailto:ChrisB@Cross-Check.com Mike Naughton Senior Programmer/Analyst Judd Wire, Inc. 124 Turnpike Road Turners Falls, MA 01376 413-863-4357 x444 mnaughton@juddwire.com +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.