IT17569: UNINITIALIZED VARIABLE CAUSES INCORRECT DATE IN AMQ7486 MESSAGE TEXT.

APAR status

• Closed as program error.

Error description

• A invalid date is shown in the text of error message AMQ7486.
  
  The message should
  resemble the formatted output from the DSPMQTRN utility.
  
  Example of incorrect output, >> and << tags have been added
  around the incorrect entry for emphasis
  
  ***************************************************************
  02/14/2017 09:16:08 AM - Process(9771.5) User(user)
  Program(amqzmuc0)
                      Host(hostname) Installation(Installation1)
                      VRMF(8.0.0.5) QMgr(qmgr)
  
  AMQ7486: Transaction 0.28672 was preventing log space from being
  released.
  
  EXPLANATION:
  A long running transaction was detected. Message AMQ7469 or
  AMQ7485 has been
  issued indicating if the transaction was rolled back or rolled
  forward in the
  log to allow the log space to be released. The internal
  transaction identifier
  is 0.28672 which can be correlated with 'dspmqtrn -a' output.
  The transaction
  started at 09.16.01 2017-02-14   and first wrote to the queue
  manager recovery
  log at >>01.00.00 1970-01-01<<  . The following transaction
  context may be useful
  in identifying the application causing this behaviour:
  TRANNUM(0.28672) . This
  message can be correllated with the previous AMQ7469 or AMQ7485
  message in the
  queue manager error logs.
  ACTION:
  Identify the application responsible for the long running unit
  of work and
  ensure this application is creating and completing transactions
  in a timely
  manner. If the application is working as expected it may be
  appropriate to
  increase the size of the queue manager recovery log.
  
  ****************************************************************
  **************************
  

Local fix

• For accurate information concerning the LOG date the customer
  should use the dspmqtrn command.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users of WebSphere MQ with large transactions which fill the log
  files.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  A coding error meant that an unitialized value was used as the
  inserted data in the AMQ7486 message if a timing window was
  encountered during a roll forward of the MQ log.
  

Problem conclusion

• The WebSphere MQ code has been changed to correctly handle an
  uninitialized date field prior to filling in the AMQ7486
  message.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v7.5       7.5.0.8
  v8.0       8.0.0.7
  v9.0 CD    9.0.3
  v9.0 LTS   9.0.0.2
  
  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

  WEBSPHERE MQ 7.

• Fixed component ID

  5724H7240

Applicable component levels