IT24871: Queue manager incorrectly tries to recreate a missing active linear log file

APAR status

• Closed as program error.

Error description

• The user ends their Queue Manager and moves the files to another
  machine, but omits one or more of the log files needed for
  restart.
  
  During the next strmqm, the queue manager incorrectly creates a
  fresh (empty) log file, which it then cannot use to complete
  queue manager startup because it contains no user data.
  
  This appears on the console:
    AMQ7017: Log not available
  
  FDC files appear with these details:
  amqzmuc0 HL066203 mqlInitIOTask   xecF_E_UNEXPECTED_RC
  amqzmuc0 HL048036 mqlReadLogPages Unknown(2)
  amqzxma0 HL200143 mqlRandomRead   hrcE_MQLP_BADLSN
  amqzxma0 ZX146001 zxcStartupLogic lpiRC_LOG_NOT_AVAILABLE
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users who are running strmqm on a queue manager that has Linear
  Logging, and, because of some administrative mistake, have not
  copied all of MQ's log files into position beforehand.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  The queue manager was recreating a log file if it is missing,
  but this was not valid.  The queue manager then read that log
  file, and reported that it was inconsistent with the rest of the
  log.  This was true, but the queue manager should not have
  recreated it in the first place.
  

Problem conclusion

• The product code has been corrected so that recreation of a
  missing log file does not happen in this scenario.  Instead, the
  correct behaviour of the MQ code is to abandon queue manager
  startup, with helpful text in the FDC file suggesting what has
  gone wrong.
  
  Now, this scenario will produce an FDC with the following
  details:
  
  Probe Id :- HL221088
  Component :- Init_Recoverable
  Major Errorcode :- hrcE_MQLO_FNEX
  Comment1 :- A Qmgr Log File is missing - has it been removed?
  Comment2 :- Maybe the Log file system is not mounted correctly?
  Comment3 :- Filename:S0000003.LOG
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v7.5       7.5.0.9
  v8.0       8.0.0.11
  v9.0 LTS   9.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 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