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 » CDATA error

Post new topic  Reply to topic
 CDATA error « View previous topic :: View next topic » 
Author Message
vandi
PostPosted: Thu Jan 22, 2009 1:28 pm    Post subject: CDATA error Reply with quote

Acolyte

Joined: 13 Dec 2008
Posts: 67

Hi ALL,

I am trying to extract content of the message from XML message and put in the CDATA section.

For ex: The below one is my xml message. I want to extract Name Info ad put in CDATA.

<Staff>
<StaffNumber>99</StaffNumber>
<NameInfo>
<LastName>Doe</LastName>
<FirstName>Jane</FirstName>
</NameInfo>
</Staff>



I have given

SET OutputRoot.XMLNS.Z.(XML.CDataSection) =
CAST(ASBITSTREAM(InputRoot.XMLNS.Staff.NameInfo OPTIONS FolderBitStream) AS CHAR
CCSID InputRoot.MQMD.CodedCharSetId ENCODING InputRoot.MQMD.Encoding)

Once the control comes out of compute Node and message is written to MQOUTPUT node. I am getting Parsing error in MQ output node.

Please let me know where I am going wrong.
javascript:emoticon('')
Back to top
View user's profile Send private message
kimbert
PostPosted: Fri Jan 23, 2009 1:36 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

Quote:
I am getting Parsing error in MQ output node.
Please quote the error. If necessary, take a user trace to get the full error text, or look in the system event log.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Fri Jan 23, 2009 3:51 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

Also it is unhealthy when you cast your bitstream as char to set it to the CCSID of the Input as you did not specify a CCSID in your ASBITSREAM command. Suggestion use the same CCSID in both ASBITSTREAM and CAST... You might be hitting some weird CCSID translation problem especially if your input message was in EBCDIC....

Now if due to that fact some character translates into something that is not authorized for the CData section you are SOL.

Review ASBITSTREAM syntax

Let's see with input message in CCSID 500.... and broker CCSID = 819

You are creating the bitstream in CCSID 0 (defaults to the platform the broker is on. Check value with mqsiservice -v? ). If the broker is running on Unix under CCSID 819 you might get 819 here. Better to set the CCSID explicitely... You are then casting this to a char using CCSID 500 on the BLOB ... and you expect something else than gibberish???

Have fun.
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
vandi
PostPosted: Fri Jan 23, 2009 12:48 pm    Post subject: Reply with quote

Acolyte

Joined: 13 Dec 2008
Posts: 67

Thanks Saper. I am able to do it.
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 » CDATA error
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.