| Author |
Message
|
| ivandu |
 Posted: Wed Jun 04, 2003 8:45 am Post subject: MQWF migration issue (from V3.3.0CSD4 to V3.4.0CSD1) |
 |
|
Newbie
Joined: 04 Jun 2003
Posts: 5
Location: Toronto, ON, Canada
|
We have successfully upgraded our MQWF server (AIX 5.1 ML03) to V3.4.0 in our lab. When we test our existing applications on a NT4 desktop with V3.3.0 Client installed, we are getting an error code 100 (FMC_ERROR_INTERNAL) from an C++ API call (UserSettings). But this application works fine on a NT desktop with V3.4 Client installed.
We are planning to do the upgrade in two steps in production. First upgrade the server, then the client. But if we can't get this problem resolved, we have to do it in one shot, which is more risky.
Anyone has this issue too? Your help would be greatly appreciated!
 |
|
| Back to top |
|
 |
| vennela |
| Posted: Wed Jun 04, 2003 9:41 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
I can give my opinion on this.
If you want to do 2-phase upgrades, then I think you should do it the other way. Upgrade clients first and then upgrade server. But if you are talking about fat client then I am not sure.
Though the changes are minimal between 3.3.2 and 3.4, 3.3.0 and 3.4 should have quite a few differences (this is just a guess because I have not worked on 330).
-------
Venny |
|
| Back to top |
|
|
| ivandu |
| Posted: Wed Jun 04, 2003 10:01 am Post subject: |
|
|
Newbie
Joined: 04 Jun 2003
Posts: 5
Location: Toronto, ON, Canada
|
No matter what client (Fat or Thin) you are using, I don't think you can upgrade the client first. Because the new client most likely is not able to talk to the old server, but the old client should be able to talk to the new server.
BTW - We are using FAT client.
 |
|
| Back to top |
|
|
| Andy |
| Posted: Wed Jun 04, 2003 8:16 pm Post subject: |
|
|
Centurion
Joined: 14 May 2003
Posts: 122
|
I dont understand the importance of order in which you upgrade client and server. You should upgrade both in any order, then only you going to try to make client-server connection....
Thanks
_________________
 Andy |
|
| Back to top |
|
|
| ivandu |
| Posted: Thu Jun 05, 2003 6:46 am Post subject: |
|
|
Newbie
Joined: 04 Jun 2003
Posts: 5
Location: Toronto, ON, Canada
|
We have thousands of desktop machines connected to the MQWF Server. Since we are using fat client, all the applications have to be distributed to those desktop machines. If anything wrong, we need to back out everything. But our business can not be stopped (this is a banking system). So we will upgrade the MQWF server first, let it run for serveral days or weeks, making sure the business part is Okay, then upgrade the clients. When you are dealing with a big system, you should consider more than just technical factors. That's why we are taking this approach.
|
|
| Back to top |
|
|
| sshaker |
| Posted: Fri Jun 06, 2003 6:14 am Post subject: |
|
|
Disciple
Joined: 20 Sep 2002
Posts: 185
|
let me put forward my experience with this.. the order does matter!!
we upgraded our client to 3.4 on one environment and tried to talk to server (yet to upgrade) and it did not work.. and IBM told higher version cient will not work with lower version server (that is 34 client to 332 server).. fyi.
_________________
shaker |
|
| Back to top |
|
|
| kriersd |
| Posted: Fri Jul 25, 2003 10:16 am Post subject: |
|
|
Master
Joined: 22 Jul 2002
Posts: 209
Location: IA, USA
|
IBM does state that the client (Web or thick) can be two versions back from the server. Yes, I agree that the order DOES matter. You must upgrade the server first, then the client.
just my $0.02
_________________
Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
| Back to top |
|
|
| kriersd |
| Posted: Wed Oct 22, 2003 2:03 pm Post subject: |
|
|
Master
Joined: 22 Jul 2002
Posts: 209
Location: IA, USA
|
Take a look at the README.txt in the SP3 update. Here is a quote.
| Quote: |
API call UserSettings() on the service
object returns RC=100 on clients before V340,
if the server is V340.
Set a new profile variable on the server to allow back-level
clients to connect to a server with 3.4. without the RC=100
error.
With the fmczchk utility, you can change your profile. You
need to change all server profiles with back-level clients,
if this API is used.
The following example sets the needed profile variable for
the configuration ID FMC.
"fmczchk -c inst:m,FMC_BEHAVE_LIKE_332,1 -yFMC"
|
_________________
Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
| Back to top |
|
|
| kriersd |
| Posted: Fri Oct 24, 2003 7:47 am Post subject: |
|
|
Master
Joined: 22 Jul 2002
Posts: 209
Location: IA, USA
|
There is slight typo in the doc for SP2..
FMC_BEHAVE_LIKE_332 <--- should actually be FMC_BEHAVE_LIKE_V332
Dave
_________________
Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
| Back to top |
|
|
|
|
