PH50224: AFTER PH35218, INCORRECT 0X0000 IN SOME OUTPUT DATA RECORDS OR ABENDS0C4 DURING UNLOAD OF LOB/XML COLUMN

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• After the enhancement PH35218/PB50930, regardless of the setting
  of the DB2SORT_BLOCK subparameters of VUU030/ULOPTNS, the
  following issues can occur:
  Issue #1) Incorrect two bytes with low value (0x0000) are
  present within the last 16 bytes of one or several output
  records. The issue is very unlikely and depends on the amount of
  data to be unloaded. If no partition parallelism is involved,
  the affected record is the last record of the unloaded dataset.
  If partition parallelism is involved, several records can be
  affected.
  Any kind of unload can be affected by the issue except for the
  following ones :
  - an unload run in SQL mode with no zIIP usage
  - an unload run in native mode with no zIIP usage and requesting
  the data from a unique table space be unloaded into a single
  output dataset with no LDS parallelism into action.
  Issue #2) An ABENDS0C4 occurs when unloading a LOB/XML column
  When very unlikely timing conditions are fulfilled by the Db2
  HPU internal processes, an ABENDS0C4 can occur if all the
  following conditions are also fullfilled :
  - LOB or XML data is unloaded
  - the unload is done in native mode
  

Local fix

• For issue #1, none but disabling the zIIP usage and partition
  parallelism (set it to 1) makes the issue even more unlikely.
  For issue #2, a new run of the unload should complete normally.
  Otherwise, If applicable, run the unload in SQL mode by
  specifying the DB2 FORCE option.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of Db2 High Performance Unload         *
  *                 for z/OS                                     *
  ****************************************************************
  * PROBLEM DESCRIPTION: After the enhancement PH35218/PB50930,  *
  *                      regardless of the setting of the        *
  *                      DB2SORT_BLOCK subparameters of          *
  *                      VUU030/ULOPTNS, the following issues    *
  *                      can occur:                              *
  *                      Issue #1) Incorrect two bytes with low  *
  *                      value (0x0000) are present within the   *
  *                      last 16 bytes of one or several output  *
  *                      records. The issue is very unlikely and *
  *                      depends on the amount of data to be     *
  *                      unloaded. If no partition parallelism is*
  *                      involved, the affected record is the    *
  *                      last record of the unloaded dataset. If *
  *                      partition parallelism is involved,      *
  *                      several records can be affected.        *
  *                                                              *
  *                      Any kind of unload can be affected by   *
  *                      the issue except for the following      *
  *                      ones:                                   *
  *                      - an unload run in SQL mode with no     *
  *                        zIIP usage                            *
  *                      - an unload run in native mode with no  *
  *                        zIIP usage and requesting the data    *
  *                        from a unique table space be unloaded *
  *                        into a single output dataset with no  *
  *                        LDS parallelism into action.          *
  *                                                              *
  *                        Issue #2) An ABENDS0C4 occurs when    *
  *                        unloading a LOB/XML column            *
  *                                                              *
  *                        When very unlikely timing conditions  *
  *                        are fulfilled by the Db2 HPU internal *
  *                        processes, an ABENDS0C4 can occur if  *
  *                        all the following conditions are also *
  *                        fullfilled :                          *
  *                        - LOB or XML data is unloaded         *
  *                        - the unload is done in native mode   *
  ****************************************************************
  * RECOMMENDATION: Apply the PTF                                *
  ****************************************************************
  After PH35218, incorrect 0x0000 in some output data records, OR
  ABENDS0C4 during unload of LOB/XML column
  

Problem conclusion

• Code has been changed to fix this problem
  

Temporary fix

Comments

APAR Information

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

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

  UI83089

Modules/Macros

• INZCHECK INZCRX10 INZCRXSM INZCRXSQ INZTPMEM INZUTILK
  

Fix information

• Fixed component name

  DB2 HI PERF UNL

• Fixed component ID

  5697F4400

Applicable component levels

• R510 PSY UI83089

     UP22/11/05 P F211 {

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.