Trapping Stored Procedure Error

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