Suppressing call stacks when RPG call to Java throws Java exception

When calling Java from RPGLE (specifically, JDBC through JDBCR4), I know you can set up a monitor block to contain and handle any exceptions thrown (they're already there), but it still throws up a stack trace, then sits there for several seconds.

I wrote (on the Java400 List, full text at
<http://archive.midrange.com/java400-l/201308/msg00025.html> for reference)

...
Now, obviously, if I were doing this in Java, I'd put it in a try/catch
block. But what about calling from RPG?

to which Barbara Morris replied:

You should be able to use RPG's MONITOR block to catch the error.

If you've already tried MONITOR here, is there some reason it's not
working for you?

Hmm. The JDBCR4 service program *does* use a monitor to keep the Java exception from crashing the calling program.

But it doesn't keep the stack trace from popping up on the screen, which seems a bit unsightly.

Now, I can use an OVRDBF to redirect STDERR to a stream file, but it still sits there thinking for several seconds, before returning control.

Is there a way to suppress the call stack entirely, and avoid the long pause?

--
JHHL