|
Gary L Peskin wrote: > > There should be a stack trace somewhere showing exactly what's causing the > exception, probably a FileNotFound or an authority problem. If you can't > locate the stack trace in the job log or spool files, place a try/catch > block around the offending statement and in the catch block to a > printStackTrace. > When you call a Java method from RPG, you don't get a stack trace. The way I've debugged this kind of thing is to write a little Java method just to do the method call that the RPG program is failing on, and have the RPG program call that method instead of calling the method that's getting the error. The new method can do a try/catch and printStackTrace.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.