×
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.
Hi all,
Just found a couple things concerning the Java Toolbox (i.e. JT400) that I
thought I would share with the group. When calling RPG programs (i.e. *PGM
objects) using the ProgramCall object it (the RPG program) relinquishes
control back to the Java program too soon if calls to QShell API's are made
or if you use procedure pointers (for the purpose of callbacks) in your RPG
program.
As best I can tell, and from what I know about what is going on under the
covers, it would seem that when a new pseudo thread is created in the
callstack that gains control flow vs. the RPG program that was originally
called that it is thinking the program has abnormally ended (which is the
message I get when using program.getMessageList() upon the program failing).
I have addressed the situation by putting a data queue layer between the
Java and RPG to do communication vs. using ProgramCall and everything now
works as expected.
Any comments on why this would be happening? I would consider this a bug in
JT400 as of right now.
Aaron Bartell
http://mowyourlawn.com
midrange.com
