Version 7.4.4
 —  Operations  —

FORCE : Allow Database ID Table Entry Overwrite

Parameter Specify . . . Possible Values Default
FORCE whether the nucleus can overwrite an existing ID table entry. YES | NO NO

When an Adabas nucleus starts up, ADARUN scans the ID table to ensure that no entry exists for the nucleus. To protect the database from concurrent updates, the nucleus is not allowed to access the database if an ID table entry exists for the nucleus. You can use the FORCE parameter to indicate whether the nucleus can overwrite an existing ID table entry.

In addition, if you have Adabas 7.4.2 (with fix AN742281 applied) or Adabas 7.4.3 (with fix AN743052 applied), when an Adabas Parallel Services nucleus starts, the PLXNUC entries in the PLXCB structure are scanned to ensure an active entry for the same NUCID does not exist. If the FORCE parameter is set to YES, an Adabas Parallel Services nucleus will be able to overwrite an existing duplicate PLXNUC entry. This should only be necessary if an earlier nucleus had failed in such a way that the PLXNUC entry was not deactivated.

The ID table entry is derived from the database ID and the job name. The ID table entry is deleted when the nucleus terminates normally.

The FORCE parameter allows the nucleus to overwrite the existing ID table entry and access the database.

Warning:
Do not use the FORCE parameter unless absolutely necessary, or the integrity of the database could be lost. Ensure that no nucleus is active for the ID table entry being overwritten.

Note:
In an Adabas Cluster Services or Adabas Parallel Services environment, the FORCE parameter applies to the NUCID, rather than the database ID, because a cluster nucleus builds an ID table entry for the NUCID.

Value Meaning
YES The nucleus that is starting can overwrite an existing ID table entry. FORCE=YES is required when restarting a session that terminated abnormally with an ADAM98 message. In this case, the ID table still contains an active entry for the nucleus. Overwriting the existing entry by specifying FORCE=YES prevents further communication to the overwritten nucleus and causes loss of cross-memory environment resources, which cannot be restored until the next IPL.
NO (default) If the ID table contains an entry for the nucleus that is starting, the nucleus is denied access to the database.

Example:

If the ID table contains an active entry for DBID 7, overwrite the entry.

ADARUN PROG=ADANUC,FORCE=YES,DBID=7

Top of page