PM45471: ONCODE=350 FROM ENTRY POINT BUILD_LIMITKEY AT STATEMENT 18715

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• In DB2 Object Comparison Tool for z/OS, comparison on multiple
  tablespaces could result in message:
  IBM0361W ONCODE=350  The STRINGRANGE condition was raised.
           From entry point BUILD_LIMITKEY at statement 18715 at
           compile  unit offset +00027FAA at entry offset
           +00027FAA at address 341F164E.
           From entry point COMPARE_TABLES at statement 6961 at
           compile unit offset +00027E20 at entry offset +00027E20
           at address 34250D5A.
  Additional symptoms: oncode350
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of the DB2 Object Comparison Tool for  *
  *                 z/OS who compare two tables or two indexes   *
  *                 when specifying IGNORE fields related to     *
  *                 the PARTITIONING generic IGNORE              *
  *                 specification, and at least one of the       *
  *                 compare objects is partitioned.              *
  ****************************************************************
  * PROBLEM DESCRIPTION: In DB2 Object Comparison Tool for z/OS, *
  *                      when comparing two tables and at least  *
  *                      one of them is partitioned, if some     *
  *                      but not all IGNORE fields are specified *
  *                      and related to the PARTITIONING         *
  *                      generic IGNORE specification, there     *
  *                      are several ONCODE=350 / ONCODE350      *
  *                      warning messages in the compare job     *
  *                      log:                                    *
  *                                                              *
  *                      IBM0361W ONCODE=350                     *
  *                      The STRINGRANGE condition was raised.   *
  *                                                              *
  *                      When comparing two indexes and at least *
  *                      one of them is partitioned, if some but *
  *                      not all IGNORE fields are specified and *
  *                      related to the PARTITIONING generic     *
  *                      IGNORE specification, the compare job   *
  *                      failed with a RC=12 and the following   *
  *                      error messages are in the job log:      *
  *                                                              *
  *                      No sysindexpart row found for           *
  *                      Create index.                           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  In DB2 Object Comparison Tool for z/OS, when comparing two
  tables and at least one of them is partitioned, if some but not
  all IGNORE fields are specified and related to the
  PARTITIONING generic IGNORE specification, there are several
  ONCODE=350 / ONCODE350 warning messages in the compare job
  log:
  
  IBM0361W ONCODE=350
  The STRINGRANGE condition was raised.
  
  When comparing two indexes and at least one of them is
  partitioned, if some but not all IGNORE fields are specified and
  related to the PARTITIONING generic IGNORE specification, the
  compare job failed with a RC=12 and the following error messages
  are in the job log:
  
  No sysindexpart row found for Create index.
  ADBC002E - Severe error. Compare terminates.
  ADB0380E Module ADB2CMP - Severe error Compare terminates.
  

Problem conclusion

• Problem has been resolved and a new message has been added to
  warn users when they specify some but not all fields relating
  to generic partitioning:
  
  (W)Some but not all fields related to partitioning have
     been ignored. This may lead to unpredictable results.
     Please use generic ignore PARTITIONING if you want to
     IGNORE partition information during compare, otherwise
     please remove all ignore fields related to partitioning
     which have been specified.
  

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

•    GOC2CMF  GOC2CMP  GOC2CMR  GOC2CMT  GOC2IGN
  

Fix information

• Fixed component name

  DB2 OBJECT COMP

• Fixed component ID

  5697G6400

Applicable component levels

• R720 PSY UK74610

     UP11/12/13 P F112

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.