Print ArticlearchiveblogClose Window
ClearPath Connection

Important Changes to the ClearPath OS 2200 and MCP Software Release and Support Cycles


We recently implemented some important changes to the software release and support cycles for the ClearPath® OS 2200 and MCP operating environments.

Though the specific changes to the OS 2200 and MCP cycles are detailed below, the decision behind these updates is driven by common client feedback. Regardless of the operating environment, clients have told us that the approach we’ve followed for the last several years – where we’d deliver a major OS 2200 or MCP release annually – requires an overhaul.

While clients appreciate the ability to take advantage of new features and software fixes on a yearly basis, the time between releases is too short. Many of you have found it difficult to absorb and adopt the product changes and enhancements that frequently. Similarly, you conveyed that the current support lifecycle created the need to upgrade and manage migrations too often.

We understand these concerns and recognize that you’re juggling multiple business drivers that often dictate your IT priorities. So to help you successfully meet these goals – without forcing you to shoulder added complexity or manage additional planned downtime – we’ve implemented the following release and support cycle changes.

OS 2200 Release and Support Changes

Starting with OS 2200 release 17.0 and culminating with release 19.0, we are gradually extending the time between OS 2200 releases from 12 to 24 months. Likewise, we have increased the duration of phase 1 support for OS 2200 release 16.0 from 42 to 48 months. Beginning with OS 2200 17.0, which is planned for the third quarter of 2016, phase 1 support will increase to 60 months.

In addition, products such as Enterprise Output Manager and Operations Sentinel will continue to be delivered and supported in conjunction with each new OS 2200 software release. Migration rules, including the ability to skip releases, will not be affected by these changes. Further details will be available in revised versions of the ClearPath OS 2200 Software Planning and Migration Overview for Release 16.0 and ClearPath OS 2200 Software Release Announcement for Release 16.0.

For further details, please refer to the bulletin posted on the Unisys support site.

MCP Release and Support Changes

Effective as of the April 2015 release of MCP 17.0, we have extended the time between MCP releases from 12 to 24 months and lengthened the phase 1 support life for MCP software from 42 to 60 months.

Many existing migration rules, such as the ability to skip releases and the code file validity period, will not be affected by these changes. Details will be available in upcoming revisions to the MCP 17.0 Support and Release Policy Overview, Migration Guide, and Software Release Announcement.

Changes for other products, including Agile Business Suite (AB Suite™), Enterprise Output Manager, and Operations Sentinel have been, or will be, announced separately.

For additional information about these and other changes, please refer to the bulletin posted on the Unisys support site.