Administrator Command Reference Manual
Command Details : Detailed Descriptions of Commands : CHANGE (Project definition)
CHANGE (Project definition)
Function:
•
Changes database access type (UPDATE or MULTIWRITE), and the claim mode for multiwrite databases.
•
It also changes the file number and control mode, and brings foreign DBs up to date.
•
Optionally set PROTECTION to limit copying and extraction of data between users and projects.
In a Global Project, this command can only be given at the Hub. It can also be used to change the Primary Location of a database.
Description:
By default, databases are created with UPDATE access type, which means that they can be opened with one writer and n readers.
MODEL, DRAFT (PADD), CATALOGUE and ISODRAFT databases can be multiwrite databases, which allows more than one user to write to the same database. Multiwrite databases can have their claim mode set to IMPLICIT, in which case any element which is modified will be claimed automatically. Alternatively, the claim mode can be set to EXPLICIT, in which case users must claim elements before they can modify them, using the CLAIM command in the constructor modules. For more information, see the Reference Manual for the module.
The CHANGE command can be used to change the access mode from UPDATE to MULTIWRITE, and from MULTIWRITE, to UPDATE. It can also be used to change the claim mode of Multiwrite databases from IMPLICIT to EXPLICIT, and from EXPLICIT to IMPLICIT.
Note:
You cannot set the controlled attribute, which means that access is controlled by an external system, using this command.
If the database has an extract database created from it, the access mode must stay as Multiwrite.
If the access mode of a database used as a foreign database is changed, you should use the CHANGE FOREIGN command in the project which has included the foreign database to update the project.
Both UPDATE and MULTIWRITE databases can also have their CONTROLLED attribute set.
Setting the PROTECTION parameter will disallow copying extraction of data between projects or users which are not members of the protected database. An optional expiry date may be specified.
CHANGE dbname PROTection [ ON | OFF ] [EXPires future-date ]
In a Global Project, the CHANGE command can be used at the Hub to change the primary location of a database. The CHANGE PRIMARY command cannot complete while there are users in AVEVA E3D™ with write access to the database. The command will eventually complete once all such users have left AVEVA E3D™. You may need to use EXPUNGE to remove phantom users.
After the CHANGE PRIMARY command has been issued, users in AVEVA E3D™ with write access to the database can continue to modify the database, even if GETWORK is used. Once they have made a module switch, the database will become read-only.
If a CHANGE PRIMARY command fails, the previous primary location will normally be recovered automatically. If the recovery fails (for example, the daemon is not running), you can recover the previous Primary location using the command:
PREVOWN dbname
Use of the PREVOWN command should be avoided if possible.
Offline Locations
Before issuing a CHANGE PRIMARY command to or from an offline location, all users should have left AVEVA E3D™ at the old primary location. The TRANSFER command should first be used to bring the database at the new primary location up-to-date. Any modifications to the database at the old primary location subsequent to this TRANSFER will be lost. Only after this TRANSFER is it safe to issue the CHANGE PRIMARY command.
Examples:
CHANGE TEST/TESTDESI ACCESS MULTIWRITE
Change access rights to named database to multiwrite.
CHANGE TEST/TESTDESI CLAIM IMPLICIT
Change claim mode for named DB to IMPLICIT. This option can only be used for a MULTIWRITE database.
CHANGE TEST/TESTDESI ACCESS UPDATE
Change access rights to named DB to single write.
CHANGE TEST/TESTDESI CLAIM OFF
Change claim mode for named DB to OFF. This option can only be used for a CONTROLLED database.
CHANGE TEST/TESTDESI CONTROL OFF
Change control setting for named DB to OFF. This option can only be used for a CONTROLLED database.
CHANGE TEST/TESTDESI FINO 500
Change the Filenumber (FINO attribute) of the given database to the given number. By default, the Filenumber will be set to 0, and the filename of the database file will be derived from the database number. Using the default is recommended, particularly if you are using extracts. If you set the filenumber explicitly, the extract filename will still be derived from the Database number (NUMDB attribute), and so the consistency of filenames within an Extract family will be lost.
CHANGE TEST/TESTDESI FINO 0
Change the Filenumber (FINO attribute) of the given database to 0. This command can be used to update database files to the new file numbering convention, which will keep Extract filenames consistent within an Extract family.
CHANGE FOREIGN PIPE/PIPECATA RESET
If PIPE/PIPECATA is a local database in project AAA, and a foreign database in project BBB, and the access is changed (in AAA), you should give this command in project BBB to update the project.
Note:
On the following Change...Primary Commands
The new Primary Location will receive all outstanding updates of the database from the current Primary Location.
Note:
Offline Locations:
The Primary Location of a Database cannot be changed directly between an off-line satellite and an on-line satellite. The Primary Location of the database must first be changed to the Hub. The <date> option is not allowed for off-line Locations.
 
The following command can only be used at the Hub of a Global project:
CHANGE TEST/TESTDESI PRIMARY AT CAM
Change the primary location of the named DB to be CAM. The database will automatically become secondary at the current Primary location.
The following option is only available at the Hub of a Global Project:
CHANGE HVAC/HVAC PRIMARY AT CAM AT 2330
Change the Primary Location of the named DB to the Location CAM at the specified time. 
Command Syntax:
>- CHange -+- dbname -+- ACCess -----+--- MULTIWrite ----------------.
           |          |              |                               |
           |          |              |--- CONTRolled ----------------|
           |          |              |                               |
           |          |              ‘--- UPDAte --------------------|
           |          |                                              |
           |          |- CLAIM ------+--- IMPLicit ------------------|
           |          |              |                               |
           |          |              |--- EXPLicit ------------------|
           |          |              |                               |
           |          |              ‘--- OFF -----------------------|
           |          |                                              |
           |          |- FINO -------+--- n -------------------------|
           |          |              |                               |
           |          |              ‘--- 0 -------------------------|
           |          |                                              |
           |          |- PROTection -+--- ON -+----------------------|
           |          |              |        |                      |
           |          |              |        ‘-EXPires future date -|
           |          |              |                               |
           |          |              ‘--- 0FF------------------------|
           |          |                                              |
           |          ‘- CONTROL ----+--- ON ------------------------|
           |                         |                               |
           |                         ‘--- OFF -----------------------|
           |                                                         |
           ‘- FOREIGN dbname RESET ----------------------------------+->
Note:
The CLAIM OFF option is only applicable to Controlled databases.
The CLAIM IMPLICIT and CLAIM EXPLICIT options are only applicable to Multiwrite and Controlled databases.
The following option is only available at the Hub of a Global Project:
>--- CHange dbname --- PRIMary AT  <loc> ---+-- AT <date> --.
                                            |               |
                                            ‘---------------+--->
Querying:
>--- Query DB dbname --->
 
>--- Q PRMLOC --->
At a DB, shows the primary location.
Related Commands:
PREVOWNER, TRANSFER (Global only)
1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.
AVEVA Logo