AVEVA™ Engineering

CREATE (Project Definition)

Save PDF

TABLE OF CONTENTS

CREATE (Project Definition)

Save PDF

Last UpdatedJan 30, 2025
7 minute read

Function:

Creates Users, Windows NT authenticated users, Teams, Databases (DBs) (including extracts) and MDBs.

Description:

Update DBs can be accessed by one writer and many readers. All AVEVA base product DBs can be update.

Multiwrite DBs can be accessed by many writers and many readers. Model, Catalogue, Draft and Isodraft DBs can be multiwrite.

Multiwrite DBs can have their claim mode set to IMPLICIT, in which case any element that 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 module.

In addition, both types of DBs can be controlled, which means that access will be controlled by an external System.

The administrator can create extract DBs from Standard (Master) multiwrite DBs. Extract DBs can be Standard extracts or working extracts, and in addition, both Standard and working extracts can be variant extracts. Examples of creating the different types of extracts, and the full syntax, are given here. For general information about using extracts in Projects, refer to Multi-write Databases and Extracts.

Before a newly created extract can be used at a Satellite, all its owning extracts must have been allocated there. If the immediate parent extract is secondary at the Satellite and there are no scheduled updates, it should have been synchronised since the new extract was created.

Note:
When the daemon is used to create an extract in a Global Project, the CREATE EXTRACT command includes a recovery operation to restore the Primary Location of the DB in the event of failure of the command, prior to its ALLOCATE operation. Therefore, the PREVOWNER command is not usually needed after a failure of CREATE EXTRACT. However, the CREATE ALLOCATE operation does not have an automatic recovery operation and, in the unlikely event of this failing, PREVOWNER may be needed.

In a Global Project, the administrator can only create Teams and MDBs at the Hub. Extracts can be created at any authorized Location. Working extracts can only be created at Locations where the owning extract DB is Primary.

Offline Locations:

Working extracts cannot be created at an offline Location that is administered by the Hub. The offline Location must be locally administered.

Authorized Locations:

A Location is authorized to create extracts (for itself or an administered Location) if its NOEXTC attribute is false. The Project Hub is always authorized to create extracts.

Examples:

Creating Teams, Users and MDBs

CR TEAM PIPING

Creates the Team PIPING.

CREATE USER RAB/ROB

Creates User RAB with password ROB, default access rights.

CRE US HHJ/MICK FREE

Creates User HHJ with password MICK, free access rights.

CR MDB /STEEL

Creates the MDB /STEEL.

CR USER ‘FRED.BLOGGS1’/ABC

Creates User ‘FRED.BLOGGS1’ (non-alphabetic usernames are valid).

CR AUTHUSER NAME

Creates an NT authenticated user which should be the name of a valid Windows user.

Creating Master DBs

Note:
If the SET TEAM command has not been used to set the current teamid, then the DB Name must be prefixed by the name of the Team which owns it.

CREATE DB PIPING/PIPEDB DESI

Creates the Design DB PIPING/PIPEDB.

CREATE DB STEEL/STEELDB DESI ACC MULTIW CLAIM EXPL

Creates the multiwrite Design DB STEEL/STEELDB, with EXPLICIT claim mode.

CREATE DB STEEL/STEELDB DESI ACCESS MULTIWRITE DBNO 901

Creates the multiwrite Design DB STEEL/STEELDB, DB Number (NUMBDB attribute) 901.

CREATE DB STEEL/STEELDB DESI DBNO UNIQUE

Creates the Design DB STEEL/STEELDB, using the next available number within the Project DB range.

CREATE DB TEST/TESTDESI FINO 500

Creates the DB TEST/TESTDESI with the given file number (FINO attribute). By default, the file number will be set to 0, and the file name of the DB file will be derived from the DB Number.

Using the default is recommended, particularly if the administrator is using extracts. If the administrator sets the file number explicitly, the extract file name will still be derived from the DB Number (NUMDB attribute), and so the consistency of file names within an extract family will be lost.

CREATE DB TEST/TESTDESI FINO 0

Creates the DB TEST/TESTDESI with the file number (FINO attribute) of the given DB set to 0. This command can be used to update DB files to the new convention, which will keep extract file names consistent within an extract family.

CREATE DB PIPE/PIPEEB DESI IN AREA 501

Creates the Design DB PIPE/PIPEEB in AREA 501.

CREATE DB PIPE/PIPEEB DESI PASSWORD ‘ABCDE’

Creates the Design DB PIPE/PIPEEB with password 'ABCDE'.

Setting the PROTECTION parameter will disallow copying extraction of data between Projects or Users which are not members of the protected DB. An optional expiry date may be specified.

CREATE dbname PROTection [ ON | OFF ] [EXPires future-date ]

CREATE DB ELEC/ELECDRAWINGS PADD PRODUCT |Engineering| ACCESS MULTIWRITE

Creates a Draft DB for use in Engineering product for electrical drawings.

Creating Standard Extracts

CREATE EXTRACT PIPING/PIPE-X1 FROM PIPE/PIPEDB

Creates the extract PIPING/PIPE-X1 from the DB PIPING/PIPEDB.

CREATE EXTRACT ADMIN/PIPE-X1 FROM PIPE/PIPEDB

Creates the extract ADMIN/PIPE-X1 from the DB PIPING/PIPEDB.

