Re: MONITOR performance

--- Buck <buck.calabro@xxxxxxxxxxxx> wrote:
> Neither MONITOR nor the *PSSR have an impact on the code when an exception
> does not occur.  There is possible performance impact related to the program
> status data structure and fields beyond column 80.
> 
> In brief, MONITOR is better because it is more granular.  It will let you
> handle the exception when you get it.  The *PSSR takes you out of the
> program logic into a separate subroutine, and makes it very difficult to
> continue processing at a reasonable spot in the logic.  I use them both.
> *PSSR is my 'last ditch, no white messages ever' exception trap.  In my
> *PSSR, I issue a DUMP and then leave the program.
>   --buck

Buck, your comments echo my recollection on the issue, but it's nice to have the
voice of experience to back it up.

Curiosity question:  Do you code the *PSSR in _every_ RPG program you write?  I
absolutely abhor the possibility that a user might ever encounter a 
system-generated
error message, especially one that they can respond to!  I have rarely coded 
PSSR's
in my 20 years on RPG, but then, <gloat> my apps don't generate support calls
either</gloat>.  However, the handful of times that one of my apps have bombed,
either the opportunity to dump was missed, or the problem couldn't be 
duplicated. 
Usually, RPG errors are trapped by the CL that calls the RPG, and that takes 
control
from the user messing things further, but, again, a lot of information is lost 
doing
that.

Thanks,
GA

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com