These ASCII and EBCDIC considerations apply to both zSeries® and
i5series platforms.
- Script files:
- If a script file invokes another script file, it might not work if the
second script file is not EBCDIC encoded. In this case the content of second
script file needs to be copied to the first one.
- Properties files:
- To avoid codepage problems it is recommended that the properties files
are packaged in .jar file and are read using ResourceBundle.getBundle(). The
XML or properties file contained in a .jar file needs to be in ASCII, while
properties file that is stored in the hierarchical file system (integrated
file system for iSeries™)
needs to be in EBCDIC.
- JNI:
- When calling a c or a c++ routine from Java™ or when calling a JVM from a c or c++
program, the ASCII-EBCDIC conversion is not taken care of automatically.
- Socket communication:
- When communication takes place between an ASCII client and an EBCDIC server,
conversion might not take place automatically. When both programs are in java
and UTF is used to send or receive data then the conversion takes place automatically.
Note: Text and binary files are treated differently. Use binary
specific methods to access binary files.