[progress Communities] [progress Openedge Abl] Forum Post: Re: Trapping Error Messages...

  • Thread starter Thread starter Laura Stern
  • Start date Start date
Status
Not open for further replies.
L

Laura Stern

Guest
Re Marian Edu's post on 9/22 at 1:20: Re your last paragraph - we did not say this only works for 'stop conditions that have error messages'. We said "You would be able to code CATCH blocks using either of these new object types." (i.e., P.L.Stop or P.L.StopError. But only the latter implements Progress.Lang.Error - thus only stop conditions with error messages are the ones trappable by a CATCH block for Progress.Lang.Error or Progress.Lang.SysError. You would be able to use a CATCH block explicitly for P.L.Stop to trap STOP raised by the STOP statement, STOP-AFTER or CTRL-C and also for lock wait time-out (which is basically CTRL-C). There are other things like GPFs or Out of memory that are not trappable today with DO ON STOP and that will continue to be the case with this new feature. They will not be trappable.

Continue reading...
 
Status
Not open for further replies.
Back
Top