IBM Support

PI49246: DIFFMERGE.EXE RETURNS SUCCESS IF A NON-EXISTING MERGE TOOL IS USED IN DIFFMERGE.INI

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • Where there is a merge conflict which can not resolved
    automatically, method body of "Cl1::f1" was modified in left and
    right version.
    
    The expected result of "diffmerge.exe" is "1", which means
    according to
    documentation "a conflict was detected".
    (see
    https://www-01.ibm.com/support/knowledgecenter/SSB2MU_8.1.3/com.
    ibm.rhp.diffmerge.doc/topics/rhp_t_col_specifying_diffmerge_cmdl
    ine_syn.html)
    
    If the diffmerge.ini is configured so that
    "BaseAwareAutoMergeInvocation" is to
    a non-existing tool ("NON_EXISTING_TOOL"). then starting the
    batch file again, DiffMerge.exe will return "0".
    (Merge successful).
    
    The file "out_rpy/P1.sbs" is also written. The merged result is
    from
    "left".
    
    
    DiffMerge must not automatically merge these conflicting files.
    
    Actually, if DiffMerge detects the merge tool does not exist, it
    should
    stop merging and return "1".
    
    (It would be helpful, if diffmerge would print a error message
    for this
    situation.)
    
    In case of non-existing merge tool DiffMerge produces wrong
    results,
    but user thinks everything is okay.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Rhapsody 8.1.3                                               *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * DIFFMERGE.EXE RETURNS SUCCESS IF A NON-EXISTING MERGE TOOL   *
    * IS                                                           *
    * USED IN DIFFMERGE.INI                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • Fixed in 8.1.4
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI49246

  • Reported component name

    TLOGIC RHAPSODY

  • Reported component ID

    5724V74RP

  • Reported release

    812

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-09-23

  • Closed date

    2015-12-16

  • Last modified date

    2015-12-16

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

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

Fix information

  • Fixed component name

    TLOGIC RHAPSODY

  • Fixed component ID

    5724V74RP

Applicable component levels

  • R813 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS7P9W","label":"Rational Rhapsody"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1.2","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
16 December 2015