This document describes the Adabas Review 5.2 enhancements.
When using Adabas Review with Adabas for Mainframes Version 8.5 or above, Adabas Review works with a reduced record size. The command log extensions are categorized in three types of segments. Data will be sent only once (type 1), every minute (type 2) or all the time (type 3).
This method may be switched off with the new
INPUT
statement parameter MODE=V51. When
using Adabas Review with Adabas for Mainframes Version 8.4 or below, this feature is
not available, and the old mode will be used automatically.
The Review buffer pool is now a circular buffer pool and able to address 64-bit storage. When running reports as batch jobs, for the INPUT statement the new option REVIEWB-V64B can be used to enable 64-bit addressable storage. Buffer may be allocated with the new BUFFMB parameter. Make sure there is enough space in the REGION for this buffer.
The current REVIEW-DB repository (Natural LFILE 241) is now displayed on the top left of the main SYSREVDB maps. If applicable, the REVIEW-DB may be changed using the SET command.
In turn, on cluster environments, the display of the NucID has been moved from top left to top right, below the Target DBID.
The Target is now prefixed with Local/Hub, depending on the Review setup.
New sample report Schedule File Usage supplied, which uses TODAY (+/- nnn) as input for the Date From and Date To input field.
There are three new sample reports, called "Maximum Pct Space Used", "Remote Physical Calltype" and "ZIIP Usage per Command", please refer to Supplied Report Reference for further details.
If the specified values for the Date/Time From option in the Scheduling Options are more than 193 days and 22 hours in the future, a message will display the exact current maximum date/time.
When a report will be copied with the same name, the name of the attached display program shall be kept too. If this is not possible and the report already exists on the target environment, the name of the display program on the target will be taken. If this is not possible either, the next free new name is taken, starting from RD/RX-00001.
The REGEN ALL command is now available in Natural batch. An error report will be output by the Natural CATALL command after the REGEN ALL command was performed.
The History Intervals screen of SYSREVDB (LH – EX) has been reworked. More than one interval within one second are now shown separate. It is possible to scroll forward or backward by entering the number of lines.
Generated display programs to output monitoring data in the EDITOR mode (VX command) check the line and page size. A new terminal model 5 (27x132) will be detected, in addition to model 2 (24x80), model 3 (32x80) and model 4 (43x80).
A detailed report with LOG=Y may be defined without
fields. No fields are needed since Command logging of a detailed report with
LOG=Y will go directly to the LOG file and cannot be viewed
online. For a report without fields, no display report will be generated.
Several batch Natural commands may now be called within the same batch Natural job. Target ID (hub or local DBID) and the REVIEW-DB repository setting will be kept after a command has ended. In case of an error, the Natural batch session will not be terminated. An improved error message will be output and the next command may be processed.
The COPYREP program syntax and the output of the DBTECH program have been enhanced.
In online report output from SYSREVDB (VW command) the length of one numeric field is reduced by 1 byte. This is the byte not required for a sign (+/-). Thus, more data may be displayed on a screen. A REGEN of a display program is required for this change to take effect.
For deleting
history records, the access to the REVIEW-DB has been accelerated
(Natural READ instead of a
FIND). And DELHIST now takes care, that several
limits (time, DB calls) will not be exceeded when deleting high amount of data.
When a cluster environment runs on different LPARs, the NUCID that runs on the current LPAR will be selected by default. It is no longer the lowest NUCID number that is selected as it was in previous versions.
SYSREVDB may be started from the NaturalONE Tools and Utilites context menu. This is an interface to run SYSREVDB with Natural Web I/O (NWO) in an Eclipse environment.
Before a VIEW command will be executed, SYSREVDB compares the total field lengths of a running report with the total field length of a saved report definition. Because a report definition may have been changed since a report has been started, the generated display program may not match the cumulated data and return a Natural error.
The TECH screen (Review Repository section) of SYSREVDB displays a hint, if an EXPAND job is missing. EXPAND jobs must be run to add or change fields of the REVIEW-DB repository when migrating from a lower version, which has a different repository definition. See also Migration from Previous Versions for details.
Adabas Review may be started with ADARUN ZIIP=YES. The
AZPAD license is necessary.
When Adabas Review will be started with ZIIP=YES, zIIP may be
used in SYSREVDB.
With the command ZIIP [REVB|MAIN|HIST|AUTO],
zIIP statistics may be displayed.
With the command ZIIP[=]{YES|NO}, zIIP processing
in Adabas Review may be activated or deactivated.
In a Target definition (ET function) it may be specified if an Adabas Review target will be started with ZIIP=YES.
Further details concerning zIIP support are documented in Adabas Review for zIIP.
The new command CONFIGDB allows displaying the
CONFIGDB Review parameters without leaving the SYSREVDB utility. The parameters
are specified in the Natural text member CONFIGDB in library SYSREVDB.
In addition to the changes made to reflect enhancements and fixes, the new section Adabas Review for zIIP has been added to inform about concepts and implementation of zIIP support in SYSREVDB.