UPDATE (Global Project Administration)

Administrator Command Reference Manual

Command Details : Detailed Descriptions of Commands : UPDATE (Global Project Administration)

UPDATE (Global Project Administration)

Updates the current location and an immediate neighbour.

This is a two-way process, unlike SYNCHRONISE. Databases at the current location and databases at a neighbouring 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. See 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 neighbouring 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 Global Management User Guide.

Updates of individual databases can also be made with locations which are not immediate neighbours. In this case, the update obeys network routing. The database will be synchronised with the database at locations on the route to the primary location; and updated with the database on the route from the primary location to the destination.

Both Locations (and any intermediate locations) must be on-line.

Note:

This command is called ‘Update Routed’ in the transaction database.

Examples of updating constructor databases:

UPDATE ALL WITH LON

All databases at the current location and all databases at Location LON will be compared, and updated so that all have the most recent data.
If LON is not an immediate neighbour, then updates will also be run at intermediate locations. For example if CAM is between the current location ABC and LON, 3 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 database at the current location will be compared with the PIPES/PIPES database at Location CAM. Updates will be transferred from the most up-to-date database 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 on-line.

•

Scheduled updates run updates concurrently for several databases. The update is scheduled as follows:

•

First the Global database will be updated;

•

Then 5concurrent DBLIST updates will be scheduled. The databases are distributed across these 5 update commands.

•

Where possible, extracts will be included in the same update as their parent database;

•

The system databases are updated in a separate DBLIST update.

•

Scheduled updates will not start if the previous update for the same Update event (LCOMD) is still running. If duplicate scheduled updates are required, then additional Update events are required. However since the standard update runs 5 updates concurrently, this should not be necessary. The results of Inter-db macro transfer and failures from Other-data transfer are recorded in the Transaction database.

UPDATE DBLIST <update-list> <update-options>

Where <update-list> may contain one or more of the following –

•

•

•

SYSTEM/DB FOR <locnam>

•

•

Valid elements include MDB, DBSET, DB or LOC elements.

Examples of updating system databases:


UPDATE SYSTEM WITH CAM The System database for the current location, at the current location, will be compared with the System database for the current Location at Location CAM. Updates will be transferred from the most up-to-date database to the other. UPDATE SYSTEM FOR OXF WITH CAM The System database for location OXF at the current Location will be compared with the System database for location OXF at Location CAM. Updates will be transferred from the most up-to-date database to the other.

Examples of updating the global database:


UPDATE GLOBAL WITH CAM The Global database at the current location will be compared with the Global database at Location CAM. Updates will be transferred from the most up-to-date database 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:

1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.