Version 7.5.1
 —  Adabas Parallel Services 7.5 Release Notes  —

Required Environment

This document covers the following topics:


Operating System Environment

Adabas Parallel Services version 7.5 requires

* Support for z/OS.e is currently restricted to client programs executing in batch, or under TSO or Com-plete.

Top of page

Software AG Product Environment

Adabas Parallel Services version 7.5 requires Adabas version 7.4.2 or later. The FRZ.ADA744.MVSLX01 dataset, included with Adabas 7.4.4, includes all the current LX dataset maintenance available to use Adabas Parallel Services 7.5.1 with Adabas 7.4.4 or its prior releases.

If, however, you have only Adabas 7.4.2 installed, the following zaps must be applied if Adabas Parallel Services version 7.5 is to function properly:

In z/OS or OS/390 environments, the following additional zaps must also be applied to Adabas 7.4.2 systems:

For BS2000 environments, Software AG recommends that you use Adabas version 7.4.4. If, however, you are using Adabas 7.4.3, you must apply zap AB743002. In addition, if Adabas version 7.4.2 is used, the following additional zaps must be applied:

If you are using Adabas 7.4.2 in VSE environments, the following additional zaps must be applied:

Please check ServLine24 for cluster-related Adabas zaps as well, when installing Adabas Parallel Services version 7.5.

If Entire Net-Work 5.8.1 is installed, the following zap must also be applied: WM58074M.

If you install Adabas Online System (AOS), either the demo version delivered with Adabas 7.4 or the version 7.4 AOS selectable unit is required. AOS is compiled under Natural version 3.1 and runs on that and all subsequent versions of Natural.

The full version 7.4 AOS selectable unit is required for the triggers and stored procedures facility.

Top of page

Applying Zaps to Parallel Service Components

Usually zaps for Parallel Services nuclei can be applied and made active one nucleus at a time. That is, individual nuclei can be shut down, have the zap applied, and be brought up again without ever shutting down the entire cluster. This is the default way of applying zaps, which is in effect if the zap description does not explicitly state otherwise.

In some cases, it may be possible that applying and activating a zap one nucleus at a time would introduce erroneous behavior in the nuclei that have not yet been zapped. If this is the case for a zap, it will be clearly indicated in the zap description, and instructions will be given for how to apply and activate the zap properly.

Zaps to the SVCCLU component of the Adabas router (Adabas SVC), as well as the ADACOM task/job, always require the shutdown of the entire cluster before they cay be activated, since every Parallel Services cluster works with only one router (SVC) and one ADACOM, and since both must stay active as long as the cluster is active.

Top of page