Restrictions

• Users of JAAS features in September, 2003 PTF UQ80389 who are running the JVM on z/OS V1R2 or lower will encounter a load error for libThreadSubject.so, which manifests itself in the form of an error message similar to the following:

Could not load dll : 
 /{JAVA_INSTALL_DIR}/bin/libThreadSubject.so
: EDC5130I Exec format error.
java.lang.UnsatisfiedLinkError: 
   /{JAVA_INSTALL_DIR}/bin/libThreadSubject.so: 
EDC5130I Exec format error.
  at java.lang.ClassLoader$NativeLibrary.load(Native Method)
  at java.lang.ClassLoader.loadLibrary0(ClassLoader.java
       (Compiled Code))
  at java.lang.ClassLoader.loadLibrary(ClassLoader.java
       (Compiled Code))
  at java.lang.Runtime.loadLibrary0(Runtime.java(Inlined 
        Compiled Code))
  at java.lang.System.loadLibrary(System.java(Inlined 
        Compiled Code))

where {JAVA_INSTALL_DIR} is the directory in which the Java product is installed.

This problem is fixed with PTF UQ82210 which became available in November, 2003.

• If you are creating a socket in Java and calling Socket.getTcpNoDelay(), apply PTF UQ42728.
• If you use TCP/IP V3, IBM recommends you apply APAR PQ37095. The problem description of the APAR is:
  • Socket Close Processing is delaying too long when using option SO_LINGER
• The SDK1.3.1 product at PTF level UQ70881 and the SDK1.4.0 generally available product both have a problem if the "export LANG=" environment variable is used without explicitly including the corresponding IBM code page designation. (Note that this problem has been corrected in the subsequent PTF, UQ71871.)
  
  If you are using "Hr_HR" (for example) as the language desired and set "export LANG=Hr_HR", you will receive an "OC4" abend. In order to avoid getting the abend, when specifying a language, use the following format:
  
  

  export LANG=Hr_HR.IBM-870
  

  The problem is described in APAR PQ67912. The default settings are not affected. We are working on a PTF to resolve the problem.
  
  The circumvention is to specify the encoding part for the LANG setting. For example:
  
  

       export LANG=Hr_HR.IBM-870
       export LANG=Ja_JP.IBM-939
       export LANG=Ko_KR.IBM-933
  

  export statements for other LANG circumventions would be similar
  
  
• To ensure restoring of all the program attribute bits set when the product is delivered, the userid under which the installation is done, must have the following:
  • UID(0) or READ access or higher to the BPX.SUPERUSER facility class
  • be connected to a group that has a GID
  • have READ access or higher to the BPX.FILEATTR.PROGCTL and BPX.FILEATTR.APF facility classes
  
  With the installation of PTF UQ73928 or above, the userid must also have READ access or higher to BPX.FILEATTR.SHARELIB facility classes.
  
  If access to BPX.FILEATTR.SHARELIB is not available, there will be a warning message. The JVM will still be usable, but performance with will not be optimized.
  
  
• If using hardware encryption via IBMJCE4758 on z/OS V1R3 or below, a customer may experience a failure executing the following command:

   hwkeytool -genkey -keyalg RSA -keystore RSAkeystore 
       -storetype JCE4758KS 
  

  Please see information in APAR PQ73916 for status and bypasses.
  
  

Other Considerations

To allow IMS to run with the SDK1.4 Java product in addition to running with the SDK1.3 Java product:

1. The SDK1.3 product must be at PTF UQ76273 or later
2. The SDK1.4 product must be at PTF UQ77468 or later
3. For IMS V7, install PTF=UQ80879 (APAR=PQ76609)
4. For IMS V8, install PTF UQ82427

Note: for running with the SDK1.4 product, follow the IMS instructions to specify the XPLINK environment.

To allow DB2 to run with the SDK1.4 Java product in addition to running with the SDK1.3 Java product:

1. The SDK1.3 product must be at PTF UQ76273 or later
2. The SDK1.4 product must be at PTF UQ77468 or later
3. For DB2 V7, install PTF=UQ81669 (APAR= PQ76769)
4. For DB2 V8, the support is included in the base.