
	Version 8.2.4	SEARCH INDEX CONTENTS \| PDF PAGE PDF BOOKS \| HOME UP PREV NEXT

— DBA Reference Summary —

Adabas Utilities

Utility Function	Use to...
ADAACK ACCHECK	Check the address converter for a specific file or range of files or for a specific ISN or range of ISNs.
ADACDC	Produce a file containing the delta of all changes made to the database over the period covered by the input protection logs. You can also use this utility to produce a file that lists each individual insert and delete transaction made to the database over the period covered by the input protection logs (without producing a delta of these changes).
ADACMP COMPRESS	Edit and compress data records that are to be loaded into the database.
ADACMP DECOMPRESS	Decompress individual files in the Adabas database.
ADACNV CONVERT	Convert a database to higher Adabas version.
ADACNV REVERT	Revert a database to a lower Adabas version.
ADADBS ADD	Add a new data set to the Associator or Data Storage.
ADADBS ADDCLOG	Dynamically add a command log (CLOG) data set
ADADBS ADDPLOG	Dynamically add a protection log (PLOG) data set
ADADBS ALLOCATE	Allocate an extent of a specific size for an address converter, Data Storage, or normal or upper index.
ADADBS CHANGE	Change the standard length or format of a field.
ADADBS CVOLSER	Print the Adabas file extents on a given volume.
ADADBS DEALLOCATE	Deallocate a file extent for an address converter, Data Storage, or normal index or upper index.
ADADBS DECREASE	Decrease the size of the last data set currently being used for the Associator or Data Storage.
ADADBS DELCLOG	Dynamically delete a command log (CLOG) data set
ADADBS DELCP	Delete checkpoint records.
ADADBS DELDE	Logically delete descriptors.
ADADBS DELETE	Delete a file from a database.
ADADBS DELFN	Logically delete fields from a database file.
ADADBS DELPLOG	Dynamically delete a protection log (PLOG) data set
ADADBS DSREUSE	Activate or deactivate the reuse of Data Storage blocks for a file.
ADADBS ENCODEF	Change the file encoding of a file.
ADADBS EXPFILE	Insert or remove files in an expanded file chain.
ADADBS INCREASE	Increase the size of the last data set currently being used for the Associator or Data Storage.
ADADBS ISNREUSE	Reuse ISNs in a database.
ADADBS MODFCB	Modify various parameters for a non-system Adabas file.
ADADBS MUPEX	Set the maximum count for MU and PE fields in a database.
ADADBS NEWFIELD:	Add one or more fields to a file.
ADADBS ONLINVERT	Start an online invert process.
ADADBS ONLREORFASSO	Start an online process to reorder the Associator of specified files.
ADADBS ONLREORFDATA	Start an online process to reorder the Data Storage of specified files.
ADADBS ONLREORFILE	Start an online process to reorder the Associator and Data Storage of specified files.
ADADBS OPERCOM	Issue operator commands to the Adabas nucleus.
ADADBS PRIORITY	Set or change the Adabas priority of a user.
ADADBS REACTLOG	Reactivate command logging.
ADADBS RECORDSPANNING	Enable or disable record spanning for a file.
ADADBS RECOVER	Recover allocated space by rebuilding the free space table (FST).
ADADBS REFRESH	Set a file to empty status.
ADADBS REFRESHSTATS	Reset the statistical values maintained by the Adabas nucleus for its current session.
ADADBS RELEASE	Release a descriptor from the descriptor space.
ADADBS RENAME	Rename a file or database.
ADADBS RENUMBER	Change the number of a file in the database.
ADADBS REPLICATION	Activate or deactivate replication for an Adabas database file.
ADADBS REPTOR	Activate, deactivate, open, or close an Event Replicator for Adabas resource.
ADADBS RESETDIB	Reset entries in the active utility list.
ADADBS RESETPPT	Resets the PPT blocks on the Associator data set.
ADADBS SPANCOUNT	Count and display the number of records in a file that are spanned.
ADADBS TRANSACTIONS	Suspend and resume update transaction processing for the database.
ADADBS UNCOUPLE	Uncouple files in the database.
ADADBS UNDELDE	Undelete logically deleted descriptors.
ADADBS UNDELFN	Logically undelete fields from a database file.
ADADCK DSCHECK	Check Data Storage and the Data Storage space table (DSST) of specified files in the database.
ADADEF DEFINE	Define a database and checkpoint file.
ADADEF MODIFY	Change field encodings.
ADADEF NEWWORK	Define a Work file.
ADAFRM	Format Adabas database components.
ADAICK ACCHECK	Check the address converter of a specified database file.
ADAICK ASSOPRINT	Print and dump Associator blocks.
ADAICK BATCH	Set the printout width to 132 characters per line.
ADAICK DATAPRINT	Print and dump Data Storage blocks for specified RABNs.
ADAICK DSCHECK	Print and dump the content of Data Storage records in a file.
ADAICK DUMP	Request that blocks be printed in dump format.
ADAICK FCBPRINT	Print and dump the file control block (FCB) of a file.
ADAICK FDTPRINT	Print and dump the field definition table of a file.
ADAICK GCBPRINT	Print and dump the general control blocks (GCBs).
ADAICK ICHECK	Check the index against the address converter.
ADAICK INT	Request that blocks be printed in interpreted print format.
ADAICK NIPRINT	Print and dump the normal index for a file.
ADAICK NOBATCH	Set the print width to 80 characters per line.
ADAICK NODUMP	Suppress dump print format.
ADAICK NOINT	Suppress interpreted print format.
ADAICK PPTPRINT	Print and dump the parallel participant table (PPT).
ADAICK UIPRINT	Print and dump the upper index for a file.
ADAINV COUPLE	Define one descriptor for each of two files to be coupled.
ADAINV INVERT	Create descriptors, subdescriptors, superdescriptors, hyperdescriptors, phonetic descriptors or collation descriptors for existing fields in a file.
ADALOD LOAD	Load a file into the database.
ADALOD UPDATE	Add or delete a large number of records (ISNs) to or from an existing file.
ADAMER	Run the ADAM estimation. This utility produces statistics that indicate the number of Data Storage accesses required to find and read a record when using an ADAM descriptor.
ADAORD REORASSO	Reorder the Associator.
ADAORD REORDATA	Reorder Data Storage.
ADAORD REORDB	Reorder the database.
ADAORD REORFASSO	Reorder the Associator for a single file.
ADAORD REORFDATA	Reorder Data Storage for a single file.
ADAORD REORFILE	Reorder a file.
ADAORD RESTRUCTUREDB	Restructure the database.
ADAORD RESTRUCTUREF	Restructure single files.
ADAORD STORE: Store Files	Load one or more files into an existing database using output produced by the ADAORD RESTRUCTURE functions.
ADAPLP	Print data protection records from the protection log (PLOG) or Work data sets.
ADAPRI	Print the contents of a block (or range of blocks) contained in the Associator, Data Storage, Work, temp, sort, multiple data set command log, multiple data set protection log, or the recovery log data set.
ADARAI CHKDB	Check that the recovery status of the nucleus is the status specified by the CHKDB function (active or inactive).
ADARAI DISABLE	Disable recovery logging by setting the RLOG table (control block) to inactive status.
ADARAI LIST	View the recovery log contents in table form.
ADARAI PREPARE	Initialize and start recovery logging to the recovery log.
ADARAI RECOVER	Build a recovery job stream for recovering the Adabas database or selected database files.
ADARAI REMOVE	Disable recovery logging by updating the Associator GCBs to indicate that recovery logging (that is, the Recovery Aid) is no longer active in the database, and that information will no longer be recorded in the recover log (RLOG).
ADAREP	Request a database status report.
ADARES BACKOUT SIBA	Back out updates applied between two specified checkpoints using the sequential protection log (SIBA).
ADARES BACKOUT DPLOG or MPLOG	Back out updates applied between two checkpoints contained on the same dual or multiple protection log.
ADARES CLCOPY	Copy the dual command log.
ADARES COPY	Copy a sequential protection log or save tape.
ADARES MERGE CLOG	Merge nucleus cluster command logs.
ADARES PLCOPY	Copy protection log data to a sequential data set.
ADARES REGENERATE	Reapply all the updates performed between two checkpoints.
ADARES REPAIR	Repair one or more Data Storage blocks, using the protection log and the output of the ADASAV utility.
ADASAV RESTONL	Restore a database from a database SAVE data set created while the Adabas nucleus was active.
ADASAV RESTONL FILES	Restore files to their original RABNs in an existing database. Files are restored from a file or database SAVE data set created while the Adabas nucleus was active.
ADASAV RESTONL FMOVE	Restore files to any free space in an existing database. Files are restored from a file or database SAVE data set created while the Adabas nucleus was active.
ADASAV RESTONL GCB	Restore the general control blocks (GCBs), Associator RABNs 3-30 of the database, the checkpoint file, the security file (if present), and all specified files. These file structures are restored from a database SAVE data set created while the Adabas nucleus was active.
ADASAV RESTORE	Restore a database from a database SAVE data set created while the Adabas nucleus was inactive.
ADASAV RESTORE FILES	Restore files to their original RABNs in an existing database. Files are restored from a file or database SAVE data set created while the Adabas nucleus was inactive.
ADASAV RESTORE FMOVE	Restore files to any free space in an existing database. Files are restored from a file or database SAVE data set created while the Adabas nucleus was inactive.
ADASAV RESTORE GCB	Restore the general control blocks (GCBs), Associator RABNs 3-30 of the database, the checkpoint file, the security file (if present), and all specified files. These file structures are restored from a database SAVE data set created while the Adabas nucleus was inactive.
ADASAV RESTPLOG	Restore changes contained in the protection log (PLOG) to the already restored database or files.
ADASAV SAVE	Save the contents of the database to a sequential data set.
ADASAV SAVE FILES	Save the contents of one or more files to a sequential data set.
ADASEL	Select and decompress information in the Adabas sequential (SIBA) or dual/multiple (PLOG) protection log and write it to a print data set (DDDRUCK/ DRUCK) or a user-specified output data set.
ADAULD UNLOAD FILE	Unload a specified Adabas file.
ADAVAL	Validate any or all files within an Adabas database except the checkpoint and security files.
ADAWRK	Produce reports from records in the autorestart area of Work part 1. This information can be used when the database autostart fails and the database will not come up. It can help you determine how to handle database recovery.
ADAZAP	Display (in hexadecimal format) and optionally change the contents of the Associator, Data Storage, or Work data sets.
ADAZIN	Print Adabas maintenance and SVC information.
Field Definition Statements	Define or modify a field definition. Field definition statements can be specified in various Adabas utility functions.

