Administrator Command Reference Manual
System and Global Projects
System and Global Projects
This chapter describes how ADMIN elements and their attributes, in a System database differ when a Global project is used.
You can navigate to the elements in the System and Global databases, and query their members and attributes in the normal way.
A full list of Elements and their Attributes is included in the Data Model Reference Manual.
Session information is stored separately in the COMMs database; and the MISC database stores inter-db macros and messages. The communications world element in the COMMs database contains the project lock. This may be set or cleared using LOCK and UNLOCK syntax.
When you use the MAKE GLOBAL command to make a standard project into a global project, the Standard System database is split into two new database files; the Global database and the (local) System database.
A modified sysvir.dat virgin database is used to upgrade the System database file xxxsys, where xxx is the 3-character project code. The communications world element LCOMW is added. The glbvir.dat database template file is used to create the Global database file xxxglb.
The existence of the xxxglb database file shows that the project is global.
The following elements are added:
•
The communications world element LCOMW
•
The Global Locations world element GLOCW, which will own GRPLI elements which in turn own GRP elements
•
The Global Team World element GTMWL
•
The Global Stamp World element GSTWLD. If stamps exist in the System database, they are all copied to the Global Stamp World element and deleted from the System database.
The attributes of these elements and their members, and the changes to other ADMIN database elements which occur when a Project is made Global, are described in the following pages.
The Global database contains information that is common to all Locations running a Global project. The Global database is readable at all locations but is it can only be written to at the Hub. Changes to the Global database are propagated to all the other Locations. This means that the Global database is the same at every Location, except during the short time changes are being propagated.
Each local System Database contains project information that is specific to the Location. The local administrator can write to the local system Database. A local System database is similar to the System database in a non-global Project. The main difference is that some of the standard ADMIN elements will be redundant. The differences are described below.
Session information is stored separately in the COMMs database; and the MISC database stores inter-db macros and messages. The Comms and Misc databases are local to each Location.
The communications world element in the COMMs database contains the project lock and isolation flags. The project lock may be set or cleared using LOCK and UNLOCK; and the Isolation flag may be set true or false using ISOLATION syntax. Both lock and isolation may be set or queried remotely by the Hub or an administering location.
1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.
AVEVA Logo