Structure of the Local System Database

The local System Database (DB) contains the data for local Fonts, Modules, Users, MDBs, DB Sets, Scopes and ACRs: these elements correspond to those that existed in the System DB of a Standard Project. The communications data is held in a new LCOMW Location Comms World element. The Team World and Role Worlds still exist in the local System DB, but they are empty. The Team data is stored in the Global Team World element GTMWL in the Global DB, and the Role data is stored in the Global Role World.

The TEAM and USER elements in the Standard System DB cross-reference each other, that is, each Team element holds a list USLI of Users belonging to the Team and each User element holds a list TMLI of Teams to which the User belongs. In the Global DB, a Team does not maintain a USLI list of Users belonging to it.

Note:
This means that a report of all Users at every Location in the Project can only be obtained by combining reports from each Location.

The TMLI list in the USER element in the local System DB will continue to provide a list of Teams to which a User at a particular Location belongs.

In the same way that a TEAM element no longer maintains a list of Users in that Team, a DB element in a Team does not maintain a list of MDBs to which the DB belongs. The MDB element in the local System DB keeps a list of DBs belonging to it.

The detailed changes to the elements and attributes are described below.

STAT Element

This element already exists in the local System DB, but certain attributes have been relocated to the Global System DB. The attributes are the same as in a Standard Project with the addition of:

Note:
When a Location is created, the LOCRF attribute in its local System DB will be set to the reference of its LOC Location element in the Global System DB.

LCOMW Element

The Location Communications World element LCOMW is called /*LC. It contains elements that describe the communications between one Location and all the other Locations with which it can communicate. The LCOMW element owns a LCOMC element, LCOML elements and LCTIML elements.

LCOMC Element

The LCOMC element contains general details about the configuration of the Admin daemon at the current Location. There should be only one LCOMC element in the DB.

Attributes:

LCOML Element

The LCOML element contains a list of LCOMD elements, each of which specifies details about the communications link between the current site and one other site, as described below.

Attributes:

LCOMD Element

The LCOMD element contains specific details about the communications link between the current site and one other site, and controls scheduled updates. There will be one LCOMD element for each Location, which has a communications link with the current Location.

Attributes:

The Timer values are:

For example:

The attributes TIMES and TIMEE are not implemented at this release.

Files such as Isodraft external plot files are not propagated automatically by the Global daemon. However, there is a mechanism in the daemon to allow such files to be transferred to and from neighboring Locations, during scheduled updates (or the UPDATE ALL command). The directory to receive transferred files is defined by the environment variable %IMPORT%. Each Location to which files are to be transferred requires its own transfer directory - %EXP_ABC% for Location ABC. Transfer of other data is described more fully in the AVEVA Global User Guide.

Offline Locations:

Note:
Transfer of such files to or from offline Locations must be done manually.

LCTIML Element

The LCTIML element is present in a Global Project only and has the following functions:

• It overrides the default transaction event timings.

• It contains a LEVENL attribute, which sets the time interval for the event loop for all Locations, in seconds.

• It contains attributes that control the frequency of automatic merges on the transaction DB.

• It contains a list of LCTIMD elements, each of which specifies details about the event timings between the current site and one other site, as described below.

Attributes:

At times specified by LMERTI, the transaction DB will automatically be merged and commands deleted as specified by the LMERSU and LMERFA attributes. The LMERDL attribute must be set to true. For example, the automerge data could be set as follows:

LMerti ’59 23 * * 3,6’

LMersu 10

Lmerfa ‑1

Lmerdl true

In this example, the daemon would delete all successful commands older than 10 days and merge the transaction DB. Failed commands would not be deleted.

Note:
If both LMERSU and LMERFA are set to ‑1, then the transaction DB will not be merged.

LCTIMD Element

The LCTIMD element contains details about the event timings between the current site and one other site. There will be one LCTIMD element for each Location that communicates with the current Location.

Attributes: