× 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.


  • Subject: RE: Still having *IDX problem on V4R4
  • From: "Stone, Brad V (TC)" <bvstone@xxxxxxxxxxxxxx>
  • Date: Tue, 1 Feb 2000 17:35:33 -0600

SCott, 

This is a question for someone else, but from what they've told me, no
matter how a record is added, program or DFU, this happens.

I'll have them look at the job log.




> -----Original Message-----
> From: Scott Mildenberger [mailto:Smildenber@Washcorp.com]
> Sent: Tuesday, February 01, 2000 4:38 PM
> To: 'MIDRANGE-L@midrange.com'
> Subject: RE: Still having *IDX problem on V4R4
> 
> 
> Brad,
>       Another thing, does this happen no matter how the 
> record is added?
> For example, does it happen when adding a record with DFU?  
> What if another
> user has the file open when the record is added, what 
> happens?  Does the job
> log of the job adding the record have any info?
> 
> 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
> > +---
> +---
> | 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 thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.