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



Steve,

We'd rather not touch the iSeries Access ODBC driver. We want to get assurance that the current driver, 9.0.4 from V5R2 for example, will work seamlessly after we upgrade the OS to V5R4. Is this realistic?

Bryan

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Rhody, Steve
Sent: Wednesday, April 08, 2009 9:54 AM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: OS upgrade planning and ODBC

Bryan,

I suggest obtaining a statement of compliance from each ISV before you
upgrade. Ideally, they should (by now) have tested their app against
the v5r4 iSeries Access ODBC driver as well as the SQL engine on the IBM
i host. If any of the apps have issues with the ODBC driver, they
should be able to remain on the v5r3 version of iSeries Access until
those issues can be resolved.

You may also want to consider deleting any SQL packages related to these
applications immediately after you upgrade the host to v5r4. IBM
software support suggested this as good practice after some of ours
became corrupt during past o/s upgrades.

SQL packages hold sql access plan information, and can cause the
requesting application technical difficulties if they fill up or become
corrupt. The ISV's should be able to help you identify which belong to
their respective applications (WRKOBJ *ALL/*ALL *SQLPKG will give you a
comprehensive list)...but it is VERY important that you not delete the
IBM-supplied versions in QSYS.

Steve
--




Steve Rhody
Crate and Barrel
1935 Techny Road Unit 15
Northbrook, Illinois 60062
T 847.239.6426
F 847.562.9611
E srhody@xxxxxxxxxxxxxxxxxx


This communication (including any attachments) may contain confidential or other privileged information. If you are not the intended recipient, or believe that you have received this communication in error, please do not print, copy, retransmit, disseminate, disclose or otherwise use this information. Also, please notify the sender by email that you have received this transmission in error, and delete this email from your system. Thank you.-----Original Message-----
date: Wed, 8 Apr 2009 08:18:43 -0500
from: "Burns, Bryan" <Bryan_Burns@xxxxxxxxxxxx>
subject: OS upgrade planning and ODBC

What the best practice to follow if you're planning an OS upgrade and
want to ensure that the ODBC connections to your system i will work
after the upgrade? That is, does anyone have something on their OS
upgrade checklist they will share with respect to ODBC?

In our case we have 3 apps doing ODBC: Domino, Cognos and UPS Worldship
and we'll be upgrading to V5R4 from V5R3. Do I just ensure with IBM
that the respective iSeries for Access ODBC driver is compatible with
V5R4?

As always, thanks in advance for any replies.

Bryan Burns
iSeries Specialist
ECHO, Incorporated
Lake Zurich, Illinois





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.