IT41850: QUEUEFILE MIGRATION PROCESS DOES NOT STOP

APAR status

• Closed as program error.

Error description

• The migration of a queue is performed by the migration process
  Due to a race condition the amqoqmig process may enter an
  infinite loop.
  If that happens, the queue migration has already been completed!
  The amqoqmig process does not detect the end of the migration
  and keeps waiting.
  The process does not consume noticable system resources.
  There is absolutely no impact to MQ or the system apart from a
  process running that is not needed any more.
  The queue is migrated but the migration process amqoqmig is
  still running.
  The user could check the AMQPARMS file (RUNNSCNF) for
  information on the queue file migration.
  

Local fix

• He should make sure the migration is in fact finished.
  If that is the case, he could stop the amqoqmig process.
  

Problem summary

• A programming error in the amqoqmig process.
  The amqoqmig process waits until the original (old) queue file
  disappears.
  There was a race condition in this check and so the amqoqmig
  process never noticed the original queuefile has alreadybeen
  removed.
  

Problem conclusion

• The source code has been improved. It was possible to avoid
  this race condition.
  

Temporary fix

• He should make sure the migration is in fact finished.
  If that is the case, he could stop the amqoqmig process.
  

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

  MQ FOR HPE NS O

• Fixed component ID

  5724A3904

Applicable component levels