Gary L Peskin wrote:
Sorry, I'm confused about exactly what the problem is. What do you mean
"The bytes I'm getting in the properties are correct ... but they are the
ebcdic values, not unicode.". Do you mean that the String javaVersion is
coming out as gobbledygook or what?

When I look at the properties object (in debug) there are entries shown. And the byte values that are showing in the property object correspond to the EBCDIC bytes in the IFS file ...

From RDI debug:

value char[16] (id=63)
[0] Â [\u0091]
[1] Â [\u0081]
[2] Â [\u00a5]
[3] Â [\u0081]
[4] K [\u004b]
[5] Â [\u00a5]
[6] Â [\u0085]
[7] Â [\u0099]
[8] Â [\u00a2]
[9] Â [\u0089]
[10] Â [\u0096]
[11] Â [\u0095]
[12] ~ [\u007e]
[13] Ã [\u00f1]
[14] K [\u004b]
[15] Ã [\u00f5]

From DSPF:

9181A581 4BA58599 A2899695 7EF14BF5 0D25 java.version=1.5

So the data is being read from the input stream, but it's not being translated from EBCDIC to Unicode.

Since the IFS file has CCSID 37 ... and the JT400 object knows this, I would expect the contents to be properly translated from CCSID 37 to Unicode.

david


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

This mailing list archive is Copyright 1997-2025 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.