Re: ILE error message handling

[bmorris@xxxxxxxxxx]

>Date: Wed, 7 Mar 2001 08:27:46 -0600
>From: "Jade Richtsmeier" <jade.richtsmeier@MCIS.cog.mn.us>
>
>Here's my situation.  I have a program that is made up of four modules.
The
>program is called from a menu and is compiled with the QILE activation
>group.  All of our service programs are compiled with *caller activation
>group.  If there is an error in any one of the modules or one of the
service
>programs, the program just 'hangs'.  PSSR isn't handling the error.  I
have
>the PSSR routine defined in every module and service program.

Jade, I'm not aware of any problem that will cause a PSSR not to handle the
error.  What I would do if I were you is step through the program in the
debugger during an error situation.  Before you get the error, set a break
point in all the possible PSSRs just to make sure you see if you _do_
ever get to a PSSR.  I wonder if you're actually getting to a PSSR but
for some reason you're getting another error in the PSSR and therefore
looping in the PSSR.  If this turns out to be the problem, you'd want to
put some loop prevention code in the PSSR, like this:

C      *pssr      begsr
C                 if       in_pssr <> '1'
C                 eval     in_pssr = '1'
C                 ... do your PSSR stuff
C                 endif
C                 eval     in_pssr = '0'
C                 endsr

Barbara Morris


+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---