RE: Stopping processing with using a bunch of if statements

Well, I just learned something new two days in a row.

I never realized that I could send an escape message from a procedure and "monitor/catch" it in the procedure that called it when they were all in the same program. My escape messages have always been sent to an external calling program, not a procedure in the same program.

When I started programming in 1985, there was a sign on a guy's door that said "If you study 24 hours a day, 365 days a year, you still won't keep up with technology". I've never forgotten that and I'm constantly reminded of it!

Thank you Birgitta.

-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Birgitta Hauser
Sent: Thursday, February 15, 2024 3:16 AM
To: 'RPG programming on IBM i' <rpg400-l@xxxxxxxxxxxxxxxxxx>
Subject: RE: Stopping processing with using a bunch of if statements

... may be I misunderstood something
But...
Why not simply send an escape message (meanwhile there is even an opcode SND-MSG) ... and in the caller you catch the error with a Monitor Group.
BTW the error message if you need it can be taken from the program status data structure position 91-170.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser
Modernization – Education – Consulting on IBM i Database and Software Architect IBM Champion since 2020

"Shoot for the moon, even if you miss, you'll land among the stars." (Les Brown) "If you think education is expensive, try ignorance." (Derek Bok) "What is worse than training your staff and losing them? Not training them and keeping them!"
"Train people well enough so they can leave, treat them well enough so they don't want to. " (Richard Branson) "Learning is experience … everything else is only information!" (Albert Einstein)