|
marcd wrote:
> ...
> Additionally,
>
> Is there a way I can generate a java stack trace within rpg, so that I
> can figure out exactly
> what goes wrong next time?
>
Unfortunately, no. At least not currently ...
For debugging, you could write a little Java method to call the
HSSFWorkbook constructor and get a stack trace, and change your RPG
program to call your new Java method instead of the constructor.
Something like this (untested):
class DebugCREATEWB
{
org.apache.poi.hssf.usermodel.HSSFWorkbook createWB ()
{
try
{
return new org.apache.poi.hssf.usermodel.HSSFWorkbook();
}
catch (Exception e)
{
e.printStackTrace();
return null;
}
}
}
To see the stack trace, you will have to do a couple more things:
0. Sign off and back on
1. ===> ADDENVVAR QIBM_USE_DESCRIPTOR_STDIO 'Y'
2. Either
a. in your SystemDefault.properties file, add a line like this
(starting at the beginning of the line):
os400.stderr=file:stderr.txt
or b. ADDENVVAR QIBM_RPG_JAVA_PROPERTIES
VALUE('-Dos400.stderr=file:stderr.txt;')
(don't forget the semicolon) This will only work if you have a
PTF: V5R2 SI10101, V5R1 SI10069
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.