> -----Original Message-----
> From: IBM Mainframe Discussion List On Behalf Of Kirk Wolf
>
> [ snip ]
> >> - but the LE options and storage reports are also written (in
> >> EBCDIC) to stderr by default (under a Unix shell),
> >> and is also getting converted...which probably accounts for much
of
> >> the "gibberish"
> >
> > No, the LE storage report that occasionally appears in stderr is
> > perfectly readable. Only the -verbosegc output appears as
> > "gibberish", regardless what -Dxxx.encoding I specify or where I
> > specify it. And the "gibberish" appears only in stdout;
> never in stderr.
>
> But the storage report that you posted is not from the "java"
> command; it is probably from a shell.
> My guess was that the stderr output from the java command has
> output in both ASCII (from java System.err) and EBCDIC (from
> LE report).
> Perhaps your editor simply infers a codepage from the
> beginning of the file?
I still don't understand enough about the JVM to answer that. I will
note that, via my "TechQA" ETR with IBM, after I included
-Xverbosegclog:filename in the JAVA_OPTIONS I began getting
human-readable output from verbosegc in the file I specified, so
apparently the application is (was) "intercepting" its output and
translating it to who-knows-what codepage.
The project owner for this application is going to try to get a
benchmark running it on a "native" AIX machine (hopefully later this
week), so I guess I'll "sit back and wait" for a while.
Thanks for your and everybody else's help so far. I may be back. :-|
-jc-
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
