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


  1.  Home
  2. JAVA400-L
  3. August 2005

Re: OUTPUT parameter on JAVA command not valid in CL program

Monitor for message JVA0122 with a MONMSG command in your CL program.


PierceJ@xxxxxxxxxxxxxxxx wrote:

I am trying to call a Java program from a CL program.  I am able to
successfully call the Java program, but the shell doesn't go away until the
user hits enter.  I want the Java program to behave as if called with the
OUTPUT(* *CONTINUE) parameter on the JAVA call.  However, when calling Java
from CL, this parameter is not allowed.  I have successfully redirected all
my java i/o using the os400.stdout and os400.stderr properties.  I would
rather not have to submit my Java program to batch and then wait in my CL
program using some other means to avoid this behaviour.

Any ideas?

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
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.