| Author |
Message
|
| LMD |
 Posted: Fri Feb 29, 2008 1:45 am Post subject: 2026 error after WMQ 5.6 -> 6.0 migration |
 |
|
Acolyte
Joined: 30 Oct 2002
Posts: 56
Location: Paris - France
|
Hi all
A customer of mine have the following configuration :
- Windows server with WMQ 5.3 server (I know ...)
- Aix with WMQ 5.3 client 5.3 (32 bits)
- Cobol Microfocus application putting and getting message througt MQ client on Aix.
Last week he decide to upgrade the Aix box, with WQM client 6.0.2.3.
Now, each time he try go get or put messages with MQ client, he got an 2026 error (MQMD structure is not valid).
The WMQ Windows server have been updated to 5.3.0.14, same error.
Is this something related to 64 / 32 bits cohabitation, 6.0 / 5.3 cohabitation, "2026 or MQRC_MD_ERROR on Get"
http://www.mqseries.net/phpBB2/viewtopic.php?t=40908, ... ?
any ideas ?
_________________
lmd_at_demey-consulting.fr - http://demey-consulting.fr - Paris, France.
WMQ, WAS & IIB Certified.
#IBMChampion |
|
| Back to top |
|
 |
| Vitor |
| Posted: Fri Feb 29, 2008 2:17 am Post subject: Re: 2026 error after WMQ 5.6 -> 6.0 migration |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| LMD wrote: |
Last week he decide to upgrade the Aix box, with WQM client 6.0.2.3.
...
The WMQ Windows server have been updated to 5.3.0.14, same error.
|
I have to ask - why take the client to v6 but leave the server at v5.3? 
I would discount the 64/32 bit thing as I'd expect that to manifest in other ways on a server configuration. This sounds a bit application level for that.
I'm not aware of any compatibility issues v6/v5.3 client/server but my experience is of the server moving up first (easier to upgrade one server than the 200 clients attached to it). So he could try going back to a v5.3 client.
My first guess is a program bug, but you don't give any indication of the code changing. Did he recompile as part of the client upgrade (I can't remember how Microfocus references the libraries). If so, is he certain of the source code he used?
Start with 1st principles - use diagnostic facilties to check the structure of the MQMD being presented to the queue manager and figure out what it doesn't like.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Feb 29, 2008 5:54 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Upgrade that v5.3 to at least FP 12.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Feb 29, 2008 6:01 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jefflowrey wrote: |
Upgrade that v5.3 to at least FP 12.
|
| LMD wrote: |
| The WMQ Windows server have been updated to 5.3.0.14 |
Well I'm confused!
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Feb 29, 2008 6:02 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| Vitor wrote: |
| Well I'm confused! |
  
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Feb 29, 2008 6:07 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
|
| Back to top |
|
|
|
|
