×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On Tue, 5 Mar 2013, at 21:26:49, Lim Hock-Chai <Lim.Hock-Chai@xxxxxxxxxxxxxxx> wrote:
Yes, those are the options I'm using. As far as I can tell, when XML-INTO encountered a mapping error, it will abort the rest of mapping.
This is why IBM recommend that you never specify numerics as such in the target DS. If there is any chance that a non-numeric or mal-formed numeric value might be present.
Unless you originate the XML and can be certain that all numerics are indeed valid then you should define the target field as alpha and validate it your self - that way you can control the error and not have the parser die. Even if IBM were to fix your current problem there's still a possibility that there would be invalid characters in any numerics - would you want them to be set to zeros and the error not reported?
Another option would be to run a validator against the XML and perform an xslt transform to set the null entries to whatever default value you want.
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
