Command event generation

Use this page to view the situations that cause command events to be generated and to understand the circumstances in which command events are not generated

• When the CMDEV queue manager attribute is specified as ENABLED and an MQSC or PCF command runs successfully.
• When the CMDEV queue manager attribute is specified as NODISPLAY and any command runs successfully, with the exception of DISPLAY commands (MQSC), and Inquire commands (PCF).
• When you run the MQSC command, ALTER QMGR, or the PCF command, Change Queue Manager, and the CMDEV queue manager attribute meets either of the following conditions:
  • CMDEV is not specified as DISABLED after the change
  • CMDEV was not specified as DISABLED before the change

If a command runs against the command event queue, SYSTEM.ADMIN.COMMAND.EVENT, a command event is generated if the queue still exists and it is not put-inhibited.

When command events are not generated

• When a command fails
• When a queue manager encounters an error trying to put a command event on the event queue, in which case the command runs regardless, but no event message is generated
• For the MQSC command REFRESH QMGR TYPE (EARLY)
• For the MQSC command START QMGR MQSC
• For the MQSC command SUSPEND QMGR, if the parameter LOG is specified
• For the MQSC command RESUME QMGR, if the parameter LOG is specified

Parent topic: Command events

Related concepts

• Command events

Related information

• REFRESH QMGR
• START QMGR
• SUSPEND QMGR
• RESUME QMGR
• SUSPEND QMGR, RESUME QMGR and clusters