| Author |
Message
|
| mqjeff |
 Posted: Tue Oct 06, 2015 7:43 am Post subject: |
 |
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| GenCode wrote: |
mqjeff,
> Can you show the amqsbcg/amqsbcgc output of the message?
I am not sure if you mean one of the tab in RFHUTIL or using the old .NET DLL? |
I mean using the amqsbcg or amqsbcgc mq command to read the message and output it with headers and hex and text values of the message body.
Makes it easy to see what's wrong with message data, and headers.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Tue Oct 06, 2015 9:37 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Jeff means the IBM-supplied and well-documented utilities amqsbcg or amqsbcgc.
_________________
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 |
|
|
| GenCode |
| Posted: Wed Oct 07, 2015 5:39 am Post subject: |
|
|
Novice
Joined: 10 Sep 2015
Posts: 21
|
Jeff, thanks for the reply.
I did find the amqsbcgc.exe and ran it using
amqsbcgc my.queue.name my.queue.manager.name
But this is a remote queue and I don't think this works with remote queues as there is not place in the doc I see where to put "Remote Queue Manager Name" like I have using the rfhutilc, I also don't see where I can specify a remote tcp address or a port.
We can't get this info using rfhutilc since its working for the remote queue? |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Oct 07, 2015 5:52 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| GenCode wrote: |
Jeff, thanks for the reply.
I did find the amqsbcgc.exe and ran it using
amqsbcgc my.queue.name my.queue.manager.name
But this is a remote queue and I don't think this works with remote queues as there is not place in the doc I see where to put "Remote Queue Manager Name" like I have using the rfhutilc, I also don't see where I can specify a remote tcp address or a port.
We can't get this info using rfhutilc since its working for the remote queue? |
Post the command you issued, and the response you received. Saying "it didn't work" or words to that effect provide us no useful information.
amqsbcgc is the client-bindings version of amqsbcg, It connects to the qmgr you specify in the command, and MQGETs (browses) messages on the queue-name you specify in the command. As all MQGETs are local, the queue-name needs to be a QLocal or resolve to a QLocal definition.
It works.
_________________
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 |
|
|
| Vitor |
| Posted: Wed Oct 07, 2015 5:58 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| GenCode wrote: |
| But this is a remote queue and I don't think this works with remote queues as there is not place in the doc I see where to put "Remote Queue Manager Name" like I have using the rfhutilc, I also don't see where I can specify a remote tcp address or a port. |
The command line amqsbcgc doesn't have a convenient box to specify a remote tcp address or port, but it takes one like any other client application. A few moments with the InfoCenter will yield some suitable methods  
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| GenCode |
| Posted: Wed Oct 07, 2015 11:23 am Post subject: |
|
|
Novice
Joined: 10 Sep 2015
Posts: 21
|
Bruce,
> Post the command you issued
I did that, "amqsbcgc my.queue.name my.queue.manager.name"
> and the response you received.
"MQCONN failed with CompCode:2, Reason:2058"
> Saying "it didn't work" or words to that effect provide us no useful information.
Um...I never said "it didn't work", and I think I have tried to provide tons of useful information all over this thread...not sure where this came from but okay.
Thanks for the help jeff and fjb_saper it is much appreciated but at this point I am going to open a ticket with our MQ guys here at Citigroup to have them look into the message in more detail to see if they see anything. For now I will just stick with the amqmdnet library as works fine and parses the clients date without issue. This is a time sensitive project for Citigroup, when time permits I will get back to this XMS upgrade. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Oct 07, 2015 11:27 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| GenCode wrote: |
Bruce,
> Post the command you issued
I did that, "amqsbcgc my.queue.name my.queue.manager.name"
> and the response you received.
"MQCONN failed with CompCode:2, Reason:2058"
|
Because the command shell in which you're running the command lacks the client information, as I indicated above.
| GenCode wrote: |
| Thanks for the help jeff and fjb_saper |
You're welcome. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| GenCode |
| Posted: Wed Oct 07, 2015 11:44 am Post subject: |
|
|
Novice
Joined: 10 Sep 2015
Posts: 21
|
Vitor, Thanks too  That was next, look at the InfoCenter to see if I can figure out how to use amqsbcgc to connect to the remote q and get the hex for Jeff.
Before your comment I was going off this knowledge center
http://www-01.ibm.com/support/knowledgecenter/SSFKSJ_8.0.0/com.ibm.mq.adm.doc/q020800_.htm
That's why I assumed it could not connect to the remote q, let me check out the InfoCenter when I have a few and get back to everyone.
Once again...thanks, much appreciated. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Oct 07, 2015 11:46 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Oct 23, 2015 7:59 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
|
| Back to top |
|
|
|
|
