Replication Target File

A replication target file (replication target flag set) can only be updated by specially-marked replication calls from an Adabas replicator. Normal insert and update Adabas calls (A1, E1, N1, and N2) from other users will be rejected with response 17 (invalid file number) and subcode value=2 (unauthorized system file access).

However, replication target files can be converted back to normal files by using the new ADADBM function RESET_REPLICATION. In this case, the standard Adabas processing for data fields and files is restored, all Adabas commands are permitted and the standard SY option handling is enabled (see notes below).

Notes:

  1. The replication target flag can only be reestablished by a renewed initial state processing.
  2. The current status of the replication target flag can be checked using ADAREP FILES.
  3. If the replication target flag is reset in the FCB, subsequent replication commands will be rejected for this file.
  4. In a replication target file, system generated fields (SY option set) get the same values in the target record as in the source record.
Warning:
The current version of A2A replication does not support the replication of utility operations, for example ADADBM REFRESH. For this reason, utility operations are permitted on replication target files. It is the responsibility of the DBA to ensure that utility operations are performed in sync on both the source and the target file, and only when the replications are up-to-date. If utility operations are only performed on the replication target file but not on the source file (or vice versa), inconsistencies between the source and target file can occur, and the replication can get errors. ADAINV is an exception to this behavior - adding or removing descriptors does not change the data that is stored in a record, and can, therefore, be done without the risk of any inconsistencies or errors.