Upgrading CICS to use multiple releases concurrently

This scenario illustrates how you can run some of your regions at one release of CICS TS and other regions at another release of CICS TS. Doing this gives you the flexibility to offer newer features to some parts of the business, while maintaining continuity in other parts.

Examples of where a multi-release environment could be used include:
  • Allowing Java application developers to take advantage of new features in CICS Liberty as they become available, without disrupting the core infrastructure.
  • Allowing a subset of regions to exploit functions in CICS, for example, in CICS TS V5.4:
    • Using WLM Health in regions where HTTP requests are received from a Virtual IP Address (VIPA).
    • Additional MQ capability and security provided by MQ monitors
    • EXEC CICS API for asynchronous processing.
  • Maintaining a dependency on a specific version of CICS for certain applications or tools, without hindering the adoption of new function elsewhere in the environment.

In all these examples, the aim is to upgrade only a part of an existing environment, maintaining the continuity and availability of that existing environment.

About this scenario

The scenario in this section covers two of these examples of multi-release operation:
  1. Providing Java application developers with access to the most up-to-date Liberty features, while leaving the rest of the environment at the existing release of CICS TS.

    In this example, part of an application runs in a Liberty JVM server in dedicated Liberty-owning regions (LORs). This part of the application is accessed directly through HTTP and connects to existing business logic through Distributed Program Link (DPL) over MRO. High availability and load balancing for the Liberty part of the application is achieved by using port sharing and Sysplex Distributor. CICSPlex SM Workload Management (WLM) is used to load balance calls to the COBOL part of the application that runs in the existing application-owning regions (AORs).

  2. Providing application developers with access to the EXEC CICS API for asynchronous processing that is provided in CICS TS V5.4, while leaving the rest of the environment at the existing release of CICS TS.

    In this example, the new applications need to continue to interact with existing applications. To avoid impact on the existing environment, new application-owning regions will be added to the existing configuration. Work is directed dynamically to the appropriate region using CICSPlex SM Workload Management.

In both cases, this section assumes that
  • Changes are made on an LPAR-by-LPAR basis, while maintaining availability of the existing workload.
  • The CICS and CICSPlex SM agent code will be maintained at the same CICS TS release within a CICS region.
  • All CICS regions use a single, shared CSD.
  • You have checked the requirements for running existing applications and tools on the new release of CICS. (See Planning to upgrade for details of what to check.)
In outline, the scenario has these steps:
  1. Upgrade CICS Explorer to the new release.
  2. Upgrade LPAR 1 to the new release:
    1. Update the CICS SVC, LPA, and CSD
    2. Upgrade the CICSPlex SM topology
  3. For the example of providing access to up-to-date Liberty only, upgrade the Liberty-owning regions on LPAR 1.
  4. For the example of providing access to the asynchronous API only, introduce new application-owning regions on LPAR 1.
  5. Upgrade LPAR 2 to the new release:
    1. Update the CICS SVC, LPA, and CSD
    2. Upgrade the CICSPlex SM topology
  6. For the example of providing access to up-to-date Liberty only, upgrade the Liberty-owning regions on LPAR 2.
  7. For the example of providing access to the asynchronous API only, introduce new application-owning regions on LPAR 2.

Initial configuration

The diagram shows the set up of the two LPARs at the start of these examples.

The initial configurationThe diagram shows two logical partitions (LPARs), in which CICS workload is running.

All regions are running CICS TS for z/OS V5.3, with a single, shared CICS system definition file (CSD). The environment consists of a single CICSplex to manage all the CICS regions.

There are two logical partitions (LPARs):

LPAR 1 is running CICS TS for z/OS and CICSPlex® SM V5.3. It has:
  • One Maintenance Point (MP) CMAS for the CICSplex. The MP CMAS is connected to the CMAS regions that are assigned to manage the CICSplex on LPAR 1 and LPAR 2. Only the Web User Interface (WUI) server region is connected to the MP CMAS.
  • One non-Maintenance Point CICSPlex SM address space (shown as CMAS 1A in the diagram). This CMAS connects to the MP CMAS and the CMAS on LPAR 2. This CMAS is assigned to manage the CICSplex defined in the MP CMAS. All CICS regions on LPAR 1 are connected to this CMAS.
  • One Web User Interface (WUI) server. The WUI server connects directly to the MP CMAS.
  • A group of terminal-owning regions (TORs). These regions are linked to application-owning regions (AORs) on LPAR 1 and LPAR 2 using MRO connections.
  • A group of Liberty-owning regions (LORs). These regions are linked to AORs on LPAR 1 and LPAR 2 using MRO connections.
  • A group of application-owning regions (AORs). These regions are linked to terminal-owning regions (TORs) and Liberty-owning regions (LORs) on LPAR 1 and LPAR 2.