ADAACK ACCHECK: Check Address Converter Against Data Storage

graphics/util_adaack_accheck.png

ADACDC: Capture Delta Changes

graphics/util_adacdc.png

ADACMP COMPRESS: Compress an Adabas File

graphics/util_adacmp_compress.png

ADACMP DECOMPRESS: Decompress Adabas Files

graphics/util_adacmp_decompress.png

Field Definition Statements

The following syntax must be followed when entering field definitions. A minimum of one and a maximum of 3214 definitions may be specified.

Statement Type	Syntax
Field and Group
Periodic Group
Collation descriptor
Hyperdescriptor
Phonetic descriptor
Subdescriptor
Subfield
Superdescriptor
Superfield

User comments may be entered to the right of each definition. At least one blank must be present between a definition and any user comments.

ADACNV CONVERT: Convert a Database to Higher Version

graphics/util_adacnv_convert.png

ADACNV REVERT: Revert a Database to Lower Version

graphics/util_adacnv_revert.png

ADADBS ADD: Add Data Set

graphics/util_adadbs_add.png

ADADBS ADDCLOG: Dynamically Add CLOG Data Sets

graphics/util_adadbs_addclog.png

ADADBS ADDPLOG: Dynamically Add PLOG Data Sets

graphics/util_adadbs_addplog.png

