Still having *IDX problem on V4R4 -- MIDRANGE-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.

I asked before, but didn't get much.  Trying again.

Machine is V4R4.  

Have a multi-member file.  A logical built over one member with *IMMED
specified for path rebuild.

This member currently has 1,000,000+ records.  Whenever we add a record, it
takes forever to index it.  You can tell because the job that added the
record(s) says *IDX-file.

Tested it on the devo box that is also V4R4.  Same thing happens.

This causes problems with file locks.

Any ideas anyone?  

Brad
+---
| 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 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.