RE: Still having *IDX problem on V4R4

[Scott Mildenberger <Smildenber@xxxxxxxxxxxx>]

It must have something to do with the multiple members because we have
single member files with 5 to 10 million records with several logicals over
them and have never seen this, we are at V4R3.  What is specified on the
physical file for path rebuild?  Is the *IDX-file stating the logical you
refer to or what?  Are there any other logicals over the file that do not
have *IMMED for path rebuild?  Can you recreate the setup with only one
member to see how it acts?  This is a strange one to me!

Scott 

> -----Original Message-----
> From: Stone, Brad V (TC) [SMTP:bvstone@taylorcorp.com]
> Sent: Tuesday, February 01, 2000 2:50 PM
> To:   'MIDRANGE-L@midrange.com'
> 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
+---