| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQJE001: Completion Code '2', Reason '2059'. |
« View previous topic :: View next topic » |
| Author |
Message
|
| bkiran2020 |
 Posted: Wed Sep 11, 2013 10:46 am Post subject: MQJE001: Completion Code '2', Reason '2059'. |
 |
|
Master
Joined: 20 Jan 2011
Posts: 243
Location: US
|
When I migrated from MQ v6 to MQ v7 I am facing issues while connecting with a java code to the QMGR.previous it was connecting in MQ v6 and Iam using the same java program to connect in MQ v7 but getting MQRC 2059
what need to be check |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Sep 11, 2013 10:51 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You need to readup on channel security in V7. If V7.1 and up you definitely need to catch up with it. It is different from V6 or V7.0
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Sep 11, 2013 12:16 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| fjb_saper wrote: |
You need to readup on channel security in V7. If V7.1 and up you definitely need to catch up with it. It is different from V6 or V7.0
Have fun |
If you're alluding to Channel Authentication Records (grrr...  , why did they name them that?), if it's a migrated queue manager they'll be switched off.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Sep 11, 2013 12:18 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| exerk wrote: |
| fjb_saper wrote: |
You need to readup on channel security in V7. If V7.1 and up you definitely need to catch up with it. It is different from V6 or V7.0
Have fun |
If you're alluding to Channel Authentication Records (grrr... , why did they name them that?), if it's a migrated queue manager they'll be switched off. |
But if the Java has just been moved from a v6 environment to a scratch built v7 one they won't be.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Sep 11, 2013 12:19 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| Vitor wrote: |
| exerk wrote: |
| fjb_saper wrote: |
You need to readup on channel security in V7. If V7.1 and up you definitely need to catch up with it. It is different from V6 or V7.0
Have fun |
If you're alluding to Channel Authentication Records (grrr... , why did they name them that?), if it's a migrated queue manager they'll be switched off. |
But if the Java has just been moved from a v6 environment to a scratch built v7 one they won't be. |
Hence why I italicised migrate... 
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Thu Sep 12, 2013 6:25 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
I recall changes in the JAR files between WMQ V6 and V7, but that would not result in 2059.
As always, first telnet to the port to make sure you can get there at all.
Then test with amqsputc. Yes, you need an official client. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
