Adding "Destructive GET" option in MQ Panel

Hi Team,

Recently we experienced a high CPU incident caused by bad messages stuck in a specific MQ queue. The messages were looping and driving CPU consumption, which led to LPAR slowness.
To remediate, we had to prepare and run a JCL to clear the problematic messages. While effective, creating and executing the JCL was time-consuming given the criticality and urgency of the situation.
To make future mitigation faster and more operationally efficient, We would like to propose adding a "Destructive GET" option in the MQ Panel under "Manage a Local Queue".
This would allow MQ Admins to quickly remove bad messages directly from the panel, significantly reducing time-to-recovery during similar incidents.

                                                                                                              Manage a Local Queue

Select function type, then press Enter.

Function type . . . . . . . .       1. Delete
                                                  2. Create a local copy on CRP1
                                                  3. Refresh local copy
                                                  4. Clear messages
                                                  5. Clear messages(DESGET)
                                                  6. Move messages to another empty queue
                                                  7. Move messages to another queue