PH06124: CM BATCH OBJECT COMPARE ANALYZE COMMENT CHECK NAMES AREN'T TOO LONG STRINGSIZE RAISED ONCODE 150 / ONCODE150 NOT IN ADBMSGS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• When importing a change which includes a comment on a column,
  and the comment is too long, a message similar to the following
  (some numbers may differ) may appear in the REPORT DD of the
  ANALYZE job (though not in the ADBMSGS DD):
  Stringsize raised
   Error: " oncode()="      150" onloc()="PUT_MSG" online()="
      44130" onoffset()="           164" oncondcond()="" on
   condid()="            18"
   Check that names aren't too long
   Length of stmt:    826
   COMMENT ON COLUMN schema.tablename.columnname IS...
  This APAR introduces a new message instead:
  ADB7754E Comment for the column <colname> in table <name> is
  too long. Maximum comment length is 762 characters.
  This APAR ensures that the new message also appears in
  ADBMSGS DD.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the Db2 Administration Tool for     *
  *                 z/OS or Db2 Object Comparison Tool for z/OS  *
  *                 who import and analyze a comment             *
  *                 on a column.                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION: During the import and analyze of        *
  *                      a comment to a column, an               *
  *                      uninformative error message may         *
  *                      be issued if the comment is too         *
  *                      long, and the error message also        *
  *                      does not appear in ADBMSGS DD.          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If a comment that is too long is imported and analyzed,
  the job may issue an uninformative set of error messages,
  such as the following (some of the numbers may differ):
  
  Stringsize raised
  Error: " oncode()=" 150" onloc()="PUT_MSG" online()="
     44130" onoffset()=" 164" oncondcond()="" on
  condid()=" 18"
  Check that names aren't too long
  Length of stmt: 826
  
  COMMENT ON COLUMN schema.tablename.columnname
  IS...
  In addition, this message does not appear in the ADBMSGS
  DD.
  
  This APAR introduces the following message instead, and
  ensures that it is included in ADBMSGS:
  
  ADB7754E Comment for the column >colname< in table >name< is
  too long.  Maximum comment length is 762 characters.
  
  Explanation: Comment length exceeds 762 characters.
  System action: A return code of 8 is set and processing
  continues.
  User response: Ensure that the length of the comment is less
  than or equal to 62 characters. Shorten the comment and
  resubmit the job.
  

Problem conclusion

• Problem has been resolved.
  

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:

  UI60957 UI60958

Modules/Macros

•    ADBCDTS  ADB7000
  

Fix information

• Fixed component name

  DB2 ADMIN TOOL

• Fixed component ID

  568851500

Applicable component levels

• RB20 PSY UI60957

     UP19/01/29 P F901

• RC10 PSY UI60958

     UP19/01/29 P F901

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.