This document gives an overview of the Adabas utilities, which provide all of the functions necessary to manage an Adabas database.


Backup and restore database or files

The Adabas backup utility dumps/restores the contents of the database (or a specific file or files) to/from a sequential data file. The utility can also be used to copy an Adabas backup copy.


Compression of data

The compression utility compresses user data. The compressed data is used as input for the mass update utility ADAMUP. The input for this utility is the raw data together with the data definitions that describe the structure of the data provided.


Database modification

The ADADBM utility consists of the following functions which can be used to make modifications to the database:

  • The ADD_CONTAINER function adds a new container file to the Associator or Data Storage data set;

  • The ADD_FIELDS function appends one or more new fields to the end of a file's FDT;

  • The ALLOCATE functions increase the Normal Index, Upper Index, Address Converter or Data Storage space assigned to a file. The DEALLOCATE functions are the inverse;

  • The CHANGE function changes the standard length of a field in the FDT;

  • The CHANGE_FIELDS function changes a field definition;

  • The DEFINE_REFINT function defines a new referential constraint;

  • The DELCP function deletes old checkpoint records from the checkpoint file in the specified range of dates;

  • The DELETE function deletes an Adabas file or a range of files from the database;

  • The DELETE_DATABASE function deletes a database. Depending on the keyword specified, either just the containers are deleted, or the database directory and its content are deleted.

  • The DISPLAY function displays the UCB;

  • The DROP_FIELDS function marks the specified fields as not existing, which means that they can no longer be accessed;

  • The DROP_LOBFILE function is the inverse function of ADAFDU ADD_LOBFILE;

  • The DROP_REFINT function drops an existing referential constraint;

  • The EXTEND_CONTAINER function extends the last container file defined for the database;

  • The NEW_DBID function changes the identifier of the database in use;

  • The NEWWORK function allocates and formats a new Adabas WORK data set;

  • The PGM_REFRESH function is used to disable or enable refreshing an Adabas file inside an application program with an E1 command;

  • The RECOVER function returns lost space to the FST;

  • The REDUCE_CONTAINER function reduces the size of the last container file defined for the database;

  • The REFRESH function resets a file or a range of files to the state of zero records loaded;

  • The REMOVE_CONTAINER function deletes a container file;

  • The REMOVE_DROP function, used in conjunction with a subsequent REFRESH, removes dropped fields from the FDT;

  • The REMOVE_REPLICATION function stops all replication processing and deletes the replication system files;

  • The RENAME function changes the database name or the name of a loaded file;

  • The RENUMBER function renumbers a loaded file or exchanges the numbers of loaded files;

  • The REPLICATION_FILES function creates the systems files required for Adabas - Adabas replication;

  • The RESET function removes entries from the UCB;

  • The RESET_REPLICATION_TARGET function resets the replication target flag of Adabas files;

  • The REUSE function controls the reuse of data storage space or ISNs by Adabas;

  • The SECURITY function sets the security mode of the database;

  • The SYFMAX function specifies the maximum number of values generated for a system generated multiple-value field in the file specified.


Decompression of data

The ADADCU utility decompresses records to be used with a non-Adabas application program, or as input for the compression utility ADACMP. The file to be decompressed must be unloaded from the database (unload utility ADAULD) before it can be used as input for this utility. With ADADCU, complete records can be decompressed, fields can be rearranged within a record, default lengths can be changed, some types of fields can be truncated, formats can be changed and space can be allocated for the addition of new fields.


File definition

The file definition utility ADAFDU defines a file in the database. It only loads the FCB and the FDT into the database and allocates the requested space for ASSO and DATA for the specified file.


File information report

The ADAFIN utility displays information about one or more files, e.g. FDT, descriptor statistics and the fill percentage of blocks in the Data Storage, Normal Index and Upper/Main Index.


Mass add and delete

The ADAMUP utility adds or deletes large numbers of records to/from a file in the database.


Operator utility

The operator utility is used to operate the Adabas nucleus.


Reorder database or files, export/import files

The reorder utility ADAORD provides functions to reorganize a database or files within a database (REORDER function) and to migrate files between databases (EXPORT and IMPORT functions).


Database report

The ADAREP utility produces the database status report. This report contains information about the current physical layout and logical contents of the database.

The information in this report includes the following: the amount and location of the space currently allocated for the Associator and Data Storage; the amount and location of unused space available for Associator and Data Storage; database file summary; checkpoint information; Security information; information about each file in the database (space allocation, space available, number of records loaded, MAXISN setting, field definitions).


File unloading

The unload utility ADAULD unloads a file from a database or an Adabas backup copy and produces compressed records with the same format as those produced by the compression utility ADACMP. Unloaded records may be used as input for the decompression utility ADADCU or with the mass update utility ADAMUP. Records can be unloaded from a database in the sequence in which they are currently stored in Data Storage, in the sequence of a descriptor or in ISN sequence. However, records can only be unloaded from a backup copy in the order in which they were stored by the utility.