×
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.
On Wed, 24 Dec 2014 17:25:15 -0600, CRPence <CRPbottle@xxxxxxxxx>
wrote:
Thus also why a status message that is sent to other than *EXT can act
similar to an *ESCAPE message [/percolated/ in the same manner] in the
receiving program, and why the Monitor Message (MONMSG) supports
enabling a monitor; only those message types of the Exception Message
(*EXCP) class, including *ESCAPE, *STATUS and *NOTIFY Message Type
(MSGTYPE) can be monitored.
Sending *STATUS and *NOTIFY messages to be monitored for is a very
handy capability that I used recently; I think for the first time
ever.
I was writing a command processing program and didn't want to have a
Return Value parameter. I used an *ESCAPE message to the caller if
the CPP couldn't perform the requested function. (This is nothing new
of course.) But if an error occurred and the CPP was able to recover
from it successfully, I used a *STATUS message to the caller, allowing
the caller to monitor for it or not as desired.
Ken
Opinions expressed are my own and do not necessarily represent the views
of my employer or anyone in their right mind.
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
