MQSeries.net :: View topic

ChiefBrody · Posted: Wed Mar 18, 2015 5:29 am Post subject:

Hi,

we mostly use the IIB 9.0.0.2 to communicate between C/S-systems and the IBM mainframe. Sometimes we run into the problem that we get characters from the C/S-system like "ě", that can't be mapped to EBCDIC 1141 and vice versa.
We have now designed our own CCSID that maps these characters to harmless codepoints ("ě" => "e"). This works fine for single string-fields but not for xml-messages in complete.

First approach:

Our plan was to make a BLOB from the incoming SOAP- or XML-message with our self designed CCSID an then to "reparse" the "cleaned" BLOB to an XML. This also works, but unfortunately the datatypes get lost. The resulting XML has only character fields.

Here's the code I tried in a compute node where validation is set to "value and content":

DECLARE options INTEGER BITOR (RootBitStream, ValidateContentAndValue, ValidateException);

DECLARE cleanedBLOB BLOB ASBITSTREAM(InputRoot.XMLNSC, InputRoot.Properties.Encoding, SelfDesignedCCSID, , , , options);

CREATE LASTCHILD OF Environment DOMAIN('XMLNSC') PARSE(cleanedBLOB, InputRoot.Properties.Encoding, InputRoot.Properties.CodedCharSetId, , , , options);

I tried this also with the SOAP-parser with the same result.

Is there a way to use the schema information from the wsdl that is present within the application? Most forum posts I've found deal with message set names, but I do not use MRM in IIB 9.0.0.2 as suggested by IBM itself.

Second approach:

We tried to use our self designed CCSID after the mapping, at the point where we make a BLOB from the mapped DFDL-message with the ASBITSTREAM function. This results in the following error:

ParserException
File:CHARACTER:F:\build\slot1\S900_P\src\MTI\MTIforBroker\DfdlParser\ImbDFDLErrorHandler.cpp
Line:INTEGER:313
Function:CHARACTER:ImbDFDLErrorHandler::handleSerializerErrors
Type:CHARACTER:ComIbmSOAPInputNode
Name:CHARACTER:MyFlow#FCMComposite_1_1
Label:CHARACTER:MyFlow.SOAP Input
Catalog:CHARACTER:BIPmsgs
Severity:INTEGER:3
Number:INTEGER:5832
Text:CHARACTER:An error occurred whilst serializing with DFDL
Insert
Type:INTEGER:5
Text:CHARACTER:CTDV1110E: CTDV1110E : DFDL-Eigenschaft 'encoding' muss ein gÃ¼ltiger IANA-Zeichensatz oder eine gÃ¼ltige ID des codierten Zeichensatzes oder ein Ausdruck sein, der eine der folgenden MÃ¶glichkeiten zurÃ¼ckgibt: Codierung '1151'. 痰⥗.
Insert
Type:INTEGER:5
Text:CHARACTER:/DFDL/REQUEST/HEADER/OPERATION

Any ideas?

Thanx