473,322 Members | 1,718 Online
Bytes | Software Development & Data Engineering Community
Post Job

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 473,322 software developers and data experts.

V7 client and V8 client on same machine

Helpful folks,

I am in the process of upgrading our company to V8. The steps I have
outlined are as follows:

1) Upgrade all clients to latest V7 fixpack
2) Upgrade test server to latest v7 fixpack
3) Upgrade prod server to latest v7 fixpack
4) migrate test server to V8
5) Upgrade developers client workstations to V8
5a) developers test major applications for V8 compatabilites
6) migrate prod server to v8
7) Upgade all non-developer clients to v8

The problem occurs during step 5a. While the test server is at v8 and
developer workstations are at v8, and the prod server is at v7, the
developers will have a need to run tools and test emergency code fixes
against the prod server. The v8client-to-v7server incompatabilites
will make this impossible.
My question is, can the developer workstations be configured such that
they can easily 'toggle' back and forth between a v8 client and a v7
client, without having to uninstall/reinstall db2 client components?

Any feedback would be greatly appreciated.

Sean
Nov 12 '05 #1
5 2757
On Linux and UNIX, v7 and v8 clients can coexist on the same machine.

On Windows, the safest way to do this is to have separate, bootable
Windows partitions - one with the v7 client, and one with the v8
client, and reboot before using one or the other.

Sean C. wrote:
Helpful folks,

I am in the process of upgrading our company to V8. The steps I have
outlined are as follows:

1) Upgrade all clients to latest V7 fixpack
2) Upgrade test server to latest v7 fixpack
3) Upgrade prod server to latest v7 fixpack
4) migrate test server to V8
5) Upgrade developers client workstations to V8
5a) developers test major applications for V8 compatabilites
6) migrate prod server to v8
7) Upgade all non-developer clients to v8

The problem occurs during step 5a. While the test server is at v8 and
developer workstations are at v8, and the prod server is at v7, the
developers will have a need to run tools and test emergency code fixes
against the prod server. The v8client-to-v7server incompatabilites
will make this impossible.
My question is, can the developer workstations be configured such that
they can easily 'toggle' back and forth between a v8 client and a v7
client, without having to uninstall/reinstall db2 client components?

Any feedback would be greatly appreciated.

Sean


Nov 12 '05 #2
We are having the same exact issue...
We have a V7 OS 390 DB2 server and V8 server Linux UDB server and users need
the ability to connect to both
of them from their NT workstattions. V8 Windows client is not compatible
with V7 OS 390 DB2 server (thru V7 DB2 connect). Every once in a while we
keep doing uninstall/reinstall betwenn ver 8 client & ver 7 client which is
really
really ridiculous.

"Blair Adamache" <ba*******@2muchspam.yahoo.com> wrote in message
news:br**********@hanover.torolab.ibm.com...
On Linux and UNIX, v7 and v8 clients can coexist on the same machine.

On Windows, the safest way to do this is to have separate, bootable
Windows partitions - one with the v7 client, and one with the v8
client, and reboot before using one or the other.

Sean C. wrote:
Helpful folks,

I am in the process of upgrading our company to V8. The steps I have
outlined are as follows:

1) Upgrade all clients to latest V7 fixpack
2) Upgrade test server to latest v7 fixpack
3) Upgrade prod server to latest v7 fixpack
4) migrate test server to V8
5) Upgrade developers client workstations to V8
5a) developers test major applications for V8 compatabilites
6) migrate prod server to v8
7) Upgade all non-developer clients to v8

The problem occurs during step 5a. While the test server is at v8 and
developer workstations are at v8, and the prod server is at v7, the
developers will have a need to run tools and test emergency code fixes
against the prod server. The v8client-to-v7server incompatabilites
will make this impossible.
My question is, can the developer workstations be configured such that
they can easily 'toggle' back and forth between a v8 client and a v7
client, without having to uninstall/reinstall db2 client components?

Any feedback would be greatly appreciated.

Sean

Nov 12 '05 #3
Why not just leave your clients on V7 until after all servers have
been upgraded to V8? V7 client should work perfectly fine connecting
to V8 Server. So what I am saying is do your upgrade as follows.

1) Upgrade all clients to latest V7 fixpack
2) Upgrade test server to latest v7 fixpack
3) Upgrade prod server to latest v7 fixpack
4) migrate test server to V8
5) developers test major applications for V8 compatabilites
6) migrate prod server to v8
7) Upgrade developers client workstations to V8
8) Upgade all non-developer clients to v8
db*****@yahoo.com (Sean C.) wrote in message news:<2f**************************@posting.google. com>...
Helpful folks,

I am in the process of upgrading our company to V8. The steps I have
outlined are as follows:

