Databridge DMSII Support

The Databridge DMSII Support library must have OPENINQUIRY, OPENUPDATE, and FIND access to the physical database. OPENUPDATE allows the extract routines to generate a small amount of audit when doing an OFFLINE clone.

Here's an example of a guard file fragment for a physical database. In this example, the fictional site has Databridge software installed under the (DB) usercode on the family named DBPACK and the database DESCRIPTION file is called (PROD)DESCRIPTION/BANKDB ON DMSPACK.

PROGRAM (DB)OBJECT/DATABRIDGE/DBINFO ON DBPACK = RO;
PROGRAM (DB)OBJECT/DATABRIDGE/GENFORMAT ON DBPACK = RO;
PROGRAM (DB)OBJECT/DATABRIDGE/DMSIISUPPORT/BANKDB/PROD ON DBPACK = RW,
        DMVERBS = (OPENINQUIRY, OPENUPDATE, FIND);

The DMVERBS list for the physical database prevents any actual updating because DELETE, STORE, etc., are not allowed.

If you are using DBTwin or the DMSII Client, the DMSII Support library on the secondary system must have updating access as well and in that case the DMVERBS list should be omitted entirely.