This section provides an overview of upgrading Adabas System Coordinator and is applicable to the upgrading of version 8.2 SP2 and above.
The new version of Adabas System Coordinator is fully compatible with your current configuration file. No migration of the configuration file is required.
This compatibility enables the same configuration file to be shared between the new version and your current version.
The new version of Adabas System Coordinator is fully compatible with your current CORCFG module. No re-assembly of CORMCFG is required.
This compatibility enables the same CORCFG module to be shared between the new version and your current version.
If you do re-assemble CORMCFG (which is our recommendation) then the re-assembled CORCFG module will remain backward compatible with your current version. Of course, any newly implemented parameters will only take effect when the appropriate new version component is running.
The new version of the Adabas System Coordinator online services can be used to administer and monitor both new and current versions. Of course, any newly implemented configuration and monitoring capability will only take effect when the appropriate new version component is running.
Likewise, your current version of the Adabas System Coordinator online services can be used to administer and monitor both new and current versions. Of course, any newly implemented configuration and monitoring capability will not be available for use.
The following table shows the supported runtime version compatibility between the new and your current Adabas System Coordinator components:
| Client Component Version | Daemon Component Version | Database Component Version |
|---|---|---|
| Current | Current | Current |
| Current | Current | New |
| Current | New | New |
| New | New | New |
Where:
The client component consists of the CORSnn component and the COR load library made available to the client (these must always be of the same version)
The daemon component consists of the COR load library made available to the daemon
The database component consists of the COR load library made available to the database
Note:
If a particular version combination is not specified in the above
table then it is not supported.
In a multi-system environment, the Upgrade Procedure for upgrading databases and daemons must be extended across all systems as follows:
Adabas System Coordinator databases - across all systems - must be upgraded before any single daemon or client is upgraded.
Adabas System Coordinator daemons - across all systems - must be upgraded before a single client is upgraded.
If you currently use Adabas System Coordinator libraries which are shared across clients, daemons and databases then you must ensure that the library changes described in each of the steps in the Upgrade Procedure affect only the component relevant to the step itself.
This may require discontinuing the use of shared libraries until after the upgrade process has completed.
Refer to Software AG’s Empower website for the latest available maintenance for this version of Adabas System Coordinator.
If maintenance is available, we strongly recommend it is applied before proceeding with the upgrade.
Refer to the section Adabas System Coordinator -based Add-on Products in the Installation documentation for information regarding the Add-on product maintenance required for supporting this version of the Adabas System Coordinator.
Ensure any specified maintenance is applied before proceeding with the upgrade.
This section describes the required steps to upgrade Adabas System Coordinator.
For reference, the table in the Runtime Component Version Compatibility section tabulates the upgrade steps of the Adabas System Coordinator components.
In addition to the information provided here, please also refer to Adabas System Coordinator Installation documentation for further information.
Upgrade Adabas System Coordinator database components by replacing the current version of the Adabas System Coordinator database load library with the new version.
The new version of the Adabas System Coordinator database component is fully backward compatible with your current version of Adabas System Coordinator client and daemon components.
If the new version of the Adabas System Coordinator includes an LX01 library then this library must be concatenated above the Adabas 8.3 library.
The use of an LX01 library is not necessary.
Note:
In a multi-system environment, Adabas System Coordinator databases -
across all systems - must be upgraded before any single daemon or client is
upgraded.
Upgrade Adabas System Coordinator daemons by replacing the current version of the Adabas System Coordinator daemon load library with the new version.
Daemons within a group can be upgraded individually or all together at the same time.
The new version of the Adabas System Coordinator daemon is fully backward compatible with your current version of Adabas System Coordinator client components and peer daemons (daemons within the same group) but are NOT backward compatible with earlier versions of database components (which is why databases must first be upgraded as described in Step 1).
Note:
In a multi-system environment, Adabas System Coordinator daemons -
across all systems - must be upgraded before a single client is
upgraded.
Upgrade Adabas System Coordinator client components by:
relinking all Adabas link modules using the CORSnn client components from the new version
replacing the current version of the Adabas System Coordinator client load library with the new version.
The new version of the Adabas System Coordinator client component is NOT backward compatible with earlier versions of database or daemon components (which is why databases and daemons must first be upgraded as described in Steps 1 and 2).