ADADBS ALLOCATE: Allocate File Extent

graphics/util_adadbs_allocate.png

ADADBS CHANGE: Change Standard Length or Format of a Field

graphics/util_adadbs_change.png

ADADBS CVOLSER: Print Adabas Extents on Given Volume

graphics/util_adadbs_cvolser.png

ADADBS DEALLOCATE: Deallocate File Extent

graphics/util_adadbs_deallocate.png

ADADBS DECREASE: Decrease Last Associator or Data Storage Data Set Size

graphics/util_adadbs_decrease.png

ADADBS DELCLOG: Dynamically Delete CLOG Data Sets

graphics/util_adadbs_delclog.png

ADADBS DELCP: Delete Checkpoint Records

graphics/util_adadbs_delcp.png

ADADBS DELDE: Logically Delete a Descriptor

graphics/util_adadbs_delde.png

ADADBS DELETE: Delete File

graphics/util_adadbs_delete.png

ADADBS DELFN: Logically Delete Fields

graphics/util_adadbs_delfn.png

ADADBS DELPLOG: Dynamically Delete PLOG Data Sets

graphics/util_adadbs_delplog.png

ADADBS DEVENTLOG: Display Adabas Event Log

graphics/util_adadbs_delplog.png

ADADBS DSREUSE: Reuse Data Storage Blocks

graphics/util_adadbs_dsreuse.png

ADADBS ENCODEF: Change File Encoding

graphics/util_adadbs_encodef.png

ADADBS EXPFILE: Insert or Remove Files in Expanded File Chains

graphics/util_adadbs_expfile.png

ADADBS INCREASE: Increase Last Associator or Data Storage Data Set Size

graphics/util_adadbs_increase.png

ADADBS ISNREUSE: Reuse ISNs

graphics/util_adadbs_isnreuse.png

ADADBS MODFCB: Modify File Parameters

graphics/util_adadbs_modfcb.png

ADADBS MUPEX: Set Maximum Count for MU and PE Fields

graphics/util_adadbs_mupex.png

ADADBS NEWFIELD: Add New Field

graphics/util_adadbs_newfield.png

ADADBS ONLINVERT: Start Online Invert Process

graphics/util_adadbs_onlinvert.png

ADADBS ONLREORFASSO: Start Online Reorder Associator for Files

graphics/util_adadbs_onlreorfasso.png

ADADBS ONLREORFDATA: Start Online Reorder Data for Files

graphics/util_adadbs_onlreorfdata.png

ADADBS ONLREORFILE: Start Online Reorder Associator and Data for Files

graphics/util_adadbs_onlreorfile.png

ADADBS OPERCOM: Issue Adabas Operator Commands

graphics/util_adadbs_opercom.png

Operator Commands Supported by ADADBS OPERCOM

The following Adabas operator commands can be used in the ADADBS OPERCOM utility function:

This command terminates an Adabas session normally. No new users are accepted after this command has been issued. ET logic updating is continued until the end of the current logical transaction for each user. After all activity has been completed as described above, the Adabas session is terminated.

In nucleus cluster environments, the GLOBAL option can be used to terminate the Adabas session in all active cluster nuclei.
Lock a file in advance to ensure that an EXU, EXF, or UTI user will have exclusive control of the specified file. The advance-lock prevents new transactions from using the file. Once all current users have stopped using the file, the exclusive-control user has the lock. Until then, the exclusive-control user must wait.

To remove the advance lock without running the utility, see the RALOCKF command.

This command is not available in single user mode or for a read-only nucleus. It is available in cluster and non-cluster environments.

The following key points should be noted about advance-locks on files:
1. An advance-lock can be set while a file is being used.
2. A command requesting exclusive control (UTI, EXF, or EXU) over an advance-locked file will wait in the command queue until all other users stop using the file before it starts processing the file.
3. Advance-locks are automatically removed when a user gets exclusive control over the file. However, if a file is locked (via the LOCKF, LOCKU, or LOCKX commands), the locks are not removed when a user gets exclusive control over the file. (Locks must be explicitly removed, whereas advance-locks are automatically removed.)
4. Adabas will reject an advance-lock on a file that is already locked (via the LOCKF, LOCKU, LOCKX or ALOCKF commands) but will accept a lock request on an advance-locked file.
5. To ensure you have uninterrupted exclusive control over a file in a situation where you have multiple steps to run that require uninterrupted exclusive control while all steps have been processed, use a combination of advance-locking the file (ALOCKF), stopping all users of the file (STOPF), and locking the file (LOCKU). An example of this is given later in this section.
6. In the case of expanded files, an ALOCKF command is applied to the anchor file (representing the entire expanded file chain).
7. In a cluster environment, advance-locks are effective in all nuclei of the cluster.
Simple Example

