http://archive.midrange.com/java400-l/200608/msg00039.html
Also try the same with os400.stderr.
Gary
On 5/30/2007 9:17 AM, Kevin wrote:
Unfortunately, like I mentioned earlier, the Java method is called from
RPG (not using "java") and looks something like:
C MONITOR
C CALLP JMyMethod(JMyClass
C : Jparm1
C : Jparm2
C )
C ON-ERROR
C ENDMON
Josh Diggs wrote:
What you are seeing is the standard output of the java program in the qshell
environment. If you want to capture this information, the easiest way is
probably to use the greater than symbol at the end of your java command to
redirect standard out to a file.
For example
java test > /logs/testLog.txt
Of course the logs directory would need to exist in the IFS.
-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx
[
mailto:java400-l-bounces@xxxxxxxxxxxx]On Behalf Of Kevin
Sent: Wednesday, May 30, 2007 6:15 AM
To: java400-l@xxxxxxxxxxxx
Subject: Where are Java messsages logged?
This may sound like a stupid question, but where do messages from my
Java program get logged (if anywhere)? Most of my Java experience is
from the PC platform (using Eclipse).
From an interactive job, I have a CL program the calls an an ILE RPG
program that in turn instantiates my Java class. The RPG program then
calls one of the Java class methods. When the Java class file runs, the
screen changes (QSHELL?) and messages flash very quickly (way too fast
for me to read them). Some of the messages are generated from
System.out.println(), some are from Exception.printStackTrace() and some
are from thrown Exceptions. As soon as control returns back to the RPG
program the green screen changes back to the normal environment and the
Java messages are gone.
If I use one of the debuggers to stop the RPG program before the green
screen reverts back to it's normal mode, the green screen is locked up
and I can't scroll back to look at prior messages.
I have even tried a screen capture program to try and record the
messages, but I can't seem to adjust the frame rate to be able to see
all of the messages.
midrange.com
