×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hi Tim,
Am 28.02.2024 um 23:21 schrieb Tim Adair <tadair@xxxxxxxxxxxxxxxx>:
This is working very well, but I've run into another issue. When an error occurs on one of these submitted job steps, the error message is sent to the QSYSOPR message queue. Now, some of our I.T. personnel get automatically notified of any error messages on QSYSOPR, and some have a habit of responding to them even when they're not familiar with the situation.
This is really a kind of a problem. People should never respond to QSYSOPR messages without knowing what they do - but as always, it happens anyway.
So AFAIK your only solution for this problem might be the Reply Handling Exit Program:
https://www.ibm.com/docs/en/i/7.5?topic=ssw_ibm_i_75/apis/XREPLY.html
This exit program is called when a reply is sent to an inquiry message. To check if this is from one of your programs, you will have to work your way up from the reply, to the message, to the job and to the program on the call stack.
But before you go this route, you should seriously think about, if it is really impossible, to prevent "people" from answering messages, that they know nothing about. This would save you lots of time and effort.
HTH
Daniel
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.
midrange.com
