September 9, 2010  
  You are here:  Blog

QTCommunicationSimplified50.gif


Try Radicomm's Quicktalk, the first enterprise-class Push-To-Talk application for your Motorola/Symbol rugged devices, in your distribution center for free.

Click here to enter the 21st Century.


Specifying the QAQQINI Library For the OLEDB IBMDA400 and Native .NET DB2 Providers
 
Location: BlogsNetSplore's Blog    
Posted by: Joe Rattz 1/5/2010 12:48:14 PM

Specifying the QAQQINI Library For the OLEDB IBMDA400 Provider

I recently needed to modify the IGNORE_DERIVED_INDEX setting in the QAQQINI file for my ASP.NET web site.  I didn't want the change I needed to affect any other applications though.  There doesn't seem to be much on the internet telling anyone how to do this, but I finally found a way to do it through the database connection string.

You can add a "QUERY OPTIONS FILE LIBRARY=mylibrary" section to your IBMDA400 connection string to specify the library from which the QAQQINI file should be read.  This allows you to have very granular control over which QAQQINI file is used for any particular database connection.  This allowed me to have a QAQQINI file specifically for my application.

You should be aware though that there was a bug preventing this from working in some versions.  You can read more about it here:

http://www-933.ibm.com/eserver/support/fixes/fixcentral/fixdetails?multi=y&fixid=SI31388&multi=y

That link is where I first learned about the connection string property and how I ultimately ended up finding a solution.

Specifying the QAQQINI Library For the Native .NET DB2 Provider

Also, according to this document, the native .NET DB2 provider also has a connection string property named "QueryOptionsFileLibrary".

http://www.redbooks.ibm.com/redbooks/SG246440/wwhelp/wwhimpl/js/html/wwhelp.htm

You should notice that the connection string property for the native provider doesn't contain spaces while the connection string property for the OLEDB IBMDA400 provider does.  I have personally tested the IBMDA400 connection string property and it worked for me, but I have not tested the native .NET DB2 provider connection string property.  If you have and it worked, please post a comment letting others know.

Copyright ©2010 Joe Rattz
Permalink |  Trackback
 
Module Border Module Border
My Book

 

Module Border Module Border
Blog Archive
   
    

  Home|Freebies|Blog|Services|Articles|ASP.NET Depot|DotNetNuke Central|Contact Us
  Copyright 2005 Netsplore Terms Of Use Privacy Statement