Run-time support for Java™ program objects and for hot-pooling (HPJ) is withdrawn.
In CICS® TS 1.3, as an alternative to running Java programs in a Java Virtual Machine (JVM), VisualAge® for Java, Enterprise Edition for OS/390® (ET/390) could be used to bind Java bytecode into OS/390 executable files, known as Java program objects. The Java program objects were stored in OS/390 PDSE libraries and executed by CICS in a Language Environment® run-unit, or enclave. The Java run-time component of ET/390 provided this run-time support in the CICS region.
The Language Environment enclave could be built and initialized for each invocation, in which case the Java program object was executed under the QR TCB. Alternatively, to reduce performance overheads, a preinitialized and persistent enclave could be reused for multiple invocations of the program. This feature was known as hot-pooling. When hot-pooling was specified for a Java program object, CICS used the PIPI preinitialization services of z/OS® Language Environment to build the enclave, and executed the Java program object in the CICS region under the control of an open transaction environment (OTE) task control block (TCB) in H8 mode.
In CICS TS for z/OS, Version 2.3, run-time support was provided for existing hpj-compiled Java program objects, but no support was provided for developing new Java program objects nor for modifying existing Java program objects. In CICS TS for z/OS, Version 3.1, run-time support for hpj-compiled Java program objects is withdrawn.
You must migrate any hpj-compiled Java program objects to run in a Java Virtual Machine (JVM). The CICS Migration Guide explains how to do this. For information about the CICS JVM and about Java programming for CICS, see Java Applications in CICS.
If you attempt to execute a Java program object in CICS TS for z/OS, Version 3.1, an ALIG abend is issued.
The open TCB mode H8, which was used for hot-pooling Java program objects, no longer exists.