IT35323: Queue manager does not release secondary log extents after log full condition (AMQ7463)

APAR status

• Closed as program error.

Error description

• After  an event that caused all primary and secondary
  transaction
  logs to be filled up, the secondary logs continued to remain on
  the file system even after the log full condition was resolved
  a month ago.
  
  The display qmstatus command output shows the
  following:
  
  Previous QMStatus Output:
  QMNAME(QMgrName)
  STATUS(RUNNING)
  LOGINUSE(169)
  LOGUTIL(185)
  
  Current QMStatus Output:
  QMNAME(QMgrName)
  STATUS(RUNNING)
  CHINIT(RUNNING)
  CMDSERV(RUNNING)
  CONNS(1592)
  LOGINUSE(1)
  LOGUTIL(2)
  

Local fix

• Issue the runmqsc command "RESET QMGR TYPE(REDUCELOG)" to
  reduce the number of transaction logs.
  
  Note: Depending on what caused the MQ transaction log full
  condition and the current state of the logs, the "RESET QMGR
  TYPE(REDUCELOG)" may not be able to reduce the number of logs.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users using queue managers that suffer log full condition.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  A defect in MQ log space management caused MQ to fail to release
  secondary log extents once the log full condition was resolved.
  

Problem conclusion

• MQ code has been modified to fix the defect that prevented
  releasing secondary log extents.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.1 LTS   9.1.0.11
  v9.2 LTS   9.2.0.5
  v9.x CD    9.2.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 is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  IBM MQ BASE MP

• Fixed component ID

  5724H7271

Applicable component levels