×
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.
I would recommend the use of Monitor following a normal CHAIN as per
Scott Klement's previous post.
Monitor traps only the condition(s) you know your program can handle.
Any non-monitored error is thrown back up the call stack. CHAIN(e) on
the other hand leaves ALL error handling up to your program regardless
of the problem. Usually, you want the program to halt on unexpected
conditions. Better the job hang up than press on regardless and make a
mess.
My students would think themselves very clever when they discovered the
(e) extender because it make all their problems go away - and all their
solutions, too.
Tim McKenna
Systems Analyst II, Global Solutions Services, Warehouse Management
System
Global Technology Centre, McCain Foods Limited, 506-392-2831
As an Amazon Associate we earn from qualifying purchases.
This thread ...
RE: testing for record locks without using indicators, (continued)
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