In the following example, issuing the ALOCKF request to advance-lock file 32 ensures that file 32 will be available so the ADALOD UPDATE function can take exclusive control (via a UTI request) of the file for its processing:
```
ADADBS OPERCOM ALOCKF=32
ADALOD UPDATE FILE=32
```
Adabas processing proceeds in the following manner for these utility functions:
1. When the ADADBS OPERCOM ALOCKF request is submitted, file 32 is marked as advance-locked.
2. If there are any active users of file 32, the ADALOD UTI request cannot be granted immediately and will wait for the active users to end their transactions or sessions. Active users continue to issue commands against file 32. However, requests by new users for file 32 are rejected because of the advance-lock on the file.
3. When all active users of file 32 have ended their transactions or sessions, the ADALOD UTI request for exclusive control can be granted. Once exclusive control is established, ADALOD UPDATE processing can occur.
  
  As part of the successful execution of the ADALOD UTI request, the advance-lock is removed from the file. However, because ADALOD processing now has exclusive control of file 32, other users still cannot access it.
To accelerate the process and limit the wait time for the ADALOD UTI request, you can simply stop all active users of the file by force using the STOPF operator command:
```
ADADBS OPERCOM ALOCKF=32
ADADBS OPERCOM STOPF=32
ADALOD UPDATE FILE=32
```
In this case, the STOPF command will cause the nucleus to back out and stop users of file 32 before the ADALOD UTI request is granted. In addition, the advance-lock request specified by the ALOCKF command will prevent new users from accessing the file until the ADALOD UTI request for exclusive control is processed.

More Complex Example

An advance-lock set by ALOCKF cannot guarantee that multiple job steps in a series get uninterrupted exclusive control over a file, as the advance-lock is removed when the first step obtains exclusive control. Suppose an installation wants to run the following utility sequence:
```
ADAULD UNLOAD FILE=45
ADADBS REFRESH FILE=45
ADALOD UPDATE FILE=45
```
An ALOCKF request to advance-lock file 45 in this case would only work for the ADAULD UNLOAD function, because the ADAULD EXU request for exclusive control of file 45 would remove the advance-lock. If there are active users who try to issue commands against file 45, there is a chance that one of them will execute a command between the UNLOAD and REFRESH steps, or between the REFRESH and UPDATE steps. Such a user may also prevent the REFRESH or UPDATE step from obtaining exclusive control of file 45.

To ensure you have uninterrupted exclusive control over the file in this situation, use a combination of advance-locking the file (ALOCKF), stopping all users of the file (STOPF), and locking the file (LOCKU):
```
ADADBS OPERCOM ALOCKF=45
ADADBS OPERCOM STOPF=45
ADADBS OPERCOM LOCKU=45
ADAULD UNLOAD FILE=45
ADADBS REFRESH FILE=45
ADALOD UPDATE FILE=45
ADADBS OPERCOM UNLOCKU=45
```
In this example, Adabas processing proceeds in the following manner:
1. When the ADADBS OPERCOM ALOCKF request is submitted, file 45 is marked as advance-locked.
  
  The ADADBS OPERCOM STOPF request causes the nucleus to back out and stop users of file 45. (This step is optional.)
  
  The ADADBS OPERCOM LOCKU request locks the file more permanently than the ALOCKF request since the LOCKU lock will stay in effect until it is explicitly released.
2. If there are any active users updating file 45, the ADAULD EXU request cannot be granted immediately and will wait for the update users to end their transactions or sessions. Active users may continue to issue commands against file 45. However, requests by new users for file 45 are rejected because of the advance-lock on the file.
3. When all active users of file 45 have ended their transactions or sessions, the ADAULD request for exclusive-update (EXU) control can be granted. Once exclusive-update control is established, ADAULD UNLOAD processing can occur.
  
  As part of the successful execution of the ADAULD EXU request, the advance-lock is removed from the file. When ADAULD completes processing, it releases the EXU control of file 45. However, during and after the ADAULD execution, the LOCKU lock ensures that other users still cannot access the file.
4. The ADADBS utility will issue a UTI request for exclusive control of file 45, which will be granted. ADADBS REFRESH processing will then occur. When it completes, ADADBS will release exclusive control of file 45. However, the LOCKU lock ensures that other users still cannot access it.
5. The ADALOD utility will issue a UTI request for exclusive control of file 45, which will be granted. ADALOD UPDATE processing will then occur. When it completes, ADALOD will release exclusive control of file 45. However, the LOCKU lock ensures that other users still cannot access it.
6. The ADADBS OPERCOM UNLOCKU request explicitly unlocks file 45, making it available for other users.
Cancel the Adabas session immediately. All command processing is immediately suspended. A pending autorestart is in effect which in turn causes the autorestart routine to be executed during the initialization of the next Adabas session.

In nucleus cluster environments, the GLOBAL option can be used to cancel the Adabas session in all active cluster nuclei.
Switches automatic command log merging (ADARUN CLOGMRG parameter value) on or off in nucleus cluster environments.

The CLOGMRG command is global by definition and affects all nuclei in the cluster. If a NUCID is specified, it is ignored.
Dynamically override the ADARUN CT parameter value; that is, the maximum number of seconds that can elapse from the time an Adabas command has been completed until the results are returned to the user through interregion communication (which depends on the particular operating system being used). The minimum setting is 1; the maximum is 16777215.

