Planning to upgrade on z/OS

Edit online

This section describes the testing, backup, future migration considerations, and other tasks you should plan for before you upgrade older versions of the IBM® Engineering Lifecycle Management (ELM) applications to a newer version on a z/OS system.

You can upgrade from version 6.0.x to the version 7.x. Depending on your current installation, the upgrade process can be a combination of upgrading installed applications, migrating data, and installing new optional applications, like CCM (if it was not installed previously), Quality Management (QM), and Requirements Management (RM). This product documentation only covers upgrading from version 6.0.x to version 7.x.
Note: Upgrading from version 5 to version 7 is a two-step process. You must first upgrade your server to the latest fix pack of version 6 release, start the server and make sure your upgrade to version 6.x was successful, and then upgrade to version 7. For instructions on upgrading from version 5 to version 6.0.x, see the latest version 6 documentation.
Upgrades for z/OS have several significant differences from upgrades for other systems:
  • IBM Installation Manager is not compatible with installations or upgrades on z/OS
  • Installations on z/OS are handled by SMP/E (System Modification Program/Extended)
  • The Jazz® Team Server and other ELM applications on z/OS use configuration and working directories that are separate from installation directories

For advanced or deployment-specific information about upgrading, see the Installing, upgrading, and migrating section of the Jazz.net Deployment wiki.

Upgrade testing considerations

Installing an ELM application on z/OS is subject to the same restrictions as other platforms. See Deployment and upgrade planning for IBM Engineering Lifecycle Management.

Because of server architectural changes between versions and releases, you must create new configuration and work directories for the upgraded server when you upgrade to the new version from a previous version or release. Non-server components, such as build agents, can be tested at the new version or release without having an impact on previous installations. See Staging a test environment for the upgrade process for testing strategies.

Backup considerations

A repository will only work with either a 3.0.x server, a 4.0.x server, a 5.0.x server, or a 6.0.x server. Each new version, release, or fix pack updates the data model using the repository tools addTables command. The upgrade process tags the repository with a version and release number, which means that it can only be used with that version and release. If you want to maintain an existing repository, you must unload any Jazz Team Server (JTS), CCM, QM, and data warehouse repositories that you want to maintain and load them into new repositories. This process will leave the existing repositories intact as backups. The upgrade can not be rolled back without a repository backup. The details of this process are referenced in the server upgrade sections that follow.

Future migration considerations

If you are installing the ELM on z/OS for the first time, the recommended Db2® for z/OS database buffer pool size is 16K. If you have previously installed Rational® Team Concert® 3.0 using 8K database buffer pools, a future migration to 16K buffer pools might be required, so you should plan for the possibility of this migration and consider when the time might be most appropriate for your configuration. To upgrade to a larger database buffer pool size, the database content must be unloaded and loaded to a new database created with a 16K buffer pool size. Options to do that include:
  1. Use the Db2 UNLOAD and LOAD utilities provided with ELM to UNLOAD the JTS and CCM data. (This is the preferred option.)
  2. Use the IBM Engineering Workflow Management (EWM) repository tools export and import functions with JDBC to create an export file that you can import to a new repository.
  3. If you have additional tools to complete this function, use the tool set of your choice to unload the data and reload to a new database with a larger page size. This process should be tested.

Next steps

Configure your server according to the instructions that match your upgrade scenario and infrastructure that follow.

If your server environment is configured on z/OS, refer to Upgrading the server configuration on z/OS for information about how to upgrade the server.

After configuring your server, upgrade and configure optional tools and clients following the instructions in one or more of the following topics: