The migration from a previous release of CICSPlex SM to CICS® TS Version
3.1 CICSPlex SM for a CMAS and all MASs (including those MASs that act
as Web User Interface servers) that are connected to it, as well as for the CAS to
which the CMAS is connected, should be completed before CICSPlex SM is restarted.
When other CMASs at the previous release level are not migrated to this
release, a separate CAS running at the previous release level must be provided
to which the other CMASs can now connect. This is so that you can access
the EUI at the other CMASs. The CAS running at the previous release
level should only be used for administration of the CMAS-to-CMAS communications,
for example using CMTCMDEF and CMTPMDEF, and not for normal operations or
definition work.
Several skeleton post-installation members are distributed with CICSPlex SM.
You should generate these post-installation members for use during the migration.
(For information about generating the post-installation members, see the CICS Transaction Server for z/OS® Installation Guide.)
To enable you to revert to the previous release of CICSPlex SM if you encounter
problems during the migration to CICS TS Version 3.1 CICSPlex SM, you should
take back-up copies of the previous release components such as JCL, CLISTs, CICS tables, CMAS data repositories, and WUI repositories before
you start the migration process.
Note:
You can use the procedures in this topic to migrate from
Version 2.3, Version 2.2 or Release 4 of CICSPlex SM to CICS TS Version
3.1 CICSPlex SM.
In order to provide for concurrent previous release and Version 3.1 CASs
you must create a separate Version 3.1 CAS environment.
To convert a CAS from Version 2.3, Version 2.2 or Release 4 to Version
3.1, complete these steps.
Note:
If you have used the CICSPlex® SM EUI for your existing level
of CICSPlex SM, log off TSO completely and then log on again before you make any
changes to definitions or access the EUI for your new level of CICSPlex SM. Do
the same if you need to access the EUI for your existing level of CICSPlex SM after
accessing the EUI for the new level. Logging off TSO ensures that your allocation
is cleared properly.

