Version 4.6.2
 —  Release Notes  —

Software AG Product Support and Requirements

For more information about Adabas installation and prerequisites, read the various Adabas installation documents and the Adabas Operations Manual documentation.


Adabas and Adabas Review Version Compatibility

Adabas Review version runs in three modes: local, batch, and hub.

You must have Adabas 8.2 SP4 installed to use the new features in this release of Adabas Review.

Important:
If an ADALNK batch link routine has been modified to accommodate the needs of an Adabas product extension (such as Adabas Review), it should not be used for the Adabas nucleus or Adabas utility jobs.

This section covers the following topics:

Compatibility Matrix (Local Mode)

The matrix below provides an overview of the compatibility of Adabas Review in local mode with other versions of Adabas and Adabas SVC.

Note:
This table only refers to compatibility between the Adabas Server and the Adabas Review modules loaded from the server. For the compatibility of the ADALNK client modules refer to the table further down..

Adabas Review Version Adabas Version Status
4.6 8.1 SP4 (CLOGLAYOUT=5) Not compatible
4.6 8.1 SP4 (CLOGLAYOUT=8) Not compatible
4.6 8.2 SP2, SP3, and SP4 (CLOGLAYOUT=5) Not Compatible
4.6 8.2 SP2 and SP3 (CLOGLAYOUT=8) Not Compatible
4.6 8.2 SP4 (CLOGLAYOUT=8) Compatible

Compatibility Matrix (Hub Mode)

Note:
This table only refers to compatibility between the Adabas Server and the Adabas Review modules loaded from the server. For the compatibility of the ADALNK client modules refer to the table further down..

Hub Version Adabas Status
4.4 8.1 SP4 Compatible
4.4 8.1 SP4 with the ADA814LX01 library Compatible with zap RD441088
4.5 8.1 SP4 Compatible
4.5 8.2 Compatible
4.6 8.2 SP4 Compatible

Note:
In z/VSE environments, the hub node ID cannot be greater than 255.

ADALNK REVEXIT1 (REVEXITB) and REVEXIT2

To get data for all Adabas Review fields (TP monitor-specific and Natural-specific fields) that are obtained in the Adabas client address space (ADALNK), the Adabas Review 4.6 exit REVEXIT (the REVEXIT1 entry point) and the ADALNK routines from Adabas 8.2 SP4. REVEXIT (the REVEXIT2 entry point) and ADALNK routines must also be used to obtain data for all client reporting fields.

Note:
REVEXIT2 is not available on BS2000, so the functionality supplied by this is missing on this platform.

Due to changes in the interface, some incompatibilities exist between ADALNK and the Adabas Review REVEXIT exits.

The Adabas Review exits include REVEXIT1 (formerly REVEXITB in z/OS and z/VSE environments, but still REVEXITB in BS2000 environments) and REVEXIT2. These exits should be linked with ADALNK during installation, with the appropriate Adabas link globals table parameters (LGBLSET). The link globals table parameters specified via LGBLSET identify which exit entry points (REVEXIT1 or REVEXIT2) are called. If the LGBLSET parameter REVIEW=YES is set, then the exit is called by ADALNK before the Adabas call as entry point REVEXIT1; if the LGBLSET parameters RVCLNT and REVHID are also specified, then the exit is also called after the Adabas call as entry point REVEXIT2.

The modules used to perform the linkage between REVEXIT and ADALNK are provided with your Adabas Review installation with names in the format RDBLXsys, where sys is a three-character code representing the link environment (for example, MVS for z/OS environments, VSE for z/VSE, COM for Com-plete environments, IMS for IMS environments, and BS2 for BS2000 environments). For more information about performing this linkage, read the appropriate Adabas Review installation documentation.

Note:
A return code 4 from the link-edit of the globals table is acceptable because it indicates that the Review exit (REVEXITB or REVEXIT1) has not been resolved by this step. The next link-edit step in the sample jobs should resolve this and finish with return code zero.

ADALNK and REVEXIT Version Compatibility

Using incompatible version of ADALNK and REVEXIT may lead to unpredictable errors. The following table describes the compatibility of different versions of ADALNK and REVEXIT.

The ADALNK of the TP monitor running SYSREVDB must include the REVEXIT exits. If the REVEXIT exits are not included, some features might not work correctly in SYSREVDB.

Adabas ADALNK Module Versions Adabas Review REVEXIT Module Versions
4.4 SP1 4.5 SP1 4.5 SP2 4.6
8.1 SP4 Compatible Compatible Compatible Not Compatible
8.2 SP2 Only compatible with zap RD441095 Only compatible with zap RD451021 / RD451036 Compatible Not Compatible
8.2 SP3 Compatible Compatible Compatible Not Compatible
8.2 SP4 Not Compatible Not Compatible Not Compatible Compatible

CMDRESP Field Changes

Due to changes in the display programs in SYSREVDB, you cannot use SYSREVDB in Adabas Review 4.4 (or earlier versions) to display the field contents of CMDRESP correctly, unless you stay with the old scale and algorithm. For information about converting CMDRESP history data from older versions of Adabas Review to Adabas Review 4.5, read Migration from Previous Versions.

Top of page

Adabas Review Zap Requirements

All released Adabas Review zaps should be applied to the executables before completing installation.

Top of page

Natural Version Requirements

This version of Adabas Review supports Natural version 4.2 SP4 and above.

If you will be using client reporting, zap NA77060 must be applied to support use of SYSREVDB activation of client reporting.

Top of page

Adabas Cluster and Parallel Services Requirements

This version of Adabas Review supports version 8.2 of Adabas Cluster Services and Adabas Parallel Services.

Top of page

TP Monitor Support

This version of Adabas Review supports the following TP monitors:

Top of page