PK28096: SQL STATEMENT GREATER THAN 32670 CHARACTERS WHEN RUNNING OC 7.1 DB2 R810 ENFM ADBTEP2 IS APPLYING THE 32K LIMIT TO UTILITY STM

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• DB2 Version 8 ENFM, zOS 1.7, Object Compare 7.1 creates a WSL
  which includes creating a partitioned tablespace ( 32 parts )
  and reloading those partitions . The job runs rc 0 but this
  error message is also returned :
  **ERROR:  SQL STATEMENT GREATER THAN      32670 CHARACTERS
  Admin ADBTEP2 is applying the 32k limit to the length of a
  utility control statement when it should only be applied to the
  length of an SQL statement.
  

Local fix

• Please apply PTF when available.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 Administration Tool, who have   *
  *                 the following condition may be affected:     *
  *                 "running a Work Statement List on a DB2 V7   *
  *                 or DB2 V8  CM/ENFM  system where a utility   *
  *                 or SQL statement exceeds 32K"                *
  ****************************************************************
  * PROBLEM DESCRIPTION: When creating a  WSL which included a   *
  *                      partitioned tablespace (32 parts) and   *
  *                      reloading  those  partitions, the job   *
  *                      ran with  RC 0 but ADBTEP2 ended with   *
  *                      the following message:                  *
  *                      "**ERROR:  SQL STATEMENT GREATER THAN   *
  *                      32670 CHARACTERS".                      *
  *                      .*                                      *
  *                      The 32K limit was applied to each input *
  *                      statement and incorrectly set the RC to *
  *                      0 when the limit was exceeded.          *
  *                      Note:                                   *
  *                      .*                                      *
  *                      The 32K limit wrongly applied to the    *
  *                      length of a utility control statement   *
  *                      should only be applied to the length    *
  *                      of an SQL statement.                    *
  *                      .* Note:                                *
  *                      Unreported "Allocation errors from TSO  *
  *                      ALLOC" have also been addressed.        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  See Problem Description.
  

Problem conclusion

• ADBTEP2 has raised the utility statement length it can handle
  to 2MB.
  .*
  Apply the fix.
  

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

•    ADBTAL   ADBTEP2
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• R710 PSY UK18367

     UP06/10/05 P F610

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.