| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQFB Codes in DLH |
« View previous topic :: View next topic » |
| Author |
Message
|
| exerk |
 Posted: Thu Aug 29, 2019 10:02 am Post subject: MQFB Codes in DLH |
 |
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
I've just had a bit of a head-scratcher trying to sort out a message in a DLQ, said message not resolving with a recognisable code, or at least not an MQRC one.
amqsbcg gave me '1901 0000' for the Reason, which, corrected for little-endian is a hex value of X'00000199' and that wonderfully helpful command-line tool of 'mqrc 0x199' gave me nada for that code, in any combination of presenting the hex code. So, thinks me, is this a 'well-behaved' application dumping a message on the queue and actually building a DLH, but populating the Reason field with their own code?
Off I went to the wonderful KC, to see what the field type is, and I stumbled (completely by accident I might add) on the page that gave me this: MQFB_BIND_OPEN_CLUSRCVR_DEL ( X'00000119')
As far as I am concerned the mystery is solved, which led me to find the page with MQFB_* (Feedback Values) on it, but why, oh why is there not the facility to query those codes too, in the same way as MQRC?
Anyone know of a tool? Anyone?
If the answer comes back negative I may just raise an RFE 
_________________
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 |
|
 |
| markt |
| Posted: Thu Aug 29, 2019 10:38 am Post subject: |
|
|
Knight
Joined: 14 May 2002
Posts: 508
|
SupportPac MS0P has "mqidecode" (among a number of tools):
| Code: |
$ mqidecode -p fb -v 0x119 -e
MQFB_BIND_OPEN_CLUSRCVR_DEL
|
Based on the MQConstants.lookup() method available from the regular MQ Java classes if you want to build your own variants.
If I didn't know that the number was in the MQFB range, I could also do
| Code: |
$ mqidecode -p . -v 0x119 -e -n
MQFB_BIND_OPEN_CLUSRCVR_DEL
|
to search the entire numberspace for MQ (don't try it with a number like 0x1 because it maps to so many constants).
Or the non-code way is simply to grep for the decimal version of the number in cmq*.h
Last edited by markt on Thu Aug 29, 2019 11:47 am; edited 1 time in total |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Aug 29, 2019 11:37 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
You sir are a scholar and a gentleman - thank you!
And embarrassingly I find I have it installed already 
_________________
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 |
|
|
| bruce2359 |
| Posted: Thu Aug 29, 2019 11:46 am Post subject: Re: MQFB Codes in DLH |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| exerk wrote: |
I've just had a bit of a head-scratcher trying to sort out a message in a DLQ, said message not resolving with a recognisable code, or at least not an MQRC one.
MQFB_BIND_OPEN_CLUSRCVR_DEL ( X'00000119')
|
A new one on me, too. Where/how did you encounter this? Symptoms?
_________________
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 |
|
|
| exerk |
| Posted: Thu Aug 29, 2019 11:50 am Post subject: Re: MQFB Codes in DLH |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| bruce2359 wrote: |
| exerk wrote: |
I've just had a bit of a head-scratcher trying to sort out a message in a DLQ, said message not resolving with a recognisable code, or at least not an MQRC one.
MQFB_BIND_OPEN_CLUSRCVR_DEL ( X'00000119')
|
A new one on me, too. Where/how did you encounter this? Symptoms? |
Just had at least one message on the DLQ for that reason. Only thing I can think of (as it's a test env) is that the message must have been on the XMITQ for quite some time and the other end wasn't available. During that time the CLUSRCVR (or even the queue manager that hosted it) was deleted, the channel was fired up and hey presto, to the DLQ did it go.
_________________
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 |
|
|
| HubertKleinmanns |
| Posted: Thu Aug 29, 2019 10:51 pm Post subject: |
|
|
Shaman
Joined: 24 Feb 2004
Posts: 732
Location: Germany
|
exerk,
I would open a RFE. It seems, that FB codes are not part of mqrc.
When you opened the RFE, please post it to this thread. I would forward it to my german working Group (> 200 members).
_________________
Regards
Hubert |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Aug 29, 2019 11:01 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| HubertKleinmanns wrote: |
exerk,
I would open a RFE. It seems, that FB codes are not part of mqrc.
When you opened the RFE, please post it to this thread. I would forward it to my german working Group (> 200 members). |
I'll take it under consideration...
_________________
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 |
|
|
| tczielke |
| Posted: Fri Aug 30, 2019 5:45 am Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 941
Location: Illinois, USA
|
An RFE to add this mqrc makes sense, but here is an example of how to find this information from MQ from the include files that MQ builds on (as Mark mentioned earlier):
| Code: |
#Linux example
> grep 281 /opt/mqm/inc/cmq*.h | grep FB
/opt/mqm/inc/cmqc.h: #define MQFB_BIND_OPEN_CLUSRCVR_DEL 281
/opt/mqm/inc/cmqstrc.h: case 281: c = "MQFB_BIND_OPEN_CLUSRCVR_DEL"; break;
/opt/mqm/inc/cmqstrc.h: { 281, "MQFB_BIND_OPEN_CLUSRCVR_DEL" },
/opt/mqm/inc/cmqstrc.h: { "MQFB_BIND_OPEN_CLUSRCVR_DEL" , 281 },
|
The include files are the "horse's mouth", since MQ builds off of them. I usually just check them for this information.
_________________
Working with MQ since 2010. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Aug 30, 2019 5:55 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Searched google using the entire feedback code ‘MQFB_BIND_OPEN_CLUSRCVR_DEL ( X'00000119')’
Resulted in this: https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_8.0.0/com.ibm.mq.ref.dev.doc/q096230_.htm
MQFB_BIND_OPEN_CLUSRCVR_DEL ( X'00000119')
The message was on the SYSTEM.CLUSTER.TRANSMIT.QUEUE intended for a cluster queue that was opened with the MQOO_BIND_ON_OPEN option, but the remote cluster-receiver channel to be used to transmit the message to the destination queue was deleted before the message could be sent. Because MQOO_BIND_ON_OPEN was specified, only the channel selected when the queue was opened can be used to transmit the message. As this channel is no longer available, the message is placed on the dead-letter queue.
_________________
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 |
|
|
| exerk |
| Posted: Fri Aug 30, 2019 5:59 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
And that's the page I stumbled upon, and in which the 119 caught my eye...
_________________
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 |
|
|
|
|
|
| |
|
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
|
|
|
|
