Re: Still having *IDX problem on V4R4

[pytel@xxxxxxxxxx]

*IDX-file means that index is actually built (or rebuilt).
Just updating index for record add/update will not cause this.
You either have MAINT other than *IMMED, or your application explicitly
removes/adds member to logical file.

    Alexei Pytel


"Stone, Brad V (TC)" <bvstone@taylorcorp.com> on 02/01/2000 03:49:49 PM

Please respond to MIDRANGE-L@midrange.com

To:   "'MIDRANGE-L@midrange.com'" <MIDRANGE-L@midrange.com>
cc:
Subject:  Still having *IDX problem on V4R4




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