IBM Support

PH16253: COMPARE OF TABLES WITH DIFFERENT CCSIDS HAS INCORRECT RESULTS.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • 1) The number of equal rows reported is incorrect.  This only
    affects comparisons where the rows do not have unique key values
    2) The display of the row columns indicates columns have
    different values but they are equal
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Optim for z/OS users comparing tables with   *
    *                 different CCSIDs.                            *
    ****************************************************************
    * PROBLEM DESCRIPTION: 1) The number of equal rows reported is *
    *                      incorrect.  This only affects           *
    *                      comparisons where the rows do not have  *
    *                      unique key values.                      *
    *                      2) The display of the row columns       *
    *                      indicates columns have different values *
    *                      but they are equal.                     *
    ****************************************************************
    * RECOMMENDATION: Apply the provided fix.                      *
    ****************************************************************
    1) Nullable columns with NULL values are comparing not equal
    when the CCSIDs are different.
    2) For rows that are determined to be unequal, all character and
    graphic columns with different CCSIDs are shown as different in
    the browse dialog and reports.
    

Problem conclusion

  • 1) Nullable columns are correctly compared.
    2) The columns are re-compared for browse and reporting to
    indicate which columns changed.  When the CCSIDs are different
    the values must be converted prior to the compare.  This is now
    being done.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH16253

  • Reported component name

    OPTIM MOVE FOR

  • Reported component ID

    5655V0700

  • Reported release

    B70

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-08-29

  • Closed date

    2019-10-11

  • Last modified date

    2019-11-01

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

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

Modules/Macros

  • FOPMAIN  FOPMCBMN FOPMCMAI FOPMCMMN FOPMCOFN FOPMDPRC FOPMDXTR
    FOPMECMN FOPMEMAI FOPMIXMM FOPZFMMN
    

Fix information

  • Fixed component name

    OPTIM MOVE FOR

  • Fixed component ID

    5655V0700

Applicable component levels

  • RB70 PSY UI65851

       UP19/10/15 P F910

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.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B70","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 November 2019