× 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.



This was asked in the RPG400 midrange forum about a week ago.  You will have
to check the archives for it, but it had something to do with overriding
where stdout wrote to.  

HTH,
Aaron Bartell

-----Original Message-----
From: TitanRebel [mailto:TitanRebel@xxxxxxxxxxx]
Sent: Tuesday, September 09, 2003 11:57 AM
To: Java Programming on and around the iSeries / AS400
Subject: standard out and standard error on the iSeries


Is there a way to see standard out and standard error logs on a Java 
program running on the iSeries in "real time"?  I know that the Java 
programs Job produces a spooled file called QPRINT which contains the 
information for both out and err.  Unfortunately, it buffers writting to 
this file, and you can't see "real time" information.

Is there a way to make the Job write to the spooled file without 
buffering?  Or, is there a way to force a "flush" of the buffer?

Thanks.


_______________________________________________
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L)
mailing list
To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/java400-l.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.