MQMD MsgId is changed - Why - Need Explainination

Discussion:

AkBar Dar

2013-10-11 14:26:48 UTC

I need explanation, why is MsgId changing after messages is consumed in SAP.

Message is received from MQInput Node in MQ Queue, MsgId is:

414D5120555549444130312020202020524F3E442009BC4D

Then I create a SAP Control Record and take backup of the MQ Message, and MQ MsgId is still:

414D5120555549444130312020202020524F3E442009BC4D

But, When Message goes successfully through the SAP Request Node, then the MsgId is changed as:

Before SAP Node: 414D5120555549444130312020202020524F3E442009BC4D
After SAP Node: 414D5120555549444130312020202020524F3E4420088E0D

As you can MsgId is slightly different, any idea why?

Regards,
AkBar Dar

Telecommute Day: Wednesday

Disclaimer This e-mail, and any attached file(s), is intended solely for the use of the individual or entity to whom this e-mail is addressed and may contain information that is privileged, confidential or exempt from disclosure. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender or call UI at 203-499-2222 and delete this message immediately from any computer. Any other use, retention, dissemination, retransmission, printing or copying of this e-mail or its contents (including any attached files) is strictly prohibited.

To unsubscribe, write to LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html

Jason Space

2013-10-11 15:05:31 UTC

Permalink

Not familiar with SAP & MQ, how they work together, so this may not hold
much water......

After SAP consumes the message, I assume it's putting a "new" message back
onto a queue and this is where you see the MSGID change? If that is the
cause then it sounds like after SAP does its thing and puts the message
back, the put program is specifying MQPMO-NEW-MSG-ID.

From: AkBar Dar <Akbar.Dar-***@public.gmane.org>
To: MQSERIES-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org
Date: 10/11/2013 10:27 AM
Subject: MQMD MsgId is changed - Why - Need Explainination
Sent by: MQSeries List <MQSERIES-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org>

I need explanation, why is MsgId changing after messages is consumed in
SAP.

Message is received from MQInput Node in MQ Queue, MsgId is:

414D5120555549444130312020202020524F3E442009BC4D

Then I create a SAP Control Record and take backup of the MQ Message, and
MQ MsgId is still:

414D5120555549444130312020202020524F3E442009BC4D

But, When Message goes successfully through the SAP Request Node, then the
MsgId is changed as:

Before SAP Node: 414D5120555549444130312020202020524F3E44200
9BC4D
After SAP Node: 414D5120555549444130312020202020524F3E44200
88E0D

As you can MsgId is slightly different, any idea why?

Regards,
AkBar Dar

Telecommute Day: Wednesday

Disclaimer This e-mail, and any attached file(s), is intended solely for
the use of the individual or entity to whom this e-mail is addressed and
may contain information that is privileged, confidential or exempt from
disclosure. If you are not one of the named recipient(s) or otherwise have
reason to believe that you have received this message in error, please
notify the sender or call UI at 203-499-2222 and delete this message
immediately from any computer. Any other use, retention, dissemination,
retransmission, printing or copying of this e-mail or its contents
(including any attached files) is strictly prohibited.

List Archive - Manage Your List Settings - Unsubscribe
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com

To unsubscribe, write to LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html

Peter D

2013-10-11 15:56:13 UTC

Permalink

Yes that would occur from not only SAP but from any external integration - a Put is always a 'new' Put - thus creating new MsgID. This would likely be the case in a transformed Broker message too ( internal to your MQ env), where a message is consumed, transformed, and routed (Put) to another destination.

Of course that's the point of a best practice for the developers to move the MsgID to the CorrelID so that you can "correlate" that they are in fact a result of the same initial message.

/Pete

