PH67559: LAST EXPLICITLY MENTIONED EXECUTE OPTION UNDULY APPLIES TO ALL UNLOAD TABLESPACE STATEMENTS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When using multiple UNLOAD TABLESPACE statements, the last
  explicitly mentioned EXECUTE option unduly overrides previous
  explicit and all implicit EXECUTE options.
  
  
  
  * If the last explicitly mentioned EXECUTE value is NO, all of
  the other unload statements will run as if they have been
  configured with an EXECUTE NO. No data will be unloaded, even
  when EXECUTE YES is supposed to apply.
  
  
  
  * If the last explicitly mentioned EXECUTE value is YES, every
  unload statement will run as if EXECUTE YES was specified. Data
  will be unloaded even when EXECUTE NO is specified.
  
  
  This behavior is always observed as long as:
  
  
  
  
  
  * the step contains more than one UNLOAD TABLESPACE statement
  
  
  
  * at least one UNLOAD TABLESPACE statement contains the
  EXECUTE NO option and another one is intended to run with
  EXECUTE YES (regardless of whether it is explicitly specified or
  not)
  
  
  Note: When it is not explicitly mentioned, the default value
  for the EXECUTE option is YES, but due to being an implicit
  value, will not count as an explicit statement.
  

Local fix

• * Consider grouping the unloads that are meant to run with
  EXECUTE NO in a separate step
  
  
  
  * To avoid splitting the job into two or more steps, consider
  running the UNLOAD TABLESPACE statements using EXECUTE NO with
  EXECUTE YES and setting the OUTMAXROWS value to 1 to restrict
  the number of lines to be written. The performance impact of
  this workaround will depend on whether the SELECT statement
  contains a WHERE clause or not, and the table size. It should be
  noted that the WHERE clause is not used when EXECUTE NO is
  specified and can be omitted if the UNLOAD TABLESPACE statement
  is always meant to use the EXECUTE NO option.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of Db2 High Performance Unload for     *
  *                 z/OS                                         *
  ****************************************************************
  * PROBLEM DESCRIPTION: When using multiple UNLOAD TABLESPACE   *
  *                      statements, the last explicitly         *
  *                      mentioned EXECUTE option unduly         *
  *                      overrides previous explicit and all     *
  *                      implicit EXECUTE options.               *
  *                      - If the last explicitly mentioned      *
  *                        EXECUTE value is NO, all of the other *
  *                        unload statements will run as if they *
  *                        have been configured with EXECUTE NO. *
  *                        No data will be unloaded, even when   *
  *                        EXECUTE YES is supposed to apply.     *
  *                                                              *
  *                      - If the last explicitly mentioned      *
  *                        EXECUTE value is YES, every unload    *
  *                        statement will run as if EXECUTE YES  *
  *                        was specified. Data will be unloaded  *
  *                        even when EXECUTE NO is specified.    *
  *                                                              *
  *                      This behavior is always observed as     *
  *                      long as:                                *
  *                      - the step contains more than one       *
  *                        UNLOAD TABLESPACE statement           *
  *                                                              *
  *                      - at least one UNLOAD TABLESPACE        *
  *                        statement contains the EXECUTE NO     *
  *                        option and another one is intended to *
  *                        run with EXECUTE YES (regardless of   *
  *                        whether it is explicitly specified or *
  *                        not)                                  *
  *                                                              *
  *                      Note: When it is not explicitly         *
  *                      mentioned, the default value for the    *
  *                      EXECUTE option is YES, but due to being *
  *                      an implicit value, will not count as an *
  *                      explicit statement.                     *
  *                                                              *
  *                      Local Fix :                             *
  *                      Two workarounds exist.                  *
  *                                                              *
  *                      - Consider grouping the unloads that    *
  *                        are meant to run with EXECUTE NO in a *
  *                        separate step                         *
  *                                                              *
  *                      - To avoid splitting the job into two   *
  *                        or more steps, consider running the   *
  *                        UNLOAD TABLESPACE statements using    *
  *                        EXECUTE NO with EXECUTE YES and       *
  *                        setting the OUTMAXROWS value to 1 to  *
  *                        restrict the number of lines to be    *
  *                        written. The performance impact of    *
  *                        this workaround will depend on        *
  *                        whether the SELECT statement contains *
  *                        a WHERE clause or not, and the table  *
  *                        size. It should be noted that the     *
  *                        WHERE clause is not used when EXECUTE *
  *                        NO is specified and can be omitted if *
  *                        the UNLOAD TABLESPACE statement is    *
  *                        always meant to use the EXECUTE NO    *
  *                        option.                               *
  ****************************************************************
  * RECOMMENDATION: Apply the PTF                                *
  ****************************************************************
  Last explicitly mentioned EXECUTE option unduly applies to all
  UNLOAD TABLESPACE statements
  

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:

Modules/Macros

• INZUTILK
  

Fix information

• Fixed component name

  DB2 HI PERF UNL

• Fixed component ID

  5697F4400

Applicable component levels

• R520 PSY UO05248

     UP25/10/18 P F510

• R610 PSY UO05249

     UP25/10/18 P F510

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.