IBM Sterling Transformation Extender

Sterling Transformation Extender

Come for answers, stay for best practices. All we're missing is you.


#Sterling
#Supplychain
 View Only
  • 1.  Encoding Issues in WTX 8.3

    Posted 07/10/16 05:18 PM

    Originally posted by: mohit121happy


    Hi,

    I am reading the XML file(standard Pain001) and splitting it into multiple files in Output.
    After splitting the file, I am putting all the splitted xmls into disk(zos machine) by using the PUT function.

    In my Output xml files, some of the special(norwegain) characters are getting replaced and is not as expected like in Input.
    Input XML have characters          :- <Nm>Ola Normannø Å Æ @</Nm>
    Output XML it is converted like  :- <Nm>Ola NormannÝ $ [ Ø</Nm>

    Note : In both Input and Output, I am using the same Type Tree with UTF-8 encoding.
    Also I tried putting message into EBCDIC, but same Issue.

    Please suggest.Thanks


    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender
    #DataExchange


  • 2.  Re: Encoding Issues in WTX 8.3

    Posted 07/11/16 04:39 AM

    Originally posted by: paul.brett


    When you do that PUT() it will assume you want to convert to NATIVE first.  To force the engine not to do this, you need to 'fool' it into thinking the data is NATIVE already:

    =PUT("FILE","Filename.txt",CTEXT(UTF8OBJECT,"NATVE")

    This *should* solve your issue.

    Thank-you

    Paul

    Follow me on Twitter


    #DataExchange
    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender


  • 3.  Re: Encoding Issues in WTX 8.3

    Posted 07/11/16 07:25 AM

    Originally posted by: mohit121happy


    Hi Paul, Thanks for you advice,

    I have tried the suggested option and have have modified the PUT function with NATIVE type in CTEXT function.

    Now, the Output of XML file is in Binary form, so I am not able to validate the Output Splitted XML. But the Problem is still there as the End Output file is still having those Unknow characters.

     

    In our flow, we are passing this Splitted XML file (Output of First Map) as an Input to next Mapper which is suppose to generate text file as an Output from the Input XML.

    But the Output text file is still having those unknown characters instead of the one which is present in Input file.

    Important Point : Currently the second mapper is writing the Output in disk by calling sub map. I also tried using it with PUT function with CTEXT NATIVE mode, but then Mainframe system is not able to read the file due to encoding.If we PUT the file in ASCII,NATIVE,EBCDIC mode, then Mainframe is not able to read the files.

    Note : In my Windows local machine I am getting expected Output and correct characters. Problem is with the Output generated in zos machine.

    Please let me know if I am not able to exlpain it properly, I will then try to put more details.Thanks


    #DataExchange
    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender