IBM Support

PM83254: CQWeb: 'Unparseable date' error creating or opening child records on Swedish or Japanes locales

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as Permanent restriction.

Error description

  • In IBM Rational ClearQuest Web, the error occurs only if the
    field is a date reference list field type, normal date field
    does not show the problem.
    Also, it is reproducible on Japanese locale  ((UTC +0900) Osaka,
    Sapporo, Tokyo).
    
    Steps to reproduce:
     On a English Windows 2008, add Swedish as locale.
    1. Create a date reference list field on DefectTracking schema.
    2. Logon CQWeb.
    3. Try to create a record adding the date, the error occurs
    4. Create a query for defect record adding the created date
    field as a display.
    5. Run the query, the date field will display empty.
    6. Open one of the records ? Modify ? Go to tab where the date
    field exists, the error occurs.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    After upgrading to ClearQuest Version 7.1.2.9 or later on
    certain locales, including Japanese, Korean, Chinese, and
    Swedish, users might see error messages such as Unparseable
    date when viewing or working with date and time fields.
    Other users might notice a time difference of one hour for
    certain date and time fields after applying one of the
    previously mentioned patches.
    

Problem conclusion

  • There are no plans to address this problem in ClearQuest
    7.1.2.x.
    
    Please consider upgrading to ClearQuest 8.0.x where the
    problem does not occur.
    
    The following technote also explains a known workaround:
    
    http://www-01.ibm.com/support/docview.wss?uid=swg21633698
    
    Thank you for your understanding.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM83254

  • Reported component name

    CLRQUEST MSITE

  • Reported component ID

    5724G3700

  • Reported release

    712

  • Status

    CLOSED PRS

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-02-20

  • Closed date

    2013-07-16

  • Last modified date

    2013-07-16

  • 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":"SSUTY2","label":"Rational ClearQuest MultiSite"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
16 July 2013