Re: Stopping processing with using a bunch of if statements

Hi Daniel

I suggest you consider submitting these as Ideas, maybe as separate Ideas, then put references in them to one or more of the others. Your choice - if they seem related enough, bundle them. It is easier to respond to single Ideas, though. ideas.ibm.com - if you've never gone there.

Cheers
Vern

On 2/17/2024 5:02 AM, Daniel Gross wrote:

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