Migration for Java programs that do not run in a JVM (hpj-compiled Java program objects)

Run-time support for Java™ program objects and for hot-pooling (HPJ) is withdrawn in CICS® Transaction Server for z/OS® Version 3 Release 1. Any Java programs that you had processed using the VisualAge® for Java, Enterprise Edition for OS/390® bytecode binder (hpj) to run as Java program objects in CICS, must be migrated to run in a Java Virtual Machine (JVM). To do this:

To avoid problems with deprecated APIs, you should develop all new Java programs forCICS Transaction Server for z/OS, Version 3 Release 1 using an application development environment that supports Java 2 at the same version of Java as used by CICS. You may run code compiled with an older version of Java in a new runtime, provided that it does not use APIs that have been removed in the newer version of Java. Note also that enterprise beans that support the EJB 1.0 specification need to be migrated to the EJB 1.1 specification level using the Assembly Toolkit (ATK) or the Application Assembly Tool (AAT), which are supplied with IBM® WebSphere Application Server.. Enterprise beans developed using any version of the EJB specification after EJB 1.1 must restrict themselves to the EJB 1.1 APIs.

[[ Contents Previous Page | Next Page Index ]]