|
|
| |
 IBM 64-Bit SDK for z/OS, V1.4 - Restrictions and Other Considerations
(last updated October, 2006)
 | | |
Restrictions
- The z/OS MEMLIMIT parameter should be set to 256MB or greater.
- Support for hardware cryptography requires installation and initialization of the z/OS Integrated Cryptographic Service Facility (ICSF) component of z/OS or z/OS.e. That version of ICSF will be available in December 2004 as a web deliverable called: ICSF 64-bit Support for z/OS V1R6 and z/OS.e V1R6.
- For cryptographic key generation with IBMJCE4758 present:
If you have installed the IBMJCE4758 hardware provider, be sure when generating software keys that IBMJCE is before IBMJCE4758 in the java.security provider list.
For more information see
z/OS Unique Considerations for the Java 2 SDK, Standard Edition, V1.4 and
Java Cryptography Extension V1.2.1, Hardware Cryptography IBMJCE4758 Overview.
- The persistent reusable and shared classes support in the 31-bit, IBM SDK for z/OS, Java 2 Technology Edition Product (5655-I56) is not present in this 64-Bit product.
- The
new I/O (NIO) channels in this SDK and Runtime Environment have a number of limitations, listed in the following table. Click on the defect number to link to the Sun Web site that documents the limitation. To go directly to the bug, you must be a registered member of the Java Developer Connection. To see which bugs have been fixed, you should check the contents of any service refreshes of this SDK and Runtime Environment.
| List of new I/O limitations
|
|
Sun bug number
|
Brief description of limitation
|
|
4460065
|
Interruption of file-locking operations not completely implemented |
|
4643189
|
FileChannel.transferTo() fails for files > 2^31 - 1 bytes |
|
4696508
|
Selector doesn't synchronize as specified |
|
4673298
|
Locking in Preferences sometimes fails on NFS mounted drives. NIO file locking over NFS might also be affected. |
|
| |
|
|
|