Note:
The extract can be owned by a different Team from its owner.

CREATE EXTRACT PIPING/PIPE-X1 FROM PIPE/PIPEDB EXTNO 100

Creates the extract PIPING/PIPE-X1 with the extract number 100 from the DB PIPING/PIPEDB.

Creating a Master DB above an existing Master DB

CREATE MASTER PIPING/PIPE-X1 ABOVE PIPE/PIPEDB

Creates a new MDB PIPING/PIPE-X1 above the existing MDB PIPING/PIPEDB. This means that PIPE/PIPEDB is now a child extract of the new master PIPING/PIPE-X1.

Creating Working Extracts

Working extracts can only be created from a DB that is Primary at the current Location.

CREATE WORKING EXTRACT FROM DB PIPING/PIPEDB FOR USERA

Creates a working extract from PIPING/PIPEDB for USERA.

CR WORK EXTR FROM DB PIPING/PIPEDB FOR USERB EXTNO 21

Creates a working extract from PIPING/PIPEDB for USERB with extract number 21.

Creating Variant Extracts

CREATE VARIANT TEST/PIPE-V1 FROM PIPING/PIPEDB

Creates Design DB PIPING/PIPEDB.

Creating Extracts for a Satellite

CREATE EXTRACT PIPING/PIPE-X1 FROM PIPE/PIPEDB AT LON

Creates an extract PIPING/PIPE-X1 from DB PIPING/PIPEDB at Satellite with LOCID LON.

Creating Transaction DBs (Global Projects only)

CREATE DB TRANSACTION/LON

Creates a transaction DB for Location with LOCID LON.

Note:
The omission of the DB type. Transaction DBs have a special naming convention which associates them automatically with the Location. This DB is automatically created with the correct Primary Location. These are created as OVERWRITE DBs.

Command Syntax:

DBs:

>- CReate DB teamid/dbname -+- CATA -. \| \| \|- DESI -\| \| \| \|- ISOD -\| \| \| \|- PROP -\| \| \| \|- PADD -\| \| \| ‘- DICT -+- IN AREA n -. \| \| ‘-------------+--> cont cont >-- PRODuct –- productText ---> cont cont >-- ACCess -+- UPDATE -----. \| \| +- CONTRolled -. \| \| ‘- MULTIWrite -+- CLAIM -+- EXPLicit -\| \| \| ‘- IMPLicit -+--------+-> cont cont > - PROTection -+--- ON -+----------------------\| \| \| \| \| ‘-EXPires future date -\| \| \| ‘--- 0FF------------------------+--------+-> cont cont > - PASSword -+--- ‘password’ -+----------------------\| cont >---+-- EXTNO n -. \| \| ‘------------+- DBNO n -. \| \| ‘----------+-- FINO n --. \| \| ‘------------+-- DESC text --. \| \| ‘---------------+--->
userid and teamid	These are alphanumeric character strings up to 50 characters long. The following characters should be avoided:-\|’@$/*.
passwd	The passwd is an alphabetic character string up to fifteen characters long.
name	The name is a normal AVEVA base product name consisting of a slash (/) followed by up to 31 alphanumeric characters.
dbname	The dbname is a 32-character name.
productText	This is a text value giving the name of the product to be associated with the DB, eg. Engineering, E3D, Diagrams.

Extracts:

>- CReate MASTER team/db ABOVE team/db ----> cont

>- CReate ---+--- EXTRact ---.
| |
‘--- VARiant ---+--- team/db FROM team/db ----> cont

>- CReate EXTRact team/db FROM team/db -+-------------------.
| |
‘- AS AT SESSION n -+--> cont

>- CReate VARiant team/db FROM team/db --------------------> cont

>- CReate WORKing EXTRact FROM team/db FOR user ----------> cont

Standard Projects:

cont >--------+- EXTNO n -.
              |           |
              ‘-----------+- DESC text -.
                          |             |
                          ‘-------------+-->

Global Projects:

The REFBLOCKS option is used to allocate a block of reference numbers. By default, one REFBLOCK will be assigned to the extract. More reference blocks may be required if many Users are creating elements.

The AT <loc> option allows the Hub or an administering Location to create an extract DB whose Primary Location is at the specified Satellite.

Transaction DBs (Global Projects only):

>- CReate DB TRANSACTION/name ------------cont >

The name must be the LOCID of a valid Location.

Users, Teams and MDBs:

>- CReate -+- USer userid passwd -+--- FRee ------.
           |                      |               |
           |                      ‘--- GEneral ---|
           |                                      |
           |- TEam teamid ------------------------+-- DESC text ---.
           |                                      |                |
           |                                      ‘----------------|
           |                                                       |
           ‘- MDB name --------------------------------------------+->

Authenticated User:

>- CR/EATE --- AUTHUSER --- authuser --->

Querying:

>--- Query --+-- USer userid ---.
             |                  |
             |-- DB dbname -----|
             |                  |
             |-- MDB name ------|
             |                  |
             |-- Authuser ------|
             |                  |
             ‘-- TEam teamid ---+-->

Related Commands:

SET (Project definition and Global Project Administration)

MODULE (Module Definition), CHANGE (Project definition)

NEW (Project definition and Global Project Administration)

AVEVA™ Engineering