Migration tips

This section briefly lists some of the ways in which EJB and Java support has changed between CICS TS for z/OS, Version 2.2 and CICS® Transaction Server for z/OS®, Version 3 Release 1. All these changes are described in detail in Setting up Java support. They are listed here, together with some general tips, as a reminder of things to be aware of when migrating an EJB server to CICS TS for z/OS, Version 3.1.

  1. In CICS TS 2.2, JVM profiles were stored in a PDS member. In all later releases, including CICS TS for z/OS, Version 3.1, they are stored in the HFS directory pointed to by the JVMPROFILEDIR system initialization parameter.
  2. The default JVM profile used by CorbaServers in CICS TS 2.2 was DFHJVMPR. In all later releases, including CICS TS for z/OS, Version 3.1, it is DFHJVMCD.
  3. The default JVM properties file used by CorbaServers in CICS TS 2.2 was dfjjvmpr.props. In all later releases, including CICS TS for z/OS, Version 3.1, it is dfjjvmcd.props.
  4. Don't enable any new, CICS TS for z/OS, Version 3.1-specific, attributes on resource definitions during the "rolling upgrade" process. Use of these new features must wait until the whole logical server—both listener regions and AORs—has been upgraded.
  5. From a CICS TS for z/OS, Version 3.1 AOR, you can re-publish a deployed JAR file that has previously been published from an earlier release of CICS without first retracting it. The IORs of the beans are updated to 3.1 format. However, you cannot do the reverse. From an earlier release of CICS, before re-publishing a deployed JAR file that has previously been published from a CICS TS for z/OS, Version 3.1 AOR you must first retract it; furthermore, because earlier CICS releases do not understand the format of CICS TS for z/OS, Version 3.1 IORs, you must retract it from a CICS TS for z/OS, Version 3.1 AOR.
    Bear this in mind if, for any reason, you need to back out the upgrade of one or more AORs. If you ever need to revert the IORs of enterprise beans that have been published from a CICS TS for z/OS, Version 3.1 AOR to an earlier level of CICS (so that they can be routed to a back-level AOR once more) you must:
    1. Retract the deployed JAR file from a CICS TS for z/OS, Version 3.1 AOR
    2. Publish the deployed JAR file from a back-level AOR

    Trying to re-publish the beans without retracting them first, or trying to retract them from the wrong level of CICS, results in an InvalidUserKeyException: Bad version number exception.