|
I don't think dump in an on-exit makes much sense...
Sure something could go wrong in the cleanup...especially
On Wed, Oct 11, 2017 at 2:04 PM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:
On 10/11/2017 3:24 PM, Charles Wilt wrote:
So your mainline is just a call to a procedure?
Why?
Using cycle main is just inertia. Something I will address. Making the
mainline into a single sub-procedure was the first thing I tried in
order to be able to use ON-EXIT.
If you using a linear main, your mainline procedure can have an on-exit.
DUMP is disallowed in the ON-EXIT block. How do you report errors
trapped in there? I want the program to never, ever go into MSGW. When
it traps an unexpected error, I'd like to know that it happened, and
have a fighting chance of sussing out why.
--
--buck
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact copyright@midrange.com.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.