ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » RHF2Header and parsing errors

Post new topic  Reply to topic
 RHF2Header and parsing errors « View previous topic :: View next topic » 
Author Message
fitzcaraldo
PostPosted: Wed Apr 25, 2007 8:26 pm    Post subject: RHF2Header and parsing errors Reply with quote

Voyager

Joined: 05 May 2003
Posts: 98
Broker V5 CSD4 on AIX
V5.3 MQSeries everywhere.

We have a strange parsing problem I can't solve.

We have a process on VMS that writes messages to queue that are directed to a broker flow. This process has worked fine in the past but recently was changed to add two extra fields. The message set is based on a copybook and uses TDS.

Since that change when the message arrives at the broker we get a parsing error claiming that a particular field is empty (it is not). There is a single bar containing the flow and the modified message set.

If we capture the suspect message and use RFH2Util (client connection) to replay the message it works fine - but ONLY if we add an RFH2Header to the message. If we attempt to replay the message without an RFH2Header (as was the original message from VMS) we get the same parsing error.

If we deploy the same bar to a local XP workstation broker (CSD4 again) and use RFHUtil (client connection) again to write the same message it works fine - with or without an RFH2Header.

Everything about the captured message appears to be fine, it has a format of MQSTR and codepage of 819.

Any ideas?
Back to top
View user's profile Send private message
smdavies99
PostPosted: Wed Apr 25, 2007 10:52 pm    Post subject: Trace and MQRFH2 Properties? Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
Have you put a trace node in the flow and captured the ${Root}?
This should help you see if Broker has properly decoded the message according to the message set.

It is strange that adding an RFH2 Header should 'fix' the problem.
What params are you adding to the RFH2 Header?
Remember if you add message set info, it overrides any message set properties on the MQ Input node. PErhaps there is a mismatch here? Be sure to check that the propertied in the RFH2 Header and your MQ Input Node are the same.
/S
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Back to top
View user's profile Send private message
fitzcaraldo
PostPosted: Wed Apr 25, 2007 11:25 pm    Post subject: Reply with quote

Voyager

Joined: 05 May 2003
Posts: 98
The only field I am supplying in the RFH2 (Via RFH2Util) are the Format=MQSTR field. No format (Domain/Set/Type) info is supplied so therefore uses the values on the MQInput node.

I will try the trace node approach (haven't used one of those for ages!) Might be a bit difficult as the brokers are all 'black boxes' with very little access.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » RHF2Header and parsing errors
Jump to:  



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
Protected by Anti-Spam ACP
  
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.