Originally posted by: SystemAdmin

Hello,
I am testing WTX 8.4.0.3 and I tried to use z/OS XML System Services.

Manual says like this:
“To use z/OS XML System Services to parse an XML document, supply the input schema as a binary Optimized Schema Representation (OSR) file. Use the z/OS xsdorg command to generate the OSR file. Specify the path to the OSR file in the Schema > Type > Metadata property of the input card "

I have used the z/OS xsdorg command to create OSR-file from schema.
Because I run my map in z/os, input card’s definitions is like this: Schema -> Type -> Metadata -> //DD:PN010103
In my execution JCL, PN010103 points to OSR-file like this: //PN010103 DD PATH='/tmp/o.osr',PATHOPTS=(ORDONLY)

I have two version of the map, one where input TypeTree is imported from schema and other where input TypeTree is native schema.

With native schema input TypeTree, I get these error messages:
(Level 0: Offset 0, len 0, comp 1 of 0, Ä1, DI 000000000001:)
External Parser returned Error:
TYPE X'0002' (XMLParser: Invalid metadata location.).
With input TypeTree imported from schema, I get these error messages:
(Level 2: Offset 0, len 3, comp 1 of 3, Ä1, DI 000000000001:)
Data at offset 0 ('<?x') was found to be of TYPE
X'0005' (version Prolog XSD).
(Level 2: Offset 0, len 8, comp 2 of 3, Ä1, DI 000000000002:)
Data at offset 0 ('<?xml ve') was found to be of TYPE
X'0006' (encoding Prolog XSD).
(Level 1: Offset 0, len 41, comp 1 of 2, Ä1, DI 000000000003:)
Data at offset 0 ('<?xml version="1...') was found to be of TYPE
X'0004' (Decl Prolog XSD).
(Level 0: Offset 0, len 406, comp 1 of 0, Ä1, DI 000000000004:)
Data at offset 0 ('<?xml version="1...') is INVALID data of TYPE
X'0002' (Doc XSD).
(Level 0: Offset 0, len 406, comp 1 of 0, Ä1, DI 000000000005:)
External Parser returned Error:
TYPE X'0002' (Error (-1), "XMLParser: Input XML data is invalid."
SAXParseException, Fatal error Ýline: 1 column: 1¨ An exception occurred€ Type:UTFDataFormatException, Message:invalid byte (X) of a -byte sequence.
Error (-1), "XMLParser: Input XML data is invalid."
SAXParseException, Fatal error Ýline: 12 column: 26¨ Fatal error encountered during schema scan

If //PN010103 points to "normal" schema file both maps run fine.

I am quite lost with this. Can anyone please help me.

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

Originally posted by: N8JUC

It looks like your XML is in EBCDIC, and I'm going to guess (because I haven't seen it) that it says "encoding=UTF-8" on the first line of your XML. The actual encoding and the declared encoding in the "<!xml> statement must match. XML standards, by the way, state that in absence of an "encoding" declaration the encoding is UTF-8. Your DD statement seems OK, check to be sure your file is still in /tmp. Many sysprogs have an automated cleaning for /tmp to be sure it doesn't fill.

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

Originally posted by: SystemAdmin

Thank you for your answer,
Yes my XML is EBCDIC and first line in XML-document like this : <?xml version="1.0" encoding="IBM-1143"?>
IBM-1143 is for finnish/swedish EBCDIC. So this is should be right.

And maps run fine when //PN010103 points to "normal" schema file.

And yes my OSR-file is still in place in tmp folder.

I am still very lost with this and would appreciate any help.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: N8JUC

This is an "is it plugged in?" question, but are you running release 8.4?
Packaged with release 8.4 is some JCL that will run xsdsorg and copy the
result into a dataset. Its in the samples dataset SDTXSAMP(DTXSDJCL)
and set the //PN010103 DD to point to the dataset that DTXSDJCL creates.
Good Luck
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

Thank you again for your answer,
I am sorry but I don't quite understand what you mean by "is it plugged in?" question.

Yes I am using WTX8.4 and I have used sample JCL SDTXSAMP(DTXSDJCL). Our system programmer had to change it a little bit, to get it work in our environmet, but the result OSR-file should be right.

I have tested this same OSR-file with Cobol- program which does XML PARSE VALIDATING WITH FILE.
And OSR-file works fine with Cobol.

So I have a strong feeling that my problem is in WTX. I have something wrong there but I don't have any clue what it could be.

I appreciate your help
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: N8JUC

Sorry, "is it plugged in" is an apology in advance for asking a question where the answer is obvious and the person you asked probably already checked. As in when grandma's television doesn't work. I've failed to ask that kind of question in the past and it cost time and frustration.

You're right. It does appear broken. And thanks for checking on the OSR. I think you should open a PMR. Please tell them I sent you and mention this conversation.

Best Regards,
John
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: SystemAdmin

Thank you for yor help John,

We will open a PMR.

• Riitta -

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

Originally posted by: N8JUC

I think (without seeing your test case) that I've duplicated your problem. I've opened an internal tracking item.

Best Regards,
John
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: Laurent(Satisco)

Hello,

 

I'm at a client site and we're encountering a very similar issue in 8.4.1.

 

Did this internal tracking gather some results, may be in terms of updating some components or whatever?

 

Laurent

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

Originally posted by: paul.brett

I attach a fully working IBM-1143 example.  Is is very simple, though perhaps you could use this to do basic sanity checking of your environment.

I have been unable to test retrieving the OSR data from an HFS file, as I keep getting 'Invalid METADATA location' errors.

Thank-you.

Paul

Follow me on Twitter

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