Production incidentIntermediate15 min
Incident: MQ reason 2033, the order processor finds nothing to do
Monitor 09:10: queue ORDERS.NEW depth 1,800 and rising, no application reading it ORDGET log: MQGET from ORDERS.IN ended with reason 2033 every minute since 08:00
Application ORDPUT puts branch orders on a queue and application ORDGET takes them off and processes them. Change CHG4480 moves the order flow from queue ORDERS.IN to a new queue, ORDERS.NEW, in two steps: step 1 points ORDPUT at ORDERS.NEW, step 2 points ORDGET at ORDERS.NEW. Since 08:00 ORDGET reports that it finds nothing to process, while ORDERS.NEW keeps growing. Find out why and get the orders processed, without losing any.
What you will do
- Read the application log and APPS
- Display both queues and who has them open
- Finish the change safely and prove the backlog is processed
Simulated: the Lab runs entirely in your browser on a simulated, fictional z/OS system. Nothing is sent to or run on a real mainframe.
Free, no account needed.
Your work is saved on this device; sign in to keep it in your account.