Not familiar with SAP & MQ, how they work together, so this may not hold much water......
After SAP consumes the message, I assume it's putting a "new" message back onto a queue and this is where you see the MSGID change? If that is the cause then it sounds like after SAP does its thing and puts the message back, the put program is specifying MQPMO-NEW-MSG-ID.
Date: 10/11/2013 10:27 AM
Subject: MQMD MsgId is changed - Why - Need Explainination
I need explanation, why is MsgId changing after messages is consumed in SAP.
414D5120555549444130312020202020524F3E442009BC4D
414D5120555549444130312020202020524F3E442009BC4D
Before SAP Node: 414D5120555549444130312020202020524F3E442009BC4D
After SAP Node: 414D5120555549444130312020202020524F3E4420088E0D
As you can MsgId is slightly different, any idea why?
Regards,
AkBar Dar
Telecommute Day: Wednesday
Disclaimer This e-mail, and any attached file(s), is intended solely for the use of the individual or entity to whom this e-mail is addressed and may contain information that is privileged, confidential or exempt from disclosure. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender or call UI at 203-499-2222 and delete this message immediately from any computer. Any other use, retention, dissemination, retransmission, printing or copying of this e-mail or its contents (including any attached files) is strictly prohibited.
List Archive - Manage Your List Settings - Unsubscribe
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com
List Archive - Manage Your List Settings - Unsubscribe
Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com

To unsubscribe, write to LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html

T.Rob

2013-10-11 19:50:22 UTC

Permalink

All of which can be easily seen with the MA0W API Trace exit. It shows the control blocks before and after the API call and translates the bit flags to human-readable text. Highly recommended tool. If you haven't used it, it's worth investing some time to get to know it.

http://ibm.co/SupptPacMA0W

-- T.Rob

From: MQSeries List [mailto:MQSERIES-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org] On Behalf Of Peter D
Sent: Friday, October 11, 2013 11:56 AM
To: MQSERIES-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org
Subject: Re: MQMD MsgId is changed - Why - Need Explainination

Yes that would occur from not only SAP but from any external integration - a Put is always a 'new' Put - thus creating new MsgID. This would likely be the case in a transformed Broker message too ( internal to your MQ env), where a message is consumed, transformed, and routed (Put) to another destination.

Of course that's the point of a best practice for the developers to move the MsgID to the CorrelID so that you can "correlate" that they are in fact a result of the same initial message.

/Pete