In nucleus cluster environments, the CT command is global by definition and affects all nuclei in the cluster. If a NUCID is specified, it is ignored.
Display the user queue element (UQE) of each user who has executed at least one Adabas command within the last 15 minutes.

In nucleus cluster environments, the NUCID=0 option can be used to display information for all active cluster nuclei. Information is displayed for each nucleus, one after the other.
Display all posted command queue elements (CQEs). Each CQE's user ID, job name, and buffer length is displayed.

In nucleus cluster environments, the NUCID=0 option can be used to display information for all active cluster nuclei. Information is displayed for each nucleus, one after the other.
Display data integrity block (DIB). This block contains entries indicating which Adabas utilities are active and the resources being used by each utility. The DDIB function can be performed with either an active or an inactive nucleus.

In nucleus cluster environments, the information displayed by the DDIB command is global; the command can be run on any nucleus.
Display Adabas Delta Save Facility Facility (DSF) status. The Adabas nucleus displays the DSF status on the operator console as well as in the ADADBS job protocol.

This function is only available if the nucleus is run with the parameter ADARUN DSF=YES.

In nucleus cluster environments, the information displayed by the DDSF command is global; the command can be run on any nucleus.
Displays the number of access, update, EXU, and UTI users for the specified files. User types are totaled for each file, and are listed by file. Up to five files can be specified in this command. Up to 798 users are displayed.

In nucleus cluster environments, the NUCID=0 option can be used to display information for all active cluster nuclei. Information is displayed for each nucleus, one after the other.
Displays the count of commands processed for the specified file so far during the current session.

In nucleus cluster environments, the NUCID=0 option can be used to display information for all active cluster nuclei. Information is displayed for each nucleus, one after the other.
Display up to 1000 hold queue elements.
Display locked files.

In nucleus cluster environments, the NUCID=0 option can be used to display information for all active cluster nuclei. Information is displayed for each nucleus, one after the other.
Display the number of posted command queue elements (CQEs) waiting to be selected.

In nucleus cluster environments, the NUCID=0 option can be used to display information for all active cluster nuclei. Information is displayed for each nucleus, one after the other.
Display the number of ISNs currently in the hold queue.

In nucleus cluster environments, the NUCID=0 option can be used to display information for all active cluster nuclei. Information is displayed for each nucleus, one after the other.
Display the number of current users.

In nucleus cluster environments, the NUCID=0 option can be used to display information for all active cluster nuclei. Information is displayed for each nucleus, one after the other.
Note:
Not currently available for use with Adabas Parallel Services cluster nuclei.

Display status of each active reorder or invert online process together with the process ID.

In nucleus cluster environments, the NUCID=0 option can be used to display information for all active cluster nuclei. Information is displayed for each nucleus, one after the other.
Display the Adabas session parameters currently in effect.

Note:
Additional Adabas add-on products and nucleus components will display additional parameters from those shown for a classic nucleus. For a sample of this report, please review the Adabas operator command documentation.
Display the allocated pool space and the highest use level ('high water mark') reached so far during the current session by record count and by percent for the following resources:
- attached buffers (AB)
- command queue (CQ)
- format pool (FP)
- hold queue (HQ)
- pool for the table of ISNs (TBI)
- pool for the table of sequential commands (TBQ or TBLES)
- user queue (UQ)
- unique descriptor pool (DUQPOOL)
- security pool
- user queue file list pool
- work pool (WP)
- pool for global transaction IDs (XIDs; nonzero only with Adabas Transaction Manager)
- cluster block update redo pool (nonzero only for a cluster nucleus with ADARUN LRDP greater than zero)
- Work part 1 area (WKP1)
  
  Note:
  The maximum pool value of Work part 1 is derived from the LP parameter. It corresponds to the maximum number of blocks a transaction can spend on Work Part 1 before Adabas decides to back it out.
- Work part 2 area (WKP2)
- Work part 3 area (WKP3)
The actual values are displayed in nucleus message ADAN28.
Display the current Adabas nucleus operating status.
Display thread status.
Display up to five active and inactive user queue elements.
Display all user queue elements (UQEs).

In nucleus cluster environments, the NUCID=0 option can be used to display information for all active cluster nuclei. Information is displayed for each nucleus, one after the other.
Display a user queue element for the specified Adabas-assigned user ID as follows:
```
DUQE=X'A3CF2'
```
The user ID must be entered in hexadecimal format. Do not use a job name for the user ID.

In nucleus cluster environments, NUCID must always be specified because the user ID is not unique to the cluster.
Display utility user queue elements (UQEs).

In nucleus cluster environments, the NUCID=0 option can be used to display information for all active cluster nuclei. Information is displayed for each nucleus, one after the other.
Close the current dual or multiple Command log and switch to the other dual or another multiple Command log. This command is valid only if dual or multiple command logging is in effect.

In nucleus cluster environments, the GLOBAL option can be used to switch the dual or multiple command log in all cluster nuclei at the same time.
Close the current dual or multiple data Protection log and switch to the other dual or another multiple Protection log. This command is valid only if dual or multiple data protection logging is in effect.

In nucleus cluster environments, the GLOBAL option can be used to switch the dual or multiple protection log in all cluster nuclei at the same time.
Stop Adabas session. A BT (backout transaction) command is issued for each active ET logic user. The Adabas session is then terminated; no dumps are produced.

