MQSeries.net :: View topic - Reset Content Descriptor on OS390

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Reset Content Descriptor on OS390

Reset Content Descriptor on OS390

« View previous topic :: View next topic »

Author

Message

Coz

Posted: Thu Jul 11, 2002 11:23 pm Post subject: Reset Content Descriptor on OS390

Apprentice

Joined: 20 Feb 2002
Posts: 44
Location: Basel CH

Has anybody had any problems with one of these?
I am extracting a message from a database as a blob and runing it through a RCD to get it into the XML Domain.
As is usual this works fine on NT (2.1 CSD 2) but the flow is having problems on OS390 with the RCD rejecting the message saying it is not good XML.

Interestingly I can get the same error message

( MQSI2.default ) An error has been reported by the BIPXML4C component: code '22'; public id ''; line number '1'; column number '1'; current element 'XML'; error text 'Invalid document structure'.

The above error was reported by the XML parser.

Check that the XML message is well-formed and that it adheres to the XML specification.

- from the NT system by passing the EBCIDIC message through an RCD from BLOB to XML.

kirani

Posted: Fri Jul 12, 2002 8:03 am Post subject:

Jedi Knight

Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA

Coz,
Do you have ExceptionList for above error message?
Could you add a trace node after your compute node, where you are retrieving xml message from database and post the contents here.
_________________
Kiran

IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries

Coz

Posted: Fri Jul 12, 2002 11:53 am Post subject:

Apprentice

Joined: 20 Feb 2002
Posts: 44
Location: Basel CH

Hmm. i've dropped a bit of a clanger in saying that errors are the same after rechecking they aren't. OS390 complains about a an attribute expected which makes me suspect that the fault is a bit more obtuse.

I have done a flow on NT which will convert the BLOB to CHAR so i can at least see the data in RFHUTIL and will simply port the flow to OS390 on Monday and run the blob info thro it. Will post results then but I do suspect this is a fault with the RCD on OS390 which will need to be posted to IBM as the flow works quite happily on NT grabbing data from

Interesting to note that at the Vienna IBM symposium the DB2 rep was a bit dismayed to hear about the way an XML message held in a db as a CLOB cant be placed correctly in the XML parsing tree. I will be following this up with her cos quote 'What? But BLOBS are useless as you cant do anything with them.'

moogoo

Posted: Wed Nov 20, 2002 7:12 pm Post subject:

Acolyte

Joined: 20 Sep 2002
Posts: 54
Location: US

Is this true using an Oracle 8.1.x database and setting the XML attribute "AsisElementContent" (which should generate XML as long as its well formed)?

MG

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Reset Content Descriptor on OS390

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