PM47617: PRECONDITIONING APAR FOR A FUTURE FUNCTION

Obtain the fix for this APAR.

APAR status

• Closed as new function.

Error description

• Preconditioning APAR for a future function.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All DB2 10 for z/OS users of pureXML.        *
  ****************************************************************
  * PROBLEM DESCRIPTION: This is the preconditioning APAR for    *
  *                      a future function.                      *
  *                                                              *
  *                      This APAR also fixes following XML      *
  *                      related problems:                       *
  *                      1. An XML document containing xmlns=""  *
  *                         is not handled properly during       *
  *                         INSERT/LOAD/SELECT/UNLOAD using      *
  *                         Extensible Dynamic Binary XML DB2    *
  *                         Client/Server Binary XML Format(IBM  *
  *                         defined binary XML format).          *
  *                      2. Incorrect output is received when    *
  *                         an XML value index with key type of  *
  *                         SQL DECFLOAT is used for XMLEXISTS.  *
  *                         This problem would only occur when   *
  *                         the inserted data that matches the   *
  *                         key pattern is a floating point data *
  *                         and conforms to the pattern          *
  *                         (0-9)*.0+(1-9)+E... (* means 0 or    *
  *                         more, + means 1 or more). In other   *
  *                         words, the pattern has one or more   *
  *                         0s following . and then followed by  *
  *                         non-zero digit(s) and then E. For    *
  *                         example, the problem would occur     *
  *                         when the key value is 1.05E20,       *
  *                         123.000078E-1 etc. but would not     *
  *                         occur for key value 1.00E3.          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  This is the preconditioning APAR for future function.
  
  This APAR also fixed following XML related problems:
  1. An XML document containing a namespace declaraion of xmlns=""
     is not handled properly during INSERT/LOAD/SELECT/UNLOAD
     using Extensible Dynamic Binary XML DB2 Client/Server Binary
     XML Format(IBM defined binary XML format). During INSERT/
     LOAD/SELECT/UNLOAD using binary XML, when an XML document
     contains xmlns="", DB2 incorrectly skipped this info.
  
  2. Incorrect output is received when an XML index with key type
     of SQL DECFLOAT is used for XMLEXISTS.
     For example, suppose an XML index below is created
  
     CREATE TABLE T1 (ID INTEGER, DOC XML);
     CREATE INDEX INDX1 ON T1 (DOC)
         GENERATE KEY USING XMLPATTERN
             '/a/b/c'
            AS SQL DECFLOAT ;
  
     Suppose the XML document below is inserted
  
     INSERT INTO T1 (ID, DOC) VALUES(1,
       '<a><b><c>1.05E20</c></b></a>') ;
  
     The problem was caused by an error in handling the floating
     point data when generating index key values. The generated
     index key value was wrong for the above mentioned specific
     pattern (one or more 0s following . and then followed by
     non-zero digit(s) and then E) and hence caused the incorrout.
  

Problem conclusion

Temporary fix

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

Comments

• The run time portion of the future function has been added to
  DB2. Also the problems listed above have been fixed.
  

APAR Information

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

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

  UK72208

Modules/Macros

• DSNDXML  DSNNCTIB DSNNCXCO DSNNKGEN DSNNOAPU
  DSNNOBSC DSNNOBSE DSNNOBXI DSNNOBXS DSNNOCCN DSNNOGET DSNNOGIK
  DSNNONID DSNNONTS DSNNORCN DSNNORES DSNNORSQ DSNNOSCO DSNNOSEQ
  DSNNOSER DSNNOSMS DSNNOTCS DSNNOTTS DSNNOUPD DSNNOWRT DSNNOXMV
  DSNNPUL  DSNNPULP DSNNQCOM DSNNQDTM DSNNQFLR DSNNQFL2 DSNNQIV
  DSNNQLIB DSNNQMD  DSNNQOB  DSNNQOPM DSNNQOPN DSNNQOPR DSNNQOPS
  DSNNQREE DSNNQRES DSNNQSCN DSNNQTOP DSNNQXCA DSNNRXSG DSNNXEE
  DSNXEMG1 DSNXQFN  DSNXRL2  DSNXROPC
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UK72208

     UP11/09/30 P F109

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.