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




Response from JD:

Eric: your message prompted me to try disabling extended SQL support 
     within the ODBC driver, and that seems to have been effective.
     
     I should be able to complete my testing now.  Though the configuration 
     doesn't mirror the production system, I don't think this particular 
     difference will pose a problem.
     
     Thanks for all of your help.
     jd



______________________________ Reply Separator _________________________________
Subject: Re[2]: ODBC connection problem...  
Author:  <MIDRANGE-L@midrange.com > at INET_WACO
Date:    10/30/98 8:29 AM



     I'll forward this to him... How is "lazy close" specified? I'll try 
     to do a little research on this....
     
     Thanks
     
     Eric


______________________________ Reply Separator _________________________________
Subject: Re: ODBC connection problem... 
Author:  <MIDRANGE-L@midrange.com > at INET_WACO
Date:    10/29/98 8:49 PM


At 16:03 10/29/1998 , Eric DeLong wrote:
>     ODBC put a member lock on the data file. One would think that when 
>     we disconnect from the data source, the job's member lock would be 
>     removed. It's not. Since the lock is being maintained, the RFROMPCB 
>     command fails because it cannot allocate the member to clear it 
>     before transferring the new data. OS400 is at V3R2 (our development 
>     box, used for testing). This same process seems to work fine on the 
>     production box (V3R7).

Could the datasource possibly be using lazy close? I think that holds the 
connection open for a period of time, just in case it might be used again.

Pete Hall
peteh@inwave.com 
http://www.inwave.com/~peteh/

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