This does incur a slight processing overhead on the client and server, but it seems to be worth the rewarded and noticeable improvement in speed. Applications that require strict conformance to the SQL specification should use setting 1. This is a really cool option, because by default the iSeries will only package SQL statements that contain parameter markers. Watson Product Search Search. I do not recommend that you set this value, as updateable cursors cause overhead on the server side of you application.

Uploader: Faulrajas
Date Added: 26 September 2013
File Size: 58.54 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 58652
Price: Free* [*Free Regsitration Required]

Setting the value to 2 will cause the iSeries to not issue an error if the package file is corrupted or missing.

Connection string keywords

The following section deals with keywords that can be helpful when attempting to diagnose performance problems or steing errors between the client and the server.

The problem with data source strinb is that each time you attempt to connect; the program has to look up information about the connection options in the Windows registry. These same keywords and their values are stored when an ODBC data source is setup. Some values are passed as numbers, some a strings.

Specifies the set of libraries to be searched when returning information when using wildcards with catalog APIs. No action by the user is required. Setting this value to an integer indicates a size in megabytes. If not provided, the server attribute conenction is unchanged.

Keywords That Can Help in Debugging The following section deals with keywords that can be helpful when attempting to diagnose performance problems or application errors between the client and the server. A 0 value instructs the driver to use the Windows user ID and password every time a connection is attempted with the iSeries. To install the program, simply unzip the program to a temporary directory and then click the Setup.


Specifies the IBM i system ovbc to connect. See the info on the other keywords for more information. Use only as directed by your technical support provider. The allowable values are; 0 for forward slash, 1 for dash, 2 for period, 3 for comma and 4 to specify a blank.

I continue to use the previous driver name, so that my software is compatible with previous versions of Client Access. Use value 1 to turn on support for true ODBC auto-commit.

I have done a lot of experiments using record blocking and here are odbv performance tidbits; when using blocking on a select statement against arecord table I am able to achieve over 5, records per second with blocked ODBC fetches, whereas I can only retrieve records per second when not using blocking techniques.

I typically do not specify this value as SSL encryption will cause a tremendous overhead in processing power on the client and server systems.

Connecting with the basic connection string will result in a connection with all ODBC settings defaulted. Pass a 0 to not cache the package locally, pass a 1 to cache the package on the PC. Specifies how the extended dynamic package support will behave. The unistall information is also described in the V5R2 Memorandum to Users. In my web applications, I go so far as to adjust block size based on what the individual web page is doing, using larger sizes if the expected result set is large and smaller sizes if it will be small.

Ninety nine percent of the time, I connect using the default value so I do not specify this keyword. Sometimes, if the package file is small, this can improve the performance of the ODBC application.

File DSN for iSeries AS ODBC connection – Stack Overflow

Client codepage setting or 0 use default client codepage setting Default: The driver will generate a funky file name that is the concatenation of the driver name along with the application name and other funky text. When an application requests another row, the driver will not need to send another flow to the host connextion to get it.


Note that the last label statement uses the TEXT keyword, which will cause the label to become an iSeries column description whereas the label statement without the TEXT keyword specifies a column heading.

Once the string is in the clipboard you will see a message box that tells you the connection string is in the Windows Clipboard.

This setting only has an effect is the TFT is set to 0, the default. Most ODBC applications can not handle using pre-fetching so I recommend that you leave this option off as you may find you are missing records from the beginning of your result set.

This can be an awesome capability, in that it can give you very granular control of how the query optimizer works.

If you are programming a web application, you could be issuing hundreds of connections to the iSeries a minute, and the performance hit of reading the registry is not something you want to have in your application. If the login is successful, you will see a dialog box reporting that you have successfully connected to the iSeries.