In nucleus cluster environments, the GLOBAL option can be used to halt the Adabas session in all active cluster nuclei.
Lock the specified file. The specified file will be locked at all security levels.
Lock the specified file for all non-utility use. Adabas utilities can use the file normally.
Lock the specified file for all users except EXU or EXF users. EXU and EXF users can use the file normally. The lock is released automatically when an EXU user issues an OP command.
Start command logging.
Begin logging as indicated by xx for each command logged where xx is one of the following:
- CB - the Adabas control block
- FB - the Adabas format buffer
- IB - the Adabas ISN buffer
- IO - Adabas I/O activity
- RB - the Adabas record buffer
- SB - the Adabas search buffer
- UX - user data passed in the seventh parameter of the Adabas parameter list
- VB - the Adabas value buffer
- VOLIO - the extended I/O list for CLOGLAYOUT=5 and CLOGLAYOUT=8
Use the LOGWARN command to specify how often the PLOG and CLOG status is checked and resulting alert messages are produced. Valid values range from zero (0) through 2147483647 seconds. The default is 0, indicating that no PLOG or CLOG status checking occurs and no corresponding alert messages are produced. If a non-zero value is specified for LOGWARN, a valid user exit 2 or user exit 12 must also be specified.
Stop or prevent command logging.
Stop or prevent logging of xx where xx is one of the following:
- CB - the Adabas control block
- FB - the Adabas format buffer
- IB - the Adabas ISN buffer
- IO - Adabas I/O activity
- RB - the Adabas record buffer
- SB - the Adabas search buffer
- UX - user data passed in the seventh parameter of the Adabas parameter list
- VB - the Adabas value buffer
- VOLIO - the extended I/O list for CLOGLAYOUT=5 and CLOGLAYOUT=8
Note:
Not currently available for use with Adabas Parallel Services cluster nuclei.

Resume a previously suspended online reorder or invert process.

In a cluster environment, NUCID must always be specified because the online process ID is not unique to the cluster.
Note:
Not currently available for use with Adabas Parallel Services cluster nuclei.

Stop an online reorder or invert process cleanly. The process continues up to its next interrupt point in order to produce a consistent state, and then terminates after performing all necessary cleanup.

In a cluster environment, NUCID must always be specified because the online process ID is not unique to the cluster.
Note:
Not currently available for use with Adabas Parallel Services cluster nuclei.

Suspend an online reorder or invert process. The process continues up to its next interrupt point in order to produce a consistent state, performs a command throwback, and enters a state where it cannot be selected for processing. This command is useful if the online process is consuming too much of the nucleus resources.

In a cluster environment, NUCID must always be specified because the online process ID is not unique to the cluster.
Remove the advance lock on the specified file (see ALOCKF command) without running the utility.

This command is available in cluster and non-cluster environments.
Remove the advance lock on all files for which it has been set (see ALOCKF command) without running the utility.

This command is available in cluster and non-cluster environments.
Terminate online dump status. This command is normally used if online execution of the ADASAV utility has terminated abnormally.
Note:
Not currently available for use with Adabas Parallel Services cluster nuclei.

Switches READONLY status on or off.

In nucleus cluster environments, the READONLY command is global by definition and affects all nuclei in the cluster. If a NUCID is specified, it is ignored.
Note:
Not currently available for use with Adabas Parallel Services cluster nuclei.

Deactivate Adabas Review; change from hub mode to local mode; specify or change the Adabas Review hub with which a nucleus communicates.
Stop all users who are using the specified file. Any open transactions of the stopped users are backed out. Unless PURGE is also specified, a stopped user who returns (by sending a command) receives response code 9 (ADARSP009).

If the optional PURGE parameter is specified, the stopped users are also deleted (their user queue elements are removed from the user queue).

This command does not stop EXF or UTI users.

The following is an example of using the PURGE parameter:
```
ADADBS OPERCOM STOPF=5,PURGE
```
Caution:
If Adabas is running with ADARUN OPENRQ=NO (specifying that users are not required to issue an OP as the first command of the session), run the STOPF command with PURGE only if you are certain that the users to be deleted are no longer active. If a user with an open transaction is deleted, but then returns (by sending a command), no indication is given about the transaction backout. If the user continues the transaction, logical inconsistencies in the database could occur.
Stop all users who have not executed a command during the specified time interval (in seconds). Any open transactions of the stopped users are backed out. Unless PURGE is also specified, a stopped user who returns (by sending a command) receives response code 9 (ADARSP009).

This command does not stop EXF or UTI users.

If the optional PURGE parameter is specified, the stopped users are also deleted (their user queue elements are removed from the user queue).

The following is an example of using the PURGE parameter:
```
ADADBS OPERCOM STOPI=3600,PURGE
```
Caution:
If Adabas is running with ADARUN OPENRQ=NO (specifying that users are not required to issue an OP as the first command of the session), run the STOPI command with PURGE only if you are certain that the users to be deleted are no longer active. If a user with an open transaction is deleted, but then returns (by sending a command), no indication is given about the transaction backout. If the user continues the transaction, logical inconsistencies in the database could occur.
Stop and delete the user with the Adabas-assigned user ID (in the form shown in the display commands), or stop and delete all users with the specified job name (job-name). Any open transaction by the stopped users will be backed out.

Caution:
If Adabas is running with ADARUN OPENRQ=NO (specifying that users are not required to issue an OP as the first command of the session), run the STOPU command only if you are certain that the users to be deleted are no longer active. If a user with an open transaction is deleted, but then returns (by sending a command), no indication is given about the transaction backout. If the user continues the transaction, logical inconsistencies in the database could occur.

Note:
The STOPU=X'userid' command is not allowed for online reorder or invert processes. See the ONLSTOP=X'identifier' command instead.

