PM38025: INCORRECT OUTPUT WHEN LIKE PREDICATE IS USED AS MATCHING PREDICATE AND COLUMN IS CREATED WITH MIXED.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Incorrect output when LIKE predicate is used as matching
  predicate and column is created with MIXED.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users running statements when a like         *
  *                 predicate is used as the matching predicate  *
  *                 and the column is used with mixed data if    *
  *                 parallelism is enabled.                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: If statements use a like predicate      *
  *                      as the matching predicate and the       *
  *                      column is used with mixed data when     *
  *                      parallelism is enabled, incorrect       *
  *                      output may occur.                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  If parallelism is enabled for statements using a like predicate
  as the matching predicate and the column is used with mixed
  data, DB2 could possibly cut the key ranges wrong and incorrect
  ouput may occur.
  

Problem conclusion

• If parallelism is enabled for statements using a like predicate
  as the matching predicate and the column is used with mixed
  data, DB2 will cut the key ranges correctly.
  
  Additional Keywords:
  SQLPARALLELISM  SET CURRENT DEGREE ANY SQLCPUP
  SQLINCORR  INCORROUT SQLINCORROUT SQLLIKE
  

Temporary fix

• *********
  * HIPER *
  *********
  DISABLE PARALLELISM
  

Comments

APAR Information

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

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

  UK70810 UK70811 UK70809

Modules/Macros

• DSNXOLFQ
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RA10 PSY UK70809

     UP11/08/30 P F108

• R810 PSY UK70810

     UP11/08/30 P F108

• R910 PSY UK70811

     UP11/08/30 P F108

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.