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

Re: Exception handl. without using command level MONMSG

You have the RCVMSG command that will get you the error and accompanying diagnostics, if you wish. Examples are in the CL Programming manual - see InfoCenter. Chapters on handling errors and messages - I forget exactly which.

As for the command, I've never done it but here's an idea - compile the CL to LOGCLPGM (*YES) - not (*JOB). Then you can probably use RCVMSG to get the last command issued - not sure.

HTH
Vern

At 03:32 AM 3/21/2005, you wrote:
Dear members, i Have a CL program in which commands are added quite frequently . Because of the frequent addition of commands - adding command level MONMSGs to monitor each error is rendering the program BULKY. Is there any way to trap all possible error messages on all the commands in the CL program without using a Command Level MONMSG. Using program level MONMSG like CPF0000 will trap all errors - and then the user can be informed that an error has taken place using SNDPGMMSG. However, how will the user be informed of the exact error message - and on which CL command the error takes place on ?? Thanks in advance, Malini
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


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.