The user ID must be specified in hexadecimal format; for example:
```
STOPU=X'1CF2' 
```
In a cluster environment, NUCID must always be specified because the user ID is not unique to the cluster.
Force resynchronization of all ET users on the nucleus. The nucleus waits for all ET users to reach ET status before continuing.
Set non-activity time limit (in seconds) for users where u is one of the following:
- A - for access-only (ACC) users
- E - for ET logic users
- X - for exclusive control (EXF/EXU) users
If specified, time must be a value greater than zero; it overrides the ADARUN value.

In nucleus cluster environments, the TNAu commands are global by definition and affect all nuclei in the cluster. If a NUCID is specified, it is ignored.
Set transaction time limit (in seconds) for ET logic users. If specified, this value must be greater than zero; it overrides the ADARUN value. In nucleus cluster environments, the TT command is global by definition and affects all nuclei in the cluster. If a NUCID is specified, it is ignored.
Unlock the specified file and restore its usage to the prelocked status.
Unlock the specified file for utility use and restore it to its prelocked status for non-utility users.
Unlock the specified file and restore its usage to the prelocked status.
Note:
Not currently available for use with Adabas Parallel Services cluster nuclei.

Switch UTIONLY status on or off.

In nucleus cluster environments, the UTIONLY command is global by definition and affects all nuclei in the cluster. If a NUCID is specified, it is ignored.

ADADBS PRIORITY: Change User Priority

graphics/util_adadbs_priority.png

ADADBS REACTLOG: Reactivating Command Logging

graphics/util_adadbs_reactlog.png

ADADBS RECORDSPANNING: Enable or Disable Record Spanning

graphics/util_adadbs_recordspanning.png

ADADBS RECOVER: Recover Space

graphics/util_adadbs_recover.png

ADADBS REFRESH: Set File to Empty Status

graphics/util_adadbs_refresh.png

ADADBS REFRESHSTATS: Reset Statistical Values

graphics/util_adadbs_refreshstats.png

ADADBS RELEASE: Release Descriptor

graphics/util_adadbs_release.png

ADADBS RENAME: Rename a File or Database

graphics/util_adadbs_rename.png

ADADBS RENUMBER: Change File Number

graphics/util_adadbs_renumber.png

ADADBS REPLICATION: Activating or Deactivating Replication

graphics/util_adadbs_replication.png

ADADBS REPTOR: Activating, Deactivate, Open or Close an Event Replicator for Adabas Resource

graphics/util_adadbs_reptor.png

ADADBS RESETDIB: Reset Entries in Active Utility List

graphics/util_adadbs_resetdib.png

ADADBS RESETPPT: Reset PPT Blocks

graphics/util_adadbs_resetppt.png

ADADBS SPANCOUNT: Count Spanned Records

graphics/util_adadbs_spancount.png

ADADBS TRANSACTIONS: Suspend and Resume Update Transaction Processing

graphics/util_adadbs_transactions.png

ADADBS UNCOUPLE: Uncouple Files

graphics/util_adadbs_uncouple.png

ADADBS UNDELDE: Undelete a Logically Deleted Descriptor

graphics/util_adadbs_undelde.png

ADADBS UNDELFN: Logically Undelete Fields

graphics/util_adadbs_undelfn.png

ADADCK DSCHECK: Check Data Storage and DSST

graphics/util_adadck_dscheck.png

ADADEF DEFINE: Define a Database and Checkpoint File

graphics/util_adadef_define.png

ADADEF MODIFY: Change File Encodings

graphics/util_adadef_modify.png

ADADEF NEWWORK: Define a Work File

graphics/util_adadef_newwork.png

ADAFRM: Format Adabas Database Components

To format the Associator (ASSO) or Data Storage (DATA) data sets, use this syntax:

graphics/util_adafrm_assofrm.png

To format the Work (WORK), command log (CLOG), protection log (PLOG), or sort (SORT) data sets, use this syntax:

graphics/util_adafrm_workfrm.png

To format the recovery log (RLOG), use this syntax:

graphics/util_adafrm_rlogfrm.png

To format the Temp (TEMP) data set, use this syntax:

graphics/util_adafrm_tempfrm.png

To reformat blocks of an existing Associator, Data Storage, or Work data set, use this syntax:

graphics/util_adafrm_assoreset.png

ADAICK ACCHECK: Check Address Converter

graphics/util_adaick_accheck.png

ADAICK ASSOPRINT: Print/Dump Associator Blocks

graphics/util_adaick_assoprint.png

ADAICK BATCH: Set Printout Width to 132 Characters Per Line

graphics/util_adaick_batch.png

ADAICK DATAPRINT: Print/Dump Data Storage Blocks

graphics/util_adaick_dataprint.png

ADAICK DSCHECK: Print/Dump Content of Data Storage Record

graphics/util_adaick_dscheck.png

ADAICK DUMP: Activate Dump Print Format

graphics/util_adaick_dump.png

ADAICK FCBPRINT: Print/Dump File Control Block

graphics/util_adaick_fcbprint.png

ADAICK FDTPRINT: Print/Dump Field Definition Table

graphics/util_adaick_fdtprint.png

ADAICK GCBPRINT: Print/Dump General Control Blocks

graphics/util_adaick_gcbprint.png

ADAICK ICHECK: Check Index Against Address Converter

graphics/util_adaick_icheck.png

ADAICK INT: Activate Interpreted Print Format

graphics/util_adaick_int.png

ADAICK NIPRINT: Print/Dump Normal Index

graphics/util_adaick_niprint.png

ADAICK NOBATCH: Set Print Width to 80 Characters Per Line

graphics/util_adaick_nobatch.png

