Re: JDBCR4 (RPGLE calling Java) problem with passwords -- JAVA400-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: JDBCR4 (RPGLE calling Java) problem with passwords
From: Barbara Morris <bmorris@xxxxxxxxxx>
Date: Tue, 20 Aug 2013 13:40:16 -0400
List-archive: <http://archive.midrange.com/java400-l>
List-help: <mailto:java400-l-request@midrange.com?subject=help>
List-id: Java Programming on and around the IBM i <java400-l.midrange.com>
List-post: <mailto:java400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=unsubscribe>

On 8/19/2013 5:00 PM, James H. H. Lampert wrote:

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 was able to use an OVRDBF to redirect STDERR to a stream file, in
order to capture the stack trace. Would something like that be the only
solution here?

Ah, ok. I misunderstood - thought the RPG program was crashing.

I think you're right that you'll have to redirect the stderr output to prevent it from popping up.

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.