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.
Figure 6 shows a CICSPlex SM environment that is made up of the
following components:
- 3 MVS™ systems (System A, System B, System C)
- 3 CASs
- 3 CMASs
- All interconnected
- CMAS A connects to CAS A (both are in System A)
- (This is the maintenance point CMAS.)
- CMAS B connects to CAS B (both are in System B)
- CMAS C connects to CAS C (both are in System C)
- 1 CICSplex
- CMAS A is the maintenance point
- 6 CICS® regions
- 6 local MASs
- MAS A1 and MAS A2 connect to CMAS A (all are in System A)
- MAS B1 and MAS B2 connect to CMAS B (all are in System B)
- MAS C1 and MAS C2 connect to CMAS C (all are in System C)
- Systems A, B and C are at the old CICS TS release.
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:
- MVS System A CICSPlex SM TSO users
- CAS A
- CMAS A
- MAS A1
- MAS A2
Step 1: Terminate executing regions that are to be converted
- If the following systems are in execution, terminate them:
- CAS A
- CMAS A
- MAS A1
- MAS A2
Step 2: Convert MVS System A CICSPlex SM TSO users to the new version
- Create the appropriate data set allocations to point to the new version
data sets. This must not affect the allocations for TSO users on MVS Systems B and
C, which are still at the previous level.
Step 3: Convert CAS A to the new version
- Ensure that CAS B and CAS C are started.
- Remove the CAS A links to CAS B and to CAS C. Depending upon whether
the CASs share the BBIPARM data set, you must do one of the following:
- If CAS B and CAS C share the BBIPARM data set:
- From the CAS B CASDEF view:
- Issue the EDIT action command to provide editing access to the BBIPARM
data set.
- Issue the DELete action command to delete the entry for CAS A.
- Issue the SAVE command to save the changes in the BBIPARM data set.
- If CAS B and CAS C do not share the BBIPARM data set:
- From the CAS B CASDEF view, DELete the entry for CAS A, as described
above.
- From the CAS C CASDEF view, DELete the entry for CAS A, as described
for the CAS B view.
- Change the appropriate IEAAPFxx member of the SYS1.PARMLIB library to
authorize the CICSTS31.CPSM.SEYUAUTH library.
- Update the JCL used to start CAS A to point to the new data sets.
Note:
The BBIPARM data set must not contain a
BBMTYB00 member. Member BBMTYB00 will be created dynamically when CAS A
is first started. The new member will be reused when CAS A is subsequently
restarted.
- Start CAS A.
- From the CAS A CASDEF view:
- If communication out of the CICSPlex is required, issue the CHANGE action
command to modify the VTAM® APPL name for the current CAS (as indicated by a
value of YES in the Cur Sys field). Because
the value is null (or blank) before you do this, you
may find it easier to think of the action as creating the VTAM APPL name.
- If communication out of the CICSPlex is not required, leave the VTAM APPL name blank
in order to use XCF communication. The XCF group name should be EYUGR310 (this
value should be picked up automatically).
- Issue the INStall action command to install the change.
- Issue the SAVE action command to save the changes in the BBIPARM data
set.
Step 4: Convert CMAS A
to the new version
Step 5: Convert MAS A1 and MAS A2 to the new version
- Update the MAS A1 and MAS A2 CSD files, using the resource definitions
supplied in the CICSTS31.CPSM.SEYULOAD data set.
- Update the CICS group lists for MAS A1 and MAS A2.
- Update the JCL used to start MAS A1 and for MAS A2 to point to the
new data sets.
- Start MAS A1 and MAS A2.
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:
- MVS System B CICSPlex SM TSO users
- CAS B
- CMAS B
- MAS B1
- MAS B2
Step 1: Terminate executing regions that are to be converted
- IF THE FOLLOWING SYSTEMS ARE IN EXECUTION, TERMINATE THEM:
- CAS B
- CMAS B
- MAS B1
- MAS B2
Step 2: Convert MVS System B CICSPlex SM TSO users to the new version
- Create the appropriate data set allocations to point to the new version
data sets. This must not affect the allocations for TSO users on MVS System C, which
is still at the previous level.
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
- Update the MAS B1 and MAS B2 CSD files, using the resource definitions
supplied in the CICSTS31.CPSM.SEYULOAD data set.
- Update the CICS group lists for MAS B1 and MAS B2.
- Update the JCL used to start MAS B1 and for MAS B2 to point to the
new data sets and to connect to the correct CASNAME.
- Start MAS B1 and MAS B2.
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:
- MVS System C CICSPlex SM TSO user
- CAS C
- CMAS C
- MAS C1
- MAS C2
Step 1: Terminate executing regions that are to be converted
- If the following systems are in execution, terminate them:
- CAS C
- CMAS C
- MAS C1
- MAS C2
Step 2: Convert MVS System C CICSPlex SM TSO users to the new version
- Create the appropriate data set allocations to point to the new data sets.
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
- Update the MAS C1 and MAS C2 CSD files, using the resource definitions
supplied in the CICSTS31.CPSM.SEYULOAD data set.
- Update the CICS group lists for MAS C1 and MAS C2.
- Update the JCL used to start MAS C1 for MAS C2 to point to the new
data sets.
- Start MASs C1 and C2.
[[ Contents Previous Page | Next Page Index ]]