Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Engineering

Structure of the Transaction Database

  • Last UpdatedFeb 15, 2023
  • 1 minute read

The hierarchical structure of the transaction Database (DB) is shown in the illustration.

All the owner/child relations are one to many with the exception of TRMLST, TRFLST, and TRSLST. There is only one of each below an operation (TROPER) or output command (TROUCO) or an input command (TRINCO).

There is no distinction between commands received from other Locations (foreign) or from the local Location as there are no fundamental differences between them. Whether they are local or foreign is determined by their position in the hierarchy and their owner’s names.

The structure is a hierarchy leading to input commands received by the daemon, and the operations these have evaluated to.

Embedded Image (65% Scaling) (LIVE)

TitleResults for “How to create a CRG?”Also Available in