Planning to upgrade
A significant part of the overall process of upgrading is planning. This section summarizes the preparation that helps you to upgrade CICS® Transaction Server for z/OS®.
- Make sure that all the right people are involved in the plan
- Understand the drivers to upgrade, and the constraints on change, for your environment, and building this understanding into an upgrade strategy
- Check prerequisites of the new release and its compatibility with other products that you use
- Review your environment so that you can assess the impact of the new release and ensure that the plan for upgrade is complete
- Understand what changed between releases of CICS.
Your plan is iterative. The project team refines a plan of action and builds a critical path of activities as it finds out more about the tasks that are involved and the impact of changing the release of CICS.
Actions
| Your current version | Action | Mandatory or optional? |
|---|---|---|
| Clarify the drivers for upgrade | Optional, but recommended | |
| Consider the timing | Optional, but recommended | |
| Build your upgrade project team | Optional, but recommended | |
| Choose your edition of CICS TS for z/OS | Optional, but recommended | |
| Check hardware and software prerequisites | Optional, but recommended | |
| Check compatibility with other IBM products | Optional, but recommended | |
| Check compatibility with vendor products | Optional, but recommended | |
| Review your applications | Optional, but recommended | |
| Review your CICS regions | Optional, but recommended | |
| Review your vendor products | Optional, but recommended | |
| Review the service level of CICS TS for z/OS | Optional, but recommended | |
| Review the changes in CICS TS for z/OS | Optional, but recommended | |
| Develop your upgrade strategy | Optional. but recommended |
Clarify the drivers for upgrade
Clarify what is driving the upgrade of CICS. Is it to keep current? Is it a desire to use a new capability? Is it an opportunity to upgrade only some of your regions, and use different releases for different business needs? Is it a requirement so that you can meet regulatory constraints? Is it part of a bigger upgrade strategy? Your reason affects both your choice of CICS release, and when and how you upgrade.
You can choose to run some of your regions at a newer level and leave some of them at your current level. This gives you flexibility to provide access to the latest features for some parts of your business, without having to plan an upgrade of the entire environment. See Upgrading CICS to use multiple releases concurrently for an example.
Consider the timing
When you think about the schedule for upgrade, factor in your deadlines and key business dates, and any windows of change for the business infrastructure.
Build your upgrade project team
- Your technical representatives from roles such as system programming, application programming, security, and operations
- Business representatives for the lines of business that are affected by the upgrade
- Input from vendors or Business Partners whose products work with CICS.
Choose your edition of CICS TS for z/OS
- Developer Trial
- This edition is a no-charge evaluation version. It does not start
the single-version charge (SVC) clock. Use this edition to access
and explore the new technology in the new release, without having
to go through a full upgrade. You can upgrade from Developer Trial
to either Value Unit Edition or the full product, without having to
reinstall. There are some restrictions on this edition of the product;
see Developer Trial for
details.
For information about what is involved in moving from Developer Trial to a full edition, see Upgrading from Developer Trial.
- Value Unit Edition
- This runs on a qualified z Systems New Application License Charge (zNALC) LPAR. Consider this edition for eligible workloads, such as new Java workloads, that can qualify for a pricing model that is different from the full product. For more information about eligibility, see the CICS TS announcement letter on the IBM Offering Information web page.
Check hardware and software prerequisites
You can create a report that includes the requirements for your target release of CICS TS by entering the product name "CICS Transaction Server" and selecting the new version on the Detailed system requirements page. The report shows hardware, Hypervisor, and operating system requirements, and any requirements for supported software. You can choose to show only product releases, or include interim service fixes. The supported software report shows prerequisite levels for a broad range of IBM® products, including development tools, Java, databases, application servers, messaging products, event management, and problem determination tools.
Check compatibility with other IBM products
You can create reports of the related software products that are supported by your target release of CICS TS on the Compatibility reports page. The same type of software compatibility information can also be found under the "Supported Software" tab of the Detailed system requirements for CICS TS. Any requirements, such as APARs that are needed to make the software compatible, are listed in the notes or additional information in the report.
Check compatibility with vendor products
- It is supported without change on your target release.
- It requires a compatibility fix, either to CICS TS or to the product itself.
- It must be upgraded.
The IBM® Business Partner products that are supported at each CICS release from CICS TS 4.1 are listed at Business partner products. Vendor software products for z/OS shows the software developers who indicate that their products support levels of z/OS.
Always check with your vendor for definitive information on compatibility.
Review your applications
- Which applications are hosted in this region?
- Which applications use these resources?
- Which applications are affected by this change?
- If I upgrade this region, which applications are affected?
- If I upgrade this application, which regions are affected?
CICS Interdependency Analyzer can help with application analysis.
For each application, create a checklist:
- Name
- Owners: business, development, and infrastructure
- Supplier: in-house or vendor
- Execution model: single region or multiple region
- Regions hosted
- Current release and target release
- Languages
- CICS components
- Resource definitions
- CICS exits
- Other products, applications, and services
- Automation
- Test suite: what testing is required before and after the upgrade?
- Offline and batch interactions
Review your CICS regions
- Check STEPLIB and DFHRPL libraries
- Check CSD lists. Check these lists against your running regions. Sometimes resources, such as LIBRARY definitions, are added dynamically.
- Check z/OS UNIX System Services and bundle definitions for application and platform resources
- Check CICSPlex® SM configuration
- Check CICS statistics and monitoring data: what transactions are running and which applications do they belong to?
- Does the application run across the TOR, AOR, FOR configuration of multiple regions? If so, consider the implications for transaction routing, function shipping, or DPL.
Review your vendor products
You need information about the vendor products in your current environment.
- Check z/OS vendor compatibility information on Vendor support for z/OS.
- Check CICS vendor compatibility information.
- In addition, make the following checks:
- The current version of vendor product supports the target CICS release and version
- Are any PTFs required in the vendor product or in CICS?
- Can a new version of vendor code be installed in current release?
- What actions (Hold actions) need to occur: for example, recompiling exits, or upgrade steps
Review the service level of CICS TS for z/OS
Organizations that are up-to-date with service typically encounter fewer problems during the upgrade process. Gather information about the service levels in your current environment.
Review the changes in CICS TS for z/OS
A key part of upgrading is understanding the impact of changes from your current release. Changes between releases summarizes the changes to the externals of CICS TS across all in-service versions.
Develop your upgrade strategy
You need to consider whether you plan to upgrade all regions at the same time, or phase your upgrade. We assume that minimum downtime is your goal, but there are various ways to approach the upgrade with this goal in mind.
- Do you want to leave some regions running at your current release?
- For example, if you have an application that cannot be run on your target release of CICS, or if you prefer to run some applications on a newer release and rapidly pick up new features for those applications, while leaving the rest of your environment in its current state. You can see an example of an upgrade that is based on this approach in Upgrading CICS to use multiple releases concurrently.
- Will a workload run while the upgrade takes place?
- There are a number of considerations if this is your strategy:
- Can your workload cope when the routing and/or target regions are closed down for upgrading? Are alternative target regions available to execute the work? Do the remaining routing and target regions have a sufficiently high MXT value to cater for the additional throughput?
- Does your environment contain an FOR? If so, when this is shut down for an upgrade, there will be no access to the files. Are the consequences of this loss of access fully understood?
- Does your environment have any QORs or regions which own DB2 or DBCTL connections (for example)? Are these regions single point of failure? What is the impact of closing these regions for upgrading?
- Will you prepare all the components for upgrade offline, before you take them down?
- How many CMASes per release of CICS TS are active on your LPAR? During migration, new CMASes may temporarily be added. The CMAS range is between 13 and 24, depending on the value you have set for MAXCAD. See this topic for more information Specifying each CMAS correctly in IEASYSxx.
- Are you aware of the potential impact of a phased migration on a running workload? You can see an example of an upgrade that is based on this approach in Upgrading CICS with a running workload.