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



On 12 Apr 2013 13:33, Troy Hyde wrote:
I'm sure I'm overlooking something pretty basic but even with my
ninja Google skills I have been unable to determine how to make what
has got to be a simple switch.

I'm running java from RPGLE after redirecting stdout by setting the
envvar QIBM_RPG_JAVA_PROPERTIES with the value
-Dos400.stdout=file:/myfolder/myfile.txt;
and setting QIBM_USE_DESCRIPTOR_STDIO to Y.

My output is properly going to the file, but each time a new job
starts, it replaces the existing file when I would like it to
append.

Is there another environment variable or a different value that
someone can share?

The following message may be of interest?:
http://archive.midrange.com/rpg400-l/200501/msg00682.html

If so, apparently the second doc link in the above message is no longer valid. However the following message has a doc link for the usage of the FILEAPPEND for the QIBM_QSH_CMD_OUTPUT environment variable:
http://archive.midrange.com/midrange-l/201201/msg00332.html

And the following message confirms the supposition in the prior message, that the uppercase for FILEAPPEND matters:
http://archive.midrange.com/midrange-l/201201/msg00336.html

There may be something in the results of the following web search:
http://www.google.com/search?q=QIBM_RPG_JAVA_PROPERTIES+stdout


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.