Show Contents / Index / Search

Set Up Guardfiles

If your database uses guardfiles, Databridge can be included under database guardfile validation. For validation of guardfiles to work, the relevant guardfile must specify read access (RO) for the Databridge Accessory and/or the usercode under which the Databridge Accessory is running.

In addition, the Databridge (DBEngine) must have read access to the actual database guardfile. You can accomplish this in one of the following ways:

  • Run the Databridge Accessory under the usercode that owns the guardfile. For example, if the guardfile is (PROD)GUARDIAN/FILE, run the Accessory under the PROD usercode.
  • Change the security of the guardfile to PUBLIC IN.
  • Make sure that DBEngine is a privileged program. DBEngine is marked as a privileged program on the release tape.

    Note: Access to the guardfile itself is enforced by the MCP. Therefore, even if you make the database visible to the Accessories, you must still give DBEngine read access to the guardfile, as explained above.

Databridge Components and Guardfiles

Databridge Accessories and the Databridge Server Workers (but not the Databridge Server itself) must have read access to the database (physical or logical) they are using. No other rights are necessary. Because GenFormat and DBInfo always use the physical (versus a logical) database when searching for a quiet point, they require read access to the physical database.

DBEngine and Extract Workers

The DBEngine and its Extract Workers must have OPENUPDATE access to the physical database. This allows the extract routines to generate a small amount of audit and switch the active audit file. In addition, the Extract Workers require FIND access for reading the data set records during a clone.

Here's an example of guardfile fragments for a physical database. (In this example, the fictional site runs up to three Extract Workers and has Databridge software installed under the (DB) usercode on the family named DBPACK.)

PROGRAM (DB)OBJECT/DATABRIDGE/DBINFO ON DBPACK = RO;

PROGRAM (DB)OBJECT/DATABRIDGE/GENFORMAT ON DBPACK = RO;

PROGRAM (DB)OBJECT/DATABRIDGE/ENGINE ON DBPACK = RW,

DMVERBS = (OPENINQUIRY, OPENUPDATE);

PROGRAM (DB)EXTRACT/WORKER/0 = RW,

DMVERBS = (OPENINQUIRY, OPENUPDATE, FIND);

PROGRAM (DB)EXTRACT/WORKER/1 = 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 allow more than two Extract Workers to run concurrently, add entries like the ones above with the appropriate number for the last node.

Accessories and Databridge Server Workers

The Accessories and Databridge Server Workers (but not the Databridge Server itself) must be listed in the guardfile that protects the database they will be using. However, if they use a logical database instead of a physical database, put these entries in the guardfile that protects the logical database.

Here's an example of guardfile fragments for a physical or logical database. (In this example, Databridge is installed under the (DB) usercode on the family named DBPACK and the Databridge Clients run on hosts called IPADDRESS1 and IPADDRESS2.)

PROGRAM (DB)OBJECT/DATABRIDGE/SPAN ON DBPACK = RO;

PROGRAM (DB)OBJECT/DATABRIDGE/SNAPSHOT ON DBPACK = RO,

PROGRAM (DB)OBJECT/DATABRIDGE/LISTER ON DBPACK = RO;

PROGRAM (DB)OBJECT/DATABRIDGE/TANKER ON DBPACK = RO;

PROGRAM (DB)OBJECT/DATABRIDGE/AUDITTIMER ON DBPACK = RO;

PROGRAM (DB)DBSERVER/WORKER/1 ON IPADDRESS1 = RO;

PROGRAM (DB)DBSERVER/WORKER/1 ON IPADDRESS2 = RO;

PROGRAM (DB)DBSERVER/WORKER/2 ON IPADDRESS1 = RO;

PROGRAM (DB)DBSERVER/WORKER/2 ON IPADDRESS2 = RO;

If you allow more than two Databridge Server Workers to run concurrently, add entries like the ones above with the appropriate number for the last node.