PH35906: AFTER PH35218, ABENDS0C4 OR UNDULY EMPTY OUTPUT DATASET FOR AN UNLOAD STATEMENT WITH A SET OF SELECT STATEMENTS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• (HPU 5.1 only) After the enhancement PH35218/PB50930 has been
  applied, an unload involving at least two logical unload against
  tables from the same tablespace either fails with ABENDSC04 or
  unduly produces no rows for one of the logical unloads.
  
  This occurs if  the UNLOAD statement specifies a set (at least
  two) logical unloads (SELECT statements) that fulfills all the
  following conditions:
  - the SELECT statements involve tables from the same tablespace
  - the SELECT statement are processed in native mode.
  - at least one of the SELECT statement specifies an ORDER clause
  - at least one of the SELECT statements specifies no ORDER
  clause
  
  If the tablespace involved by the set of logical unloads
  mentioned above is partitioned, an ABENDS0C4 occurs.
  
  If the tablespace involved by the set of logical unloads
  mentioned above is not partitioned,, no row is systematically
  unloaded for the SELECT statements without ORDER clause
  regardless of the actual amount of data in the related table.
  

Local fix

• 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   *
  *                      has been applied, an unload involving   *
  *                      at least two logical unload against     *
  *                      tables from the same tablespace either  *
  *                      fails with ABENDSC04 or unduly produces *
  *                      no rows for one of the logical unloads. *
  *                                                              *
  *                      This occurs if  the UNLOAD statement    *
  *                      specifies a set (at least two) logical  *
  *                      unloads (SELECT statements) that        *
  *                      fulfills all the following conditions:  *
  *                      - the SELECT statements involve tables  *
  *                      from the same tablespace                *
  *                      - the SELECT statement are processed in *
  *                      native mode.                            *
  *                      - at least one of the SELECT statement  *
  *                      specifies an ORDER clause               *
  *                      - at least one of the SELECT statements *
  *                      specifies no ORDER clause               *
  *                                                              *
  *                      If the tablespace involved by the set   *
  *                      of logical unloads mentioned above is   *
  *                      partitioned, an ABENDS0C4 occurs.       *
  *                                                              *
  *                      If the tablespace involved by the set   *
  *                      of logical unloads mentioned above is   *
  *                      not partitioned, no row is              *
  *                      systematically unloaded for the SELECT  *
  *                      statements without ORDER clause         *
  *                      regardless of the actual amount of data *
  *                      in the related table.                   *
  ****************************************************************
  * RECOMMENDATION: Apply the PTF                                *
  ****************************************************************
  After PH35218, ABENDS0C4 or output dataset unduly empty for an
  UNLOAD statement with a set of SELECT statements.
  

Problem conclusion

• Code has been changed to fix this problem
  

Temporary fix

Comments

• ×**** PE21/06/10 FIX IN ERROR. SEE APAR PH38026  FOR DESCRIPTION
  ×**** PE24/04/12 FIX IN ERROR. SEE APAR PH60874  FOR DESCRIPTION
  ×**** PE24/04/12 FIX IN ERROR. SEE APAR PH60874  FOR DESCRIPTION
  

APAR Information

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

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

  UI75101

Modules/Macros

• INZ$$PRM INZBIND  INZTDSC  INZTVAR  INZUTILK
  

Fix information

• Fixed component name

  DB2 HI PERF UNL

• Fixed component ID

  5697F4400

Applicable component levels

• R510 PSY UI75101

     UP21/05/07 P F105 {

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.