Version 8.1.4
 —  Planning for Adabas 8  —

Utility Changes

All Adabas utilities have been updated to support the new extended features of Adabas 8. Some of this support appears in the form of new or modified utility parameters. In other cases, support was added internally that does not affect your use of the utility at all.

Note:
Be sure to read about the utility restrictions in Limitations and Restrictions for a brief description of what the limitations and restrictions are for utility use in Adabas 8.

This document describes the Adabas utilities whose user interface has changed in this release. For complete information about the functions of any Adabas utility, read Utilities.


ADAACK Utility Changes

Spanned record support is provided in the ADAACK utility. However, ADAACK assumes that an ISN passed to it is a primary ISN or is the only ISN for a record. If an ISN is the primary ISN for a spanned record, all of the associated segment records of the spanned record are automatically checked in the secondary address converter.

When printing error information about a particular ISN, the ADAACK utility will now indicate whether the problem is with a primary or secondary ISN, if the record is spanned.

Top of page

ADACDC Utility Changes

Spanned records are not supported by the ADACDC utility at this time. However, when the IGNORESPANNED parameter is specified in an ADACDC run, ADACDC processing ignores spanned records, issues a warning message, and continues its processing. A return code of "4" is returned.

Top of page

ADACMP Utility Changes

General Changes

Traditionally, the DD/FEHL error data set produced for ADACMP errors has truncated rejected records that exceeded the FEHL physical record length. In Version 8, the rejected records are segmented instead of truncated. Because of this change, the DD/FEHL LRECL setting must be at least 500 bytes.

ADACMP COMPRESS Changes

The following new parameters have been added to the ADACMP COMPRESS utility to support the MU/PE extension, spanned records, and LB fields:

The following changes have been made to existing ADACMP COMPRESS parameters:

When running ADACMP COMPRESS for a file that includes LB fields, a second sequential output data set (identified by the DDAUSB1 JCL DD control statement) is produced for the LOB file containing the LB field values.

ADACMP DECOMPRESS Changes

ADACMP DECOMPRESS processing supports the extended MU and PE limits and spanned records as input. The size of the value count preceding MU or PE values in each decompressed output record depends upon the extended MU and PE support for a file. A two-byte value count is given for files with extended MU and PE support. A one-byte value count is given for files without extended MU and PE support. In addition, the following functionality is supported.

Top of page

ADADBS Utility Changes

Three new database services have been added to the ADADBS utility to support the extended MU/PE field counts and record spanning:

In addition, a new RESETPPT function resets the PPT blocks on the ASSO data set.

Top of page

ADADCK Utility Changes

The ADADCK utility checks the header of a spanned record for plausibility, as follows:

A new MAXPISN parameter has also been introduced that allows you to set the maximum number of primary ISNs that will be checked for a spanned Data Storage file. The default is 1000.

Top of page

ADAFRM Utility Changes

The ADAFRM utility can now be used to clear multiple PLOG headers from the PLOG, without requiring that you reformat the entire PLOG. To do this, you should specify the NUMBER parameter in conjunction with the FROMRABN parameter and set the SIZE parameter to "1".

In addition, this utility can now handle the increased number of physical Associator and Data Storage extents (99) allowed in Adabas 8.

Top of page

ADAICK Utility Changes

If you run the ADAICK DSCHECK function, the primary and secondary ISNs are now identified in the output.

Top of page

ADALOD Utility Changes

The following new parameters are introduced for the ADALOD LOAD and UPDATE functions in support of spanned records and their associated secondary address converter:

The following new parameters and parameter values are introduced for the ADALOD LOAD functions in support of large object (LB) fields and their associated LOB files:

Top of page

ADAORD Utility Changes

To support spanned records, the following two new parameters have been added to the REORASSO, REORDB, REORFASSO, REORFILE, and STORE functions of ADAORD.

The secondary address converter is used to map the secondary ISNs of secondary spanned records to the RABNs of the Data Storage blocks where the secondary records are stored.

You can restructure databases and files from Adabas 5.1 - 5.3, 6.1, 6.2, 7.1, 7.2, or 7.4 and store them in Version 8 using ADAORD STORE. However, you cannot store the restructure output of an Adabas 8 database or file in a database running with any prior Adabas version (for example, Adabas 7).

You can restructure databases and files from an Adabas version prior to Adabas 8 and store them in an Adabas 8 database using ADAORD STORE. However, you cannot store the restructured output of an Adabas 8 database or file in a database running with any prior Adabas version (for example, Adabas 7). If you attempt this, the following warning will be generated and ADAORD will end with a CC=4:

*** Warning: The input dataset is from V8 and will not be processed

Top of page

ADAREP Utility Changes

The report produced by ADAREP now lists whether the MUPEX and spanned record options have been set for the database.

In the "Contents of Database" section of the report, the following changes have been made:

In the "File Options" section of the report, a "T" indicates that two-byte MU/PE indexes are active for the file and an "S" indicates that use of spanned records has been activated for the file. In addition, the "Contains LOB Fields" column indicates whether the file contains one or more LB fields (an "L" appears if it does) and the "LOB File" column (the last column) indicates whether or not the file is a LOB file (an "L" appears if it is). Note that these two LB field columns are mutually exclusive; only one of them will be marked.

In the "Physical Layout of the Database" section of the report, secondary address converter extents (for spanned records) are identified as "AC2" in the "Table File Type" column.

In the "File Information" section of the report, a new field called "Two Byte MU/PE" indicates whether two-byte MU/PE indexes are active for the file. In the same section, the highest, maximum expected, and minimum secondary ISN are given as well as a new field called "Spanned Rec Supp", which indicates whether or not spanned records are activated for the file. In addition, the "Contain LOB Fields" field indicates whether or not the file contains one or more LB fields and the "LOB File" field indicates whether or not the file is a LOB file.

In the Space Allocation section of the report, secondary address converter extents (for spanned records) are identified as "AC2" in the "List Type" column.

Finally, three new checkpoints may be written by the Adabas nucleus: 75, 76, and 77.

Top of page

ADASAV Utility Changes

The following new parameters are introduced for the ADASAV RESTONL FMOVE and ADASAV RESTORE FMOVE functions in support of spanned records and their associated secondary address converter:

Top of page

ADASEL Utility Changes

While there are no new parameters, ADASEL has been updated to support the MU/PE extension. In particular, when specifying indexes for MU or PE fields in an ADASEL SELECT IF statement, the indexes can now range from "1" through "65,534". Prior releases of Adabas restricted these indexes to values ranging from "1" through "191".

ADASEL recognizes spanned records in its processing, but it cannot process files containing spanned records.

Top of page

ADAULD Utility Changes

While there are no new parameters, ADAULD has been updated to support the MU/PE extension and spanned records. In particular, two new statistics listing the number of record segments that were read and written during the run are produced by the ADAULD utility.

Top of page