|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
C# to IBM MQ-Remove the MQHRF2 from the requests |
« View previous topic :: View next topic » |
Author |
Message
|
RogerLacroix |
Posted: Thu Apr 19, 2018 3:36 pm Post subject: |
|
|
![](images/avatars/136281076646ca0b3d89dee.gif) Jedi Knight
Joined: 15 May 2001 Posts: 3253 Location: London, ON Canada
|
When are you going to post the correct answer to my question of:
- Show me the Put-Appl Name from the message's MQMD for BOTH messages - one good & one bad
Note: I do NOT want to see your code.
Regards,
Roger Lacroix
Capitalware Inc. _________________ Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
Back to top |
|
![](templates/DAJ_Glass/images/spacer.gif) |
sathyapbe |
Posted: Thu Apr 19, 2018 11:44 pm Post subject: |
|
|
Novice
Joined: 16 Apr 2018 Posts: 21
|
It is empty, I haven't set any value for them. PFB,
Request without additional header:
WebSphere MQ (MQPUT)
Transmission Segment Header
API Header
Reply len..: 1238
Compl Code.: MQCC_OK (0)
Reason Code: MQRC_NONE (0)
Object Hdl.: 0x00000001
Message Descriptor
StructID.: MD
Version..: 1
Report...: 0
Msg Type.: 1
Expiry .: 3000
Feedback.: 0
Encoding.: 222-546 (FLT_IEEE_REVERSED/DEC_REVERSED/INT_REVERSED)
CCSID....: (1208)
Format...: MQSTR
Priority.: -1
Persist..: 2
Msg ID...: 000000000000000000000000000000000000000000000000
CorrelID.: 000000000000000000000000000000000000000000000000
BackoCnt.: 0
ReplyToQ.: XXXXX.XXX.RESPONSES
RepToQMgr: MPO1
UserId...:
AccntTok.: 000000000000000000000000000000000000000000000000...
AppIdData:
PutAppTyp: MQAT_NO_CONTEXT (0)
PutAppNme:
PutDatGMT:
PutTimGMT:
AppOriDat:
Put Message Options
MQPUT/MQGET
Data (732 bytes)
Request with additional headers:
WebSphere MQ (MQPUT)
Transmission Segment Header
StructID..: TSHM
MQSegmLen.: 1600
Convers ID: 1
Request ID: 0
Byte order: Little endian (0x02)
SegmType..: MQPUT (0x86)
Ctl Flag 1: 0x30, Last Seg, First Seg
Ctl Flag 2: 0x00
LUW Ident.: 0000000000000000
Encoding..: 222-546 (FLT_IEEE_REVERSED/DEC_REVERSED/INT_REVERSED)
CCSID.....: (1252)
Reserved..: 0x0000
API Header
Reply len..: 1598
Compl Code.: MQCC_OK (0)
Reason Code: MQRC_NONE (0)
Object Hdl.: 0x00000001
Message Descriptor
StructID.: MD
Version..: 1
Report...: 0
Msg Type.: 1
Expiry .: 3000
Feedback.: 0
Encoding.: 222-546 (FLT_IEEE_REVERSED/DEC_REVERSED/INT_REVERSED)
CCSID....: (1208)
Format...: MQHRF2
Priority.: -1
Persist..: 2
Msg ID...: 000000000000000000000000000000000000000000000000
CorrelID.: 000000000000000000000000000000000000000000000000
BackoCnt.: 0
ReplyToQ.: XXXXX.XXX.RESPONSES
RepToQMgr: MPO1
UserId...:
AccntTok.: 000000000000000000000000000000000000000000000000...
AppIdData:
PutAppTyp: MQAT_NO_CONTEXT (0)
PutAppNme:
PutDatGMT:
PutTimGMT:
AppOriDat:
Put Message Options
MQPUT/MQGET
Data length: 1090
Rules and Formatting Header
Data (732 bytes)
Data: 3c3f786d6c2076657273696f6e3d22312e302220656e636f...
[Length: 732] |
|
Back to top |
|
![](templates/DAJ_Glass/images/spacer.gif) |
RogerLacroix |
Posted: Fri Apr 20, 2018 2:09 pm Post subject: |
|
|
![](images/avatars/136281076646ca0b3d89dee.gif) Jedi Knight
Joined: 15 May 2001 Posts: 3253 Location: London, ON Canada
|
sathyapbe wrote: |
Request without additional header:
WebSphere MQ (MQPUT)
Transmission Segment Header
API Header
...
Request with additional headers:
WebSphere MQ (MQPUT)
Transmission Segment Header
StructID..: TSHM |
What in the #$@^& is that. Who asked you to pull stuff off the wire!!!!! And of which, you pulled it off the wire GOING to the queue manager which makes it TOTALLY useless.
Do you NOT know how to look at a message sitting in the queue with MQ Explorer or MQ Visual Edit or MO71 etc... ? Or even amqsbcg?
Come on, if you don't know MQ then GET SOME TRAINING. Or at least go to MQ Technical Conference. It is extremely cheap.
Regards,
Roger Lacroix
Capitalware Inc. _________________ Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
Back to top |
|
![](templates/DAJ_Glass/images/spacer.gif) |
sathyapbe |
Posted: Sun Apr 22, 2018 8:49 pm Post subject: |
|
|
Novice
Joined: 16 Apr 2018 Posts: 21
|
Sure, I will try to learn about Queues.
I am a C# .NET developer and this project message queues are remote and even we cant access the servers. Any possible way to force the request through client attribute values without additional headers. Please advise. |
|
Back to top |
|
![](templates/DAJ_Glass/images/spacer.gif) |
Vitor |
Posted: Mon Apr 23, 2018 5:15 am Post subject: |
|
|
![](images/avatars/905340816499abc1cdfb07.jpg) Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
sathyapbe wrote: |
Please advise. |
Tell whoever gave you this task that you're out of your depth and they should have given it to someone who understands MQ or to you after they'd given you some training.
Tell them that you've tried talking to some anonymous strangers on the Internet and not only could you not get an answer from them that you would not have been able to explain due to your lack of knowledge, you'd not have been able to support if it had gone wrong.
sathyapbe wrote: |
Any possible way to force the request through client attribute values without additional headers. |
What's that going to get you? You indicated in an earlier disjointed rambling that the same code works in environment but not the other. Hence the code is working fine, there's an environmental issue and even if you could explicitly set the code to eliminate the headers, what guarantee do you have that the same environmental setting will not ignore that and add the headers back?
If you're just a developer, and you don't know MQ, and you have no access to the servers, then you need someone who does know MQ and does have that access to fix this, or assist you in fixing this.
As Roger so eloquently intimated, you've reached the "desperately and randomly looking at things" stage of debugging. This will not help you and will irritate us. Get some onsite help from someone with the access and knowledge needed to resolve this problem. This may be unpopular with your site management, but sooner or later all managers must confront the painful truth - giving a problem to the wrong person to solve just because they're within reach means the problem doesn't get solved, no matter how much you shout, bully & threaten.
You wanted advice. That's mine.
Reality sucks. Things would be much better if the real world looked like the scenarios in management training, but it doesn't. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
![](templates/DAJ_Glass/images/spacer.gif) |
|
|
|
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
|
|
|
|