Re: Import taking over 24 hours -- RPG400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Hi Paul -

2) If your target files have an index then modify the access path
maintenance on the target files from *IMMED to *REBLD or *DLY during the
load [CHGPF MAINT(*DLY)].  After you've loaded the data then change the file
back to *IMMED to cause an index rebuild to occur on the files.  If these
files have any logical files then just delete those logicals until after the
conversion or do the same access path maintenance modification on them.

That's a very good point. I had a load program that I was testing which took over 48 hours to run.

I changed it to use DSPDBR to an outfile to change all logicals to *REBLD, then ran the load, then changed the logicals back to *IMMED. I did an OPNDBF *INP on each logical after changing it to *IMMED to force the index to be rebuilt synchronously as part of the load job.

It took about 40 minutes to run, including all of the index rebuilds!

-- Ken http://www.ke9nr.net/ Opinions expressed are my own and do not necessarily represent the views of my employer or anyone in their right mind.

This mailing list archive is Copyright 1997-2025 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.