Utilities
4
ADABAS UTILITIES
Database services such as loading or deleting files are handled by an integrated set of online and
batch-mode “utilities”. Most utilities can be run in parallel with normal database activity to
preclude interruption of daily production. See the ADABAS Utilities Manual for more
information.
ADABAS utilities address initial design and load operations, backup/restore/recovery routines,
database modification routines, and audit/control/tuning procedures.
Note:
See the Optional Extensions chapter starting on page 71 for information about ADABAS
ONLINE SYSTEM/Basic Services, a menu-driven, interactive DBA tool.
Initial Design and Load Operations
ADACMP : Compress / Decompress
ADACMP COMPRESS is used to edit and compress data records to be loaded into the database
using ADALOD; ADACMP DECOMPRESS is used to decompress individual files for data
structure or field definition changes, or for use as input to non-ADABAS programs.
COMPRESS
Input
ADACMP input data must be in a sequential dataset/file. Indexed sequential and VSAM input
cannot be used. The records may be fixed, variable, or of undefined length. The maximum input
record length permitted depends on the operating system. The maximum compressed record
length is restricted by the Data Storage block size in use and the maximum compressed record
length set for the file (see the MAXRECL parameter, ADALOD utility). The input records can
be in either blocked or unblocked format.
It is possible to omit the input dataset if the parameter NUMREC=0 is supplied.
ADABAS Concepts and Facilities
The logical structure and characteristics of the data for input to COMPRESS are described with
field definitions statements (FNDEF to define fields or groups of fields; SUBFN and SUPFN
to define sub- or superfields, respectively; HYPDE, PHONDE, SUBDE, and SUPDE to define
various types of descriptors). Field definitions are used to create the ADABAS Field Definition
Table (FDT).
By default, input data records are processed in the order of the field definition statements. The
FORMAT parameter allows you to change the order of field processing or skip fields.
Processing
ADACMP COMPRESS edits and compresses the data records.
Editing includes checking each field defined with a “packed” (P) or “unpacked” (U) format to
ensure that the field value is numeric and in the correct format. Any record that contains invalid
data is written to the ADACMP error dataset and is not written to the compressed dataset.
ADABAS user exit 6 can be used to specify additional editing to be performed during ADACMP
COMPRESS processing. See the ADABAS DBA Reference Manual for information about user
exits.
Compression includes removing trailing blanks from alphanumeric fields; removing leading
zeros from numeric fields; removing trailing zeros in floating-point format fields; and packing
numeric unpacked fields. Fields with the fixed (FI) option are not compressed, and empty fields
located at the end of the record are neither stored nor compressed. Null value fields are processed
differently depending on options being used. SQL null value processing is supported.
Output
Processed data records are written out together with the file definition information to a
sequential dataset with the “variable blocked” record format. This dataset, or several such
datasets from multiple ADACMP executions, can be used as input to the ADALOD utility. The
dataset can be used as input to ADALOD even if it contains no records, meaning that no records
were provided on the input dataset or all records were rejected during editing.
The ADACMP processing report indicates the approximate amount of space required in Data
Storage for the compressed records by device type (specified with the DEVICE parameter) and
for Data Storage padding factors between 5 and 30 percent. The compression rate is computed
based on the real amount of data used as input to the compression routine.
Utilities 4
51
DECOMPRESS
ADACMP DECOMPRESS accepts as input data records from existing ADABAS files, either
directly without separate file unloading, or already unloaded with the ADAULD utility. If a file
is directly decompressed, it is unloaded without FDT information as part of the decomperssion
process, which can save time when decompressing larger files.
Direct decompression of multiclient files can be limited to records for a specific user only when
a valid owner ID (ETID parameter) is specified.
The FORMAT parameter may be used to decompress the record to a format other than that
specified by the FDT. This is particularly useful when the FDT of an existing file is to be
changed.
Processed data records are written to a sequential dataset with the “variable blocked” record
format. Rejected data records are written to the error dataset.
ADALOD : Loader
The ADALOD LOAD function loads a file into the database. Compressed records produced by
the ADACMP or ADAULD utility may be used as input.
ADALOD loads each compressed record into Data Storage, builds the Address Converter for
the file, and enters the field definitions for the file into the Field Definition Table (FDT).
ADALOD also extracts the values for all descriptors in the file together with the ISNs of all
records in which the value is present, to an intermediate dataset. This dataset is then sorted into
value/ISN sequence and entered into the Associator inverted lists.
The ADALOD UPDATE function is used to add or delete a large number of records to/from an
ADABAS file. The UPDATE function requires considerably less processing time than the
repetitive execution of the ADABAS add/delete record commands. Records to be added may
be the compressed records produced by the ADACMP or ADAULD utility. The ISNs of records
to be deleted can be provided either in an input dataset or by using control statements.
Records may be added and other records deleted during a single execution of ADALOD.
ADABAS Concepts and Facilities
ADAULD : Unload
The ADAULD utility unloads an ADABAS file. ADABAS files are unloaded to
permit the data to be processed by a non-ADABAS program. In this case, the file must also be
decompressed after unloading using the DECOMPRESS function of the ADACMP utility.
create one or more test files, all of which contain the same data. This procedure requires that
a file be unloaded, and then reloaded as a test file with a different file number.
change the Field Definition Table (FDT). This requires that the file be unloaded, decompressed,
compressed using the modified field definitions, and reloaded. If the ADADBS utility is used
to add field definitions to a file, the file does not need to be unloaded first.
The sequence in which the records are unloaded may be
physical the order in which they are physically positioned within Data Storage.
logical a sequence controlled by the values of a user-specified descriptor.
ISN ascending ISN sequence.
The unloaded record output is in compressed format. The output records have the same format
as the records produced by the ADACMP utility.
Utilities
Backup / Restore / Recovery Routines
ADAPLP : Protection Log / Work Print
The ADAPLP utility prints data protection records contained on the ADABAS Work dataset or
the ADABAS data protection log. You can specify whether to print
ALL all protection records—the default
ASSO just Associator protection records
DATA just Data Storage protection records
C1 records resulting from ADABAS C1 commands
C5 records resulting from ADABAS C5 commands
EEKZ records written at completion of a nucleus buffer flush
ET records resulting from ADABAS ET commands
REPR Work dataset records used by Autorestart to repair the index
SAVO records resulting from online SAVE database/file operations
VEKZ records written at completion of update commands
The number of protection records printed can be reduced even more by specifying a file, ISN,
or RABN.
ADARAI : Recovery Aid
The ADABAS Recovery Aid utility ADARAI can be used to automate and optimize database
recovery. See also the restart/recovery information in the ADABAS Operations Manual.
ADARAI supports all ADABAS-compatible tape management systems.
The ADARAI utility prepares the recovery log files (RLOGs), lists the information contained
in the RLOGs, creates the job control statements to recover the database, and disables ADARAI
logging.
The RLOGs record the information about datasets, utility parameters, and protection logs
needed to build the recovery job control statements. There are two RLOGs: the primary file
(DDRLOGR1 or RLOGR1) and a mirror file (DDRLOGM1 or RLOGM1). The mirror file must
always exist; it can be used to recover the database if the primary file is not accessible.
ADABAS Concepts and Facilities 4
54
Information is stored on the RLOG by generations. A “generation” includes all activity between
consecutive ADASAV SAVE/RESTORE (database) and/or RESTORE GCB operations. The
first generation includes the first ADASAV SAVE/RESTORE (database) or RESTORE GCB
operation and extends to (but excludes) the second.
Minimally, the RLOG retains the number of generations specified by the MINGENS parameter
during the ADARAI PREPARE step. However, a maximum of 32 generations will be stored on
the RLOG if there is enough space available.
Systems using the Recovery Aid feature require a formatted recovery log (RLOG) dataset pair
(normal and mirrored), which must first be formatted with the ADAFRM utility and then
defined using the ADARAI utility.
ADARES : Restart
The ADARES utility performs functions related to database recovery:
BACKOUT removes all the updates applied between two checkpoints. The checkpoints used
are normally the result of a non-synchronized checkpoint command (C1) but may also be
synchronized checkpoints. The complete database may be included in the backout process, or
backout may be limited to selected files.
CLCOPY copies a command log dataset from disk to a sequential dataset. This function is
necessary only if dual command logging is in effect for an ADABAS session.
COPY copies a sequential ADABAS protection log dataset. This function should be executed
if the ADABAS session in which the sequential protection log dataset was created was
terminated abnormally.
PLCOPY copies a protection log dataset from disk to a sequential dataset. This function is
necessary only if dual protection logging is in effect for an ADABAS session.
REGENERATE reapplies all the updates performed between two user-specified checkpoints.
The checkpoints specified may be the result of a non-synchronized checkpoint command (C1)
but may also be synchronized checkpoints. The REGENERATE function may process all files
or be limited to one or more files. It is most often used after the database (or one or more files)
has been restored to a previous status with the RESTORE or RESTONL function of the
ADASAV utility.
REPAIR repairs one or more blocks in Data Storage that, for any reason, have become unusable.
The most recent save tape of the database and any protection log tapes created thereafter are used
as input to this function.
Utilities
ADASAV : Save / Restore Database or Files
The ADASAV utility saves and restores the contents of the database, or one or more files, to or
from a sequential dataset. ADASAV should be run as often as required for the number and size
of the files contained in the database, and the amount and type of updating. For large databases,
ADASAV functions may be run in parallel for the various disk packs on which the database is
contained.
Special ADASAV functions are available for use with the ADABAS DELTA SAVE FACILITY.
For more information, see the ADABAS DELTA SAVE FACILITY Manual.
RESTONL functions restore from a SAVE dataset created while the ADABAS nucleus was
active (that is, online); RESTORE functions restore from a SAVE dataset created while the
ADABAS nucleus was inactive (that is, offline).
RESTONL and RESTORE have the subfunctions GCB, FILES, and FMOVE:
Without a subfunction, RESTONL and RESTORE restore entire databases.
With the GCB subfunction, they restore the General Control Block, Associator RABNs 2–30
of the database, and specified files.
With the FILES subfunction, they restore one or more files into an existing database to their
original RABNs.
With the FMOVE subfunction, they restore one or more files into an existing database to any
free space, allowing changes to extent sizes.
If changes occurred during the online SAVE, the RESTONL function is followed automatically
by the RESTPLOG function. RESTPLOG applies the updates that occurred during, and
therefore were not included in, the online SAVE.
RESTPLOG is also executed following a RESTONL or RESTONL FILES function that ended
before the protection log (PLOG) updates were completely restored. RESTPLOG applies the
database updates not applied by the unsuccessful RESTONL function.
The SAVE function to save a database or one or more files may be executed while the ADABAS
nucleus is active (online) or inactive (offline). If the Recovery Aid option is active, a SAVE
database operation begins a new RLOG generation.
ADABAS Concepts and Facilities
ADASEL : Select Protection Data
The ADASEL utility selects information in the ADABAS sequential (SIBA) or dual (PLOG)
protection log. ADASEL decompresses the information and writes it to a print dataset
(DDDRUCK or DRUCK) or to a user-specified output dataset.
The protection log contains information on all updates applied to the database during a given
ADABAS session. Information selected by ADASEL can be used for auditing or as input to a
NATURAL or non-ADABAS program.
You can select before-images, after-images, or both for new, updated, and deleted records. You
can also select data written to the protection log by an ADABAS C5 command.
Database Modification Routines
ADADBS : Database Services
All ADADBS functions can also be performed using ADABAS ONLINE SYSTEM/Basic
Services. When the ADABAS Recovery Aid is active, using Basic Services is preferable for file
change operations because it writes checkpoints that are necessary for recovery operation.
ADADBS offers a variety of functions, any number of which may be performed during a single
execution of the utility.
Database Functions
The ADD function adds a new dataset to the Associator or Data Storage. The dataset to be added
may be on a device type that is the same as that currently being used or different. A maximum
of five datasets each may be assigned to the Associator and Data Storage.
The DECREASE function decreases the size of the last dataset currently being used for
Associator or Data Storage. The space to be released must be available in the Free Space Table
(FST).
The DECREASE function does not deallocate any of the specified physical extent space. To
deallocate space, you must decrease the database with the DECREASE function; save it with
ADASAV SAVE; reformat the datasets with ADAFRM; and restore the database with ADASAV.
Utilities
The INCREASE function increases the size of the last dataset currently being used for the
Associator or Data Storage. This function may be executed any number of times for the
Associator. The maximum of five Data Storage Space Tables (DSSTs) limits Data Storage
increases to four before all five Data Storage extents must be combined into a single extent with
either the REORASSO or REORDB function of the ADAORD utility.
The NEWALTS function assigns additional alternate RABN blocks for the Associator or Data
Storage. Existing alternate RABN definitions cannot be changed with NEWALTS.
Alternate RABN blocks can be used in place of RABN blocks that are physically damaged. If
ADABAS detects that a write operation is not successful, ADABAS selects an alternate block
of the same type, and the data is written to it. This alternate RABN is then used in place of the
original block for all subsequent read and write operations.
The RENAME function changes the name assigned to a (file or) database. If a file is not
specified or is specified with file number zero, the database is renamed.
File Functions
The ALLOCATE function is used to allocate a logical extent (an Address Converter, Data
Storage, Normal or Upper Index) of a specific size. The DEALLOCATE function is used to
deallocate a logical extent. Only one extent may be allocated or deallocated per ADADBS
execution.
The CHANGE function changes the standard length of an ADABAS field. No modifications to
records in Data Storage are made by this function. The user is, therefore, responsible for
preventing references to the field that would cause invalid results because of an inconsistency
between the new standard length as defined to ADABAS and the actual number of bytes
contained in the record.
The DELETE function deletes an ADABAS file from the database. The file may not be coupled.
If an ADABAS expanded file is specified, the complete expanded file (the anchor and all
component files) is deleted. This function results in the deallocation of all logical extents
assigned to the file. The released space may be used for a new file or for a new extent of an
existing file.
The DSREUSE function determines, for a specified file, whether Data Storage blocks that
become free as a result of record deletion are reused. Block reuse is originally determined when
a file is loaded into the database with the ADALOD FILE function, or when the system file is
defined with the ADADEF DEFINE function. In both cases, block reuse defaults to “YES” if
not specified.
ADABAS Concepts and Facilities
The ISNREUSE function determines, for a specified file, whether ADABAS reuses the ISN of
a deleted record for a new record. If not, each new record is assigned the next higher unused ISN.
For a specified ADABAS file that is not a system file, the MODFCB function modifies
parameters such as file padding factors for the Associator or Data Storage; maximum size of
secondary logical extent allocations for Data Storage, Normal Index, and Upper Index;
maximum compressed record length permitted; and whether a user program is allowed to
perform a file refresh operation by issuing a special E1 command.
The NEWFIELD function adds one or more fields to a specified ADABAS file that is not a
system file. The new field definition is added to the end of the Field Description Table (FDT).
NEWFIELD cannot be used to specify actual Data Storage data for the new field; the data can
be specified later using ADABAS add or update commands, or NATURAL commands.
The REFRESH function sets the file to “0” records loaded; sets the first extent for the Address
Converter, Data Storage, Normal Index, and Upper Index to “empty” status; and deallocates
other extents.
The RELEASE function releases a descriptor from descriptor status. All space currently
occupied in the Associator inverted list for this descriptor is released. The space can then be
reused for this file by reordering or by ADALOD UPDATE. No changes are made to Data
Storage.
The RENAME function changes the name assigned to a file or database. If a file is not specified
or is specified with file number zero, the database is renamed.
The RENUMBER function changes the number of an ADABAS file that is not a system file.
If the new number specified is already assigned to another file, the RENUMBER function will
not execute.
The UNCOUPLE function eliminates the coupling relationship between two files.
Other Functions
The CVOLSER function prints the ADABAS file extents that are contained on a disk volume
specified by its volume serial number.
The DELCP function deletes checkpoint information recorded up to and including a specified
date; checkpoint information recorded after the date specified is not deleted. After running
ADADBS DELCP, the remaining records are reassigned ISNs to include those ISNs made
available when the checkpoint records were deleted. The lower ISNs are assigned but the
chronological order of checkpoints is maintained.
Utilities
The OPERCOM function issues operator commands to the ADABAS nucleus. ADABAS issues
a message to the operator, confirming command execution. Only the update ADABAS nucleus
(NUC01) running in an ADASMP multiprocessing or an ADAPLEX+ nucleus cluster is allowed
to run ADABAS utilities such as ADADBS. The optional SMPID or PLXID parameter,
respectively, allows you to redirect the OPERCOM commands to another (read-only) nucleus
in the cluster for execution, just as though the command had been issued by a locally run
ADADBS OPERCOM operation.
The PRIORITY function sets or changes the ADABAS priority of a user. A user’s priority can
range from 0 (the lowest) to 255 (the highest, and the default). The priority value is added to
the operating system priority by the interregion communications mechanism. The user for
which a priority is to be set or changed is identified by the same user ID provided in the
ADABAS Control Block (OP command, Additions 1 field).
The RECOVER function recovers space allocated by rebuilding the Free Space Table (FST).
RECOVER subtracts file, DSST, and alternate RABN extents from the total available space.
The REFRESHSTATS function resets statistical values maintained by the ADABAS nucleus for
its current session. Parameters may be used to restrict the function to particular groups of
statistical values:
ALL (the default) resets values for the combination of CMDUSAGE, COUNTERS,
FILEUSAGE, POOLUSAGE, and THREADUSAGE.
CMDUSAGE resets the counters for ADABAS direct call commands such as Lx, Sx, or A1.
COUNTERS resets the counter fields for local or remote, physical or logical calls, ADABAS
STAR calls, format translations, format overwrites, autorestarts, protection log switches, buffer
flushes, and command throw-backs.
FILEUSAGE resets the count of commands for each file.
POOLUSAGE resets the high-water marks for the nucleus pools such as the Work pool, the
Command Queue, or the User Queue.
THREADUSAGE resets the count of commands for each ADABAS thread.
ADABAS maintains a list of the files used by each ADABAS utility in the Data Integrity Block
(DIB). The DDIB operator command (or ADABAS ONLINE SYSTEM/Basic Services)
displays this block to determine which jobs are using which files. A utility removes its entry
from the DIB when it terminates normally. If a utility terminates abnormally (for example, the
job is cancelled by the operator), the files used by that utility remain “in use”. The RESETDIB
function releases any such files and resets the DIB entries for a specified job and/or a particular
utility execution.
ADABAS Concepts and Facilities
ADADEF : Define a Database
The ADADEF utility is used to define a new database, including the Checkpoint file, or to define
a new Work file (NEWWORK function) for an existing database.
Databases are defined with name, ID, components (Associator, Data Storage, and Work) with
device type and size.
ADABAS uses certain files to store system information. The Checkpoint file is used to store
checkpoint data as well as user data provided with the ADABAS CL and ET commands. It is
required and must be specified in the ADADEF DEFINE (database) function.
Before database components (Associator, Data Storage, and Work) can be defined with
ADADEF, each must be formatted by the ADAFRM utility.
ADAFRM : Format Datasets
The ADAFRM utility formats the ADABAS direct access (DASD) datasets; that is, the
Associator, Data Storage, and Work datasets as well as the intermediate storage (Temp, Sort,
and command/dual protection/recovery logging) datasets.
Formatting with ADAFRM comprises two basic operations: creating blocks (that is, RABNs)
on the specified tracks/cylinders; and filling the created blocks with binary zeros (nulls).
Any new dataset must be formatted before it can be used by the ADABAS nucleus or an
ADABAS utility. After increasing a dataset with the ADADBS INCREASE or ADD function,
new RABNs must also be formatted.
ADAFRM also provides functions to “reset” existing Associator, Data Storage, or Work blocks
to binary zeros (nulls).
More than one ADAFRM function (ASSOFRM, DATAFRM, RLOGFRM, and so on) can be
performed in the same job. However, each function must be specified on separate statements.
Utilities
ADAINV : Invert
The ADAINV utility is used to
create a descriptor (INVERT function); or
couple two files (COUPLE function).
The INVERT function
modifies the Field Definition Table (FDT) to indicate that the specified field is a descriptor; and
adds all values and corresponding ISN lists for the field to the inverted list.
The newly defined descriptor may then be used in the same manner as any other descriptor. This
function may also be used to create a subdescriptor, superdescriptor, phonetic descriptor, or
hyperdescriptor.
The COUPLE function adds a common descriptor to two files (updates their inverted lists). Any
two files may be coupled provided that a common descriptor with identical format and length
definitions is present in both files. A single file may be coupled with up to 18 other files, but
only one coupling relationship may exist between any two files at any one time. A file may not
be coupled to itself.
Note:
Only files with numbers 255 or lower can be coupled.
Changes affecting a coupled file’s inverted lists are automatically made to the other file. The
DBA should consider the additional overhead required to update the coupling lists when the
descriptor used as the basis for coupling is updated, or when records are added to or deleted from
either file. For example, if a field used as the basis for coupling contains a large number of null
values and is not defined with the NU (null suppression) option, the result may be a significant
increase in execution time and required disk space to store the coupling lists.
An interrupted ADAINV operation can be restarted without first having to restore the file.
ADABAS Concepts and Facilities
ADAORD : Reorder
Three types of functions are available within the ADAORD utility; only one function may be
executed during a given execution of ADAORD.
Reorder Functions
The REORASSO function physically reorders all Associator blocks for all files; REORFASSO
reorders the Associator for a single file. This eliminates Associator space fragmentation, and
combines multiple Address Converter, Normal and Upper Index, and Data Storage Space Table
(DSST) component extents into a single logical extent for each component.
The REORDATA function reorders Data Storage for all files in the database; REORFDATA
reorders Data Storage for a single file. This condenses extents containing only empty blocks,
and also eliminates any Data Storage fragmentation caused by file deletion.
The REORDB function performs both the REORASSO and REORDATA functions in a single
ADAORD execution; the REORFILE function performs both the REORFASSO and
REORFDATA functions in a single ADAORD execution. The records may be reordered in the
logical sequence by a descriptor, by ISN, or in the current sequence.
Restructure Functions
The RESTURCTURE functions are used to relocate a database or specified files to a different
physical device.The RESTRUCTUREDB function unloads an entire database to a sequential dataset;
RESTRUCTUREF unloads one or more files to a sequential dataset. This dataset can be used
as input to the STORE function.
Store Function
The STORE function loads one or more files into an existing database using the output produced
by the RESTRUCTURE functions or the REORDB function.
Utilities
Audit / Control / Tuning Procedures
ADAACK : Check Address Converter
ADAACK should only be used for diagnostic purposes. It checks
the Address Converter for a specified file(s) and ISN range. It is used in conjunction with
ADAICK.
each Address Converter element to determine whether the Data Storage RABN is within the
used portion of the Data Storage extents specified in the File Control Block.
the ISN for each record in each Data Storage block within the specified ISN range to ensure that
the Address Converter element for that ISN contains the correct Data Storage RABN.
ADADCK : Check Data Storage
ADADCK should only be used for diagnostic purposes. It checks the Data Storage and the Data
Storage Space Table (DSST) of a specific file (or files) in the database.
ADADCK reads each used Data Storage block (according to the Data Storage extents in the File
Control Block) and checks whether:
the block length is within the permitted range (4 block length physical block size).
the sum of the lengths of all records in the Data Storage block plus 4 equals the block length.
any record exists with a record length greater than the maximum compressed record length for
the file or with a length 0.
any duplicate ISNs exist within one block.
the associated DSST element contains the correct value. If not, the DSST must be repaired (see
REPAIR parameter).
ADABAS Concepts and Facilities
ADAICK : Check Index and Address Converter
ADAICK should only be used for diagnostic purposes. It checks the physical structure of the
Associator. This includes validating the index based upon the descriptor value structures and
the Associator extents defined by the General Control Block (GCB) and File Control Block
(FCB).
ADAICK can
check index and Address Converter for specific files;
print/dump the contents of any Associator or Data Storage block in the database; or
produce a formatted print/dump of the contents of the GCB, FCBs, and FDTs.
ADAMER : ADAM Estimation
The ADAMER utility produces statistics that indicate the number of Data Storage accesses
required to find and read a record when using an ADAM descriptor. This information is used
to determine
whether the number of accesses required to retrieve a record using an ADAM descriptor would
be less than the standard ADABAS accessing method;
the amount of Data Storage space required to produce an optimum distribution of records based
on the randomization of the ADAM descriptor.
The input data for ADAMER is a dataset containing the compressed records of a file produced
by the ADACMP or ADAULD utility.
The field to be used as the ADAM descriptor is specified with the ADAMDE parameter. A
multiple value field or a field contained within a periodic group may not be used. The ISN
assigned to the record may be used instead of a descriptor as the basis for randomization
(ADAMDE=ISN).
The ADAM descriptor must contain a different value in each record, since the file cannot be
successfully loaded with the ADAM option of the ADALOD utility if duplicate values are
present for the ADAM descriptor. The ADAMER utility requires a descriptor field defined as
unique (UQ), but does not check for unique values; checking for unique descriptor values is done
by the ADALOD utility when loading the file as an ADAM file.
Utilities
The BITRANGE parameter may be used to specify that a given number of bits are to be
truncated from each ADAM descriptor value before the value is used as input to the
randomization algorithm. This permits records containing ADAM descriptor values beginning
with the same value (for example, 40643210, 40643220, 40643344) to be loaded into the same
physical block in Data Storage. This technique can be used to optimize sequential reading of
the file when using the ADAM descriptor to control the read sequence, or to remove
insignificant information such as a check digit.
ADAREP : Report
The ADAREP utility produces the database status report, which provides information
concerning the current physical layout and logical contents of the database.
The information provided in this report includes
a database overview: the database name, number, creation date/time, file status, and current log
number.
current space resources for Associator, Data Storage, and Work: amount and locations of
currently used space, allocated but unused space, and alternate RABN blocks.
summary and detailed file information: summary by file of ISN, extent, padding factor,
used/unused Associator and Data Storage space, and file options; and detailed, optionally by
file, that includes all summary information plus MINISN/MAXISN settings, detailed space
information, creation and last use date/time, Field Definition Table (FDT) contents, and general
or extended Checkpoint file information.
checkpoint information: general and extended Checkpoint file information.
physical structure: Associator/Data Storage RABN information including device type,
VOLSER number, file number (if appropriate), and usage (AC, NI/UI, Data Storage, DSST,
alternate, or unused).
ADABAS Concepts and Facilities
ADAVAL : Validate the Database
The ADAVAL utility validates any or all files within an ADABAS database except the
Checkpoint and Security files.
ADAVAL compares the actual descriptor values contained in the records in Data Storage with
the corresponding values stored in the Associator to ensure that the Associator and Data Storage
are synchronized, and that there are no values missing from the Associator.
Before running ADAVAL, the consistency of the inverted lists should be checked with the
ADAICK utility.
ADAPRI : Print Selected ADABAS Blocks
The ADAPRI utility prints the contents of a block (or range of blocks) contained in the
Associator, Data Storage, Work, Temp, Sort, dual command log (CLOG), dual data protection
log (PLOG), the recovery log (RLOG), or the DELTA SAVE images (DSIM) dataset.
ADABAS UTILITIES
Database services such as loading or deleting files are handled by an integrated set of online and
batch-mode “utilities”. Most utilities can be run in parallel with normal database activity to
preclude interruption of daily production. See the ADABAS Utilities Manual for more
information.
ADABAS utilities address initial design and load operations, backup/restore/recovery routines,
database modification routines, and audit/control/tuning procedures.
Note:
See the Optional Extensions chapter starting on page 71 for information about ADABAS
ONLINE SYSTEM/Basic Services, a menu-driven, interactive DBA tool.
Initial Design and Load Operations
ADACMP : Compress / Decompress
ADACMP COMPRESS is used to edit and compress data records to be loaded into the database
using ADALOD; ADACMP DECOMPRESS is used to decompress individual files for data
structure or field definition changes, or for use as input to non-ADABAS programs.
COMPRESS
Input
ADACMP input data must be in a sequential dataset/file. Indexed sequential and VSAM input
cannot be used. The records may be fixed, variable, or of undefined length. The maximum input
record length permitted depends on the operating system. The maximum compressed record
length is restricted by the Data Storage block size in use and the maximum compressed record
length set for the file (see the MAXRECL parameter, ADALOD utility). The input records can
be in either blocked or unblocked format.
It is possible to omit the input dataset if the parameter NUMREC=0 is supplied.
ADABAS Concepts and Facilities
The logical structure and characteristics of the data for input to COMPRESS are described with
field definitions statements (FNDEF to define fields or groups of fields; SUBFN and SUPFN
to define sub- or superfields, respectively; HYPDE, PHONDE, SUBDE, and SUPDE to define
various types of descriptors). Field definitions are used to create the ADABAS Field Definition
Table (FDT).
By default, input data records are processed in the order of the field definition statements. The
FORMAT parameter allows you to change the order of field processing or skip fields.
Processing
ADACMP COMPRESS edits and compresses the data records.
Editing includes checking each field defined with a “packed” (P) or “unpacked” (U) format to
ensure that the field value is numeric and in the correct format. Any record that contains invalid
data is written to the ADACMP error dataset and is not written to the compressed dataset.
ADABAS user exit 6 can be used to specify additional editing to be performed during ADACMP
COMPRESS processing. See the ADABAS DBA Reference Manual for information about user
exits.
Compression includes removing trailing blanks from alphanumeric fields; removing leading
zeros from numeric fields; removing trailing zeros in floating-point format fields; and packing
numeric unpacked fields. Fields with the fixed (FI) option are not compressed, and empty fields
located at the end of the record are neither stored nor compressed. Null value fields are processed
differently depending on options being used. SQL null value processing is supported.
Output
Processed data records are written out together with the file definition information to a
sequential dataset with the “variable blocked” record format. This dataset, or several such
datasets from multiple ADACMP executions, can be used as input to the ADALOD utility. The
dataset can be used as input to ADALOD even if it contains no records, meaning that no records
were provided on the input dataset or all records were rejected during editing.
The ADACMP processing report indicates the approximate amount of space required in Data
Storage for the compressed records by device type (specified with the DEVICE parameter) and
for Data Storage padding factors between 5 and 30 percent. The compression rate is computed
based on the real amount of data used as input to the compression routine.
Utilities 4
51
DECOMPRESS
ADACMP DECOMPRESS accepts as input data records from existing ADABAS files, either
directly without separate file unloading, or already unloaded with the ADAULD utility. If a file
is directly decompressed, it is unloaded without FDT information as part of the decomperssion
process, which can save time when decompressing larger files.
Direct decompression of multiclient files can be limited to records for a specific user only when
a valid owner ID (ETID parameter) is specified.
The FORMAT parameter may be used to decompress the record to a format other than that
specified by the FDT. This is particularly useful when the FDT of an existing file is to be
changed.
Processed data records are written to a sequential dataset with the “variable blocked” record
format. Rejected data records are written to the error dataset.
ADALOD : Loader
The ADALOD LOAD function loads a file into the database. Compressed records produced by
the ADACMP or ADAULD utility may be used as input.
ADALOD loads each compressed record into Data Storage, builds the Address Converter for
the file, and enters the field definitions for the file into the Field Definition Table (FDT).
ADALOD also extracts the values for all descriptors in the file together with the ISNs of all
records in which the value is present, to an intermediate dataset. This dataset is then sorted into
value/ISN sequence and entered into the Associator inverted lists.
The ADALOD UPDATE function is used to add or delete a large number of records to/from an
ADABAS file. The UPDATE function requires considerably less processing time than the
repetitive execution of the ADABAS add/delete record commands. Records to be added may
be the compressed records produced by the ADACMP or ADAULD utility. The ISNs of records
to be deleted can be provided either in an input dataset or by using control statements.
Records may be added and other records deleted during a single execution of ADALOD.
ADABAS Concepts and Facilities
ADAULD : Unload
The ADAULD utility unloads an ADABAS file. ADABAS files are unloaded to
permit the data to be processed by a non-ADABAS program. In this case, the file must also be
decompressed after unloading using the DECOMPRESS function of the ADACMP utility.
create one or more test files, all of which contain the same data. This procedure requires that
a file be unloaded, and then reloaded as a test file with a different file number.
change the Field Definition Table (FDT). This requires that the file be unloaded, decompressed,
compressed using the modified field definitions, and reloaded. If the ADADBS utility is used
to add field definitions to a file, the file does not need to be unloaded first.
The sequence in which the records are unloaded may be
physical the order in which they are physically positioned within Data Storage.
logical a sequence controlled by the values of a user-specified descriptor.
ISN ascending ISN sequence.
The unloaded record output is in compressed format. The output records have the same format
as the records produced by the ADACMP utility.
Utilities
Backup / Restore / Recovery Routines
ADAPLP : Protection Log / Work Print
The ADAPLP utility prints data protection records contained on the ADABAS Work dataset or
the ADABAS data protection log. You can specify whether to print
ALL all protection records—the default
ASSO just Associator protection records
DATA just Data Storage protection records
C1 records resulting from ADABAS C1 commands
C5 records resulting from ADABAS C5 commands
EEKZ records written at completion of a nucleus buffer flush
ET records resulting from ADABAS ET commands
REPR Work dataset records used by Autorestart to repair the index
SAVO records resulting from online SAVE database/file operations
VEKZ records written at completion of update commands
The number of protection records printed can be reduced even more by specifying a file, ISN,
or RABN.
ADARAI : Recovery Aid
The ADABAS Recovery Aid utility ADARAI can be used to automate and optimize database
recovery. See also the restart/recovery information in the ADABAS Operations Manual.
ADARAI supports all ADABAS-compatible tape management systems.
The ADARAI utility prepares the recovery log files (RLOGs), lists the information contained
in the RLOGs, creates the job control statements to recover the database, and disables ADARAI
logging.
The RLOGs record the information about datasets, utility parameters, and protection logs
needed to build the recovery job control statements. There are two RLOGs: the primary file
(DDRLOGR1 or RLOGR1) and a mirror file (DDRLOGM1 or RLOGM1). The mirror file must
always exist; it can be used to recover the database if the primary file is not accessible.
ADABAS Concepts and Facilities 4
54
Information is stored on the RLOG by generations. A “generation” includes all activity between
consecutive ADASAV SAVE/RESTORE (database) and/or RESTORE GCB operations. The
first generation includes the first ADASAV SAVE/RESTORE (database) or RESTORE GCB
operation and extends to (but excludes) the second.
Minimally, the RLOG retains the number of generations specified by the MINGENS parameter
during the ADARAI PREPARE step. However, a maximum of 32 generations will be stored on
the RLOG if there is enough space available.
Systems using the Recovery Aid feature require a formatted recovery log (RLOG) dataset pair
(normal and mirrored), which must first be formatted with the ADAFRM utility and then
defined using the ADARAI utility.
ADARES : Restart
The ADARES utility performs functions related to database recovery:
BACKOUT removes all the updates applied between two checkpoints. The checkpoints used
are normally the result of a non-synchronized checkpoint command (C1) but may also be
synchronized checkpoints. The complete database may be included in the backout process, or
backout may be limited to selected files.
CLCOPY copies a command log dataset from disk to a sequential dataset. This function is
necessary only if dual command logging is in effect for an ADABAS session.
COPY copies a sequential ADABAS protection log dataset. This function should be executed
if the ADABAS session in which the sequential protection log dataset was created was
terminated abnormally.
PLCOPY copies a protection log dataset from disk to a sequential dataset. This function is
necessary only if dual protection logging is in effect for an ADABAS session.
REGENERATE reapplies all the updates performed between two user-specified checkpoints.
The checkpoints specified may be the result of a non-synchronized checkpoint command (C1)
but may also be synchronized checkpoints. The REGENERATE function may process all files
or be limited to one or more files. It is most often used after the database (or one or more files)
has been restored to a previous status with the RESTORE or RESTONL function of the
ADASAV utility.
REPAIR repairs one or more blocks in Data Storage that, for any reason, have become unusable.
The most recent save tape of the database and any protection log tapes created thereafter are used
as input to this function.
Utilities
ADASAV : Save / Restore Database or Files
The ADASAV utility saves and restores the contents of the database, or one or more files, to or
from a sequential dataset. ADASAV should be run as often as required for the number and size
of the files contained in the database, and the amount and type of updating. For large databases,
ADASAV functions may be run in parallel for the various disk packs on which the database is
contained.
Special ADASAV functions are available for use with the ADABAS DELTA SAVE FACILITY.
For more information, see the ADABAS DELTA SAVE FACILITY Manual.
RESTONL functions restore from a SAVE dataset created while the ADABAS nucleus was
active (that is, online); RESTORE functions restore from a SAVE dataset created while the
ADABAS nucleus was inactive (that is, offline).
RESTONL and RESTORE have the subfunctions GCB, FILES, and FMOVE:
Without a subfunction, RESTONL and RESTORE restore entire databases.
With the GCB subfunction, they restore the General Control Block, Associator RABNs 2–30
of the database, and specified files.
With the FILES subfunction, they restore one or more files into an existing database to their
original RABNs.
With the FMOVE subfunction, they restore one or more files into an existing database to any
free space, allowing changes to extent sizes.
If changes occurred during the online SAVE, the RESTONL function is followed automatically
by the RESTPLOG function. RESTPLOG applies the updates that occurred during, and
therefore were not included in, the online SAVE.
RESTPLOG is also executed following a RESTONL or RESTONL FILES function that ended
before the protection log (PLOG) updates were completely restored. RESTPLOG applies the
database updates not applied by the unsuccessful RESTONL function.
The SAVE function to save a database or one or more files may be executed while the ADABAS
nucleus is active (online) or inactive (offline). If the Recovery Aid option is active, a SAVE
database operation begins a new RLOG generation.
ADABAS Concepts and Facilities
ADASEL : Select Protection Data
The ADASEL utility selects information in the ADABAS sequential (SIBA) or dual (PLOG)
protection log. ADASEL decompresses the information and writes it to a print dataset
(DDDRUCK or DRUCK) or to a user-specified output dataset.
The protection log contains information on all updates applied to the database during a given
ADABAS session. Information selected by ADASEL can be used for auditing or as input to a
NATURAL or non-ADABAS program.
You can select before-images, after-images, or both for new, updated, and deleted records. You
can also select data written to the protection log by an ADABAS C5 command.
Database Modification Routines
ADADBS : Database Services
All ADADBS functions can also be performed using ADABAS ONLINE SYSTEM/Basic
Services. When the ADABAS Recovery Aid is active, using Basic Services is preferable for file
change operations because it writes checkpoints that are necessary for recovery operation.
ADADBS offers a variety of functions, any number of which may be performed during a single
execution of the utility.
Database Functions
The ADD function adds a new dataset to the Associator or Data Storage. The dataset to be added
may be on a device type that is the same as that currently being used or different. A maximum
of five datasets each may be assigned to the Associator and Data Storage.
The DECREASE function decreases the size of the last dataset currently being used for
Associator or Data Storage. The space to be released must be available in the Free Space Table
(FST).
The DECREASE function does not deallocate any of the specified physical extent space. To
deallocate space, you must decrease the database with the DECREASE function; save it with
ADASAV SAVE; reformat the datasets with ADAFRM; and restore the database with ADASAV.
Utilities
The INCREASE function increases the size of the last dataset currently being used for the
Associator or Data Storage. This function may be executed any number of times for the
Associator. The maximum of five Data Storage Space Tables (DSSTs) limits Data Storage
increases to four before all five Data Storage extents must be combined into a single extent with
either the REORASSO or REORDB function of the ADAORD utility.
The NEWALTS function assigns additional alternate RABN blocks for the Associator or Data
Storage. Existing alternate RABN definitions cannot be changed with NEWALTS.
Alternate RABN blocks can be used in place of RABN blocks that are physically damaged. If
ADABAS detects that a write operation is not successful, ADABAS selects an alternate block
of the same type, and the data is written to it. This alternate RABN is then used in place of the
original block for all subsequent read and write operations.
The RENAME function changes the name assigned to a (file or) database. If a file is not
specified or is specified with file number zero, the database is renamed.
File Functions
The ALLOCATE function is used to allocate a logical extent (an Address Converter, Data
Storage, Normal or Upper Index) of a specific size. The DEALLOCATE function is used to
deallocate a logical extent. Only one extent may be allocated or deallocated per ADADBS
execution.
The CHANGE function changes the standard length of an ADABAS field. No modifications to
records in Data Storage are made by this function. The user is, therefore, responsible for
preventing references to the field that would cause invalid results because of an inconsistency
between the new standard length as defined to ADABAS and the actual number of bytes
contained in the record.
The DELETE function deletes an ADABAS file from the database. The file may not be coupled.
If an ADABAS expanded file is specified, the complete expanded file (the anchor and all
component files) is deleted. This function results in the deallocation of all logical extents
assigned to the file. The released space may be used for a new file or for a new extent of an
existing file.
The DSREUSE function determines, for a specified file, whether Data Storage blocks that
become free as a result of record deletion are reused. Block reuse is originally determined when
a file is loaded into the database with the ADALOD FILE function, or when the system file is
defined with the ADADEF DEFINE function. In both cases, block reuse defaults to “YES” if
not specified.
ADABAS Concepts and Facilities
The ISNREUSE function determines, for a specified file, whether ADABAS reuses the ISN of
a deleted record for a new record. If not, each new record is assigned the next higher unused ISN.
For a specified ADABAS file that is not a system file, the MODFCB function modifies
parameters such as file padding factors for the Associator or Data Storage; maximum size of
secondary logical extent allocations for Data Storage, Normal Index, and Upper Index;
maximum compressed record length permitted; and whether a user program is allowed to
perform a file refresh operation by issuing a special E1 command.
The NEWFIELD function adds one or more fields to a specified ADABAS file that is not a
system file. The new field definition is added to the end of the Field Description Table (FDT).
NEWFIELD cannot be used to specify actual Data Storage data for the new field; the data can
be specified later using ADABAS add or update commands, or NATURAL commands.
The REFRESH function sets the file to “0” records loaded; sets the first extent for the Address
Converter, Data Storage, Normal Index, and Upper Index to “empty” status; and deallocates
other extents.
The RELEASE function releases a descriptor from descriptor status. All space currently
occupied in the Associator inverted list for this descriptor is released. The space can then be
reused for this file by reordering or by ADALOD UPDATE. No changes are made to Data
Storage.
The RENAME function changes the name assigned to a file or database. If a file is not specified
or is specified with file number zero, the database is renamed.
The RENUMBER function changes the number of an ADABAS file that is not a system file.
If the new number specified is already assigned to another file, the RENUMBER function will
not execute.
The UNCOUPLE function eliminates the coupling relationship between two files.
Other Functions
The CVOLSER function prints the ADABAS file extents that are contained on a disk volume
specified by its volume serial number.
The DELCP function deletes checkpoint information recorded up to and including a specified
date; checkpoint information recorded after the date specified is not deleted. After running
ADADBS DELCP, the remaining records are reassigned ISNs to include those ISNs made
available when the checkpoint records were deleted. The lower ISNs are assigned but the
chronological order of checkpoints is maintained.
Utilities
The OPERCOM function issues operator commands to the ADABAS nucleus. ADABAS issues
a message to the operator, confirming command execution. Only the update ADABAS nucleus
(NUC01) running in an ADASMP multiprocessing or an ADAPLEX+ nucleus cluster is allowed
to run ADABAS utilities such as ADADBS. The optional SMPID or PLXID parameter,
respectively, allows you to redirect the OPERCOM commands to another (read-only) nucleus
in the cluster for execution, just as though the command had been issued by a locally run
ADADBS OPERCOM operation.
The PRIORITY function sets or changes the ADABAS priority of a user. A user’s priority can
range from 0 (the lowest) to 255 (the highest, and the default). The priority value is added to
the operating system priority by the interregion communications mechanism. The user for
which a priority is to be set or changed is identified by the same user ID provided in the
ADABAS Control Block (OP command, Additions 1 field).
The RECOVER function recovers space allocated by rebuilding the Free Space Table (FST).
RECOVER subtracts file, DSST, and alternate RABN extents from the total available space.
The REFRESHSTATS function resets statistical values maintained by the ADABAS nucleus for
its current session. Parameters may be used to restrict the function to particular groups of
statistical values:
ALL (the default) resets values for the combination of CMDUSAGE, COUNTERS,
FILEUSAGE, POOLUSAGE, and THREADUSAGE.
CMDUSAGE resets the counters for ADABAS direct call commands such as Lx, Sx, or A1.
COUNTERS resets the counter fields for local or remote, physical or logical calls, ADABAS
STAR calls, format translations, format overwrites, autorestarts, protection log switches, buffer
flushes, and command throw-backs.
FILEUSAGE resets the count of commands for each file.
POOLUSAGE resets the high-water marks for the nucleus pools such as the Work pool, the
Command Queue, or the User Queue.
THREADUSAGE resets the count of commands for each ADABAS thread.
ADABAS maintains a list of the files used by each ADABAS utility in the Data Integrity Block
(DIB). The DDIB operator command (or ADABAS ONLINE SYSTEM/Basic Services)
displays this block to determine which jobs are using which files. A utility removes its entry
from the DIB when it terminates normally. If a utility terminates abnormally (for example, the
job is cancelled by the operator), the files used by that utility remain “in use”. The RESETDIB
function releases any such files and resets the DIB entries for a specified job and/or a particular
utility execution.
ADABAS Concepts and Facilities
ADADEF : Define a Database
The ADADEF utility is used to define a new database, including the Checkpoint file, or to define
a new Work file (NEWWORK function) for an existing database.
Databases are defined with name, ID, components (Associator, Data Storage, and Work) with
device type and size.
ADABAS uses certain files to store system information. The Checkpoint file is used to store
checkpoint data as well as user data provided with the ADABAS CL and ET commands. It is
required and must be specified in the ADADEF DEFINE (database) function.
Before database components (Associator, Data Storage, and Work) can be defined with
ADADEF, each must be formatted by the ADAFRM utility.
ADAFRM : Format Datasets
The ADAFRM utility formats the ADABAS direct access (DASD) datasets; that is, the
Associator, Data Storage, and Work datasets as well as the intermediate storage (Temp, Sort,
and command/dual protection/recovery logging) datasets.
Formatting with ADAFRM comprises two basic operations: creating blocks (that is, RABNs)
on the specified tracks/cylinders; and filling the created blocks with binary zeros (nulls).
Any new dataset must be formatted before it can be used by the ADABAS nucleus or an
ADABAS utility. After increasing a dataset with the ADADBS INCREASE or ADD function,
new RABNs must also be formatted.
ADAFRM also provides functions to “reset” existing Associator, Data Storage, or Work blocks
to binary zeros (nulls).
More than one ADAFRM function (ASSOFRM, DATAFRM, RLOGFRM, and so on) can be
performed in the same job. However, each function must be specified on separate statements.
Utilities
ADAINV : Invert
The ADAINV utility is used to
create a descriptor (INVERT function); or
couple two files (COUPLE function).
The INVERT function
modifies the Field Definition Table (FDT) to indicate that the specified field is a descriptor; and
adds all values and corresponding ISN lists for the field to the inverted list.
The newly defined descriptor may then be used in the same manner as any other descriptor. This
function may also be used to create a subdescriptor, superdescriptor, phonetic descriptor, or
hyperdescriptor.
The COUPLE function adds a common descriptor to two files (updates their inverted lists). Any
two files may be coupled provided that a common descriptor with identical format and length
definitions is present in both files. A single file may be coupled with up to 18 other files, but
only one coupling relationship may exist between any two files at any one time. A file may not
be coupled to itself.
Note:
Only files with numbers 255 or lower can be coupled.
Changes affecting a coupled file’s inverted lists are automatically made to the other file. The
DBA should consider the additional overhead required to update the coupling lists when the
descriptor used as the basis for coupling is updated, or when records are added to or deleted from
either file. For example, if a field used as the basis for coupling contains a large number of null
values and is not defined with the NU (null suppression) option, the result may be a significant
increase in execution time and required disk space to store the coupling lists.
An interrupted ADAINV operation can be restarted without first having to restore the file.
ADABAS Concepts and Facilities
ADAORD : Reorder
Three types of functions are available within the ADAORD utility; only one function may be
executed during a given execution of ADAORD.
Reorder Functions
The REORASSO function physically reorders all Associator blocks for all files; REORFASSO
reorders the Associator for a single file. This eliminates Associator space fragmentation, and
combines multiple Address Converter, Normal and Upper Index, and Data Storage Space Table
(DSST) component extents into a single logical extent for each component.
The REORDATA function reorders Data Storage for all files in the database; REORFDATA
reorders Data Storage for a single file. This condenses extents containing only empty blocks,
and also eliminates any Data Storage fragmentation caused by file deletion.
The REORDB function performs both the REORASSO and REORDATA functions in a single
ADAORD execution; the REORFILE function performs both the REORFASSO and
REORFDATA functions in a single ADAORD execution. The records may be reordered in the
logical sequence by a descriptor, by ISN, or in the current sequence.
Restructure Functions
The RESTURCTURE functions are used to relocate a database or specified files to a different
physical device.The RESTRUCTUREDB function unloads an entire database to a sequential dataset;
RESTRUCTUREF unloads one or more files to a sequential dataset. This dataset can be used
as input to the STORE function.
Store Function
The STORE function loads one or more files into an existing database using the output produced
by the RESTRUCTURE functions or the REORDB function.
Utilities
Audit / Control / Tuning Procedures
ADAACK : Check Address Converter
ADAACK should only be used for diagnostic purposes. It checks
the Address Converter for a specified file(s) and ISN range. It is used in conjunction with
ADAICK.
each Address Converter element to determine whether the Data Storage RABN is within the
used portion of the Data Storage extents specified in the File Control Block.
the ISN for each record in each Data Storage block within the specified ISN range to ensure that
the Address Converter element for that ISN contains the correct Data Storage RABN.
ADADCK : Check Data Storage
ADADCK should only be used for diagnostic purposes. It checks the Data Storage and the Data
Storage Space Table (DSST) of a specific file (or files) in the database.
ADADCK reads each used Data Storage block (according to the Data Storage extents in the File
Control Block) and checks whether:
the block length is within the permitted range (4 block length physical block size).
the sum of the lengths of all records in the Data Storage block plus 4 equals the block length.
any record exists with a record length greater than the maximum compressed record length for
the file or with a length 0.
any duplicate ISNs exist within one block.
the associated DSST element contains the correct value. If not, the DSST must be repaired (see
REPAIR parameter).
ADABAS Concepts and Facilities
ADAICK : Check Index and Address Converter
ADAICK should only be used for diagnostic purposes. It checks the physical structure of the
Associator. This includes validating the index based upon the descriptor value structures and
the Associator extents defined by the General Control Block (GCB) and File Control Block
(FCB).
ADAICK can
check index and Address Converter for specific files;
print/dump the contents of any Associator or Data Storage block in the database; or
produce a formatted print/dump of the contents of the GCB, FCBs, and FDTs.
ADAMER : ADAM Estimation
The ADAMER utility produces statistics that indicate the number of Data Storage accesses
required to find and read a record when using an ADAM descriptor. This information is used
to determine
whether the number of accesses required to retrieve a record using an ADAM descriptor would
be less than the standard ADABAS accessing method;
the amount of Data Storage space required to produce an optimum distribution of records based
on the randomization of the ADAM descriptor.
The input data for ADAMER is a dataset containing the compressed records of a file produced
by the ADACMP or ADAULD utility.
The field to be used as the ADAM descriptor is specified with the ADAMDE parameter. A
multiple value field or a field contained within a periodic group may not be used. The ISN
assigned to the record may be used instead of a descriptor as the basis for randomization
(ADAMDE=ISN).
The ADAM descriptor must contain a different value in each record, since the file cannot be
successfully loaded with the ADAM option of the ADALOD utility if duplicate values are
present for the ADAM descriptor. The ADAMER utility requires a descriptor field defined as
unique (UQ), but does not check for unique values; checking for unique descriptor values is done
by the ADALOD utility when loading the file as an ADAM file.
Utilities
The BITRANGE parameter may be used to specify that a given number of bits are to be
truncated from each ADAM descriptor value before the value is used as input to the
randomization algorithm. This permits records containing ADAM descriptor values beginning
with the same value (for example, 40643210, 40643220, 40643344) to be loaded into the same
physical block in Data Storage. This technique can be used to optimize sequential reading of
the file when using the ADAM descriptor to control the read sequence, or to remove
insignificant information such as a check digit.
ADAREP : Report
The ADAREP utility produces the database status report, which provides information
concerning the current physical layout and logical contents of the database.
The information provided in this report includes
a database overview: the database name, number, creation date/time, file status, and current log
number.
current space resources for Associator, Data Storage, and Work: amount and locations of
currently used space, allocated but unused space, and alternate RABN blocks.
summary and detailed file information: summary by file of ISN, extent, padding factor,
used/unused Associator and Data Storage space, and file options; and detailed, optionally by
file, that includes all summary information plus MINISN/MAXISN settings, detailed space
information, creation and last use date/time, Field Definition Table (FDT) contents, and general
or extended Checkpoint file information.
checkpoint information: general and extended Checkpoint file information.
physical structure: Associator/Data Storage RABN information including device type,
VOLSER number, file number (if appropriate), and usage (AC, NI/UI, Data Storage, DSST,
alternate, or unused).
ADABAS Concepts and Facilities
ADAVAL : Validate the Database
The ADAVAL utility validates any or all files within an ADABAS database except the
Checkpoint and Security files.
ADAVAL compares the actual descriptor values contained in the records in Data Storage with
the corresponding values stored in the Associator to ensure that the Associator and Data Storage
are synchronized, and that there are no values missing from the Associator.
Before running ADAVAL, the consistency of the inverted lists should be checked with the
ADAICK utility.
ADAPRI : Print Selected ADABAS Blocks
The ADAPRI utility prints the contents of a block (or range of blocks) contained in the
Associator, Data Storage, Work, Temp, Sort, dual command log (CLOG), dual data protection
log (PLOG), the recovery log (RLOG), or the DELTA SAVE images (DSIM) dataset.
posted by Perfect Bhawa at
6:34 AM
0 Comments:
Post a Comment
<< Home