This document lists the Adabas 8.6 enhancements.
Adabas V8.6 introduces the option to increase the buffer pool to multiple gigabytes –
for example, LBP=12G or 12 gigabytes. This allows installations to seek a
higher buffer efficiency and fewer read I/Os from the database, quicker command response
times, and the potential for putting a higher workload on Adabas.
Prior to version 8.6, Adabas supported buffer pools in 31-bit addressable storage (above the 16-megabyte line) but not in 64-bit addressable storage (above the 2-gigabyte bar). Therefore, the buffer pool could only be as large as the space available between the 16-megabyte line and the 2-gigabyte bar. In practice, the size of the buffer pool was limited to a maximum of 1.0-1.5 gigabytes, depending on the system configuration.
Adabas V8.6 now supports the so called "buffer pool above the bar."
For L1 and L4, a new Command Option2 = 'J' is available. The option allows to read the records of a file in descending ISN sequence. See L1 and L4 Commands: Read / Read and Hold Record > Function and Use in the Command Reference part of the documentation for further details.
To support the new Command Option2 = 'J' in Adabas Fastpath and Adabas Vista, make sure that the following fixes are applied:
AW822072 and AW822075 (AFP)
AV822059 and AV822062 (AVI)
With Natural for Mainframes 9.2.2 and above, this command option can be used in statements like READ BY ISN DESCENDING.
For L1 and L4, a new Command Option2 = 'K' is available. The option allows to read
the records of a file in ISN sequence by specifying a TO ISN, an ISN at
which the read sequence should end. See L1 and L4 Commands: Read / Read and
Hold Record > Function and Use in the Command
Reference part of the documentation for further details.
To support the new Command Option2 = ‘K’ in Adabas Fastpath and Adabas Vista, make sure that the following fixes are applied:
AW822072 and AW822075 (AFP)
AV822059 and AV822062 (AVI)
With Natural for Mainframes 9.2.2 and above, this command option can be used in statements like READ BY ISN [ASCENDING | DESCENDING] ENDING AT.
In Adabas V8.6 SP1, ADADBS OPERCOM DRES expands, introducing two new parameters,
SESSION and TS.
Prior to Adabas. V8.6 SP1, ADADBS OPERCOM DRES only returned High Watermark statistic since the last refresh. If ADADBS REFRESHSTATS ALL or ADADBS REFRESHSTATS POOLUSAGE has not been invoked, high watermark statistics collected from the start of the nucleus are displayed.
When the SESSION parameter is specified, the user receives
statistics collected from the start of the nucleus, even if a REFRESHSTATS has been
invoked.
When the user specifies TS, a date and time is output for when
the high watermark was recorded. The date-time statistic will correspond to the last
refresh, or the full session, depending on which is specified. To make this
information easier to read, the Current Usage and High
Watermark columns have been switched in the output order.
Prior to Adabas V8.6 SP1, ADARES BACKOUT required the sequential protection log dataset (DDBACK) to reside on tape.
Adabas V8.6 SP1 and later permits DDBACK to reside either on tape or on disk.
When DDBACK points to multiple concatenated sequential protection log datasets, all these datasets must be either on tape or on disk. A mixture of tape and disk datasets concatenated together under the DDBACK DD is not supported.
The ADARES PLCOPY and ADARES COPY utilities can now use the parameter UTICPLISTALL to display all utility checkpoints.
Prior to this addition, UTICPLIST could only display SYNP, SYNV, and SYNS checkpoints. Now you can use UTICPLISTALL instead of UTICPLIST to display all utility checkpoints for PLCOPY and COPY.
The ADASEL utility can now display user data written by an ET command with the DISPLAY option ETUSERDA.
When choosing to DISPLAY ETUSERDA, all ET records are displayed. The records without
ET user data attached display ETUSERDA unavailable. When you
choose to display ET user data, you can specify the user data with a logical operator
followed by the value-criterion ETUSERDA, which limits the ADASEL OUTPUT to only
records with the specified user data, if they are present. For more information about
the ADASEL utility, see Utilities > ADASEL Utility: Select Protection
Data.
As of Adabas V8.6 SP1, ADAZIN has been enhanced to support the printing of maintenance information about load modules for the following products:
Adabas CICS Interface (ACI)
COR-based Add-ons including:
Adabas System Coordinator (COR)
Adabas Fastpath (AFP)
Adabas Vista (AVI)
Adabas Transaction Manager (ATM)
Adabas SAF Security (AAF)
Adabas Service for Java (AJZ)
Adabas V8.6 introduces a new layout for the SYNS-5B checkpoint record.
The SYNS-5B checkpoint record contains information on refresh statistics. Prior to Adabas V8.6, only High Watermark statistics were written to the record for 18 pools upon a statistics refresh or nucleus shutdown. In the event of a statistics refresh, the Interval High Watermark is written to the record. Otherwise, the Session High Watermark is written to the checkpoint record.
The SYNS-5B checkpoint record now includes Allocated size, the High Watermark size, and each pool's associated timestamp. The new checkpoint record also includes the Redo Pool, Auditing Pool, and Replication Pool. The Auditing Pool and Replication Pool use an 8-byte size and an 8-byte High Watermark.
These new enhancements can be viewed in the ADAREP extended checkpoint output as well as the extended XML output.
ADA861 provides the following enhancements to the processing of TEMP and SORT datasets in utilities ADAINV, ADALOD and ADAULD:
Allow SORT and TEMP to be dynamically extended when full.
Support writing to SORT and TEMP even though the datasets have not been pre-formatted (e.g. via ADAFRM).
Support temporary dataset usage for TEMP and SORT, e.g.:
//DDTEMPR1 DD DSN=&&TEMP,DISP=(NEW,DELETE), // SPACE=(CYL,(100,100)),VOL=(,,,10) //DDSORTR1 DD DSN=&&SORT,DISP=NEW, // SPACE=(CYL,(100,100)),RECFM=F,BLKSIZE=8904
Prior to ADA861, the TEMPSIZE and
SORTSIZE parameters were mandatory. With ADA861,
TEMPSIZE and SORTSIZE become optional
parameters.
If TEMPSIZE/SORTSIZE is specified, the
utility will process TEMP/SORT in the same way as in previous versions, i.e.
pre-formatting of TEMP/SORT is required and dynamically extending the dataset is not
available.
By omitting the TEMPSIZE/SORTSIZE
parameter, users can take advantage of the enhancements listed above.
When TEMPSIZE/SORTSIZE is omitted, the
user can either let the utility choose the TEMP/SORT device type (by omitting the
TEMPDEV/SORTDEV parameter), or else
set the TEMP/SORT device type by specifying
TEMPDEV/SORTDEV.
When both TEMPSIZE/SORTSIZE and
TEMPDEV/SORTDEV are omitted and
TEMP/SORT is unformatted, users can specify the block size to be used for TEMP/SORT
via JCL. The sample JCL for DDSORTR1 above provides an example of this. In this case,
the block size in the JCL will be used if it matches an Adabas device type. A JCL
block size which does not match an Adabas device type is treated as an error. For the
list of Adabas device types and corresponding block sizes, see Supported Adabas
Device Types.
For processing TEMP/SORT datasets which are not pre-formatted, Software AG recommends
omitting both TEMPSIZE/SORTSIZE and
TEMPDEV/SORTDEV, and not specifying a
block size via JCL. The utility will then select an optimum block size.
When both TEMPSIZE/SORTSIZE and
TEMPDEV/SORTDEV are omitted and
TEMP/SORT is pre-formatted, the utility retains the block size of the existing
dataset.
Note that it is still possible for TEMP/SORT to fill up. Users should define TEMP and SORT datasets with secondary extents large enough to hold all required data.
See the ADAINV, ADALOD and ADAULD Utilities documentation for guidance on the size requirements for TEMP/SORT datasets, and for more detailed information about the processing of TEMP and SORT.
With the new Adabas add-on product Adabas Auditing for Mainframes, several enhancements touch Adabas components. Most notably, a new direct access container type ALOG is available (DDNAME DDALOGRx). It is used to record the Audit Events by the Adabas Auditing server on behalf of the Adabas nuclei. Please see the Adabas Auditing for Mainframe documentation for details.
With Adabas V8.6 SP1 and later, when using options A, W, H from the main menu to display Session High Water Marks, a timestamp is now recorded for the time of the event.
You can now display the individual status of each PLOG or CLOG dataset in the Adabas Online System facility. This functionality can also be used in Adabas version 8.5.4 with the optional zap AY854181.
For more information about the CLOG/PLOG dataset status, see Using Adabas Online System (AOS) > Performing System Operator Command Functions > CLOG/PLOG Dataset Status in the Adabas Online System documentation..
When displaying a selected User Queue Element (UQE), you can now press PF4 to refresh the information associated with that UQE.
From the Main Menu, choose option A Session Monitoring, then Q Display Queues, A Display User Queue Elements, then type a D on the selection line for the User Queue Element of your choice, and you are given the details of that UQE. It is on this map, that you can press PF4 to display any updated information of the UQE.
Modify File Information now displays the Target ID for the given file if Replication=ON.
From the Main Menu, choose option F File Maintenance, then M Modify File parameters, and specify a file number. If Replication=ON, the resulting screen includes the Target ID of the Reptor that is in use for this file.
When displaying user queue elements (UQE), command queue elements (CQE), or hold
queue elements (HQE) in the Adabas Online System facility, you can now use the new
program function key PF5 Filter to filter the displayed information.
For more information about the filtering function, see Using Adabas Online System (AOS) > Monitoring Adabas Sessions > Displaying Queues in the Adabas Online System documentation.
In Adabas V8.6 SP1, ADABAS DRES OPERATOR COMMAND expands, introducing two new parameters, SESSION and TS.
Prior to Adabas. V8.6 SP1, the ADABAS DRES OPERATOR COMMAND only returned High Watermark statistics since the last refresh. If ADADBS REFRESHSTATS ALL or ADADBS REFRESHSTATS POOLUSAGE has not been invoked, high watermark statistics collected from the start of the nucleus are displayed.
When the SESSION parameter is specified, the user receives statistics collected from the start of the nucleus if a REFRESHSTATS has been invoked. However, if a REFRESHSTATS has not been invoked, the ADAN2J message will be displayed informing the user that these stats have not yet been generated. Interval statistics, which have been collected from the start of the nucleus, will be displayed.
When the user specifies TS, a date and time are output for when the high watermark was recorded. The date-time statistic will correspond to the last refresh, or the full session, depending on which is specified.
In this enhancement, there have been some slight adjustments to the alignment of the column headers. Specifically, the “Size” label has been shifted to the right 1 column, and the “High Watermark” label has been shifted left 1 column.
The following enhancements have been aded to SYSREVDB on Adabas Review version 5.3.1.1. For more information, refer to the Adabas Review documentation.
You can now start Adabas Review online when you enter the new SYSREVDB command in a
Natural prompt. If required, the SYSREVDB command performs a LOGON to the
library SYSREVDB and starts the program MENU.
You can now initialize Adabas Review when you enter the INSTALL or
INSTALL ALL command in a Natural prompt for SYSREVDB or from batch
Natural.
Running the INSTALL DB command now repairs the Adabas Review repository
if sample reports are missing or multiple copies of a sample report are found.
When you view the technical system information with the TECH command,
the Database System Environment screen now shows the Adabas Review repository version
if the repository is allocated with SYSREVDB 4.7 SP1 or lower.
The header of generated programs in Basic mode now uses the same standard header as programs in Editor mode.
The redisplay mode in the output of a Basic mode program now shows readable values for hexadecimal fields. The color of the redisplay mode output is now turquoise.
When you execute the RESET HISTORY command, no data is lost. Running the
command now also provides a preview mode and detailed information about the lock
status of the file and the processed data.
When you execute the HELP command command, help information for the
specified general Adabas Review command command is provided. For
example, HELP HELP provides help information of the HELP
command itself.
When you execute the HELP * command, the available general Adabas
Review commands are listed.
If a question mark (?) is entered in the command line, the available
general Adabas Review commands are listed.
In the help screen of an Adabas Review field, you can press PF2 to display field specific information.
The following commands are new in SYSREVDB:
The new Adabas Review commands EXEC natcmd or // natcmd
executes the Natural command natcmd. After execution, the SYSREVDB
main menu is started.
The new Adabas Review command NATURAL natcmd executes the Natural
command natcmd. It provides the same functionality as the Adabas
Review command NAT.
The new Adabas Review command TERM terminates the Natural session.
It provides the same functionality as the Adabas Review commands FIN
and QUIT.
The new Adabas Review command TRACE maintains the SYSREVDB internal
trace.
The new Adabas Review program REVTRACE maintains the SYSREVDB internal
trace.
The user profile access rule Change LFILE Info? indicates now
whether users are allowed to run the SET or SETFILE
command.
Adabas V8.6 introduces a new JOBS library for Adabas CICS (ACIvrs.JOBS).
The following table indicates the old and new location for the sample jobs provided for Adabas CICS.
| Sample Job Name | Old Location | New Location |
|---|---|---|
| ASMCINS | ACIvrs.SRCE | ACI861.JOBS |
| ASMCOPT | ACIvrs.SRCE | ACI861.JOBS |
| CPYCICSM | ADAvrs.JOBS | ACI861.JOBS |
| JCLALCI | ADAvrs.JOBS | ACI861.JOBS |
| JCLCOBI | ADAvrs.JOBS | ACI861.JOBS |
| JCLLNCS | ADAvrs.JOBS | ACI861.JOBS |
| LNKATRU | ACIvrs.SRCE | ACI861.JOBS |
| LNKGCICS | ACIvrs.SRCE | ACI861.JOBS |
As of Adabas V8.6 SP1, ADASMF Storage pool termination statistics now include a High Watermark timestamp for each pool. These statistics provide the Date and Timestamp of the High Watermark occurrence.
The sample user exit 12 (UEX12) for submitting ADARES xLCOPY jobs has been enhanced. UEX12 now supports more Adabas configurations, and the provided load module can be used without modifying its source and reassembling it.
The following list gives a summary of the provided enhancements:
Support the copying of ALOG (ALA audit server log) datasets in addition to CLOG and PLOG datasets.
Introduce the following reporting enhancements:
Report the log dataset status indicators in readable text instead of hexadecimal flags.
Report the number of in-use (i.e., not free) log datasets.
Print an additional message line when all log datasets are full.
Print the message lines with unique message code suffixes.
Print the status message lines with one multi-line WTO request.
Support the initiating of the ADARES xLCOPY execution
using an MVS START command, where ADARES runs as a started task.
Prepare more customization options using zaps.
For details, see the section Using Sample User Exit 12 in User, Hyperdescriptor, Collation Descriptor, and SMF Exits.