If you are running Java™ applications in a JVM server, when you upgrade you must check whether the applications use IBM® or vendor classes that are available in the JRE. The OSGi framework has stricter rules for loading classes and you might need to change your applications to run them in a JVM server in this release.
Any package that is prefixed with java is loaded by the OSGi framework as required by the application. If an application uses an IBM or vendor package that is supplied with the JRE, such as com.ibm.misc, you must create a middleware OSGi bundle to make these classes available to the OSGi framework. If you do not change the application, transactions abend with an AJ05 code and java.lang.ClassNotFoundException errors are written to the JVM server error log and CICS® system log.
You do not need to complete these steps for the CICS Java classes, as the JCICS classes are automatically made available in the OSGi framework.
The OSGi bundle fragments are loaded when the OSGi framework is initialized. When the application is called, the application can access the IBM or vendor classes.