UPDATE (Global Project Administration)
- Last UpdatedJan 30, 2025
- 3 minute read
Function:
Updates the current Location and an immediate neighbor.
Description:
This is a two-way process, unlike SYNCHRONISE. Databases (DBs) at the current Location and DBs at a neighboring Location will be updated, according to which Location has the most up-to-date version.
Inter-DB connection macros will also be transferred, and any update script will be run. Update scripts are linked with Update events by setting the EXECA and EXECA attributes of the LCOMD element. For further information, refer to Structure of the Global Database.
Files such as Isodraft, backing-sheets files and 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 the AVEVA Global User Guide.
Updates of individual DBs can also be made with Locations which are not immediate neighbors. In this case, the update obeys network routing. The DB will be synchronized with the DB at Locations on the route to the Primary Location; and updated with the DB on the route from the Primary Location to the destination.
Both Locations (and any intermediate Locations) must be online.
Examples of updating constructor DBs:
|
UPDATE ALL WITH LON All DBs at the current Location and all DBs at Location LON will be compared, and updated so that all have the most recent data. If LON is not an immediate neighbor, then updates will also be run at intermediate Locations. For example, if CAM is between the current Location ABC and LON, three updates will be run - between ABC and CAM, between CAM and LON, and finally again between CAM and ABC. |
|
UPDATE PIPES/PIPES WITH CAM The PIPES/PIPES DB at the current Location will be compared with the PIPES/PIPES DB at Location CAM. Updates will be transferred from the most up-to-date DB to the other. |
|
UPDATE DIRECT CTBATEST/DESI WITH CAM The UPDATE DIRECT command is deprecated and should be used with caution. This updates directly with the specified Location ignoring the network routing. This may cause ‘Reverse propagation’ warnings, since intermediate Locations will not be updated. This functionality is provided for upwards compatibility with older versions of Global. |
|
Both Locations (and any intermediate Locations) must be online. Scheduled updates run updates concurrently for several DBs. The update is scheduled as follows:
|
|
UPDATE DBLIST <update-list> <update-options> Where <update-list> may contain one or more of the following:
|
Examples of updating System DBs:
|
UPDATE SYSTEM WITH CAM The System DB for the current Location, at the current Location, will be compared with the System DB for the current Location at Location CAM. Updates will be transferred from the most up-to-date DB to the other. UPDATE SYSTEM FOR OXF WITH CAM The System DB for Location OXF at the current Location will be compared with the System DB for Location OXF at Location CAM. Updates will be transferred from the most up-to-date DB to the other. |
Examples of updating the Global DB:
|
UPDATE GLOBAL WITH CAM The Global DB at the current Location will be compared with the Global DB at Location CAM. Updates will be transferred from the most up-to-date DB to the other. |
Command Syntax:
|
>- UPDATE ------+- DIRECT --------------------. |-----------------------------| |-- dbname -------------------| | | | .------<------. | | / | | |-- DBLIST --<update-list>-+--| | | |-- SYSTEM -+- FOR ----<loc>--| | | | | `-----------------| |-- GLOBAL -------------------| | | `-- ALL ----------------------+- WITH <loc> -------> The <update-list> can be as follows: <update-list>--+--GLOBALdb --------------------. | | |--SYSTEM-- --|-- FOR ---<loc>--| | `-----------------| |-- DB ---<dbname>--------------| | | `-- <element-id>----------------+---> The <element-id> may be an MDB, DBSET, DB or LOC. |
Related Commands: