× 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.


  1.  Home
  2. MIDRANGE-L
  3. July 2005

Re: CLP logging level

Hi Rob
I've always had a similar feeling especially with what I generically term "the operational stuff".
Basically I divide the operational programs into two groups - the ones that must finish regardless and where I can deal with the errors later and the ones that I want to alert me in the case of a problem. The first group get the default handler, the second group get my hand coding and when my hand coding fails I get paged.
You also still have the choice to exercise whether you want global handling or not or to be paged at a more atomic level. At the risk of another lesson from SImon (bring it on - always interesting ;) ) you can still override at command level by an appropriately placed MONMSG CPF0000 (or CPF9999 ? ) after a specific command and therefore cause those specific command lines you do not want to go to the default handler to use something specific. The default global handler is only used when a MONMSG is not coded after a command line to handle errors and it has been specified. 

Regards
Evan Harris

At 01:52 a.m. 29/07/2005, you wrote:

I understand the concept of a nice global default handler.  I'm just not
sure that I agree with it.  There are numerous times that if my CL blows
up on a particular line that I could deal with the situation externally,
then reply with an R, or I, to the message and let it continue on.  Then,
add a project to my list to modify the code to handle the situation
automatically in the future.  Wouldn't I lose this capability with a
global default handler?

Rob Berendt
--
Group Dekko Services, LLC

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.