ADAICK NODUMP: Suppress Dump Print Format

graphics/util_adaick_nodump.png

ADAICK NOINT: Suppress Interpreted Format

graphics/util_adaick_noint.png

ADAICK PPTPRINT: Print/Dump Parallel Participant Table

graphics/util_adaick_pptprint.png

ADAICK UIPRINT: Print/Dump Upper Index

graphics/util_adaick_uiprint.png

ADAINV COUPLE: Define File-Coupling Descriptors

graphics/util_adainv_couple.png

ADAINV INVERT: Create Descriptors

graphics/util_adainv_invert.png

ADALOD LOAD: Load a File

graphics/util_adalod_load.png

ADALOD UPDATE: Add/Delete Records

graphics/util_adalod_update.png

ADAMER Utility: ADAM Estimation

graphics/util_adamer.png

ADAORD REORASSO: Reorder Associator

graphics/util_adaord_reorasso.png

ADAORD REORDATA: Reorder Data Storage

graphics/util_adaord_reordata.png

ADAORD REORDB: Reorder Database

graphics/util_adaord_reordb.png

ADAORD REORFASSO: Reorder Associator for a Single File

graphics/util_adaord_reorfasso.png

ADAORD REORFDATA: Reorder Data Storage for a Single File

graphics/util_adaord_reorfdata.png

ADAORD REORFILE: Reorder File

graphics/util_adaord_reorfile.png

ADAORD RESTRUCTUREDB: Restructure Database

graphics/util_adaord_redb.png

ADAORD RESTRUCTUREF: Restructure Single Files

graphics/util_adaord_ref.png

ADAORD STORE: Store Files

graphics/util_adaord_store.png

ADAPLP: Print Data Protection Records from PLOG/Work

graphics/util_adaplp.png

where type is one of the following:

graphics/util_adaplp_type.png

ADAPRI: Print Selected Adabas Blocks

graphics/util_adapri.png

ADARAI CHKDB: Check the Database Recovery Status

graphics/util_adarai_chkdb.png

ADARAI DISABLE: Deactivate Recovery Logging

graphics/util_adarai_disable.png

ADARAI LIST: Display Current RLOG Generations

graphics/util_adarai_list.png

ADARAI PREPARE: Initialize and Start the RLOG

graphics/util_adarai_prepare.png

ADARAI RECOVER: Build a Recovery Job Stream

graphics/util_adarai_recover.png

ADARAI REMOVE: Remove the Recovery Aid

graphics/util_adarai_remove.png

ADAREP: Request Database Status Report

graphics/util_adarep.png

ADARES BACKOUT SIBA: Back Out Updates Using the Sequential Protection Log (SIBA)

graphics/util_adares_backout_plognum.png

ADARES BACKOUT DPLOG or MPLOG: Back Out Updates Using the Dual or Multiple Protection Log

graphics/util_adares_backout_dplog.png

ADARES CLCOPY: Copy Dual Command Log

graphics/util_adares_clcopy.png

ADARES COPY: Copy a Sequential Protection Log or Save Tape

graphics/util_adares_copy.png

ADARES MERGE CLOG: Merge Nucleus Cluster Command Logs

graphics/util_adares_merge.png

ADARES PLCOPY: Copy Protection Log to Sequential Data Set

graphics/util_adares_plcopy.png

ADARES REGENERATE: Regenerate Updates

graphics/util_adares_regenerate.png

ADARES REPAIR: Repair Data Storage Blocks

graphics/util_adares_repair.png

ADASAV RESTONL: Restore Database from Online Source

graphics/util_adasav_restonl.png

ADASAV RESTONL FILES: Restore Files to Original RABNs from Online Source

graphics/util_adasav_restonl_files.png

ADASAV RESTONL FMOVE: Restore Files to Any RABNs from Online Source

graphics/util_adasav_restonl_fmove.png

ADASAV RESTONL GCB: Restore Database Incremental from Online Source

graphics/util_adasav_restonl_gcb.png

ADASAV RESTORE: Restore Database from Offline Source

graphics/util_adasav_restore.png

ADASAV RESTORE FILES: Restore Files to Original RABNs from Offline Source

graphics/util_adasav_restore_files.png

ADASAV RESTORE FMOVE: Restore Files to Any RABNs from Offline Source

graphics/util_adasav_restore_fmove.png

ADASAV RESTORE GCB: Restore Database Incremental from Offline Source

graphics/util_adasav_restore_gcb.png

ADASAV RESTPLOG: Restore Protection Log Only

graphics/util_adasav_restplog.png

ADASAV SAVE: Save Database

graphics/util_adasav_save.png

ADASAV SAVE FILES: Save Specified Files

graphics/util_adasav_save_files.png

ADASEL Utility: Select Protection Data

graphics/util_adasel.png

Value Criterion
Output Instruction
IF Processing

Value Criterion

graphics/util_adasel_valcrit.png

Output Instruction

graphics/util_adasel_output_instr.png

IF Processing

graphics/util_adasel_if.png

ADAULD UNLOAD FILE: Unload Specified File

graphics/util_adauld.png

ADAVAL Utility: Validate the Database

graphics/util_adaval.png

ADAWRK Utility: Work Area Recovery Reports

graphics/util_adawrk.png

ADAZAP Utility: Display or Modify Asso, Data, and Work Data Sets

graphics/util_adazap.png

ADAZIN Utility: Print Adabas Maintenance and SVC Information

graphics/util_adazin.png

SEARCH INDEX CONTENTS | PDF PAGE PDF BOOKS | HOME UP PREV NEXT