Thank you so much Evan, this is very helpful. I think I'll upgrade the drivers and test them on the current databases, as you indicated, because I doubt that IBM or an ISV is going to state support for old drivers because of variables like service levels of the iSeries for Windows package.
Regards,
Bryan Burns
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Evan Harris
Sent: Wednesday, April 08, 2009 5:57 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: OS upgrade planning and ODBC
Hi Bryan
If you decide to upgrade the ODBC driver you should be able to do this in
advance and verify that the application continues to work with your current
database before doing the upgrade.
My experience is largely that this simply is not an issue, although as
someone else pointed out, sometimes the SQL packages on the iSeries need to
be deleted in order for the connection to work properly; be sure not to
delete the IBM supplied model packages and back them all up beforehand.
Running STROBJCVN after the upgrade seems to reduce the messing around with
SQLPKG objects after the event.
Generally speaking I attempt to identify these kinds of connections before
the upgrade and then ensure that they are tested immediately after the
upgrade activities have completed. This means I can deal with any issues (if
there are any) before mainstream production re-commences. Normally this is
sufficient for this type of stuff. Dial-up and modem connections are more
likely to require some intervention.
If you want to be *certain* then you'd need to do a test upgrade beforehand
probably on another box and verify that the connections work or if it is
sufficient get the vendors to verify that it will be OK. My guess is their
verification will be wishy-washy enough that you will have to test in
advance or take the risk (minimal in my opinion).
Regards
Evan Harris
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Burns, Bryan
Sent: Thursday, 9 April 2009 1:19 a.m.
To: MIDRANGE-L@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
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.