Problem

Solutions

An accessory cannot find DBEngine

Most likely the accessory is running under a different usercode than where the DBEngine is located. If this is unavoidable, use the SL command to define the DBEngine function name, as follows (assuming DBEngine is located under the DBA usercode on a pack called DBAPACK):

SL DATABridge Engine = (DBA)OBJECT/DATABRIDGE/ENGINE ON DBAPACK

An accessory displays a message indicating a version mismatch and then terminates

Most likely the DATABridge software you are running was compiled using different versions of the DATABridge API (SYMBOL/DATABRIDGE/INTERFACE). Make sure that all of the DATABridge software is from the same release.

A task called DATABRIDGE/MISSING_AUDIT_FILE displays the title of a missing file and then waits for an accept.

A necessary audit file is missing. Restore the audit file to the proper disk family and then enter the AX command. (No additional text is required after the AX.) This will tell DBEngine to retry the audit file search. You cannot do an FA to redirect the search to another disk family. Alternatively, if the file cannot be restored, DS the waiting task (DATABRIDGE/MISSING_AUDIT_FILE); DBEngine will terminate the current operation with an error.

A worker displays the following message:

Possible AUDIT JOB 'runaway zipper' problem

OK to start jobs for AFN firstAfn thru lastAfn

The Worker is then suspended in the Waiting Entries.

This message can occur in the rare event that DBServer would zip more than 10 AUDIT JOB jobs one after the other, and it is intended to trap a bug that has been difficult to reproduce.

You can either enter an OK to continue or a DS to terminate the Worker, but please do a DS ARRAYS and send the program dump to Attachmate technical support.