IBM Support

PM12022: Batch update behavior differs between ClearQuest for Windows client and RCP (Eclipse) client

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as Permanent restriction.

Error description

  • There is a discrepancy in the way the IBM Rational ClearQuest
    (CQ) for Windows client and the ClearQuest client (Rich Client
    Platform) (RCP) client process a multiple record update
    operation when a modification to the record is included in the
    validation hook of the modify action or the validation hook of a
    base action.
    
    The Windows client seems to consider the operation on the
    validation hook as part of the modification to be propagated to
    all records, while the RCP client does not.
    
    The result of this is that in the Windows client all the records
    but the first that was selected get the modification from the
    validation hook twice, one as the result of their own validation
    hook and another one as part of the modifications to the first
    record supposed to be propagated to all the records. In the RCP
    client the modification generated by the validation hook of the
    first record is not propagated to the other records.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Batch update behavior differs between RCP client and Windows
    clients.
    

Problem conclusion

  • This issue has been addressed in the new ClearQuest Web
    8.0.1 Multi-Record Update feature.
    
    There are no plans to fix this in the CQ Eclipse and CQ
    Windows Client.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM12022

  • Reported component name

    CLEARQUEST UNIX

  • Reported component ID

    5724G3601

  • Reported release

    710

  • Status

    CLOSED PRS

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-04-12

  • Closed date

    2013-06-20

  • Last modified date

    2013-06-20

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

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

Fix information

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSSH5A","label":"Rational ClearQuest"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
20 June 2013