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


  • Subject: RE: global MONMSG to catch everything
  • From: bmorris@xxxxxxxxxx
  • Date: Wed, 6 Oct 1999 09:30:13 -0400




>Date: Tue, 5 Oct 1999 11:35:20 -0400
>From: "Dan Bale" <dbale@genfast.com>
>
>Bob, good point about RPG inquiry messages.  Is there a way to trap those in
the
>CL program?  RPG0000, RPX0000?  Or do you have to trap it in the RPG program?

Dan,
If you use ILE, and have your ILE CL in the same (non-dftactgrp) activation
group as your ILE RPG, there will be no RPG inquiry message.  The RPG program
will just stop (although a cancel handler will run if you have enabled one).
Any other programs in the program stack between the CL and the RPG will also
just stop without ceremony.

If you don't use ILE, you have to trap RPG errors in the RPG program (pssr,
infsr).

As Bob warns, this is a very dangerous technique if you don't code the MONMSG
handler correctly, and if you don't use cancel handlers (luckily, cancel
handlers are much easier to use than condition handlers ...)

Barbara Morris


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.