I really failed by omitting too much code from my example. I really can't stack them because not every procedure will be called every time. For example, the middle procedure might only run if it is processing a specific type of record but the last procedure will always be called, assuming errors were not found in the previously called procedures.
I was really hoping there was some new type of GOTO that was available in free format but not as ugly to the program internally. We all know how wonderful a GOTO out of a procedure cleaned up after itself.
I'm now leaning toward submitting the processing logic so that the submitted job can just abend on error (SNDPGMMSG *ESCAPE) and have the interactive job go into a monitoring loop (with a delay) to watch what the submitted program is doing and report accordingly.
-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of VERNON HAMBERG Owner via RPG400-L
Sent: Wednesday, February 14, 2024 7:06 PM
To: rpg400-l@xxxxxxxxxxxxxxxxxx
Cc: VERNON HAMBERG Owner <vhamberg@xxxxxxxxxxxxxxx>; rpg400-l@xxxxxxxxxxxxxxxxxx
Subject: RE: Stopping processing with using a bunch of if statements
Ah, you did a test sooner than my typing could go!
The behavior you found and that I just described is sometimes called shortcutting logical expressions. I couldn't quickly find a reference to that behavior in the ILE RPG reference manual, might be there or in the Programmer's Guide.
As to the other issue, we'd need to see more - I wonder if something like a cascading set of CALLs could do it -
If Call1;
// do some stuff
if Call2;
// do more stuff
if Call3;
// do even more stuff
endif;
endif;
endif;
Or put the some and more and even more in each respective procedure, you'd still return the result as true or false.
HTH
Vern
On Wed, 14 Feb, 2024 at 5:58 PM, smith5646midrange@xxxxxxxxx <smith5646midrange@xxxxxxxxx> wrote:
To: 'rpg programming on ibm i'
I take back my statement. The machine stops after the first procedure called if it returns *off. Not what I expected. I learned something new.
Unfortunately, the part that I left out by stripping down the code is there is also logic between the called procedures so stacking them like you showed does not work for this case.
-----Original Message-----
From: smith5646midrange@xxxxxxxxx<mailto:smith5646midrange@xxxxxxxxx> <smith5646midrange@xxxxxxxxx<mailto:smith5646midrange@xxxxxxxxx>>
Sent: Wednesday, February 14, 2024 6:39 PM
To: 'RPG programming on IBM i' <rpg400-l@xxxxxxxxxxxxxxxxxx<mailto:rpg400-l@xxxxxxxxxxxxxxxxxx>>
Subject: RE: Stopping processing with using a bunch of if statements
My subject line should have read ...WITHOUT using a bunch of if statements. Oops.
If there is an error in Procedure2, I do not want Procedure3 or Procedure4 to run. Won't the if that you provided execute all three and then check the status of the IF?
-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx<mailto:rpg400-l-bounces@xxxxxxxxxxxxxxxxxx>> On Behalf Of Brian Johnson
Sent: Wednesday, February 14, 2024 6:05 PM
To: RPG programming on IBM i <rpg400-l@xxxxxxxxxxxxxxxxxx<mailto:rpg400-l@xxxxxxxxxxxxxxxxxx>>
Subject: Re: Stopping processing with using a bunch of if statements
How about something like this...
Have each procedure return a success indicator where *on = success, then
Begin Procedure1
if Procedure2()
and Procedure3()
and Procedure4() ;
clear Errorfound ;
else;
Errorfound = *on;
return;
endif;
Mainline can then test for Errorfound that was set by the procedures.
On Wed, Feb 14, 2024 at 4:10 PM <smith5646midrange@xxxxxxxxx<mailto:smith5646midrange@xxxxxxxxx>> wrote:
I have an RPGLE program that calls a number of procedures. If it is
in a procedure and it detects an error, I want it to stop processing
and exit back to the main procedure where the initial screen is
displayed to inform the user of the error. I do not want the program
to abend. Is there a way do to this without placing an if statement
after each procedure? That could get really ugly and it would
probably be easy to miss one because not all procedures can encounter
an error.
...
--
Brian Johnson
brian.johnson.mn@xxxxxxxxx<mailto:brian.johnson.mn@xxxxxxxxx>
--
This is the RPG programming on IBM i (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx<mailto:RPG400-L@xxxxxxxxxxxxxxxxxx> To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx<mailto:RPG400-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives at
https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related questions.
--
This is the RPG programming on IBM i (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx<mailto:RPG400-L@xxxxxxxxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx<mailto:RPG400-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives at
https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related questions.
--
This is the RPG programming on IBM i (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at
https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.
midrange.com
