|
Marco, Your not alone with this problem. I have exact the same problem, but because my 7 programs (7 different spreadsheets) will only be needed once in production I fire up the debug and run the programs without any troubles. But what bothers me.... late in 2005 I developed another application taking data from a spreadsheet up in a workfile in QSYS. Adding data from files in QSYS to that workfile and then updated the spreadsheet with new data. This application has been running every day since it went in production, and it have never failed. Best regards, Leif ----- Original Message ----- From: "Marco Facchinetti" <facchinetti@xxxxxxxxx> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: 10. maj 2006 12:23 Subject: POI, HSSFR4 and Debug > Hi, I wrote a simple program to read an Excel file, modify some cells and > > write back on the Ifs. Of course, since I'm an rpg programmer, I used the > service program provided by Scott Klement (HSSFR4). > > The problem is when I run the pgm from the command line I've got an error > > Message . . . . : Java exception received when calling Java method. > Cause . . . . . : RPG procedure HSSF_OPEN in program xlib/HSSFR4 received > Java exception "java.io.IOException:" when calling method > "<init>" with signature "(Ljava.io.InputStream;)V" in class > "org.apache.poi.poifs.filesystem.POIFSFileSystem". > > If I call the same program using the debug (STRDBG PGM(LE36) UPDPROD(*YES) > SRVPGM(HSSFR4)) it's working perfectly. > > POI .jar files are in /QIBM/UserData/Java400/ext. > > Any hint, idea or... > > Thanks in advance > > Marco > > P.S. I saw the thread in: > http://archive.midrange.com/java400-l/200505/msg00133.html > but he ended up writing Java code to fix the problem.
As an Amazon Associate we earn from qualifying purchases.
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.