Introduce a Single Command and Unified State to Disable a Queue

Use Case:

Currently, disabling message flow on a queue requires setting two separate attributes: PUT(DISABLED) and GET(DISABLED). Administrators must either issue two commands or remember to include both attributes in one command. During critical incidents or when automating queue management, this adds complexity and increases the risk of human error.

Impact:

• Operational Efficiency: Faster response during outages or maintenance by reducing steps.

• Automation: Easier scripting for bulk queue operations with a single, predictable attribute.

• Risk Reduction: Eliminates partial disablement scenarios caused by typos or omissions.

• Auditability: Provides a clear, unified indicator of queue status for monitoring and compliance.

Proposed Change:

Introduce an optional attribute or command to disable both PUT and GET in one step, such as:

• STATUS(DISABLED)

• or DISABLE(ALL)

Include an ENABLE(ALL) counterpart for reactivation.

This enhancement should also be reflected in MQ Explorer, providing a single “Disable All” option for PUT and GET, improving consistency between CLI and GUI.

Semantics:

When an administrator disables a queue, it should represent a single operational state where the queue is fully inactive for both PUT and GET operations. This unified state would make the term “disabled” intuitive and reduce ambiguity. Currently, disabling a queue informally means disabling PUT and GET separately. The proposed change formalizes this concept into a single, clear state.

Benefits:

• Simplifies queue management for administrators.

• Improves clarity for operators and auditors.

• Reduces risk of partial disablement during critical operations.

• Aligns GUI and CLI behavior for consistency.

• Establishes a clear semantic meaning for “disabled” in MQ operations.cy.