Preliminary steps

  1. Review Migration tips.
  2. If you are migrating from CICS TS 2.2, ensure that APAR PQ 79565 is installed in all your CICS TS 2.2 regions. This APAR improves CICS TS 2.2 diagnostics, should CICS® TS for z/OS®, Version 3.1 workload arrive at a CICS TS 2.2 region. It also allows a CICS TS 2.2 request processor (AOR) to receive work from a CICS TS for z/OS, Version 3.1 request receiver (listener).
  3. Set the AUTOPUBLISH option on all your CORBASERVER definitions to NO. Setting a CorbaServer to autopublish IORs into the JNDI name spaces could disrupt the migration process.
  4. If you use a distributed routing program to balance method requests for enterprise beans and CORBA stateless objects across the AORs of your logical server, customize your routing program to use the DYRLEVEL parameter. DYRLEVEL is a migration aid. It contains the level of CICS required in the target AOR to successfully process the routed request. (Note that this is the specificnot the minimum—level of CICS required to process the request successfully.) In a mixed-level logical server, when your routing program is invoked for route selection (or route selection error), it can use the value of DYRLEVEL to determine whether to route the request to a back-level or CICS TS for z/OS, Version 3.1 AOR.

    For details of how to use DYRLEVEL, and definitive information about writing a distributed routing program, see the CICS Customization Guide.

    Install your customized program on all the regions (both listeners and AORs) of the EJB server.

    If you use CICSPlex SM to workload-balance method requests you can skip this step. The CICSPlex SM routing program supplied with CICS Transaction Server for z/OS, Version 3 Release 1 checks the DYRLEVEL field and routes requests accordingly.