Has the application or IBM MQ for z/OS stopped processing work?
There are several reasons why the system would unexpectedly stop processing work including problems with the queue manager, the application, z/OS, and the data sets.
There are several reasons why the system would unexpectedly stop processing work. These include:
- Queue manager problems
- The queue manager might be shutting down.
- Application problems
- An application programming error might mean that the program branches away from its normal processing, or the application might get in a loop. There might also have been an application abend.
- IBM MQ problems
- Your queues might have become disabled for MQPUT or MQGET calls, the dead-letter queue might be full, or IBM MQ for z/OS might be in a wait state, or a loop.
- z/OS and other system problems
- z/OS might be in a wait state, or CICS or IMS might be in a wait state or a loop. There might be problems at the system or sysplex level that are affecting the queue manager or the channel initiator. For example, excessive paging. It might also indicate DASD problems, or higher priority tasks with high processor usage.
- Db2 and RRS problems
- Check that Db2 and RRS are active.
In all cases, carry out the following checks to determine the cause of the problem:
Parent topic: Making initial checks on z/OS