The Java for OS/390 FAQ () contains these notes on ASCII/EBCDIC issues: 'One important aspect of the S/390 environment that can sometimes raise portability issue with Java code is that OS/390 uses the EBCDIC character encoding instead of the more common ASCII. Within the scope of the JVM, all character and string data is stored and manipulated in Unicode, and I/O data outside of the virtual machine (disk, network, and so forth) is converted to the native platform encoding. However, Java applications that implicitly assume ASCII in specific situations might require some alterations to run as expected under OS/390. There are a number of environmental tricks that are often useful to test whether implicit ASCII assumptions are in effect.

I posted code to do EBCDIC to ASCII in another thread. What ASCII data would you convert to. COBOL to Java - Converting EBCDIC to ASCII Overview Mainframes use EBCDIC character-set to maintain data files. During the migration of a COBOL application to Java.

For instance, for config files read in during start-up (or other 'adminstrative' file manipulation), you can use a simple command-line utility to convert those files to the appropriate encoding that you require. Free Download Horse Riding Games Full Version. In some cases, changing JVM properties can also allow successful functionality tests, but because this can produce other side effects, the long term solution is sometimes best addressed in code. The Java language contains the abstractions necessary to handle the switch between character encodings.