×
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.
Hi Barbara,
Am 17.02.2024 um 00:37 schrieb Barbara Morris <bmorris@xxxxxxxxxx>:
Begin Main;
Display screen for input;
MONITOR;
Procedure1();
ON-EXCP MSG_BAD_THING_A; // named constant for some message ID
// bad thing A happened
ON-EXCP MSG_BAD_THING_B;
// bad thing B happened
ENDMON;
Display screen showing results of processing;
End Main;
The snd-msg/monitor/on-excp op-codes are really great.
In the daily doing I only miss a few things:
a) an option to suppress an "on-excp" handled message to show up in the job log, like:
on-excp(n) 'CPF9801';
b) an option to receive the message data of a handled message with "on-excp" like:
on-excp 'CPF9801' msgData;
c) an option to receive the message id and message data with "on-exit" on abnormal end like:
on-exit abnormalEnd msgId msgData;
d) an option to easier define the target of a message like:
snd-msg *escape ... %target(*pgmbdy:1);
Another solution for many of these cases would be a "rcv-msg" op-code to receive a message that was sent with "snd-msg" - with options to "remove" the message and receive the message id, text and/or data.
This would make it many things so much easier.
Kind regards,
Daniel
As an Amazon Associate we earn from qualifying purchases.
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.