| Author |
Message
|
| mqjeff |
 Posted: Sat Jun 25, 2011 11:47 am Post subject: |
 |
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Both the CCSID and the Encoding should properly match the contents of the message.
If you choose to allow your users to set these fields to random, non-meaningful values, then you should educate your users that this can and/or will cause issues including MQRCs. |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Sat Jun 25, 2011 11:49 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| mqjeff wrote: |
I would use MQ v7 Message Properties instead of an RFH header.
These should get mapped to RFH headers when moving to a v6 qmgr or when connecting to a v6 qmgr (to the best of my knowledge). |
Or if the property control attribute of the destination is set to COMPAT or RFH2 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| rekarm01 |
| Posted: Sat Jun 25, 2011 1:27 pm Post subject: Re: Java API: MQRC 2421 writing RFH2 on certain platforms |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| notoneword wrote: |
| if I set the Encoding of the message to 546, I'll get 2421 errors again. |
Which Encoding is that? MQMD.Encoding, or MQRFH2.Encoding?
The MQMD.Encoding describes the expected byte order of the MQLONG fields in the MQRFH2 Header, (including any optional NameValueLength fields).
| notoneword wrote: |
| MQBYTE[] NameValueData: 0x00000014424d4d41444d494e3a524648322d4d5347202020 |
That part is a bit misleading. It ought to look more like:
| Quote: |
MQLONG NameValueLength: 20 (0x00000014)
MQBYTE[] NameValueData: 0x424d4d41444d494e3a524648322d4d5347202020 |
|
|
| Back to top |
|
|
| notoneword |
| Posted: Sat Jun 25, 2011 3:34 pm Post subject: |
|
|
Apprentice
Joined: 17 May 2011
Posts: 37
|
| Quote: |
| Which Encoding is that? MQMD.Encoding, or MQRFH2.Encoding? |
Sorry, good point - MQMD.Encoding was set to 546. I can't recall if the MQRFH2.Encoding value was 546 at that point or not. |
|
| Back to top |
|
|
| sumit13 |
| Posted: Wed Jul 20, 2011 4:26 am Post subject: RC2421 with MQ7.0.1.3 |
|
|
Newbie
Joined: 20 Jul 2011
Posts: 3
|
| We recently migrated to MQ7.0.1.3, since then i am getting error for RFH2 header. Same code was working fine earlier. We are not taking care of RFH Struclength to be multiplied of 4 and we are not using any folder name in header. Please suggest if any of them could be issue, because i can not make changes on code(I can make changes only if the things are pretty sure). We are using it on AIX platform and not using JMS. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jul 20, 2011 4:34 am Post subject: Re: RC2421 with MQ7.0.1.3 |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| sumit13 wrote: |
| We recently migrated to MQ7.0.1.3 |
From what? What version was it working fine in? Why not go to WMQ7.0.1.5 (as per IBM's recommendation earlier in this post)?
| sumit13 wrote: |
| We are not taking care of RFH Struclength to be multiplied of 4 |
Oops.
| sumit13 wrote: |
| and we are not using any folder name in header. |
Oops.
| sumit13 wrote: |
| Please suggest if any of them could be issue, because i can not make changes on code(I can make changes only if the things are pretty sure). |
Well based on this thread & general information then yes, any of them could be the issue. Is it pretty sure they're the issue? It's pretty sure something is the issue with your code so you're probably going to end up making changes. Changes for these issues? Who can say?
Why not change your code to use JMS/XMS (as also suggested earlier in this thread)?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jul 20, 2011 11:30 am Post subject: Re: RC2421 with MQ7.0.1.3 |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| sumit13 wrote: |
| We recently migrated to MQ7.0.1.3, since then i am getting error for RFH2 header. Same code was working fine earlier. We are not taking care of RFH Struclength to be multiplied of 4 and we are not using any folder name in header. Please suggest if any of them could be issue, because i can not make changes on code(I can make changes only if the things are pretty sure). We are using it on AIX platform and not using JMS. |
You are at MQ V 7... Why build an RFH at all. Use the V7 properties and set the queue's propctl attribute to have the qmgr create the RFH for you.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| sumit13 |
| Posted: Wed Jul 20, 2011 11:20 pm Post subject: |
|
|
Newbie
Joined: 20 Jul 2011
Posts: 3
|
Thanks for the replies 
We have migrated MQ from v6 to v7.
It is working fine by introducing folder name in header, however the other end is still at v6 and they were getting error in parsing the header. I can not suggest adjustment for them to remove folder name.
I found that PROPCTL queue option on IBM site, which can be set to FORCE so that it will work as v6. We have one queue manager and several queue and only one of them used RFH2 header. So PROPCTL = FORCE option need to be applied on a particular queue(not on queue manager) and other queue will remain unaffected.
And this I have to do on GET side not on PUT side, Please correct if I am wrong in. |
|
| Back to top |
|
|
| sumit13 |
| Posted: Thu Jul 21, 2011 5:36 am Post subject: |
|
|
Newbie
Joined: 20 Jul 2011
Posts: 3
|
| For the above post, i guess changing queue attribute will work if the receiving queue is upgraded from v6 to v7. Do we have similar option if the queue from which we are putting the data is upgraded from v6 to v7. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Jul 21, 2011 7:47 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| sumit13 wrote: |
| For the above post, i guess changing queue attribute will work if the receiving queue is upgraded from v6 to v7. Do we have similar option if the queue from which we are putting the data is upgraded from v6 to v7. |
If you are putting to V7 the channel process is supposed to handle the transformation if the destination is V6.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
