IBM Support

IT10777: WEBSPHERE MQ JMS TRACE DISPLAYS INCORRECT NUMERICAL DATE FORMAT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • IBM MQ v8 classes for JMS trace displays an incorrect numerical
    date format. The month numerical value shown is one month less
    than the actual date.
    
    For example:
    
    [28/08/15 21:09:29.560.01] 0001 static
    c.i.m.c.commonservices.trace.Trace
    
    
    The date field shown here is "08" for the month, which we would
    interpret at August (the 8th month). However this trace was
    actually collected in September.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of the WebSphere MQ classes for Java and JMS, including
    WebSphere MQ Managed File Transfer, at a level of code which
    includes APAR IT05061.
    
    At the time of writing, this is the MQ versions:
    
    Version Maintenance Level
    v7.0 7.0.1.13
    v7.1 7.1.0.7
    v7.5 7.5.0.5
    v8.0 8.0.0.2
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    APAR IT05061 introduced date formats to WebSphere MQ classes for
    Java/JMS trace, where previously only a time stamp was recorded:
    
      http://www.ibm.com/support/docview.wss?uid=swg1IT05061
    
    
    This APAR incorrectly assumed that the Java
    "java.util.GregorianCalendar" output a numerical format for the
    month field where the first month (January) had the value "1",
    through to December with the value "12".
    
    This is incorrect - month fields returned by
    "java.util.GregorianCalendar" begin at 0 for January through to
    11 for December.
    
    
    This could be confusing when reading trace files. However there
    is no product functional issue associated with this trace data
    inconsistency.
    

Problem conclusion

  • The WebSphere MQ classes for JMS trace output has been updated
    to output a numerical value for the month field in keeping with
    the our natural language interpretation, where January starts
    with the value "1".
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.0       7.0.1.14
    v7.1       7.1.0.8
    v7.5       7.5.0.6
    v8.0       8.0.0.5
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT10777

  • Reported component name

    WMQ BASE MULTIP

  • Reported component ID

    5724H7251

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-08-19

  • Closed date

    2015-09-30

  • Last modified date

    2015-12-07

  • 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

    WMQ BASE MULTIP

  • Fixed component ID

    5724H7251

Applicable component levels

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYHRD","label":"IBM MQ"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.0.0.0","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
07 December 2015