×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 8/19/2013 8:27 PM, James H. H. Lampert wrote:
Is there a way to suppress the call stack entirely, and avoid the long
pause?
Are you using the QIBM_RPG_JAVA_EXCP_TRACE environment variable to
enable the stack trace? Unlike other Java-related environment variables
that are only checked at JVM startup, the RPG runtime checks that one
for every Java method call that gets an exception.
So you could turn it off (remove it or set it to a value other than 'Y')
when you expect a Java exception on a method call, and then turn it back
on after the call. But then you miss getting the stack trace for
different exceptions than the ones you expect.
So maybe better would be to embrace the stack trace and add some code in
your RPG program to write additional information (RPG program,
timestamp, what exceptions are considered ok at that point, etc) to
stderr when you get a Java exception, to put the stack trace in context.
This mailing list archive is Copyright 1997-2024 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.
midrange.com
