A phased migration scenario

Figure 6, Figure 7, Figure 8, and Figure 9 and the discussions that accompany them show a CICSPlex® SM environment at an earlier release and the steps you would take to convert that environment to Version 3.1. Note that this scenario presents one way you might perform the migration; you might find another set of procedures to be more appropriate to your own environment.

The environment

Figure 6. An environment at an earlier release
 The figure shows the systems, their interconnections, and release levels that are described by the following list. This figure is also the basis for the next 3 figures in this topic. We shall refer back to it to explain the changes that are taking place.

Figure 6 shows a CICSPlex SM environment that is made up of the following components:

Objective 1: Convert MP CMAS to the new version

Figure 7. Converting the maintenance point CMAS to the new version
 The figure has changed from the previous version. In System A all CICS systems are now at the new version. CAS-A is no longer connected to CAS-B or CAS-C, but B and C remain connected to one another. The CMAS systems (A B and C) remain interconnected despite the different release levels they are at.

As shown in Figure 7, when you complete Objective 1 the connections from CAS A to CAS B and from CAS A to CAS C will be removed.

The conversion of the maintenance point CMAS A to the new version requires conversion for the following:

Step 1: Terminate executing regions that are to be converted

Step 2: Convert MVS System A CICSPlex SM TSO users to the new version

Step 3: Convert CAS A to the new version

Step 4: Convert CMAS A to the new version

Step 5: Convert MAS A1 and MAS A2 to the new version

Objective 2: Convert CMAS B to the new version

Figure 8. Converting CMAS B to the new version
 The figure has changed again. As well as system a, in System B all CICS systems are now at the new version. CAS-B is reconnected to CAS-A but neither is now connected to CAS-C. The CMAS systems (A B and C) remain interconnected despite the different release levels they are at.

As shown in Figure 8, when you complete Objective 2 the connection from CAS A to CAS B will be reestablished and the connection from CAS B to CAS C will be removed. The conversion of CMAS B to the new version requires conversion for the following:

Step 1: Terminate executing regions that are to be converted

Step 2: Convert MVS System B CICSPlex SM TSO users to the new version

Step 3: Convert CAS B to the new version

Step 4: Convert CMAS B to the new version

Step 5: Convert MAS B1 and MAS B2 to the new version

Objective 3: Convert CMAS C to the new version

Figure 9. Converting CMAS C to the new version
 The figure has changed once more. All CICS systems are now at the new version. All CAS interconnections are re--established. From a connection point of view the figure is the same as the starting point. From a CICS release level point of view, All systems are now at the new CICS release level.

As shown in Figure 9, when you complete Objective 3 the connections from CAS C to CAS B and from CAS C to CAS A will be reestablished.

The conversion of CMAS C to the new version requires conversion for the following:

Step 1: Terminate executing regions that are to be converted

Step 2: Convert MVS System C CICSPlex SM TSO users to the new version

Step 3: Convert CAS C to the new version

Step 4: Convert CMAS C to the new version

Step 5: Convert MAS C1 and MAS C2 to the new version

[[ Contents Previous Page | Next Page Index ]]