PI96568: XML DOC ERR SQLCODE = -20398 ON LOAD INSERT

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• The following DB2 error may be reported while processing
  extracted DB2 XML data for INSERT or LOAD:
  
  XML DOC ERR SQLCODE = -20398 on LOAD INSERT
  
  DSNU283I  -DQAJ 038 09:39:08.75 DSNURWBF - XML ERROR
  
        SQLCODE = -20398
  
        SQLERRM = 75 O    BOM                       XML
  
             .RC=000C,RSN=3064.
  
        SQLSTATE= 2200M
  
        SQLERRP = DSNNOPAR
  
        SQLERRD = FFFFFE16 00000000 00000000 FFFFFFFF 00000000
  00000000
  
  ERROR SEVERITY :1
     INPUT RECORD    :             1
     DISCARD RECORD  :             1
     ERROR TYPE      :             XML DOC ERR
     RELATED ERROR   :             0
     TABLE NAME      : AUTO3_TARGET.DAT_ENG_TBL1
  ERROR SEVERITY :1
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Optim for z/OS users.                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * 1. The following DB2 error may be reported while processing  *
  * extracted DB2 XML data for INSERT or LOAD:                   *
  *                                                              *
  * XML DOC ERR SQLCODE = -20398 on LOAD INSERT                  *
  * DSNU283I  -DQAJ 038 09:39:08.75 DSNURWBF - XML ERROR         *
  *       SQLCODE = -20398                                       *
  *       SQLERRM = 75 O    BOM                       XML        *
  * .RC=000C,RSN=3064.                                           *
  *       SQLSTATE= 2200M                                        *
  *       SQLERRP = DSNNOPAR                                     *
  *       SQLERRD = FFFFFE16 00000000 00000000 FFFFFFFF 00000000 *
  * 00000000                                                     *
  *                                                              *
  * ERROR SEVERITY :1                                            *
  *    INPUT RECORD    :             1                           *
  *    DISCARD RECORD  :             1                           *
  *    ERROR TYPE      :             XML DOC ERR                 *
  *    RELATED ERROR   :             0                           *
  *    TABLE NAME      : AUTO3_TARGET.DAT_ENG_TBL1               *
  * ERROR SEVERITY :1                                            *
  *                                                              *
  * 2. Alignment is off on the Update/Insert Process Report      *
  * panel. The columns which specify counts for the processed    *
  * rows are misaligned (RTC72615).                              *
  *                                                              *
  * 3. CONSTRAINT name in the DDL generated with the CREATE      *
  * function missing delimiting quotes when it contains DBCS or  *
  * special characters. This may cause DB2 errors while creating *
  * affected objects (RTC69646).                                 *
  *                                                              *
  * 4. VSAM open errors may be reported while performing ARCHIVE *
  * creation with INDEXES and a prior processing was             *
  * unsuccessful leaving the VSAM data sets in inconsistent      *
  * state (RTC72612). The processing is being aborted.           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply the provided fix.                                      *
  ****************************************************************
  1. Optim incorrectly handled FETCHing of XML data when data
  truncation occurred because of insufficient buffer size. This
  may have led to invalid or incomplete XML data being stored in
  an EXTRACT or ARCHIVE files. Subsequent attempts to process such
  data may have led to DB2 error as documented.
  
  2. The alignment of columns in the processing report needs to be
  adjusted.
  
  3. Processing logic missing for CONSTRAINT logic when delimiting
  quotes are required around the object name.
  
  4. VSAM open errors during INDEX creation can be safely ignored
  and processing should continue.
  

Problem conclusion

• 1 . Optim code has been modified to address the problem. Note
  that Optim ARCHIVE or EXTRACT files created prior to application
  of this APAR which contained XML data may need to be recreated.
  
  2. 3. 4. Problems have been corrected.
  

Temporary fix

Comments

APAR Information

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

  PI96567

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

Modules/Macros

• FOPUMCBT FOPMCOLP FOPMDMAI FOPMUXIM FOPZFMMN FOPCFPMN FOPMIXMM
  FOPMADDE FOPMCDRT FOPMCOLA FOPMARCN FOP09A   FOPMAMAI FOP05A
  FOPMMUTL FOPHSTM  FOPUUNLD FOP01A   FOPMEMAI FOPMAFCN FOPMAIN
  FOP00003 FOP00203 FOPMMJBS FOP0AA   FOPMECMN FOP1ODRV FOPMTMDB
  FOPMDPRC FOPMMCMN FOPMMCMR FOP0ITKA FOP08A   FOPMCOFN FOPVOU
  FOPZFBMN FOP00A   FOPMCENU FOP4IPMN FOP4ZHSH FOPMDBMN FOPOMN
  FOPMSELM FOP9APIM FOP07A   FOPMCMAI FOPMDXTR FOP4PEMN FOP9GINF
  FOP4TRCE FOP1OSFN FOP3DTPR FOP4PMMN FOP00103 FOPMDDDL FOPCXLIB
  FOPIO    FOP00303 FOPMMUNU FOPZMAIN FOPZSUB
  

Fix information

• Fixed component name

  OPTIM MOVE FOR

• Fixed component ID

  5655V0700

Applicable component levels

• RB30 PSY UI55419

     UP18/04/27 P F804 ¢

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.