The ADAZAP utility can be executed only when the Adabas nucleus is inactive.
ADAZAP is used to display in hexadecimal format and optionally to change the contents of the ASSO, DATA, or WORK data sets.
Note:
If you use ADAZAP to change the DBID of the database in the GCB in ASSO RABN 1 (2 bytes
at offset 0), set the ADARUN DBID parameter for this ADAZAP execution to the new DBID that
will be in effect after the change to be made. (This applies to ADA854, ADA853 with AU853040
applied, ADA852 with AU852056 applied, and ADA851 with AU851069 applied. ADAZAP required the
old DBID to be specified in the ADARUN DBID parameter without this correction. This did not
allow changing the DBID in a copy of the database container datasets while Adabas was active
on the original database.)
Because a significant element of risk is involved in modifying physical database blocks, the use of this utility is restricted. Software AG will provide the master code necessary to run the ADAZAP utility only on written request to the individuals at each customer site who are authorized to receive it.
In addition, Software AG strongly recommends that you use your external security system to protect ADAZAP just as you protect other ZAP programs.
Software AG also recommends that a current save tape be available before running ADAZAP. If an error occurs during ADAZAP execution, it may be necessary to restore the affected file or database.
If the data is successfully altered, a SYNP 3F checkpoint record is written containing the REP and VER data to provide an audit trail of any changes that have been made.