LOCK (Project Administration)
- Last UpdatedFeb 22, 2022
- 1 minute read
Function:
Locks the Project Database (DB) and prevents any other User from entering the DB until the Project is unlocked.
In a Global Project, a Project DB can be locked remotely from the Hub.
Description:
LOCK has no effect on Users already accessing a Project; it simply prevents people from entering that Project. If the System administrator is planning to execute a major change, particularly if the administrator is to incorporate new versions of modules, they should first use the LOCK command to lock the Project, then send a message to all Users asking them to leave the AVEVA base product, make the required changes when there are no Users left actively in the Project, and finally use the UNLOCK command to unlock it.
The locking and unlocking commands are not recorded in the transaction DB.
Examples:
|
LOCK Locks the Project DB. LOCK AT LON Locks the Project DB at the remote Location LON. Only available at the Hub of a Global Project or at the administering Location for the Location (in this example, the administering Location for LON). |
Command Syntax:
|
>--- LOCK ------> |
Querying:
>--- Query LOCK --->
Only available at Hub of a Global Project or at the administering Location:
|
>--- Query LOCK ---+--- AT <loc> ---. |
Related Commands: