Run the Tanker Accessory

For each DMSII database, you must run the Tanker Accessory.

  • First, to create a parameter file for the specified database
  • Second, to put the Tanker Accessory in the mix, where it runs continuously until you terminate it

Whenever you start WFL/DATABRIDGE/TANKER, the Tanker Accessory looks for the last commit in the filtered audit file and resumes filtering from that point. The Tanker Accessory performs a commit at the end of each transaction group and then updates the header.

To run the Tanker Accessory

  1. Define the filters you want to use in DATA/GENFORMAT/databasename/CONTROL. See Creating a Filter.
  2. Compile a tailored support library. See Tailoring a Support Library.
  3. From CANDE, start the Tanker Accessory by entering one of the following commands. You must include the quotation marks.

    START WFL/DATABRIDGE/TANKER ("databasename")

    where databasename indicates the title of the DESCRIPTION file without the DESCRIPTION node.

    — or —

    START WFL/DATABRIDGE/TANKER ("databasename", "logicaldatabasename")

    Example:

    START WFL/DATABRIDGE/TANKER ("(PROD)INVENTORY ON DEVPACK")

    indicates that the Tanker Accessory should use this file

    (PROD)DESCRIPTION/INVENTORY ON DEVPACK

    When you run Tanker Accessory, a parameter file (such as, DATA/TANKER/databasename/CONTROL) is created.

  4. Edit the parameter file that was created in step 3 to include all of the filters you created via the DBGenFormat utility in step 1.
  5. Run the Tanker Accessory again using the following syntax. You must include the quotation marks.

    START WFL/DATABRIDGE/TANKER ("databasename")

    — or —

    START WFL/DATABRIDGE/TANKER ("databasename", "logicaldatabasename")

    This time, the Tanker Accessory uses the Tanker Accessory parameter file (DATA/TANKER/databasename/CONTROL or DATA/TANKER/logicaldatabasename/CONTROL) to filter audit files according to the filters you created.

    Note: If you are running DATABridge Plus, the Tanker Accessory can filter up to (and include) the active audit file.

  6. Make sure that each user-written Accessory that uses prefiltered audit files calls the DBINITFILTER entry point in the Engine. For more information, see Preparing Accessories for the Tanker Accessory.
  7. To check on Tanker Accessory status or terminate the Tanker Accessory, see the next section, Tanker Accessory Commands.