| Author |
Message |
 Topic: Migration Tips |
guest_2008
Replies: 2
Views: 1726
|
 Forum: WebSphere Message Broker (ACE) Support Posted: Thu Jun 01, 2006 12:01 pm Subject: Migration Tips |
Hi All,
We are planning to upgrade our system from WBIMB V5 to V6.
So what are the important points to be considered? Basically I am looking the impacts analyse for the below areas:
1. Configura ... |
| Topic: Problem with message version changing from 2 to version 1 |
guest_2008
Replies: 28
Views: 17280
|
Forum: General IBM MQ Support Posted: Sun May 28, 2006 3:19 pm Subject: Problem with message version changing from 2 to version 1 |
Hi All,
This topic is more useful and i have same MQMDE issue in our application,
As per our design ,we are talking the copy of message from channel using channel exit program and it is changin ... |
| Topic: MsgDesc "2".. |
guest_2008
Replies: 20
Views: 11852
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sat May 27, 2006 2:14 pm Subject: MsgDesc "2".. |
In the below i have posted the failed message header details :
XQH xxx_xxxxxxxxxxx_xxx.xxQ xxxxxxxxQM1 MD ÿÿÿÿ ... |
| Topic: MsgDesc "2".. |
guest_2008
Replies: 20
Views: 11852
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sat May 27, 2006 1:51 pm Subject: MsgDesc "2".. |
Hi..
Once again thanks for your link. Already I have this information and also I am able to understand the structure of MQMD and MQMDE but the problem is: What is combination (MQMD1+MQMDE) of heade ... |
| Topic: MsgDesc "2".. |
guest_2008
Replies: 20
Views: 11852
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sat May 27, 2006 1:41 pm Subject: MsgDesc "2".. |
Thanks Jeff ...
but we can't change the design at this point ? this is an one of our production issue !! |
| Topic: MsgDesc "2".. |
guest_2008
Replies: 20
Views: 11852
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sat May 27, 2006 12:09 pm Subject: MsgDesc "2".. |
Hi...
It is more useful your information’s, but I need to clarify the one more point...
Already we are stripping XQH (104byts) + MQMD1 (324 bytes) and reading the rfh2 header values from paylo ... |
| Topic: MsgDesc "2".. |
guest_2008
Replies: 20
Views: 11852
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sat May 27, 2006 6:15 am Subject: MsgDesc "2".. |
Thanks for your reply..
I can’t ignore the complete MQXQH and expecting unique values in the AppliIdentitydata field to our meet our business requirement and also the same flow is working fine wi ... |
| Topic: MsgDesc "2".. |
guest_2008
Replies: 20
Views: 11852
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sat May 27, 2006 4:48 am Subject: MsgDesc "2".. |
See,our design is :
Whatever the message is passing to broker, we are talking the copy of message from channel using channel exit program and it is changing the MQMD & payload information and t ... |
| Topic: MsgDesc "2".. |
guest_2008
Replies: 20
Views: 11852
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sat May 27, 2006 4:25 am Subject: MsgDesc "2".. |
We are not reading the XMitq valuse but if the message format is MQRFH2, then we are parsing the Rfh2 header to get the usr folder values.
If the application is sending the MQMD 2 message then we ... |
| Topic: MsgDesc "2".. |
guest_2008
Replies: 20
Views: 11852
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sat May 27, 2006 3:45 am Subject: MsgDesc "2".. |
Hi,
The logic behind this...
Input message is passed to the input node and MQXQH values are verified using MRM and the same header values loaded into local environment
Input Root = MQXQH a ... |
| Topic: MsgDesc "2".. |
guest_2008
Replies: 20
Views: 11852
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri May 26, 2006 12:59 pm Subject: MsgDesc "2".. |
Hi Wayne,
Thanks for your mail...
I have message flow which is reading the message and doing the following steps:
1. Using MRM (message set) parsed the MQMD1 version values and removing 424 b ... |
| Topic: MsgDesc "2".. |
guest_2008
Replies: 20
Views: 11852
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri May 26, 2006 9:07 am Subject: MsgDesc "2".. |
Hi,
Thanks for your reply...
Now I am able to understand the MQMD version2 structure, actually it is
MQMD2 = MQMD1+MQMDE
I am using the MRM message set and reading payload data for parsing th ... |
| Topic: MQRFH2 parser exception |
guest_2008
Replies: 7
Views: 4629
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri May 26, 2006 3:57 am Subject: MQRFH2 parser exception |
Hi fjb,
Thanks for your mail,
Yeah you are correct! But I am not processing the message from XmitQ,.
Actually we are parsing the RFH2 header values from the payload and storing those values in ... |
| Topic: MsgDesc "2".. |
guest_2008
Replies: 20
Views: 11852
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri May 26, 2006 3:28 am Subject: MsgDesc "2".. |
Hi All,
What is the different between the MQMD V1 & V2 message types?
In the payload message we are getting RFH2 header is prefixed with MQMDE header and unable parse the RFH2 header and esq ... |
