Re: Trapping Stored Procedure Error

On Fri, May 15, 2015 at 9:52 AM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

> On 5/15/2015 9:04 AM, Charles Wilt wrote:
> > I would expect the Java program to see the error.  Unless either the Java
> > program or the RPGLE/CL is submitting a new job.
>
> I'm hardly the expert on this stuff but my personal experience is like
> Gad's.  Say I have an RPG program with no MONITOR, *PSSR, etc.  When an
> error occurs - like substring out of range - the default error handler
> gets control.  At this point, the RPG program is essentially suspended,
> because the default error handler is probably displaying a message to
> *EXT - QSYSOPR, no doubt.  Until that message is answered, RPG doesn't
> get control, and until RPG gets control, the database manager doesn't
> get control and until that happens, JDBC thinks the stored procedure is
> running a long time.
>
>
​Buck....yeah you're correct, didn't click that the job was going into MSGW.

​Charles