T
Thomas Mercer-Hursh
Guest
It might be worth tabulating all of the possible sources of a STOP condition and clearly identifying 2 properties - whether they are reasonably trapable and whether or not there is an associated message. Then, review the ones without messages and ask yourself if it is appropriate that it have no message. One of the issues here is the extent to which the condition is likely to occur in normal processing. STOP-AFTER, for example, is not really a condition where one would expect to bail out, but rather one in which one might like to give information to the user and ask for a course of action. It seems like it would be easy enough to create a useful message to convey what happened.
Continue reading...
Continue reading...