1) Upgrade all clients to latest V7 fixpack
2) Upgrade test server to latest v7 fixpack
3) Upgrade prod server to latest v7 fixpack
4) migrate test server to V8
5) Upgrade developers client workstations to V8
5a) developers test major applications for V8 compatabilites
6) migrate prod server to v8
7) Upgade all non-developer clients to v8

The problem occurs during step 5a. While the test server is at v8 and
developer workstations are at v8, and the prod server is at v7, the
developers will have a need to run tools and test emergency code fixes
against the prod server. The v8client-to-v7server incompatabilites
will make this impossible.
My question is, can the developer workstations be configured such that
they can easily 'toggle' back and forth between a v8 client and a v7
client, without having to uninstall/reinstall db2 client components?

Any feedback would be greatly appreciated.

Sean

Nov 12 '05 #4
Thanks for all the useful feedback. One of the details I left out, is
that some of the 'clients' that will be talking to the db server are
application servers. This is the functionality that the developers
will need to test, running their workstation as an application server
against the database. I would of course like to upgrade all the
application servers to the v8 client, but as Spencer implies, perhaps
this is not a critical step. I will probably leave that as a follow up
item, and perhaps convince one developer to be the v8 testing dupe, so
that only his workstation will need to worry about
uninstalling/reinstalling client code as needed, and have him test
each application server functionality one-by-one.
Thanks again folks.
Nov 12 '05 #5
Thanks for all the useful feedback. One of the details I left out, is
that some of the 'clients' that will be talking to the db server are
application servers. This is the functionality that the developers
will need to test, running their workstation as an application server
against the database. I would of course like to upgrade all the
application servers to the v8 client, but as Spencer implies, perhaps
this is not a critical step. I will probably leave that as a follow up
item, and perhaps convince one developer to be the v8 testing dupe, so
that only his workstation will need to worry about
uninstalling/reinstalling client code as needed, and have him test
each application server functionality one-by-one.
Thanks again folks.
Nov 12 '05 #6

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

2
by: Marcus | last post by:
I have created a DTS package that pulls data in from Oracle into SQL Server. When I run it directly on the server (from Enterprise Manager), it works fine. When I run it from Enterprise Manager on...
2
by: quotto | last post by:
I have written a web server application using ASP.Net that handles requests from an HTTP client. I wrote a small test client in VB6 using the MSINet ActiveX control, to load test the server. The...
1
by: laststubborn | last post by:
Hi ; I m trying to create Merge Replication. I was able to create the replication on the same machine, however my aim is to use client machine and do all the neessary work on the client machine...
3
by: Tim Burris | last post by:
At the top here i will put a quick description of my problem followed by the long description. This way you want get bored reading! : short version what is the best/recommended way for ASPNET...
5
by: rohitkumar | last post by:
I am trying to build a web application which can execute dos print command on the client machine. This application will read a file stored in server and it will create a folder on client machine...
4
by: Remote_User | last post by:
Hi, When I create a WCF client (hosting the service is fine) and the service on the same machine everything works is good. But when I want to have the client on a different machine this fails....
11
by: BiffMaGriff | last post by:
Hello, .Net 2.0 I am creating a windows forms application for deployment on a client's machine. The program works fine on my local but the output on the client machine is wrong. Since the...
0
by: Demetris | last post by:
Hi, I would like to thank you first again for the replies. Actually to clear some things out, I have an application called Moody's Financial Analyst which sits on Oracle (the server mentioned...
0
by: DolphinDB | last post by:
Tired of spending countless mintues downsampling your data? Look no further! In this article, you’ll learn how to efficiently downsample 6.48 billion high-frequency records to 61 million...
0
by: ryjfgjl | last post by:
ExcelToDatabase: batch import excel into database automatically...
1
isladogs
by: isladogs | last post by:
The next Access Europe meeting will be on Wednesday 6 Mar 2024 starting at 18:00 UK time (6PM UTC) and finishing at about 19:15 (7.15PM). In this month's session, we are pleased to welcome back...
0
by: ArrayDB | last post by:
The error message I've encountered is; ERROR:root:Error generating model response: exception: access violation writing 0x0000000000005140, which seems to be indicative of an access violation...
1
by: CloudSolutions | last post by:
Introduction: For many beginners and individual users, requiring a credit card and email registration may pose a barrier when starting to use cloud servers. However, some cloud server providers now...
1
by: Defcon1945 | last post by:
I'm trying to learn Python using Pycharm but import shutil doesn't work
1
by: Shællîpôpï 09 | last post by:
If u are using a keypad phone, how do u turn on JavaScript, to access features like WhatsApp, Facebook, Instagram....
0
by: Faith0G | last post by:
I am starting a new it consulting business and it's been a while since I setup a new website. Is wordpress still the best web based software for hosting a 5 page website? The webpages will be...
0
isladogs
by: isladogs | last post by:
The next Access Europe User Group meeting will be on Wednesday 3 Apr 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM). In this session, we are pleased to welcome former...

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.