PI69203: INCONSISTENT RESULTS WHEN UNLOADING FROM BAD IMAGE COPY

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When unloading the data in native mode, DB2 HPU performs some
  integrity checking of the data source, i.e. the underlying VSAM
  data sets or the image copy data set the data are to be taken
  from. However, some inconsistent situations might not be
  detected such as the following ones:
  ·         Incorrect situation #1 :
  o   Description: the map points to the address of a an incorrect
  record and the table space is not a multiple table table space.
  
  o   DB2 HPU behavior: in such a case, as HPU does not check the
  OBID value, the inconsistent record situation is not caught and
  HPU processes the record further which leads to an error.
  
  o   Known symptoms : an ABENDS0C7 might occur.
  
  ·         Incorrect situation #2 :
  o   Description: the map points to hole.
  o   DB2 HPU behavior: As HPU does not expect a hole to be
  pointed by an idmap, it takes this hole for a short regular
  record and pads it to the required/expected length.
  o   Known symptoms: an empty row might be unloaded instead of
  reporting the incorrect situation.
  These two incorrect situations come from the fact the input data
  source is not DB2 compliant. Therefore, it might more likely
  occur when attempting to unload the data from an image copy that
  was not checked by a DB2 utility rather than from the VSAM data
  set under control of DB2. However, HPU should be fitted with the
  ability to detect and report the above mentioned two incorrect
  situations.
  
  PB46645
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of IBM DB2 High Performance Unload     *
  *                 z/OS.                                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: When unloading the data in native       *
  *                      mode, DB2 HPU performs some integrity   *
  *                      checking of the data source, i.e. the   *
  *                      underlying VSAM data sets or the image  *
  *                      copy data set the data are to be taken  *
  *                      from. However, some inconsistent        *
  *                      situations might not be detected such   *
  *                      as the following ones:                  *
  *                      - Incorrect situation #1 :              *
  *                        o Description: the map points to the  *
  *                          address of a an incorrect record    *
  *                          and the table space is not a        *
  *                          multiple table table space.         *
  *                        o DB2 HPU behavior: in such a case,   *
  *                          as HPU does not check the OBID      *
  *                          value, the inconsistent record      *
  *                          situation is not caught and HPU     *
  *                          processes the record further which  *
  *                         leads to an error.                   *
  *                        o Known symptoms : an ABENDS0C7       *
  *                          might occur.                        *
  *                      - Incorrect situation #2 :              *
  *                         o Description: the map points to     *
  *                           hole.                              *
  *                         o DB2 HPU behavior: As HPU does not  *
  *                           expect a hole to be pointed by     *
  *                           an idmap, it takes this hole for   *
  *                           a short regular record and pads    *
  *                           it to the required/expected        *
  *                           length.                            *
  *                         o Known symptoms: an empty row       *
  *                           might be unloaded instead of       *
  *                           reporting the incorrect situation. *
  *                      These two incorrect situations come     *
  *                      from the fact the input data source is  *
  *                      not DB2 compliant. Therefore, it might  *
  *                      more likely occur when attempting to    *
  *                      unload the data from an image copy      *
  *                      that was not checked by a DB2 utility   *
  *                      rather than from the VSAM data set      *
  *                      under control of DB2. However, HPU      *
  *                      should be fitted with the ability to    *
  *                      detect and report the above mentioned   *
  *                      two incorrect situations.               *
  *                      pb 46645                                *
  ****************************************************************
  * RECOMMENDATION: APPLY the PTF.                               *
  ****************************************************************
  N/A (Enhancement)
  

Problem conclusion

• APPLY the PTF.
  

Temporary fix

Comments

• ×**** PE17/08/03 PTF IN ERROR. SEE APAR PI85458  FOR DESCRIPTION
  

APAR Information

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

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

Modules/Macros

•    INZ$$PRM
  

Fix information

• Fixed component name

  DB2 HI PERF UNL

• Fixed component ID

  5697F4400

Applicable component levels

• R430 PSY UI45327

     UP17/03/14 P F703

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.