xml input stage not reading new xml file

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
skp
Premium Member
Premium Member
Posts: 135
Joined: Wed Dec 26, 2007 1:56 am
Location: India

xml input stage not reading new xml file

Post by skp »

Hi ,

I am getting a very weird issue when using xml file. My xsd has the pattern value as <xs:pattern value="[a-zA-Z \-]*"/> (size 40) which accepts a to z letters capitals and smaller plus '-' in between the word.

My New xml file having item code like 'Honda-model-B' which is throwing enumeration errors though the pattern is correct.
My old xml file has item code like 'Ford-escort-Un' which is accepting and completing the job with no issues.

Can some one let me know what would be the potential cause for this issue.

Thanks
eostic
Premium Member
Premium Member
Posts: 3838
Joined: Mon Oct 17, 2005 9:34 am

Post by eostic »

Hard to say...could be a lot of things. But here are some things to review...

a) uncheck "validation" to see if xsd checking of this pattern is truly the issue. Does the failure still occur.

b) validate the document with its xsd manually. There are tons of available online validators. One I have used is this one. See if it fails there. Maybe you will get different messages to help.

c) what release? Could be that there is some issue with the xalan/xerces (xml tooling used within the xmlInput Stage) in the release of Information Server that you are on.

d) try the hierarchical stage, which does things a bit different in regard to xsd import and validation of incoming content.

Ernie
Ernie Ostic

blogit!
<a href="https://dsrealtime.wordpress.com/2015/0 ... ere/">Open IGC is Here!</a>
UCDI
Premium Member
Premium Member
Posts: 383
Joined: Mon Mar 21, 2016 2:00 pm

Post by UCDI »

any chance it flipped your char encoding somewhere? Sometimes things like the - symbol are damaged (ms word will damage hyphens and quotes, for example, when it "autocorrects" the correct ascii symbol to some gibberish value).

I would check the source data string against the ascii chart if there is any possibility that the data itself looks correct but has "lookalike" bad symbols.
Post Reply