You control the available responses by having programs handle errors. When the programming is poorly done and errors are not handled, the system's default error handlers are called. That is, the <i>correct</i> way is to monitor for errors in the program code and to have the program run instructions that are appropriate for whatever errors arise. Since errors can be essentially anything, there is no way for us to tell you how to handle an inquiry message. It's perfectly possible to handle a message automatically and thereby start an infinite loop, especially if the automatic response is 'R'etry. If you want to restrict a particular reply, you can register <a href="http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/apis/XREPLY.htm">a program that you write</a> against the QIBM_QMH_REPLY_INQ exit point. And you can write <a href="http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/apis/XDEFAULT.htm">your own default handlers for *ESCAPE messages</a> as well -- those could help avoid having selected inquiry messages from appearing on workstations, but wouldn't be easy to get to 'automatically handle' the actual problems. The kinds of inquiry messages that you're asking about are ones that indicate a significant error condition. The only real way of handling them is by coding for those conditions in the programs. Tom

You control the available responses by having programs handle errors. When the programming is poorly done and errors are not handled, the system's default error handlers are called. That is, the <i>correct</i> way is to monitor for errors in the program code and to have the program run instructions that are appropriate for whatever errors arise. Since errors can be essentially anything, there is no way for us to tell you how to handle an inquiry message. It's perfectly possible to handle a message automatically and thereby start an infinite loop, especially if the automatic response is 'R'etry. If you want to restrict a particular reply, you can register <a href="http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/apis/XREPLY.htm">a program that you write</a> against the QIBM_QMH_REPLY_INQ exit point. And you can write <a href="http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/apis/XDEFAULT.htm">your own default handlers for *ESCAPE messages</a> as well -- those could help avoid having selected inquiry messages from appearing on workstations, but wouldn't be easy to get to 'automatically handle' the actual problems. The kinds of inquiry messages that you're asking about are ones that indicate a significant error condition. The only real way of handling them is by coding for those conditions in the programs. Tom