Migration from z/OS 1.12 or z/OS 1.13 to z/OS 2.1

You can install z/OS 2.1 CIM as described above as a replacement of a previous z/OS CIM version without affecting any external programs interfacing with the CIM server, such as management applications.

During startup, the z/OS 2.1 CIM server will automatically correct eventually missing file tags in its repository. In addition, it will detect if an existing repository is up to date.

If back-level, the CIM server will automatically upgrade the repository in /var/wbem following these steps:

1. The CIM server backs up the current repository into
   • repository_old_<timestamp>

     where <timestamp> is the current time.

2. The CIM server copies the master repository from /usr/lpp/wbem/repository to /var/wbem/repository.
3. The CIM server migrates the previous repository content to the current repository.

If the CIM server does not find a repository in /var/wbem at startup, it automatically creates a default repository from the master repository that is shipped under /usr/lpp/wbem. To recover a damaged repository, you can create a new repository by removing the damaged repository from /var/wbem. Then the CIM server creates a new copy at the next startup. Please note that all your custom changes for the repository, for example additional provider registrations, will be lost in this case and have to be done again.

The CIM server also checks for syntactical errors in the cimserver.env file located in directory /etc/wbem/. Errors recognized by the CIM server are automatically corrected. The corrected version of cimserver.env replaces the old one, but the startup fails. Restart the CIM server.