Description:
Provide a trigger diagnostic report to show the success or failure of all the triggering conditions leading up to and including a triggered application being started by MQ. This would include the MQ Server code and the runmqtrm supplied program being enhanced to record all of this detail. The administrator would be able to turn on this triggering diagnostic for a queue, and then be able to provide a limit of how many messages would produce this diagnostic. For example, you could turn on triggering diagnostics for a queue and have a report created for the next 5 messages that get PUT to the queue.
Use Case:
An administrator is having issues with triggering working for an application. The administrator would then turn on triggering diagnostics for 1 message and then have a message PUT to the queue. The diagnostic report would include diagnostics like the following:
1. Open input count = 0 (successful)
2. GET allowed (successful)
3. Process defined (successful)
4. Initiation queue defined (successful)
5. INITQ open input count > 0 (successful)
6. Trigger control on (successful)
7. Trigger type not none (successful)
8. Trigger message written to INITQ (successful)
9. Trigger message GET from INITQ by runmqtrm (successful)
10. runmqtrm start of application (successful)
Business Justification:
Provide a better way for administrators to debug triggering issues.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum