Re: Program failure analysis

[Charles Wilt <charles.wilt@xxxxxxxxx>]

So your mainline is just a call to a procedure?

Why?

I hate, hate, hate this.. :)

If you using a linear main, your mainline procedure can have an on-exit.
ctl-opt main(mainline);

dcl-proc Mainline;

monitor;
  //actual mainline code
on-error;
  dump(a);
endmon;

on-exit;
 //cleanup
 return;
end-proc;

Charles

On Wed, Oct 11, 2017 at 11:45 AM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

> BLUF: How do you perform failure analysis of a program hours or days
> after the program fell over?
>
> I have a programming pattern that I use in order to capture a post
> mortem dump in the case of a catastrophic error that I didn't foresee.
> I wrap the entire cycle main program in a MONITOR block and run the
> cleanup everywhere I RETURN, as well as in the ON-ERROR block; it looks
> like this:
>
> monitor;
> ...
> // all is well
> wrkReturnCode = '1';
> wrkReturnMsg = 'All is well';
> exsr setReturnState;
> return;
> ...
> on-error;
>   wrkReturnCode = '0';
>   wrkReturnMsg = 'Casters up!';
>   exsr setReturnState;
>   return;
> endmon;
>
> begsr setReturnState;
>   QsyReleaseProfileHandle(profile_current_handle: errorStruc);
>   if err_use <> 0;
>     dump(a) 'release current';
>   endif;
>   ...
> endsr;
>
>
> Then, ON-EXIT came along!  Following the hint in the manual, I moved all
> the code into a single sub-procedure and called that from the mainline.
> Within that sub-procedure, I put this:
>
> dcl-proc...
>
> ON-EXIT;
>   QsyReleaseProfileHandle(profile_current_handle: errorStruc);
>   if err_use <> 0;
>     dump(a) 'release current';
>   endif;
>   ...
> end-proc;
>
> DUMP is disallowed by RNF0203 (in capital letters, no less!)  What do
> other RPGers think about this programming pattern?  How do you handle
> post failure diagnosis?  Log4RPG?  Spooled file?  CEE4RAGE + *NEW
> activation group?
>
> --
>   --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