This document describes the Adabas Review 4.8 enhancements.
The following table summarizes the changes made to Adabas Review fields in this release. For complete information about fields, read Field Reference.
| Field Name | New or Changed | Release | Description |
|---|---|---|---|
| L3DE | Changed | 4.8 SP1 | The L3DE field now also shows the descriptor obtained from the Additions 1 field of an ACB or ACBX L6 command call. |
| CCALLS | New | 4.8 SP1 | The counter of successful client calls. |
| CCALLU | New | 4.8 SP1 | The counter of unsuccessful client calls. |
|
FBFIELDS |
Changed | 4.8 SP1 | In earlier versions, these fields were not allowed for detailed reports, but no check was made to see whether they were used. Now using these fields in a batch report or in an Autostarted report will result in the error message REV20008; defining a new report with one of these fields in SYSREVDB will result in the error message REV00003. |
|
FBSEGnn |
Changed | 4.8 SP1 | In earlier versions, these fields were documented as not being allowed for detailed reports. Starting with Adabas ReviewVersion 4.8 SP1, these fields can be used in detailed reports. |
You can use the Natural Program SETCM to manage client reporting in batch mode. Please refer to Natural Program SETCM in the section Managing Client Reporting in Batch.
When using user-defined display programs in SYSREVDB it was not possible
to SAVE or REGENERATE
such a program. This was to avoid the overwrite of user changes.
Now a pop-up window will appear when such a report is about to be saved and the user can decide whether to overwrite the existing program or to create a new display program.
A new function RU has been implemented. See
the section Regenerating a
User-Defined Display Program for details.
Performance enhancements in the following areas are introduced with Adabas Review 4.8 SP1:
Overall performance increase in a standard environment;
Increased performance for RULE processing with wildcards;
Increased performance in the handling of Review history data. This
applies when writing history data as well when issuing the
LH (list history) command from within SYSREVDB.
The performance overhead when running with Review in local mode, but no reports are actively started is dramatically minimized. The Adabas zaps AN826109 or AN832037 or AN833005 including their post- and prerequisites need to be applied.
The behavior of DBID=11111 specifications will be different than in previous releases. This specification will now no longer behave in a manner identical to specifying DBID=ALL. Instead, this DBID will be handled as all other DBIDs. For complete information, read Specifying the Report DBID.
The data for history reports is written in intervals to the Adabas Review
repository file. Using the function EX as described
in Expanding the List
of History Reports, the list of single intervals will be
displayed. Either single instances can be processed or all data for one
report.
The display of the expanded list has changed as well the input maps when viewing or compressing history reports from the List History Reports function. These changes along with documentation changes should make the user aware that always whole intervals are processed and not only parts of an interval.
The output described in
Processing History
Data in Batch Natural (HISTORY
program) has also been changed to display not only the date but the time as
well.
A new parameter RVC-CLIENT has been added to the START function, see example program RVCALL01 in Performing Adabas Review Online Functions from Natural Programs .
The user ID displayed in messages REV20257, REV20236 and in the SYSREVDB
function "display active report information" is no
longer the Review user ID from the Review User Profile, it is now the
*INIT-USER value from Natural.
The LINESIZE for a report definition is now 255 bytes, for online and batch defined reports. For further information read about the LINE parameter in General Report Options and LINESIZE in REPORT Statement.
The numeric field calculation SUM does calculate and display a total of a field´s value. In case this total value exceeds the size of the numeric field display, the total value will be cut. For further information read Specifying Numeric Options for Summary Reports and Viewing Reports with numeric calculation SUM .
Reports which are in the end processing or the interval end processing are now displayed in the LS screen with one of the new status indicators "R" or "P". For further information refer to the table under Listing Started Reports.
When an Adabas response code is given while history data is written, the changed message
FOLLOWING ERROR APPLIES TO REPORT: report
name
with the respective report name instead of the report number will be printed and then the changed message REV20045 will be shown.
The START Natural program which can be executed in batch or as direct command in online SYSREVDB has new parameter setting, the old setting is still supported. For details, see Starting a Report in Batch Natural.
Raw log file support is now also available for autostarted or batch reports. For details, see the description of the RAW Statement under Using Batch Report Statements.
The contents of a user field can now be defined by the user dependent on a given condition. For more information, see Defining Adabas Review User Fields.
Using REVUEX1 the user can provide user-specific data to be passed to Adabas Review. The size of the available buffer has been increased from 32 to 100 bytes. For more information, see REVUEX1.
The internal naming convention for SYSREVDB Natural fixes has been changed from IS00x to IXvrsin where i is value I for fix 1 to 9, J for fix 10 to 19 and so on. The hotfix naming convention remains as before. For more information, see Accessing Technical System Information.
The Adabas Review DDMs, that you have to define to Natural Security during the installation, no longer contain the version number as part of their names. They were renamed as follows:
REVIEW-ADABAS-Vvrs-CLOG is replaced by REVIEW-ADABAS-CLOG.
REVIEW-ADABAS-Vvrss-SYSTEM is replaced by REVIEW-ADABAS-SYSTEM.
The old Adabas Review Version 4.7 SP2 DDMs are delivered for downward compatibility only.
Refer to the installation documentation corresponding to your platform for further details.