- Review the IEASYSxx member in the SYS1.PARMLIB library. The NSYSLX value
may need to be increased. (For information about the NSYSLX value for CICSPlex SM,
see the CICS Transaction Server for z/OS Installation Guide.)
- Authorize the new Version 3.1 libraries. (For information about how to
do this, see the CICS Transaction Server for z/OS Installation Guide.)
- (Only when running both a previous release and Version 3.1.) Define the VTAM® requirements for the Version 3.1 CAS. You must perform the following
steps:
- Create a VTAM application definition
- Update the configuration list
- Activate the major nodes
When the Version 3.1 CAS is going to communicate with another Version
3.1 CAS on a system that also is running multiple releases of CICSPlex SM, you
must also define the cross-domain resources. (For information about performing
these steps, see the CICS Transaction Server for z/OS Installation Guide.)
- Review the JCL in the EYUDEFDS member generated by the EYUISTAR job to
ensure that the following steps were generated when the post-installation
jobs were created:
Then run the job to create a new BBIPARM parameter repository data set
for the Version 3.1CAS.
If you are running Version 2.3, Version
2.2 or Release 4, as well as Version 3.1, and your earlier releases currently
share a single BBIPARM data set, your Version 3.1 CASs can share the same
BBIPARM data set. (For information about using EYUDEFDS, see the CICS Transaction Server for z/OS Installation Guide.)
- Update your TSO sign-on procedure to use the Version 3.1 data sets. Use
generated member EYUTSODS to allocate the libraries temporarily. (For information
about updating your TSO sign-on procedure, see the CICS Transaction Server for z/OS Installation Guide.)
- Review the changes made to the CICSPlex SM global security parameters
for Version 3.1. Make sure the BBACTDEF DD statement in the CAS startup
procedure references a data set containing the BBMTSS member distributed with
Version 3.1. (For information about this member, see the CICS Transaction Server for z/OS Installation Guide
- Use the JCL procedure in the EYUCAS member to start the CAS, verifying
the SSID and the DD statements for the Version 3.1 data sets. If you are running
both a previous release of CICSPlex SM and Version 3.1, the SSIDs for the
two CASs must be different. (For information about the JCL in EYUCAS, see
the CICS Transaction Server for z/OS Installation Guide.)
The Version 3.1 CAS is now ready for use.
You must migrate your CICSPlex SM CMAS to CICS TS Version
3.1 at the same time as you migrate the CICS system on which it runs. This is because
in CICS Transaction Server for z/OS, Version 2 Release 3 a CICSPlex SM CMAS will run only in a CICS system at the
same release level. During startup the CMAS checks the CICS release level
and terminates with message EYUXL0142 if the release does not match.
To convert a CMAS to Version 3.1:
The CMAS is ready to be cold started.
When you have successfully migrated all your systems to CICSPlex SM Version
3.1 you can delete the previous release groups and group lists from each CMAS’s
CSD. (For information about how to do this, see Deleting the previous release definitions from CSD files.)
To convert a MAS to Version 3.1, you need to do the following:
- Authorize the Version 3.1 libraries. (For information about doing this,
see the CICS Transaction Server for z/OS Installation Guide.)
- Reassemble the CICS resource definition table load modules. Reference
the library containing the Version 3.1 resource entry copy books to update
the resource tables with the newest entries. (For information about updating
the resource definition table load modules for a MAS, see the CICS Transaction Server for z/OS Installation Guide.)
- Update the CSD file with the Version
3.1 group of resource definitions. At Version 3.1, this group is EYU310G1.
(For information about updating the CSD file for a MAS, see the CICS Transaction Server for z/OS Installation Guide.)
- If all MASs that use the same CSD and group list are being migrated
at the same time, update the CSD to add the Version 3.1 group to, and remove
the previous release group from the group list. However, if the same CSD and
group list are being used by MASs that will run multiple releases of CICSPlex SM concurrently,
create a new group list in the CSD by performing the following steps:
- APPEND the old group list to a new group list name.
- Update the CSD to add the Version 3.1 MAS group.
- Add the Version 3.1 MAS group to the new group list.
- Remove the previous release MAS group from the new group list.
For more information about adding a (new release) group to the group
list in the CSD, see the CICS Transaction Server for z/OS Installation Guide.
To create a new group list in the CSD, use a statement
of the following form as input to DFHCSDUP:
APPEND LIST(old_list) TO(new_list)
To remove a previous release group from a group list, use a
statement of the following form as input to DFHCSDUP:
REMOVE LIST(new_list) GROUP(old_group)
where new_list is the group list used by the MAS and old_group is the previous release group to be removed. The old_group name depends on the type of MAS and whether CICSPlex SM code is used from
the LPA. Table 32 lists the release group names for each environment.
If a new group list is created, the GRPLIST CICS system initialization
parameter for the MAS, in the SIT or in startup overrides, should be changed
to specify the name of the new group list.
- When previous release modules are in the link pack area (LPA), you must
ensure the Version 3.1 modules are used in place of the previous release modules.
(For information about how to do this, see the CICS Transaction Server for z/OS Installation Guide.)
- Edit the JCL used to start the MAS changing the previous release of CICSPlex SM library
names to the Version 3.1 names. (For information about the MAS startup JCL,
see the CICS Transaction Server for z/OS Installation Guide.)
In the sequential data set or partitioned
data set member identified by the CICS SYSIN statement, verify that the CICS
system initialization table (SIT) parameter EDSALIM is
included, and set it to a value of at least 50MB. 50MB is the minimum EDSALIM
required to start the MAS agent for CICSPlex SM Version 2.3 and later versions.
The MAS is ready to be cold started.
When you have successfully migrated all your systems to CICSPlex SM Version
3.1 you can delete the previous release groups from each MAS’s CSD.
(For information about how to do this, see Deleting the previous release definitions from CSD files.)
Workload management
If you use the workload management functions of CICSPlex SM and you use your own version
of the CICSPlex SM user-replaceable Workload Routing Action Module, EYU9WRAM,
you must recompile and link-edit your version of EYU9WRAM using the Version
3.1 libraries. For information on how to do this, see the description of customizing
the dynamic transaction routing program in the CICSPlex System Manager Managing Workloads manual.
Application programming interface
CICSPlex SM API programs written to run in a previous release MAS can
be run in a Version 3.1 MAS. You can either continue to access the data
provided by the previous release or access the new data available from Version
3.1. For a discussion of the compatibility between releases of the API, see the CICSPlex System Manager Application Programming Guide.
Both the Web User Interface server and the CMAS that it connects
to must be at the highest level of CICSPlex SM and CICS within the CICSplex. This means that
both must be at the same level as the maintenance point CMAS.
Before you migrate a Web User Interface server, you must migrate
the CMAS that it connects to. You must migrate the Web User Interface server
before you migrate any other MASs. If the CMAS that the Web User Interface
server connects to is not the maintenance point CMAS, you must migrate the
maintenance point CMAS at the same time.
As the CICS system that acts as your Web User Interface server is a local MAS,
all the considerations that apply to a local MAS also apply to a Web User
Interface server.
To convert a Web User Interface server to Version 3.1 you should:
- Migrate the MAS that acts as your Web User Interface server.
Update the CSD file with
the Version 3.1 Web User Interface group of definitions. At Version 3.1, this
group is EYU310GW.
- Migrate the contents of the Web User Interface server repository (EYUWREP).
If you have Web User Interface servers connected to CMASs other
than the maintenance point CMAS, which have many other MASs connected to them,
you might not want to migrate the other MASs at the same time as the CMAS.
In that case you might consider using the following phased migration path:
- Define a new Version 3.1 CMAS on the same MVS image as the Web User Interface server.
- Connect the Version 3.1 CMAS to the CICSplex that the Web User Interface
server CMAS is connected to. (It will not become available for use until the
maintenance point CMAS has been migrated. If you see message EYUCP0022E at
this time, there is no need to take any action.)
- Migrate the maintenance point CMAS to Version 3.1 and take down the Web
User Interface server at the same time. Migrate the Web User Interface server
to Version 3.1 and, when you restart it, connect it to the Version 3.1 CMAS. The Version 3.1 CMAS should now connect successfully to the Version
3.1 maintenance point CMAS.
- Migrate the remaining MASs when required, and connect them to the Version
3.1 CMAS as you restart them.
- When you have moved all the MASs to the Version 3.1 CMAS, you can remove
the original CMAS.
Assuming you are running the latest CICSPlex SM 2.3
and 3.1 maintenance levels, you can convert one LPAR at a time from 2.3 to
3.1.
- A CICSPlex SM 3.1 WUI can only connect to a 3.1 CMAS.
- A CICSPlex SM 2.3 WUI can only connect to a 2.3 CMAS.
- A CICSPlex SM 2.3 WUI connected to a 2.3 CMAS can retrieve data from a
MAS connected to a 3.1 CMAS (assuming it is not a resource type which is
unique to CICS TS 3.1) if the CMAS participates in the management of the CICSplex.
- A CICSPlex SM 2.2 WUI can only connect to a 2.2 CMAS.
- A CICSPlex SM 2.2 WUI connected to a 2.2 CMAS can retrieve data from a
MAS connected to a 3.1 CMAS (assuming it is not a resource type which is
unique to CICS TS 3.1) if the CMAS participates in the management of the CICSplex.
- A CICSPlex SM 3.1 WUI connected to a 3.1 CMAS can retrieve data from any
MAS connected to any CMAS if the CMAS participates in the management of the
CICSplex.
Migrating the MAS and updating the Web User Interface CSD group
To migrate the MAS and update the Web User Interface CSD group you should
follow the instructions for converting a MAS as described in Converting a MAS to Version 3.1.
You
must also replace the CSD group EYU230GW with EYU310GW in the group list used
by the Web User Interface server or create a new group list containing EYU310GW.
(For CICS Transaction Server for z/OS Version 3 Release 1 EYU310GW is included in the CSD when the CSD file is updated
with the Version 3.1 resource definitions, EYU964G1).
Migrating the contents of the Web User Interface server repository
(EYUWREP)
InCICS Transaction Server for z/OS Version 3 Release 1 some internal Web User Interface repository record versions
have been incremented to facilitate the new features in view definitions For
this reason, if your existing Web User Interface repository contains customized
view sets or menus, it is essential that you migrate your view set and menu
definitions.
To migrate the Web User Interface server repository to the current version:
- Export your view set and menu definitions with your Web User Interface
server still running at your current release. It is not necessary for the
Web User Interface server to be connected to a CMAS to do this. For information
about exporting definitions see the CICSPlex System Manager Web User Interface Guide and the CICSPlex System Manager Web User Interface Guide.
- Create a new Web User Interface server repository using the JCL described
in the CICS Transaction Server for z/OS Installation Guide.
- Start the Web User Interface server at the new release using the new Web
User Interface server repository.
- Import the new starter set definitions (the supplied set of view set and
menu definitions with names beginning EYUSTART).
- Import your previous release view set and menu definitions, specifying
the SKIP option on the Duplicate Names field of the COVC panel. This prevents
the new starter set definitions being overwritten by starter set definitions
exported from a previous release.
Note:
If you do accidently overwrite
the new starter set definitions with starter set definitions exported from
a previous release, you can re-import the new starter set definitions specifying
the OVERWRITE option on the Duplicate Names field of the COVC panel.
For information about importing view set and menu definitions see the CICSPlex System Manager Web User Interface Guide and the CICSPlex System Manager Web User Interface Guide. For information about the starter
set see the CICSPlex System Manager Web User Interface Guide.
You do not need to make any changes to existing customized views and menus
you may have created but you can consider modifying or creating view sets
to take into account the new attributes and resources.
Notes:
- You can import into a CICS TS for z/OS, Version 3.1 Web User Interface server repository,
Version 2.3 or Version 2.2 view set and menu definitions.
- You can import view set and menu definitions exported by a CICS TS for z/OS, Version 3.1 Web
User Interface server into a CICS Transaction Server for z/OS, Version 2 Release 3 Web User Interface server repository.
However, any new attributes or resources introduced in CICS TS for z/OS, Version 3.1 are not accessible
in the CICS Transaction Server for z/OS, Version 2 Release 3 Web User Interface server. You may wish to remove these
attributes and view sets using the View Editor. For information about the
View Editor see the CICSPlex System Manager Web User Interface Guide.
When you have successfully migrated all your systems to CICSPlex SM Version
3.1, you can delete the Version 2.3 definitions from each CMAS’s and MAS’s
CSD. This can be done by upgrading each CSD using module EYU9R230, which is
supplied in CICSTS31.CPSM.SEYULOAD.
When this JCL is run, EYU9R230 attempts to delete all Version 2.3 groups
and group lists from the CSD. However, because not all of the items the job
attempts to delete are actually defined in the CSD, DFHCSDUP gives a return
code of 04. The DFHCSDUP SYSPRINT output lists those items that were deleted
and those that were not found. For further information about updating the
CSD, see the CICS Transaction Server for z/OS Installation Guide.
[[ Contents Previous Page | Next Page Index ]]