Re: STRDBG/ENDDBG required to prevent Java open exception

Jon Paris wrote:

 >> ... mentions that three file descriptors should be opened in the job for
Java I/O to work when the JVM is started by the invocation API

I notice that in your RPG code Barbara that all files are opened read/write
whereas the C example only opens null1 that way, the others are write only.
Is that another error in the C example or doesn't it make any difference ?

Hmm, good catch.  I had another version of the program that opened one
for read and two for write; I forgot about that when I merged them to
use a loop.  The new version does seem to fix up the various problems
with Java I/O.  (I originally wrote it because the os400.stdout and
os400.stderr Java properties seemed to be ignored unless the file
descriptors were opened before any I/O was done by Java.)

I'm not sure if it makes a difference, but I suspect not.  I don't think
it could be the case that these file descriptors are actually used for
stdin, stdout and stderr; I think that for some reason they just have to
exist.  If they were actually used, you would probably have to ensure
(somehow) that file descriptor 0 was stdin (read-capable), 1 was stdout
(write capable) and 2 was stderr (write capable).