18.08.2013 Views

ClearPath OS 2200 Series Release 13.2 Software Planning and ...

ClearPath OS 2200 Series Release 13.2 Software Planning and ...

ClearPath OS 2200 Series Release 13.2 Software Planning and ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Virtual Machine for the Java Platform on <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> JProcessor (JPJVM)<br />

<strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> <strong>Release</strong> 12.1<br />

JVM Level 4R2A<br />

Migration<br />

The following statement in quotes from section 3.2 Environment Variables in the JVM<br />

user guide for <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> <strong>Release</strong> 12.0 is no longer valid <strong>and</strong> is removed from<br />

the JVM user guide for <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> <strong>Release</strong> 12.1: “The FILE.ENCODING value<br />

should be added only if the default coded character set (CCS) does not correspond to the<br />

CCS associated with the default locale or the locale in force when the JVM on <strong>OS</strong> <strong>2200</strong><br />

is initiated.” Setting the system property to anything other than one of the Sun provided<br />

st<strong>and</strong>ard character sets is dangerous. It can cause JVM initialization failures in Java SE<br />

1.5. Sun added a new java.nio charset mechanism in Java J2SE 1.4. Sun left the old<br />

deprecated converter mechanism in place, but its usefulness has eroded over time. The<br />

new java.nio charset mechanism should be used for Unisys provided charsets.<br />

<strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> <strong>Release</strong> 12.0<br />

JVM Level 4R2<br />

Compatibility<br />

JVM 4R2 requires CIFS 6R3 or higher.<br />

5.54. Virtual Machine for the Java Platform on<br />

<strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> JProcessor (JPJVM)<br />

<strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> <strong>Release</strong> 12.1<br />

JPJVM Level 6.1<br />

Migration<br />

The following statement in quotes from section 3.2 Environment Variables in the CP12.0<br />

JPJVM user guide is no longer valid <strong>and</strong> is removed from the CP12.1 JPJVM user guide.<br />

“The FILE.ENCODING value should be added only if the default coded character set<br />

(CCS) does not correspond to the CCS associated with the default locale or the locale in<br />

force when the JVM on <strong>OS</strong> <strong>2200</strong> is initiated.” Setting the system property to anything<br />

other than one of the Sun provided st<strong>and</strong>ard character sets can cause JVM initialization<br />

failures in Java SE 1.5. In Java SE 1.6, it is silently ignored <strong>and</strong> UTF-8 is used instead of<br />

what was specified. Sun Microsystems added a new java.nio charset mechanism in Java<br />

J2SE 1.4. Sun Microsystems left the old deprecated converter mechanism in place, but<br />

its usefulness has eroded over time. The <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> JProcessor JVM only<br />

supports the new java.nio charset mechanism for Unisys provided charsets.<br />

<strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> <strong>Release</strong> 12.0<br />

JPJVM Level 6.0<br />

Compatibility<br />

The CIFS utility, ZIPUT, requires use of the <strong>OS</strong> <strong>2200</strong> JVM which can be installed<br />

concurrently with JPJVM. The I18N proprietary classes have been removed.<br />

5–60 7831 0349–043

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!