| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Completion Code 2, Reason 2026 |
« View previous topic :: View next topic » |
| Author |
Message
|
| Gary Zhong |
 Posted: Thu Aug 15, 2002 1:55 pm Post subject: Completion Code 2, Reason 2026 |
 |
|
Newbie
Joined: 15 Aug 2002
Posts: 7
|
I am in the process of moving an existing MQ/JMS application from Sun Solaris to HP-UX 11. The application uses JMS message listener, waits for a message from OS390 mainframe in a MQ queue, processes it, and send a reply to the reply queue specified with the originial message.
Java 1.3.1 on the UX side, and non JMS code on the mainframe side. It worked fine on Sun Solaris.
I'm getting the MQJMS2007 exception with linked MQException of reason code 2026 on the return leg, i.e., sending the processed message from UNIX back to the mainframe.
I have displayed the text message it tried to send and the reply queue name just before the queueSender.send(textMessage) line, so I know it is right there where the exception was thrown. But I'm also handcuffed from doing any further investigation beause the send method comes with JMS and there is no way that I know of to look at the MQ Message header prepared by JMS.
The reply queue is not defined in JMS Adm ldap because I rely on the incoming message to tell me where to go with the reply. In this particular case, the displayed queue name of the queueSender is queue://MQM4/MSG.REPLY?targetClient=1
where MSG.REPLY is the local queue on the mainframe side.
Any idea why it works in Sun but not HP? Any comment is appreciated. Thanks in advance.
Gary |
|
| Back to top |
|
 |
| RogerLacroix |
| Posted: Thu Aug 15, 2002 8:23 pm Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Hi,
Are you using an older version of MQ on HP-UX? 2026 points to an MQMD error. Older versions of MQ did not support v2 of the MQMD.
later
Roger...
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| Gary Zhong |
| Posted: Fri Aug 16, 2002 5:17 am Post subject: |
|
|
Newbie
Joined: 15 Aug 2002
Posts: 7
|
| Both the HP-UX and Sun Solaris has MQ v5.2 on it. The mainframe is MQ v2.1 |
|
| Back to top |
|
|
| Gary Zhong |
| Posted: Fri Aug 16, 2002 7:02 am Post subject: |
|
|
Newbie
Joined: 15 Aug 2002
Posts: 7
|
Update: I used Throwable to printStackTrace of this error: Her is what I got -
Throwable: javax.jms.JMSException: MQJMS2007: failed to send message to MQ queue
javax.jms.JMSException: MQJMS2007: failed to send message to MQ queue
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironm
ent.java:418)
at com.ibm.mq.jms.MQQueueSender.sendInternal(MQQueueSender.java:673)
at com.ibm.mq.jms.MQQueueSender.send(MQQueueSender.java:223)
at com.ibm.mq.jms.MQQueueSender.send(MQQueueSender.java:256)
.... |
|
| Back to top |
|
|
| bower5932 |
| Posted: Fri Aug 16, 2002 7:57 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
I just found this in the Application Programming Guide:
MQMD_VERSION_2
Version-2 message descriptor structure.
This version is supported in the following environments: AIX, HP-UX, OS/2, AS/400, Sun Solaris, Windows NT, plus MQSeries clients connected to these systems.
I would guess that your problem is that the MQMD isn't supported on the OS/390. |
|
| Back to top |
|
|
| technok |
| Posted: Mon Sep 16, 2002 4:42 am Post subject: setVersion() method |
|
|
Novice
Joined: 14 Oct 2001
Posts: 17
Location: Hong Kong
|
For JAVA, setVersion() method is available to put a message with MQMD_VERSION_1 option. 
_________________
Techno K
IBM Certified MQ/WMQI Specialist |
|
| 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
|
|
|
|
