|
James wrote: > Change system value QUPSMSGQ to point to QSYS/QSYSMSG. Set this > message queue in break mode and write a break handling program and > assign it to the message queue. Is a break handling program really the best way to monitor the QSYSMSG message queue? My understanding is that break handling programs are best suited to interactive jobs. To have the queue in break mode there has to be a job that has the queue allocated. In this example it could be the system console, but if the console gets signed off the queue goes back into hold mode and the messages are not monitored. OTOH if you have a batch NEP monitoring the queue it can be simply sitting on a RCVMSG with WAIT(*MAX) without a separate program having to be invoked. The NEP can examine every message that arrives in the queue, take the appropriate action, then loop round and go back sleep. Surely this is preferable to using a break handler? Dave... =========================== The opinions expressed in this communication are my own and do not necessarily reflect those of my employer.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.