PI54571: RESULTS DIFFER IN COMPARE WILDCARD TO PREVIOUS VS COMPARE EXPLICIT TO PREVIOUS

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• Customer reports that when specifying a wildcard
  character on the COMPARE ... TO PREVIOUS command,
  Path Checker generates inconsistent results versus running Path
  Checker explicitly specifying each DBRM
  on the COMPARE ... TO PREVIOUS command.
  
  For example the following two scenarios:
  
  Running Path Checker with the following command:
  
  COMPARE PACKAGE VERCOL1.*       IN SYSADM.PLAN_TABLE
                                         TO PREVIOUS
  
  The following messages are issued in SYSPRING indicating a
  change:
  
   CKP224I The cost estimate in the DSN_STATEMNT_TABLE
           changed, and the previous estimated value for
           service units was 2,241.
   CKP227I The cost estimate in the DSN_STATEMNT_TABLE
           changed, and the previous estimated value for
           CPU consumption was 852 miliseconds.
  
  But running Path Checker specifying the DBRM PGMV1T2 shows
  expected "no changes" as follows:
  
   COMPARE PACKAGE VERCOL1.PGMV1T2 IN SYSADM.PLAN_TABLE
                                         TO PREVIOUS
  
    CKP203I For the program PGMV1T2, 1 SQL statements had
            the same access path and 0 SQL statements had
            different access paths.
    CKP204I For the program PGMV1T2, 1 SQL statements were
            available for processing in the source program
            and 0 SQL statements did not match in the
            program being compared.
  

Local fix

• Until PTF is applied.
  Do not use "COMPARE ... TO PREVIOUS" with wildcard '*'.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: Users of DB2 Path Checker z/OS.              *
  ****************************************************************
  * PROBLEM DESCRIPTION: Customer reports that when specifying   *
  *                      a wildcard character on the COMPARE     *
  *                      ... TO PREVIOUS command, Path Checker   *
  *                      generates inconsistent results versus   *
  *                      running Path Checker explicitly         *
  *                      specifying each DBRM on the COMPARE     *
  *                       ... TO PREVIOUS command.               *
  *                                                              *
  *                      For example the following two           *
  *                      scenarios:                              *
  *                      Running Path Checker with the           *
  *                      following command:                      *
  *                                                              *
  *                      COMPARE PACKAGE VERCOL1.*       IN      *
  *                       SYSADM.PLAN_TABLE                      *
  *                       TO PREVIOUS                            *
  *                                                              *
  *                      The following messages are issued in    *
  *                      SYSPRINT indicating a change:           *
  *                       CKP224I The cost estimate in the       *
  *                       DSN_STATEMNT_TABLE changed, and the    *
  *                       previous estimated value for service   *
  *                       units was 2,241.                       *
  *                       CKP227I The cost estimate in the       *
  *                       DSN_STATEMNT_TABLE changed, and the    *
  *                       previous estimated value for CPU       *
  *                       consumption was 852 miliseconds.       *
  *                                                              *
  *                      But running Path Checker specifying     *
  *                      the DBRM PGMV1T2 shows expected         *
  *                      "no changes" as follows:                *
  *                                                              *
  *                       COMPARE PACKAGE VERCOL1.PGMV1T2 IN     *
  *                        SYSADM.PLAN_TABLE                     *
  *                       TO PREVIOUS                            *
  *                                                              *
  *                        CKP203I For the program PGMV1T2, 1    *
  *                       SQL statements had the same access     *
  *                       path and 0 SQL statements had          *
  *                       different access paths.                *
  *                        CKP204I For the program PGMV1T2, 1    *
  *                       SQL statements were available for      *
  *                       processing in the source program and   *
  *                       0 SQL statements did not match in the  *
  *                       program being compared.                *
  ****************************************************************
  * RECOMMENDATION: APPLY the PTF.                               *
  ****************************************************************
  Code has been changed to correct this condition.
  

Problem conclusion

• APPLY the PTF.
  

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

•    CKPPTHCK
  

Fix information

• Fixed component name

  DB2 PATH CHECKE

• Fixed component ID

  5655E3901

Applicable component levels

• R420 PSY UI34832

     UP16/01/29 P F601

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.