RE: Is RPG 'DEAD"

I don't know what is so hard about writing something that works like a finally - put the endmon just before the stuff you WOULD have put in a finally-block - badabing it is always run - no one needs a *PSSR anymore.

I know - that is a gross over simplification! Nonetheless - put monitor at the start of a procedure and endmon where i suggested - very nice. And if there is stuff you want NOT to run, put an IF around it - set a flag in the On error block that gets tested. OR put in the dreaded GOTO - that's all these blocks are, after all!!

Ducking!
Vern

-------------- Original message --------------
From: "Wilt, Charles" <WiltC@xxxxxxxxxx>

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Steve Richter
Sent: Wednesday, June 18, 2008 12:50 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: Is RPG 'DEAD"

On Wed, Jun 18, 2008 at 12:19 PM, Lim Hock-Chai
wrote:

Personally, I think java's try/catch is so overrated. What do you do

when you catch an

error?

close files, release the locks, ...

someone posts here a question about "resource unavailable" that is
related to an IFS file that cant be opened. The cause being another
job which has neglected to close the IFS file it opened. try finally
blocks eliminate this class of problem in your applications.

I don't think so...

Try/Finally allows an application to ensure that resources are always cleaned up
even if an exception
occurs. Thus preventing resource leaks.

On the IBM i, the OS does it for you. When an application is closed normally,
via returning with *LR
= *ON, or as a result of an exception, the OS will release any (most?) resources
held.

I say any (most?) above since _I_ can't think of anyway to cause a resource leak
in RPGLE;
particularly if running in an activation group other than the default. But IBM
does provide the
Register Call Stack Entry Termination User Exit Procedure (CEERTX) API and the
Register Activation
Group Exit Procedure (CEE4RAGE) API. So perhaps Scott or Barbara can come up
with a leaky RPGLE
application.

However, activation groups and the APIs mentioned above provide a way for an
application programmer to
handle his own clean up. You could consider them the ultimate Finally block.

As far as the IFS file in use you mentioned, caused by "another
job which has neglected to close the IFS file it opened." Not possible. As
mentioned above, the OS
won't allow it. So the application intentionally had the file still open. In
fact, if you're
thinking about the message from John McKee back on May 29th, the problem was he
had the file open via
EDTF in another session.

Charles Wilt
--
Software Engineer
CINTAS Corporation - IT 92B
513.701.1307

wiltc@xxxxxxxxxx





This e-mail transmission contains information that is intended to be
confidential and privileged. If you receive this e-mail and you are not a named
addressee you are hereby notified that you are not authorized to read, print,
retain, copy or disseminate this communication without the consent of the sender
and that doing so is prohibited and may be unlawful. Please reply to the
message immediately by informing the sender that the message was misdirected.
After replying, please delete and otherwise erase it and any attachments from
your computer system. Your assistance in correcting this error is appreciated.
--
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.