LPAR 2 is also running CICS TS for z/OS and CICSPlex SM V5.3. It has:
  • One non-Maintenance Point CICPlex SM address spaces ((shown as CMAS 2A in the diagram). This CMAS is connected to the MP CMAS and to the CMAS on LPAR 1. This CMAS is assigned to manage the CICSplex defined in the MP CMAS. All CICS regions on LPAR 2 are connected to the CMAS.
  • A group of terminal-owning regions (TORs). These regions are linked to application-owning regions (AORs) on LPAR 1 and LPAR 2 using MRO connections.
  • A group of Liberty-owning regions (LORs). These regions are linked to AORs on LPAR 1 and LPAR 2 using MRO connections.
  • A group of application-owning regions (AORs). These regions are linked to terminal-owning regions (TORs) and Liberty-owning regions (LORs) on LPAR 1 and LPAR 2.

Both sets of TORs are defined with the same z/OS Communications Server generic resource. This means that, when the regions are shut down on one LPAR, the work transfers to the regions on the second LPAR. CICSPlex SM can pass work that comes in to a TOR to any available AOR. This means that, each TOR connects to every AOR.

All Liberty-owning regions (LORs) receive work using Sysplex Distributor and port-sharing.

The CICSplex has a Workload Management Specification with a default "rule" which routes work from the terminal-owning regions and Liberty-owning regions to the application-owning regions. This means that, when the regions are shut down on one LPAR, the work transfers to the regions on the second LPAR.

Back up any data sets that you need to retain

Before you start any upgrade, you should back up any data sets that you need to retain. These data sets include CICS system definition data sets (CSDs), CICSPlex SM data repositories, and exported WUI repositories.

Although we recommend that you keep a back-up of your CMAS data repositories, if you later need to back out the upgrade, you should use the EYU9XDUT job to reset the repository. See Upgrading CICSPlex SM for details.

Upgrade the CICS Explorer

Upgrade the CICS Explorer to a version that supports the target new release: in this example, CICS TS 5.4.

Upgrade the first LPAR

In this section, you upgrade one LPAR completely, then start the upgrade on the second LPAR. Start with the LPAR on which the MP CMAS is running. If you are not running a WUI server, ignore the steps that refer to it.

  1. Dynamically update the CICS SVC while CICS is running. Use the same SVC number as the CICS TS 5.3 SVC, but replace it with the CICS TS 5.4 SVC. The highest-level CICS SVC is backwards-compatible. You need to do this because all CICS regions that are communicating by using MRO on the same LPAR must use the same SVC, and because CICS does not start with a down-level SVC.
  2. Ensure interregion communication (IRC) is closed on every system on the LPAR, including batch jobs and any potential users of EXCI.
  3. Dynamically update the LPA modules while the interregion communication (IRC) is closed.
  4. Re-open interregion communication (IRC) in the active CICS regions on LPAR 1 and confirm that the CICS connections have been acquired.
  5. Upgrade the CSD. Ensure that all GRPLISTs that are used by the CICS regions on either LPAR include the required CSD compatibility groups (see CICS-supplied compatibility groups for details).
  6. Shut down the MP CMAS, upgrade it and restart.
  7. Shut down the WUI, upgrade it and restart.
  8. Check that the CICSplex is working:
    • Check that the unmodified CICS TS V5.3 CMASs have reconnected to the upgraded CICS TS V5.4 MP CMAS.
    • Check that the CICS Explorer and WUI server are correctly showing the active CICS TS V5.3 CICS regions
  9. Create a new CICS TS 5.4 CMAS and start it.
  10. Use the CICS Explorer or WUI to create CMAS-to-CMAS definitions (CMTCMDEF) from the existing CMAS regions to the new CMAS.
  11. Use the CICSPlex SM EYU9XDBT utility to create a batch job to define CMAS-to-CMAS definitions from the new CMAS to the existing CMASs. You can use the CICSPlex SM sample EYUJXBT2 as a template for the commands.
  12. Assign the new CMAS to manage the CICSplex:
    • In the CICS Explorer SM Administration perspective, use the CICSplex definitions view to right-click on the CICSplex and select Assign to CMAS.
    • Use the CICS Explorer or WUI to confirm that the new CMAS is listed as an Active CMAS in the CICSplex view.

The diagram shows the configuration on LPAR 1 after step 8.

LPAR 1 is partially upgraded. The MP CMAS and WUI have been upgraded and verified but the new CMAS that runs V5.4 is not yet in place.The diagram shows two logical partitions (LPARs), in which CICS workload is running. The MP CMAS and WUI server in LPAR 1 are now running CICS TS V5.4.

Upgrade Liberty regions on LPAR 1

The steps in this section are required only for the example of providing Java application developers with access to the most up-to-date Liberty features, while leaving the rest of the environment at the existing release of CICS TS.

In these steps, all Liberty-owning regions on the LPAR are stopped, upgraded, and restarted at the same time. An alternative sequence would be to do this on each region at a time.

  1. Quiesce the Liberty-owning CICS regions on LPAR 1 and perform a shutdown, ensuring that it is stopped cleanly (see message DFHRM0204).
  2. Upgrade the CICS region:
    1. Remove any compatibility groups from the GRPLIST for the Liberty-owning regions.
    2. Update the JCL to make sure that you use the CICS TS V5.4 data sets, licence, and UNIX System Services (USS).
    3. Change the EYUPARMs to reference the CMASSYSID of the new CMAS (shown as CMAS 1B in the diagram).
  3. Restart the region with START=INITIAL. When you restart the region on LPAR 1, it runs on a newer JVM server and connects to the latest CICS TS V5.4 CMAS.
  4. The workload initiates and runs.
  5. Wait for 24 hours to confirm that the mixed mode is functioning.

The diagram shows the resulting configuration on LPAR 1.

The Liberty-owning regions in LPAR 1 are upgraded and restarted. The diagram shows two logical partitions (LPARs), in which CICS workload is running. The Liberty-owning regions in LPAR 1 are connected to a CMAS at CICS TS V5.4.

Introduce new application-owning regions on LPAR 1

The steps in this section are required only for the example of providing application developers with access to the EXEC CICS API for asynchronous processing that is provided in CICS TS V5.4, while leaving the rest of the environment at the existing release of CICS TS.

  1. Define new application-owning regions on LPAR. These should be clones of the existing AOR regions.
    1. Remove any compatibility groups from the GRPLIST for the regions.
    2. Add the CSD resource definitions for the new asynchronous application resource definitions to the GRPLIST for the new regions.
    3. Update the JCL to make sure that you use the CICS TS V5.4 data sets, license, and UNIX System Services (USS).
    4. Change the EYUPARMs to reference the CMASSYSID of the new CMAS.
  2. Update the CICSplex Workload:
    1. Define a new CICS System definition (CSYSDEF) for each new AOR required on both LPAR 1 and LPAR 2.
    2. Define a new CICS Group (AOR2) in the CICSplex and add the new AORs to it.
    3. Add the new CICS group as a sub-group to the existing AOR CICS group.
    4. Create a new “routing rule” to route the new asynchronous application transactions to the new application-owning regions.
    5. Install the new "routing rule" into the CICSplex.
  3. Start the new AORs on LPAR 1.
  4. Check that the new AORs on LPAR 1 are shown as active target regions under the new routing rule, when they become active.
  5. Check that the existing workload is distributed across the previous and new AORs but that the new asynchronous application is routed only to the new CICS TS V5.4 AORs.

The diagram shows the resulting configuration on LPAR 1.

AORs at the latest release level are active in LPAR 1 and integrated with the CICSplex Workload.The diagram shows two logical partitions (LPARs), in which CICS workload is running. The AORs in LPAR 1 are connected to a CMAS at CICS TS V5.4.

Upgrade LPAR 2

  1. Dynamically update the CICS SVC while CICS is running. Use the same SVC number as the CICS TS 5.3 SVC, but replace it with the CICS TS 5.4 SVC. The highest-level CICS SVC is backwards-compatible. You need to do this because all CICS regions that are communicating by using MRO on the same LPAR must use the same SVC, and because CICS does not start with a down-level SVC.
  2. Ensure interregion communication (IRC) is closed on every system on the LPAR, including batch jobs and any potential users of EXCI.
  3. Dynamically update the LPA modules while the interregion communication (IRC) is closed.
  4. Re-open interregion communication (IRC) in the active CICS regions on LPAR 2 and confirm that the CICS connections have been acquired.
  5. Create a new CICS TS 5.4 CMAS (shown as CMAS 2B in the diagram) and start it.
  6. Use the CICS Explorer or WUI to create CMAS-to-CMAS definitions (CMTCMDEF) from the existing CMAS regions to the new CMAS.
  7. Use the CICSPlex SM EYU9XDBT utility to create a batch job to define CMAS-to-CMAS definitions from the new CMAS to the existing CMASs. You can use the CICSPlex SM sample EYUJXBT2 as a template for the commands.
  8. Use the CICS Explorer or WUI to confirm that the link between the existing MP CMAS and the new CMAS is active.
  9. Assign the new CMAS to manage the CICSplex:
    • In the CICS Explorer SM Administration perspective, use the CICSplex definitions view to right-click on the CICSplex and select Assign to CMAS.
    • Use the CICS Explorer or WUI to confirm that the new CMAS is listed as an Active CMAS in the CICSplex view.

Upgrade the Liberty-owning regions on LPAR 2

The steps in this section are required only for the example of providing Java application developers with access to the most up-to-date Liberty features, while leaving the rest of the environment at the existing release of CICS TS.

  1. Quiesce the Liberty-owning CICS regions on LPAR 1 and perform a Shutdown, ensuring that it is stopped cleanly (see message DFHRM0204).
  2. Upgrade the CICS region:
    1. Remove any compatibility groups from the GRPLIST for the Liberty-owning regions
    2. Update the JCL to make sure that you use the CICS TS V5.4 data sets, licence, and UNIX System Services (USS).
    3. Change the EYUPARMs to reference the CMASSYSID of the new CMAS.
  3. Restart the region with START=INITIAL. When you restart the region on LPAR 1, it runs on a newer JVM server and connects to the latest CICS TS V5.4.0 CMAS.
  4. The workload initiates and runs.

The diagram shows the resulting configuration on LPAR 2.

The LORs in LPAR 2 are running CICS TS 5.4.The diagram shows two logical partitions (LPARs), in which CICS workload is running. The LORs in LPAR 2 are connected to a CMAS running CICS TS 5.4.

Introduce new application-owning regions on LPAR 2

The steps in this section are required only for the example of providing application developers with access to the EXEC CICS API for asynchronous processing that is provided in CICS TS V5.4, while leaving the rest of the environment at the existing release of CICS TS.

  1. Define new application-owning regions on LPAR 2. These should be clones of the existing AOR regions.
    1. Remove any compatibility groups from the GRPLIST for the regions.
    2. Add the CSD resource definitions for the new asynchronous application resource definitions to the GRPLIST for the new regions.
    3. Update the JCL to make sure that you use the CICS TS V5.4 data sets, license, and UNIX System Services (USS).
    4. Change the EYUPARMs to reference the CMASSYSID of the new CMAS on LPAR 2.
  2. Start the new AORs on LPAR 2.
  3. Check that the new AORs on LPAR 2 are shown as Active CICS regions.
  4. Check that the new AORs on LPAR 2 are shown as active target regions under the new routing rule, when they become active.
  5. Check that the existing workload is distributed across the previous and new AORs but that the new asynchronous application is routed only to the new CICS TS V5.4 AORs.

The diagram shows the resulting configuration on LPAR 2.

AORs at the latest release level are active in LPAR 2.The diagram shows two logical partitions (LPARs), in which CICS workload is running.

Final configuration

The diagram shows the final set up of the two LPARs that are used in this example.

The final configuration after upgrading to use multiple releases concurrently.The diagram shows two logical partitions (LPARs), in which CICS workload is running.

Some regions are running CICS TS for z/OS V5.3. Other regions are running CICS TS for z/OS V5.4. The environment consists of a single CICSplex to manage all the CICS regions.



example_multirelease.html | Timestamp icon Last updated: Sunday, 4 June 2017