Re: Exiting a sub procedure

Not really, however....

You could do something like so.

Lets say your original procedure is named MyProcedure().

Rename the MyProcedure() to OriginalProcedure()

Create a new MyProcedure() with the following:
/free
rtnVar = OriginalProcedure();
if rtnVar;
//returned *ON
else;
//returned *OFF do something
endif;

return rtnVar;
/end-free


IIRC, you don't use service programs, so any program using the module with
MyProcedure() will need to be updated.

With a service program, assuming you use binder source, you can do the same
thing, without having to touch the calling programs at all. Just make sure
you don't change the order of the exported procedures in the binder source,
just add OriginalProcedure() to the end.

HTH,
Charles


On Mon, Nov 24, 2008 at 3:37 AM, David FOXWELL <David.FOXWELL@xxxxxxxxx>wrote:

Hello,

I'll be surprised if there's anything but NO to this question, but I've
learned on this list that if you don't ask you don't learn so here goes
anyway.

I have a subprocedure with many RETURN *OFF coded within. Now I need to add
some code in the case of it returning *OFF. I think I have to copy this code
before every RETURN *OFF. Is there anything that let's me call another
procedure on exiting this subprocedure? I just wondered when debugging and
noticing that RETURN *OFF seems to step to the line at the end of the sub
procedure.
I don't want this code done by the calling procedures as they are many and
external.

Thanks.
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.