IBM Support

PM46057: Address the issue to save current time value when saving date only field in CQ Web client 7.1.1/7.1.2

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When saving a date value 'e.g. 2011-07-14' in a Date only field,
    The current time '05:06:07' is also being stored with the date
    value in the backend database unintentionally in Rational
    ClearQuest Web version 7.1.1.0 or later, while it works as
    expected in version 7.1.0.x/7.0.1.x.
    As a result, The Query result set will start to show the time in
    CQ web client, CQ Eclipse RCP client, CQ Window client.
    
       CQ Web v 7.1.0.0 stores the date only value in database like
    '2011-07-14 00:00:00'
       CQ Web v 7.1.1.0 stores the date only value in database like
    '2011-07-14 05:06:07'  ?-! the current time is saved which we
    don't expect.
       Note: In order to avoid confusion, I assume the CQ Web
    server's machine local time zone is GMT+0.
    
    In CQ Win/RCP clients starts to show  '2011-07-14' -?
    '2011-07-14 05:06:07' in a query result set.
    In CQ Web clients starts to show '2011-07-14' -? '2011-07-14
    05:06:07' in a query result set.
    In a Query export starts to show '2011-07-14' -? '2011-07-14
    05:06:07'.
    
    This was discussed and a valid concern for possibly affecting
    date range based queries.  These can possibly be affected by the
    time value of the field depending on region they are being run
    from.
    
    - CQWeb client in 7.1.1.x, 7.1.2 will set current time of a date
    only field's backend date/time stored contents.
    - This issue can cause unexpected, incorrect results of date
    range based queries across multiple GMTs as Windows, Eclipse
    clients will differentiate in setting the default/expected time
    for date only fields.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When saving a date value 'e.g. 2011-07-14' in a Date only
    field, the current time '05:06:07' is also being stored with
    the date value in the database ClearQuest Web version
    7.1.1.0 or later.  This behavior is not consistent with
    ClearQuest Eclipse and Windows Client.
    

Problem conclusion

  • A fix is available in ClearQuest 7.1.1.8, 7.1.2.5 and
    8.0.0.1.
    
    Technote # 1572056 explains this change in behavior in more
    detail.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM46057

  • Reported component name

    CLEARQUEST WIN

  • Reported component ID

    5724G3600

  • Reported release

    711

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-08-19

  • Closed date

    2011-12-16

  • Last modified date

    2011-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

    CLEARQUEST WIN

  • Fixed component ID

    5724G3600

Applicable component levels

  • R711 PSN

       UP

[{"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.1","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
16 December 2011