| Author |
Message
|
| guogangli |
 Posted: Fri May 01, 2015 1:57 pm Post subject: MQCONNX() returns 2059 after WMQ is Upgraded to 7.5.0.4 |
 |
|
Novice
Joined: 02 Mar 2009
Posts: 15
|
Hi All,
After WebSphere MQ on a Sun/Solaris 10 (SPARC platform) is upgraded from 7.0.1.2 to 7.5.0.4, MQCONNX() call returns 2059. Queue managers are running. Applications just make MQCONN() call can connect to queue managers.
Did anyone out there encounter the similar problem?
Thank you for your help!
Grant Li
CSG International Inc |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Fri May 01, 2015 3:08 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Did you look at the error logs?
Could be to CHLAUTH causing RC 2009. Have you created CHLAUTH rules for your channels?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat May 02, 2015 9:49 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
|
| Back to top |
|
|
| tczielke |
| Posted: Sat May 02, 2015 2:41 pm Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 941
Location: Illinois, USA
|
Was the queue manager created new at 7.5? When you upgrade an existing queue manager from 7.0.1 to 7.5, the CHLAUTH will be disabled.
_________________
Working with MQ since 2010. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Sat May 02, 2015 4:08 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
"Upgrade" has multiple connotations. How exactly did you do so?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| guogangli |
| Posted: Mon May 04, 2015 7:22 am Post subject: |
|
|
Novice
Joined: 02 Mar 2009
Posts: 15
|
Thank you all for your replies.
The problem was resolved. It turned out the applications were built with MQ 7.0.1.2. When they connect the 7.5.0.4 queue managers, MQCONNX() call failed with 2059. An FDC file shows "AMQ6125: WebSphere MQ was unable to open a message".
After the applications are built with MQ 7.5.0.4, they can connect to the 7.5.0.4 queue managers, and MQCONNX() call succeeded.
Thanks again.
Grant Li
CSG International, Inc |
|
| Back to top |
|
|
| zpat |
| Posted: Mon May 04, 2015 9:44 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
These different versions of client and queue manager will interoperate.
There is no need to upgrade (other than for currency), however applying more recent maintenance than fixpack 2 would be advisable (I think fixpack 7.0.1.12 is out now).
Always a bad idea to let your client maintenance level get 5 years out of date...
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| guogangli |
| Posted: Tue May 05, 2015 12:11 pm Post subject: |
|
|
Novice
Joined: 02 Mar 2009
Posts: 15
|
Jedi,
I am sorry I didn't make it clear. We do not use WMQ client. Our applications are built with WMQ server libraries. We have to upgrade to a newer WMQ version, because the support to V7.0.1 will be expired in September 2015.
This is the first time we observed that the two versions of WMQ are not compatible. Applications built with V7.0.1.2 libraries don't work with V7.5.0.4 running queue managers.
Thanks!
Grant Li
CSG International, Inc |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed May 06, 2015 4:54 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
|
|
