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



On 13-Mar-2015 11:16 -0500, Jeff Young wrote:
After further consultation at the client, I have determined that they
were having a problem using this connection string from a .NET
program running on a non IBM i system and connecting to the IBM i.
Provider=IBMDA400;Data Source=xxx.xxx.xxx.xxx;User Id=*****;Password=*****
;Default Collection=T47FILES;Naming Convention=1;Library
List=R47MODS,R47PTF,R47OBJ,T47MODSDTA,T47FILES,*Libl
When they removed the *Libl from the end, it worked fine.
Is there an equivalent value to use when using the IBMDA400 OLEDB
client?

I always have a difficult time finding any explicit\definitive and consistent examples or even documentation that matches examples that are claimed\known to be functional. The best I can recall, is that the special value *USRLIBL is supported [though not *LIBL] as I had alluded in my prior reply could be included in the list of comma-separate library names. There is some documentation that might /support/ that allusion, though the syntax does not match the example; instead of "LibraryList" or "Library List" [of which I have seen claimed as used successfully; just as the latter was, in the above-quoted message], the following doc shows "DefaultLibraries".?.?:
<http://www.ibm.com/support/knowledgecenter/api/content/ssw_ibm_i_71/rzaik/rzaikconnstrkeywordsservprop.htm>
_Connection string keywords - Server properties_


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.