| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQRC 2095 with MQReply Node : SOLVED, Howver.... |
« View previous topic :: View next topic » |
| Author |
Message
|
| girish_tharwani |
 Posted: Wed Feb 13, 2013 1:00 am Post subject: MQRC 2095 with MQReply Node : SOLVED, Howver.... |
 |
|
Voyager
Joined: 01 Aug 2001
Posts: 88
Location: Pune, India
|
A message flow (MQReply Node) is trying to send replies to remote queue manager using replytoq and replytoqmgr.
The replytoqmgr (QM1) and the broker qmgr are in cluster but replytoq (ABC) is not in cluster.
Its failing with "2013-02-13 07:30:27.508294 49 UserTrace BIP2638I: The MQ output node 'MyMessageFlow.MQ Reply.ComIbmMQOutput' attempted to write a message to queue ''ABC'' connected to queue manager ''QM1''. The MQCC was '2' and the MQRC was '2095'.
2095 (082F) (RC2095): MQRC_NOT_OPEN_FOR_SET_ALL
Explanation
An MQPUT call was issued with the MQPMO_SET_ALL_CONTEXT option specified in the PutMsgOpts parameter, but the queue had not been opened with the MQOO_SET_ALL_CONTEXT option.
My problem is that I am not doing MQOPEN and MQPUT. MQReply node is doing that and MQReply node, unlike MQOUTPUT node, does not give options for controlling the context setting options.
If anyone had encountered this in past and can help, I will really appreciate.
Last edited by girish_tharwani on Wed Feb 13, 2013 10:10 pm; edited 1 time in total |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Feb 13, 2013 1:27 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
What are you all trying to set on the MQMD? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| girish_tharwani |
| Posted: Wed Feb 13, 2013 1:47 am Post subject: |
|
|
Voyager
Joined: 01 Aug 2001
Posts: 88
Location: Pune, India
|
its largly a copy of what comes in with reqeust. This is what trace is showing after the failure:
(0x01000000:Name ):MQMD = ( ['MQHMD' : 0x14821fd0]
(0x03000000:NameValue):SourceQueue = 'NAME_REDECTED' (CHARACTER)
(0x03000000:NameValue):Transactional = TRUE (BOOLEAN)
(0x03000000:NameValue):Encoding = 546 (INTEGER)
(0x03000000:NameValue):CodedCharSetId = 1208 (INTEGER)
(0x03000000:NameValue):Format = 'MQHRF2 ' (CHARACTER)
(0x03000000:NameValue):Version = 2 (INTEGER)
(0x03000000:NameValue):Report = 0 (INTEGER)
(0x03000000:NameValue):MsgType = 8 (INTEGER)
(0x03000000:NameValue):Expiry = -1 (INTEGER)
(0x03000000:NameValue):Feedback = 0 (INTEGER)
(0x03000000:NameValue):Priority = 0 (INTEGER)
(0x03000000:NameValue):Persistence = 0 (INTEGER)
(0x03000000:NameValue):MsgId = X'39500e9675af11e2a64e16730fe600000000000000000000' (BLOB)
(0x03000000:NameValue):CorrelId = X'000000000000000000000000000000000000000000000000' (BLOB)
(0x03000000:NameValue):BackoutCount = 1 (INTEGER)
(0x03000000:NameValue):ReplyToQ = 'ABC ' (CHARACTER)
(0x03000000:NameValue):ReplyToQMgr = 'QM1 ' (CHARACTER)
(0x03000000:NameValue):UserIdentifier = ' ' (CHARACTER)
(0x03000000:NameValue):AccountingToken = X'0000000000000000000000000000000000000000000000000000000000000000' (BLOB)
(0x03000000:NameValue):ApplIdentityData = ' ' (CHARACTER)
(0x03000000:NameValue):PutApplType = 0 (INTEGER)
(0x03000000:NameValue):PutApplName = ' ' (CHARACTER)
(0x03000000:NameValue):PutDate = DATE '2013-02-13' (DATE)
(0x03000000:NameValue):PutTime = GMTTIME '07:30:21.480' (GMTTIME)
(0x03000000:NameValue):ApplOriginData = ' ' (CHARACTER)
(0x03000000:NameValue):GroupId = X'414d51204d5153503036584220202020e47e185198613820' (BLOB)
(0x03000000:NameValue):MsgSeqNumber = 1 (INTEGER)
(0x03000000:NameValue):Offset = 0 (INTEGER)
(0x03000000:NameValue):MsgFlags = 1 (INTEGER)
(0x03000000:NameValue):OriginalLength = -1 (INTEGER)
) |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Feb 13, 2013 1:53 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You should not be setting all these fields.
You should be passing in the request MQMD and only setting the fields you need changed...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| girish_tharwani |
| Posted: Wed Feb 13, 2013 1:59 am Post subject: |
|
|
Voyager
Joined: 01 Aug 2001
Posts: 88
Location: Pune, India
|
We are *not* setting these fields. As I said, our response MQMD is largly what our reqeust MQMD is. We copy over.
Another interesting observation...when I created ABC locally on brokeramgr and set replytoqmgr as "brokerqmgr" in reqeust message, it works fine so issue occurs only when the routing is via SCTQ. |
|
| Back to top |
|
|
| girish_tharwani |
| Posted: Wed Feb 13, 2013 10:09 pm Post subject: MQRC 2095 with MQReply Node : SOLVED, Howver.... |
|
|
Voyager
Joined: 01 Aug 2001
Posts: 88
Location: Pune, India
|
2095 was misleading. It suggested that queue was opened successfully but put failed. However, we were able to capture a MQ event messages corresponding to this broker error which told us that MQOPEN issued by MQREPLY itself was failing with 2035. The event message also told us that MQOO used on MQOPEN call was 10256. 10256 : MQOO-FAIL-IF-QUIESCING + MQOO-SET-ALL-CONTEXT + MQOO-OUTPUT
We did +setall for mqbrkrs id on SCTQ and it fixed the issue.
However, my concern is, why in the world MQREPLY node is opening the queue with MQOO-SET-ALL-CONTEXT? MQREPLY code does not provide us the option of controlling the cotext settings like MQOUTPUT node does so it seems hardcoded in MQREPLY to use MQOO of 10256. Why?? |
|
| 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
|
|
|
|
