Re: Convert from free to fixed

and the condition manager is now looking for somebody to shoot.

... monitor is your friend

and a condition handler is your BEST friend.

The *PSSR subroutine is archaic and not a good solution when managing application errors that run on a web server. I would strongly suggest using condition handlers for this as you have MUCH more control over how to proceed. Further, *PSSR is an 'after the event' clean-up routine. Not only has the exception been thrown but it has percolated to the control boundary, promoted to a function check (CPF9999) and the condition manager is now looking for somebody to shoot.

Condition handlers beat monitor because monitor will handle any exception thrown within the monitor group. Condition handlers work even better than MONMSG because you can choose to handle the exception based on any criteria you wish. Also, the condition handler is called BEFORE the original *ESCAPE or *NOTIFY message has reached the control boundary so the call stack is pristine. You can write code in your condition handler to pause the process so you can debug the problem. I have been able to recover from divide by zero, substring length and array index errors this way. The process continues from the next line of code as if nothing went wrong. You can't beat that!

I genuinely believe it is one of the many unsung heros of ILE.

Cheers

Larry Ducie



--
This is the RPG programming on the IBM i / System i (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.