text: Q:
  
  queue files corruption in MQ in circular logging
  
  I am using circular logging.  Because of human intervention, one of the
  queue files is corrupted.
  Since the circular logging is not having the ability of recovering the 
  corrupted queue files, what will be the next steps it will take?
  Will queue manager create an empty queue file for that queue and start
  enrolling the messages to it? Else, it will just show the pending
  messages in the queue but not allow the applications to process?
  
  A:
  
  As you correctly note, MQ cannot recover from a damaged queue file when it is configured for circular logging.
  
  Will queue manager create an empty queue file for that queue and start enrolling the messages to it? Else, it will just show the pending messages in the queue but not allow the applications to process?
  
  None of the above.  The queue manager will return an error to any process attempting to access that queue.  
  When a queue file is damaged, it may or may not have had messages in it.  There is no automatic recovery possible that would correctly reconcile the state of any messages that may have been enqueued, therefore no further processing is done on that queue and any access returns an error.  Human intervention is required in that case and the fix is to delete and redefine the queue using runmqsc.
  If additional queue recovery is required to make sure messages are not lost in such cases, linear logging is mandatory.
  
  