Adabas Review version 4.4, which is used with Adabas version 8.1.3 and above, adds a number of new features to enhance the product's usability.
Adabas Review monitors the performance of Adabas environments and the applications executing within them. You can use information retrieved about Adabas usage when tuning application programs to achieve maximum performance with minimal resources.
This document covers the following topics:
Before attempting to install Adabas Review, ensure that the host operating system is at the minimum required level. Complete information on the platforms supported by Software AG and Adabas Review is provided at this link: http://www.softwareag.com/Corporate/products/prodavail/default.asp.
This version of Adabas Review is released for the following operating environments:
z/OS: All versions currently supported by IBM.
z/VSE: All versions currently supported by IBM.
BS2000: For information on the BS2000 OSD versions supported by this release ofAdabas Review, access Software AG's ServLine24 web site at http://servline24.softwareag.com/public/. In the left menu of this web page, expand My ServLine24 and log into Secured Services. Once you have logged in, you can expand Products in the left menu of the web page and select Product Roadmaps to access the Product Version Roadmaps application. This application allows you to review platform support information for specific Software AG products and releases.
Note:
In z/VSE and BS2000 environments, the Hub node ID cannot be greater
than 255.
Software AG provides support for the operating system versions supported by their respective manufacturers. Generally, when an operating system provider stops supporting a version of an operating system, Software AG will stop supporting that operating system version.
Although it may be technically possible to run a new version of Adabas Review on an old operating system, Software AG cannot continue to support operating system versions that are no longer supported by the system’s provider.
If you have questions about support, or if you plan to install Adabas Review on a release, version, or type of operating system other than those included at the link above, consult Software AG technical support to determine whether support is possible, and under what circumstances.
Adabas Review version 4.4 runs in three modes: local, batch, and hub.
In local mode, Adabas Review runs in the Adabas address space.
In batch mode, Adabas Review runs as a batch job.
In hub mode, Adabas Review runs as a server in its own address space with a client interface in the Adabas address space.
Adabas Review 4.4 requires Adabas version 8.1.3 or above in local mode. Running Adabas Review 4.4 in hub mode requires that the Adabas 8.1.3 load library be concatenated with the Adabas Review 4.4.1 load library in the startup job. Except under BS2000 where the version 7.4 SVC (router) is required, the SVC and the databases being monitored can be version 7.1 or above.
Adabas Review 4.4 requires Natural version 4.1.4 or above.
Adabas Review version 4.4 supports Adabas Cluster Services version 7.4 and Adabas Parallel Services 7.5 in hub mode.
For more information about Adabas installation and prerequisites, read the various Adabas installation documents and the Adabas Operations documentation.
For information on how long a product is supported by Software AG, access Software AG's ServLine24 web site at http://servline24.softwareag.com/public/.
From the web site, expand My ServLine24 on the menu to the left, and log into Secured Services. Once you have logged in, expand Products in the left menu of the web page and select Product Roadmaps to access the Product Version Roadmaps application. This application allows you to request support information for specific products and releases.
Refer to the following sections for details about installation prerequisites for Review 4.4:
This section provides information on the zaps required for compatibility of Adabas Review 4.4 (in both local and hub modes) with other versions of Adabas and Adabas SVC. Please note the following information when reviewing the compatibility matrices:
This section covers the following topics:
The matrix below provides an overview of the compatibility of Review 4.4 local mode with other versions of Adabas and Adabas SVC.
| Review | Adabas | Status |
|---|---|---|
| 4.4 | 7.4 | Not compatible |
| 4.4 | 8.1.3 cloglayout=5 | Not compatible (zap required for compatibility) |
| 4.4 | 8.1.3 cloglayout=8 | Compatible |
| 4.3 | 7.4 | Compatible |
| 4.3 | 8.1.3 cloglayout=5 | Compatible |
| 4.3 | 8.1.3 cloglayout=8 | Not compatible (needs zap RD432098 to produce error message) |
Running Review 4.4 in Hub mode with an Adabas 7.4 load library is not supported. The same applies to a Review 4.3. HUB with an Adabas 8.1.3 load library.
| Hub Version | Adabas | SVC | Status |
|---|---|---|---|
| 4.3 | 7.4 | 7.4 | Compatible |
| 4.4 | 7.4 | 7.4 | Compatible |
| 4.3 | 7.4 | 8.1 | Compatible |
| 4.4 | 7.4 | 8.1 | Compatible |
| 4.3 | 8.1.3 cloglayout=5 | 8.1 | Compatible |
| 4.4 | 8.1.3 cloglayout=5 | 8.1 | Compatible |
| 4.3 | 8.1.3 cloglayout=8 | 8.1 | Not compatible (needs zap RD432098 to produce error message) |
| 4.4 | 8.1.3 cloglayout=8 | 8.1 | Compatible |
Note:
In z/VSE and BS2000 environments, the Hub node ID cannot be greater
than 255.
In batch mode, the processor runs as a batch job that processes sequential Adabas command log data sets created either with command log layout 5 (CLOGLAYOUT=5) or command log layout 8 (CLOGLAYOUT=8).
In z/VSE environments, zaps RD441012 (Adabas Review) and AN813003 (Adabas) need to be applied for Hub mode data collection
There is no special migration or conversion (such as an EXPAND job) of the repository file needed when upgrading from Adabas Review Version 4.3. to Adabas Review 4.4. In addition, there is no need to initialize the repository file with the INSTALL DB command.
If an existing Review repository file is used with a new Natural FNAT file, the function REGEN ALL needs to be executed. For more information about REGEN ALL, read Regenerating All Display Programs.
Reports that use the ECBS field (such as the sample job PRILOG REPORT in the Adabas Review 4.3 installation) must be changed to avoid problems. For more information, read Removed Functionality.
When upgrading from Adabas Review 4.2 to Adabas Review 4.4, an intermediate upgrade to Review 4.3. is needed.
The following enhancements have been made in this release.
Review 4.4 is fully compatible with Adabas 8 and now provides support for the Adabas Adarun CLOGLAYOUT=8 parameter.
Two new ADARUN parameters, REVLOGBMAX and REVLOGMAX, are provided to limit the size of the buffers and the CLOG record as a whole. See the ADARUN Parameters documentation in the appropriate Installation and Operations guides for more information.
A new filter mechanism is included in Review 4.4 which optionally limits the amount of data sent from Adabas to Review, resulting in enhanced performance of Review.
See Record Filtering for more information.
The values of the ENV statement's ENV-FACTOR parameter have been increased in Review 4.4. The maximum value is now 99999.9999 rather than the previous 9.9999.
See ENV Statement.
When there are severe communication problems between the Adabas client side and the Hub either in TRANS-PORT or in non TRANS-PORT mode, the message ARST07 or ARST08 will be issued, and the communication to the Review hub will be stopped. The Adarun parameter REVIEW will be switched to NO. To reactivate the communication to the Hub, the parameter can be switched on again.
In this release, the example jobs HUBJCL and LOCAL in the REVvrs.SRC library on BS2000 do not set the DBID parameter because we believe that setting a default DBID in these jobs might lead to problems in the setup of the environment. Instead, the DBID should be specified in the Natural area of Adabas Review for the default DBID in the user profile, or the Natural LFILE=(241,...) parameter. And for the Adabas Review hub database, the REVIEW parameter should set the hub DBID (or if is LOCAL, then it is its own DBID).
The following functionality was removed in this release:
The ECBS field has been removed because it is no longer provided by the Adabas nucleus. Reports containing this field are no longer executable and the field must be removed from the report.
Note:
The sample report PRILOG REPORT, provided in earlier versions of
Adabas Review, contains this field. If you are upgrading your Adabas Review (in
other words, this is not a new installation), you will need to manually edit
the PRILOG REPORT and remove the ECBS field.
If the ECBS field is not removed from the reports, errors will occur when executing the REGEN ALL function, as the reports will not regenerate.
If a report containing the ECBS field is used to store history data, you must build a new report with a different name that does not included the ECBS field. This new report can then be used to store new history data and the data already available in the history file can be accessed using the old report.
When an Adabas command log record in the new ACBX structure has multiple buffers specified, only the first buffer of each ABD type (i.e., the first Formatbuffer) is used by Review for building the contents of the Adabas Buffer Fields.
The fields FBL, RBL, SBL, VBL, and IBL are not supported at the moment.
In z/VSE and BS2000 environments, the Hub node ID cannot be greater than 255.
The documentation for this product is new with this release. However, when additional updated versions of the documentation are created, you can review them by linking to the Software AG documentation web site: http://documentation.softwareag.com/. If you have a Servline24 account, updated and past versions of the documentation can also be reviewed and downloaded by linking to the Software AG Servline24 web site: http://servline24.softwareag.com/public/. If you do not have a ServLine24 user ID and password yet, you will find instructions for registering on this site (free for customers with maintenance contracts).
The Adabas Review documentation includes:
online HTML topics describing all aspects of the product;
Adobe Acrobat Reader Portable Document Format (PDF) files created from the HTML topics;
Adobe Acrobat Reader Portable Document Format (PDF) files for a series of manuals created from the HTML topics.
No hard-copy documentation is provided, although you can print the PDF and HTML files on your local printer.
With Service Pack 2 (SP2) for Windows XP and Service Pack 1 (SP1) for Server 2003, Microsoft introduced a range of powerful new security features that restrict active content that runs locally on your computer. Active content includes ActiveX controls, Java applets, and JavaScript. Software AG's documentation web pages contain some JavaScript, and the SEARCH, INDEX and CONTENTS capabilities are implemented as Java applets. As a result, when viewing documentation web pages that reside on your PC using Internet Explorer and Mozilla Firefox under Windows XP SP2, note that active content is blocked. You must explicitly and repeatedly allow active content if you want to make use of the documentation's full navigation features. Note that this behavior is only observed when reading web pages installed locally on your PC, including those on CD in the PCs CD-ROM drive.
The active content for which Software AG is responsible, that is, the JavaScript code in our HTML documentation pages, will not harm your computers. The risk in using the navigation applets is negligible: Software AG has received no reports from users concerning any harm caused to a computer by the applets. We therefore suggest that when reading Software AG documentation in a local context, you should allow active content via the Security settings in the browser (with Internet Explorer, usually found under Tools > Internet Options > Advanced).
Full details of alternatives can be found on the home page of the suppliers of the navigation applets: http://www.phdcc.com/xpsp2.htm.
A product version is identified by the first two digits of the versioning number. Software AG distinguishes between major and minor versions according to the amount of functionality or technology added to the product. All other digits indicate correction levels.
In the product documentation, the notation vrs, vr, or simply v is often used as a placeholder for the current product version, for example, in data set or module names.
| Placeholder | Meaning | Definition |
|---|---|---|
| v | version | Major Version
The first digit of the product version number indicates major architecture and functionality implementation or enhancement that adds value to the product. |
| r | release | Minor Version
The second digit of the version number indicates functionality addition or enhancement that adds value to the product. |
| s | system maintenance level | Correction Level
Correction levels contain error corrections only, without new functionality, including documentation of all modifications and repairs. In case it is necessary to include functional changes into a correction level, an exception handling process ensures that corresponding quality assurance activities are triggered. These functional changes are documented. The main target is to avoid impacts when you install such a correction level. The third number of an Adabas version denotes the system maintenance level. On certain platforms supported by Adabas, additional levels may exist, such as update package, patch level, service pack and hot fix. |
Here are links to PDF files of the Release Notes for prior versions of Adabas Review that are still supported. They are provided for users who may be upgrading from an earlier version.
