Re: Trapping Stored Procedure Error

[Charles Wilt <charles.wilt@xxxxxxxxx>]

I would expect the Java program to see the error.  Unless either the Java
program or the RPGLE/CL is submitting a new job.

You'd probably be best served by posting the question to the JAVA-400 list
with some of the Java source.

Charles

On Fri, May 15, 2015 at 8:57 AM, Gad Miron <gadmiron@xxxxxxxxx> wrote:

> Hello guys
>
> We have a Java-Windows application that uploads text files (one at a time)
> to the iSeries/System i/AS400 machine and then calls a Stored Procedure to
> process
> the file uploaded.
> The SP calls an RPG program that in turn conditionally call other RPG/CL
> programs.
> all of the above is executed in a QZDASOINIT job (spawned especially?)
>
> Sometimes one of the RPG/CL programs in the process "bombs" (with a CPFXXX)
> but the guy using th Java application is not aware of it, it is the SYSOPR
> actually that
> sees the MSGW status of the QZDASOINIT job and calls a programmer to look
> at it.
>
> Now,
> Is there a way to trap the errors and inform the Java application user that
> there was an error ?
> This* without* inserting MONITOR lines in the RPG programs and manually
> returning
> some kind of a return code?
>
> The Java programmer tell me she can trap an error but an error is not
> received.
> (perhaps it is another QZDASOINIT job? )
>
> Any advice will be appreciated
>
> Regards
> Gad
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>