Administrator Command
Reference Manual
Command Details
:
Detailed Descriptions of Commands
: DELETE (Project definition)
DELETE (Project definition)
Function
:
Deletes elements from the project.
Notes on Deleted Files
When a database is deleted, its file is renamed by addition of the suffix .deleted. The renamed file is actually deleted on the next SAVEWORK or module switch, once the change has been saved in the system or global database.
This arrangement allows database files to be recovered after a crash, by the AVEVA E3D™ exit handler. However, if the exit handler cannot be invoked (for example, due to a loss of power) then the files with the .deleted suffix can be restored manually, to make the project directory consistent with the system or global database.
Description
:
The DELETE command can be used to delete Admin elements.
The DELETE command cannot be abbreviated. This helps protect against accidental deletion. To avoid the risk of database corruption, all deletion of DBs (i.e. the files inside the Project Directory) must be done from the ADMIN module and not by using operating system utilities or commands.
Notes on Global Projects:
You can only delete Teams, Databases, Locations and Groups at the Hub.
Offline locations
:
When a location is deleted, the system administrator must make sure that the system database for that location is deleted from all other locations.
Refer to
Running Global Projects
for further information about
Deleting Databases
and
Using Extracts
from a Global project.
Examples:
DELETE USER
DELETE TEAM
DELETE MDB
DELETE DB
Deletes the current element of the appropriate type.
DELETE DB PIPEN/DESI
Deletes Database PIPEN/DESI
DELETE USER HVAC
Deletes User HVAC
DELETE TEAM PIPEN
Deletes Team PIPEN
DELETE MACRO 7
Deletes inter-db connection macro 7 in current project
DELETE MESSAGE 3
Deletes message 3 in current project
DELETE RUNFILE
Deletes runfile entry for current module.
DELETE STAMP
Deletes the stamp that is the current element.
Global Projects only:
DELETE LOCATION
Deletes the current Location. This will remove the system database file for that location from all other locations. The location may be deleted provided all databases (other than its transaction database) have been deleted.
DELETE LOCATION LON
Deletes Location LON.
DELETE GRP
Deletes the current Location Group.
DELETE LCOMD
Deletes the current communication event.
DELETE WORKING EXTRACT FROM CTATEST/DES1 FOR USERA
Deletes the working extract for USERA from the database
CTATEST/DES1
. Working extracts cannot be deleted unless the owning extract is primary at the currently administered location.
Command Syntax:
>--- DELETE ---+--- USer ------+--- user--------------------------.
| | |
| ‘----------------------------------|
| |
|--- TEam ------+--- team_name --------------------|
| | |
| ‘----------------------------------|
| |
|--- DB --------+--- db_name ----------------------|
| | |
| ‘----------------------------------|
| |
|-- WORKing -+- EXTract --. |
| | | |
| ‘- VARiant --+- FROM dbname FOR user -|
| |
|--- MDB -------+--- mdb_name ---------------------|
| | |
| ‘----------------------------------|
| |
|--- LOCation --+--- code -------------------------|
| | |
| |--- location_name ----------------|
| | |
| ‘----------------------------------|
| |
|--- GRP ------------------------------------------|
| |
|--- LCOMD ----------------------------------------|
| |
|--- MESSage n ------------------------------------|
| |
|--- MACro n --------------------------------------|
| |
|--- RUNFile --------------------------------------|
| |
|--- STAMP ----------------------------------------|
| |
| .--------<-------. |
| / | |
‘--- MOdule ----*--- integer ------| |
| | |
‘--- module_name --+---------------+-->
Note:
Locations, GRPs and LCOMDs exist in Global Projects only.
1974 to current year.
AVEVA Solutions Limited and its subsidiaries. All rights reserved.