IBM Support

PM28385: MULTIPLE FIXES IN THIS APAR: ABEND04E DSNNXML.DSNNOGET:M770

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Multiple V10 XML problems
    

Local fix

  • No Work Around
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 10 for z/OS users of XML.            *
    ****************************************************************
    * PROBLEM DESCRIPTION: DB2 10 for z/OS problems related with   *
    *                      XML:                                    *
    *                        1. ABEND04E RC00E70005                *
    *                           DSNNXML.DSNNOGET:M770              *
    *                           when the XMLMODIFY function is     *
    *                           used.                              *
    *                                                              *
    *                        2. ABEND0C4 DSNIDM.DSNICUMW+363A      *
    *                           after an UPDATE or a DELETE occurs *
    *                           on an XML column that supports     *
    *                           XML versions.                      *
    *                                                              *
    *                        3. ABEND0C4 DSNNXML.DSNNRXSG+096A     *
    *                           when XML Schema validation occurs  *
    *                           for the DSN_XMLVALIDATE function.  *
    *                                                              *
    *                        4. ABEND04E RC00E2000F DSNSVSFB+0846  *
    *                           after an XPath expression          *
    *                           processes a large number of        *
    *                           atomic values.                     *
    *                                                              *
    *                        5. Incorrect result from the          *
    *                           the XMLTABLE function when a       *
    *                           column XPath expression contains   *
    *                           a predicate that is not in the     *
    *                           last step.                         *
    *                                                              *
    *                        6. ABEND04E RC00E70005                *
    *                           DSNXGRDS.DSNXEFDA:M500             *
    *                           when there is an 'and' operator    *
    *                           in an XPath predicate.             *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
     1. ABEND04E RC00E70005 DSNNXML.DSNNOGET:M770 occurred when
        the XMLMODIFY function was used. There was a logic error
        in updating a large XML document using the XMLMODIFY
        function.
    
        ABEND04E RC00C90101 DSNIDM.DSNILREP ERQUAL(53BB) can
        occur if the XMLMODIFY function is used to update
        an XML column with an XMLSCHEMA. There was a logic
        error when a large XML document that was updated by the
        XMLMODIFY function needed to be validated against
        an XML schema.
    
        If the UPDATE statement updated many XML documents using
        the XMLMODIFY function, memory used for processing
        the XMLMODIFY function was not freed after processing
        each XML document.  This could cause the XML storage
        limit to be reached resulting in SQLCODE904 to be
        returned with RESOURCE 0000090A.
    
        In addition, after the XMLMODIFY function updated an
        XML document, there was unnecessary logic to check
        the updated XML document. This logic is removed to
        improve the XMLMODIFY performance.
    
     2. The ABEND0C4 DSNIDM.DSNICUMW+363A occurred after an
        UPDATE or a DELETE on an XML column that supports
        XML versions.  There was a logic error when deleting
        XML versions that were no longer needed.
    
     3. The ABEND0C4 DSNNXML.DSNNRXSG+096A occurred when an
        XML document was validated against an XML schema.
        Information about the XML schemas was kept in a cache.
        A logic error in searching the cache for an XML schema
        caused the ABEND0C4 DSNNXML.DSNNRXSG+096A.
    
     4. ABEND04E RC00E2000F DSNSVSFB+0846 occurred when an
        XPath expression processed a large number of atomic values.
    
        When an XMLQUERY function processed a large number of
        atomic values, there was a logic error in calculating
        the node ID for the atomic values, causing the storage
        overlay to occur.
    
     5. Incorrect result from the XMLTABLE function occurred
        when a column XPath expression contained a predicate in
        a step that is not the last step.  The following is an
        example of a SQL statement that has the problem:
    
        SELECT X.*
        FROM T1,
             XMLTABLE('/a'
                      COLUMNS B VARCHAR(10) PATH 'b c=5 /d') X
    
        The  c=5  is the predicate that is not in the last step.
        This predicate was not processed correctly, causing the
        XMLTABLE function to return an incorrect result.
    
     6. ABEND04E RC00E70005 DSNXGRDS.DSNXEFDA:M500 occurred when
        there was an 'and' operator in an XPath predicate.
        In the following example, there is an 'and' operator in
        the XPath predicate.
    
        SELECT XMLQUERY(
         '$po/purchaseOrder/items/item @partNum<4 and @partNum>2 '
          PASSING po as "po")
        FROM purchaseorders;
    
        Executing this query might cause the ABEND04E.
    

Problem conclusion

  • The XML specific problems were fixed in DB2 10 for z/OS.
    
    Additional keywords: SQLXML SMCOVERLAY
    

Temporary fix

  • *********
    * HIPER *
    *********
    

Comments

APAR Information

  • APAR number

    PM28385

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    YesHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-12-07

  • Closed date

    2011-03-25

  • Last modified date

    2011-05-01

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UK66136

Modules/Macros

  • DSNNOAPU DSNNOCLN DSNNOGIK DSNNONTS DSNNORCN
    DSNNOUPD DSNNOWRT DSNNPULP DSNNQDTM DSNNQFLR DSNNQFL2 DSNNQIV
    DSNNQMD  DSNNQOPM DSNNQOPS DSNNQSCN DSNNQTOP DSNNQXCA DSNNRXSG
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • RA10 PSY UK66136

       UP11/04/12 P F104

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 May 2011