Only cure is more programming--   monitor for the messages, add error 
checking, etc. etc.  Prevent the message from ever seeing the light 
of day!
When I write a program that has to interact with a human (ie get a 
response), I ask-- is there any way the information can be found 
without bothering someone to type in the run date or the first 
invoice number in the run.  Only after 2 or 3 iterations of "where 
can I find that info" does the inquiry bubble up to a human.
Similarly, a MONMSG in CLP will prevent a 1st level error from 
interrupting things.  You can intercept errors in RPG and other 
languages as well-- use the error indicator for disk errors, etc. 
And NEVER do you want to see a "Divide by Zero" error!
Of course-- if you don't have access to the source code...
--Paul E Musselman
.
At 3:01 PM +0000 2/16/21, Greg Wilburn wrote:
Does anyone know if there is a way to require a "response" on these messages?
No matter how much we preach, users will inevitably press <enter> 
through the message.  Would be nice if there was a way to require a 
valid response (C D I R), etc. and NOT accept <enter> as a "C".
--
As an Amazon Associate we earn from qualifying purchases.
	
 
This mailing list archive is Copyright 1997-2025 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.