On Oct 11, 2013, at 11:05 AM, Jason Space <Jason.Space-Mw4k1ySBmo6R4N/***@public.gmane.org> wrote:

Not familiar with SAP & MQ, how they work together, so this may not hold much water......

After SAP consumes the message, I assume it's putting a "new" message back onto a queue and this is where you see the MSGID change? If that is the cause then it sounds like after SAP does its thing and puts the message back, the put program is specifying MQPMO-NEW-MSG-ID.

From: AkBar Dar <Akbar.Dar-***@public.gmane.org>
To: MQSERIES-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org
Date: 10/11/2013 10:27 AM
Subject: MQMD MsgId is changed - Why - Need Explainination
Sent by: MQSeries List <MQSERIES-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org>

_____

I need explanation, why is MsgId changing after messages is consumed in SAP.

Message is received from MQInput Node in MQ Queue, MsgId is:

414D5120555549444130312020202020524F3E442009BC4D

Then I create a SAP Control Record and take backup of the MQ Message, and MQ MsgId is still:

414D5120555549444130312020202020524F3E442009BC4D

But, When Message goes successfully through the SAP Request Node, then the MsgId is changed as:

Before SAP Node: 414D5120555549444130312020202020524F3E442009BC4D
After SAP Node: 414D5120555549444130312020202020524F3E4420088E0D

As you can MsgId is slightly different, any idea why?

Regards,
AkBar Dar

Telecommute Day: Wednesday

Disclaimer This e-mail, and any attached file(s), is intended solely for the use of the individual or entity to whom this e-mail is addressed and may contain information that is privileged, confidential or exempt from disclosure. If you are not one of the named recipient(s) or otherwise have reason to believe that you have received this message in error, please notify the sender or call UI at 203-499-2222 and delete this message immediately from any computer. Any other use, retention, dissemination, retransmission, printing or copying of this e-mail or its contents (including any attached files) is strictly prohibited.

_____

<http://listserv.meduniwien.ac.at/archives/mqser-l.html> List Archive - <http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> Manage Your List Settings - <mailto:LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org?subject=Unsubscribe&BODY=signoff%20mqseries> Unsubscribe

Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at <http://www.lsoft.com/resources/manuals.asp> http://www.lsoft.com

_____

List Archive <http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage Your List Settings <http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> - Unsubscribe <mailto:LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org?subject=Unsubscribe&BODY=signoff%20mqseries>

Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com <http://www.lsoft.com/resources/manuals.asp>

_____

List Archive <http://listserv.meduniwien.ac.at/archives/mqser-l.html> - Manage Your List Settings <http://listserv.meduniwien.ac.at/cgi-bin/wa?SUBED1=mqser-l&A=1> - Unsubscribe <mailto:LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org?subject=Unsubscribe&BODY=signoff%20mqseries>

Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com <http://www.lsoft.com/resources/manuals.asp>

To unsubscribe, write to LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html

Bob Juch

2013-10-11 20:46:58 UTC

Permalink

Pete,

Well that's one standard but so also is always keeping the CorrelID
the same from request to response.

Bob Juch
Juch Services LLC

Post by Peter D
Yes that would occur from not only SAP but from any external integration - a
Put is always a 'new' Put - thus creating new MsgID. This would likely be
the case in a transformed Broker message too ( internal to your MQ env),
where a message is consumed, transformed, and routed (Put) to another
destination.
Of course that's the point of a best practice for the developers to move the
MsgID to the CorrelID so that you can "correlate" that they are in fact a
result of the same initial message.
/Pete
Not familiar with SAP & MQ, how they work together, so this may not hold
much water......
After SAP consumes the message, I assume it's putting a "new" message back
onto a queue and this is where you see the MSGID change? If that is the
cause then it sounds like after SAP does its thing and puts the message
back, the put program is specifying MQPMO-NEW-MSG-ID.
Date: 10/11/2013 10:27 AM
Subject: MQMD MsgId is changed - Why - Need Explainination
________________________________
I need explanation, why is MsgId changing after messages is consumed in SAP.
414D5120555549444130312020202020524F3E442009BC4D
Then I create a SAP Control Record and take backup of the MQ Message, and MQ
414D5120555549444130312020202020524F3E442009BC4D
But, When Message goes successfully through the SAP Request Node, then the
414D5120555549444130312020202020524F3E442009BC4D
414D5120555549444130312020202020524F3E4420088E0D
As you can MsgId is slightly different, any idea why?
Regards,
AkBar Dar
Telecommute Day: Wednesday
Disclaimer This e-mail, and any attached file(s), is intended solely for the
use of the individual or entity to whom this e-mail is addressed and may
contain information that is privileged, confidential or exempt from
disclosure. If you are not one of the named recipient(s) or otherwise have
reason to believe that you have received this message in error, please
notify the sender or call UI at 203-499-2222 and delete this message
immediately from any computer. Any other use, retention, dissemination,
retransmission, printing or copying of this e-mail or its contents
(including any attached files) is strictly prohibited.
________________________________
List Archive - Manage Your List Settings - Unsubscribe
Instructions for managing your mailing list subscription are provided in the
Listserv General Users Guide available at http://www.lsoft.com
________________________________
List Archive - Manage Your List Settings - Unsubscribe
Instructions for managing your mailing list subscription are provided in the
Listserv General Users Guide available at http://www.lsoft.com
________________________________
List Archive - Manage Your List Settings - Unsubscribe
Instructions for managing your mailing list subscription are provided in the
Listserv General Users Guide available at http://www.lsoft.com

To unsubscribe, write to LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org and,
in the message body (not the subject), write: SIGNOFF MQSERIES

Peter D

2013-10-12 05:25:21 UTC

Permalink

Agreed - once it's moved there, keep it so that it's contiguous through the transaction.

/Pete

Post by Bob Juch
Pete,
Well that's one standard but so also is always keeping the CorrelID
the same from request to response.
Bob Juch
Juch Services LLC

in the message body (not the subject), write: SIGNOFF MQSERIES
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html

To unsubscribe, write to LISTSERV-0lvw86wZMd9k/bWDasg6f+***@public.gmane.org and,
in the message body (not the subject), write: SIGNOFF MQSERIES