IT12137: WMQ-JMS TRACE DATE STAMP DISPLAYS INVALID MONTH FIELD FOR OCTOBER, NOVEMBER AND DECEMBER

APAR status

• Closed as program error.

Error description

• The time stamp for a JMS trace collected in November is of the
  format:
  
     [05/1:/15 16:13:50.123.02]
  
  The date field here should contain the characters:
  
      05/11/15
  
  and not:
  
      05/1:/15
  

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.
  
  These are the 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
  
  
  An error in the coding of this fix resulted in an incorrect date
  string being calculated, specifically for the Month field of the
  date.
  
  The problem was only seen in Months which had a numerical value
  greater than or equal to 10, and resulted in the second
  character having an unexpected character value.  For example,
  within a JVM using a ASCII compliant 'file.encoding' value (such
  as the encoding "UTF-8"), the characters seen would be:
  
    ':'  for 10th Month
    ';'  for 11th Month
    '<' for the 12th Month
  
  Note that a related APAR , IT10777, fixed a problem where the
  Month field value was one less than the typical representation,
  starting a Month '0' for January through to Month '11' for
  December.  The result of this is that for a trace collected in
  November, the data format would be of the form:
  
    [05/1:/15 16:13:50.123.02]
  
  in the 8.0.0.3 version of WebSphere MQ classes for Java/JMS, as
  this was the '10th' Month prior to the APAR IT10777.
  

Problem conclusion

• The programming error has been corrected so now the expected
  Month numerical representation is observed.
  
  ---------------------------------------------------------------
  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.4
  
  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 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 WINDOWS V7

• Fixed component ID

  5724H7220

Applicable component levels

• R710 PSY

     UP