Subscribe to this APAR
By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.
APAR (Authorized Program Analysis Report) |
Abstract
OSP-DB-OTHER-F/QSQSSUDF-T/QSQSBAS2-MSGSQ20399 XML DOCUMENT
COULD NOT BE VALIDATED
Error Description
An XML decomposition incorrectly assigned an instance type.
This caused MSGSQ20399.
Problem Summary
When an XML schema includes decomposition annotations that map
an expression to a column of a table that does not have a
character type, the decomposition may fail.
For example if an annotation maps $DECOMP_DOCUMENTID to an
INTEGER column, the decomposition process will attempt to
validate $DECOMP_CONTENT (the contents of the element or
attribute) as an xs:integer type, even if the element itself is
not necessarily required to be integer.
Problem Conclusion
All expressions and conditions will treat $DECOMP_CONTENT as
type XSD_String when evaluating the expression. This will
prevent the unexpected mapping error.
An existing XML Schema may have to be recreated after the fix is
applied in order to get the correct instance type associated
with the annotation.
Temporary Fix
Comments
Circumvention
PTFs Available
R710 SI57572 6120
R720 SI57494 6127
Affected Modules
Affected Publications
Summary Information
Status............................................ | CLOSED PER |
HIPER........................................... | No |
Component.................................. | 5770SS1DB |
Failing Module.......................... | RCHMGR |
Reported Release................... | R710 |
Duplicate Of.............................. |
System i Support
IBM disclaims all warranties, whether express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. By furnishing this document, IBM grants no licenses to any related patents or copyrights. Copyright © 1996,1997,1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017 IBM Corporation. Any trademarks and product or brand names referenced in this document are the property of their respective owners. Consult the Terms of use link for trademark information
Document Information
Modified date:
21 May 2016