CREATE (Project definition)

Administrator Command Reference Manual

Command Details : Detailed Descriptions of Commands : CREATE (Project definition)

CREATE (Project definition)

Creates USERs, Windows NT authenticated users, TEAMs, Databases (including Extracts) and MDBs.

Update databases can be accessed by one writer and many readers. All AVEVA E3D™ databases can be update.

Multiwrite databases can be accessed by many writers and many readers. MODEL, CATALOGUE, DRAFT and ISODRAFT databases can be multiwrite.

Multiwrite databases 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 Database can be controlled, which means that access will be controlled by an external system.

You can create Extract databases from standard (Master) multiwrite databases. Extract databases 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 Multiwrite Databases and Extracts in the Administrator User Guide; for information about using extracts in Global projects, refer to Merging Databases in Running Global Projects.

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 database 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, you can only create Teams and Master Databases at the Hub. Extracts can be created at any authorised location. Working Extracts can only be created at locations where the owning extract database 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.

Authorised locations:

A location is authorised to create extracts (for itself or an administered location) if its NOEXTC attribute is false. The Project hub is always authorised to create extracts.

Creating Teams, Users and MDBs

Create Team PIPING

CREATE USER RAB/ROB

Create User RAB with password ROB, default access rights

CRE US HHJ/MICK FREE

Create User HHJ with password MICK, free access rights

Create MDB /STEEL

CR USER ‘FRED.BLOGGS1’/ABC

Creates user ‘Fred.Bloggs1’ (Non alphabetic user names are valid)

CR AUTHUSER NAME

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

Creating Master Databases

Note:

If the SET TEAM command has not been used to set the current teamid, then the dbname must be prefixed by the name of the team which owns it.

CREATE DB PIPING/PIPEDB DESI

Create Design database PIPING/PIPEDB

CREATE DB STEEL/STEELDB DESI ACC MULTIW CLAIM EXPL

Create multiwrite Design DB STEEL/STEELDB, with explicit claim mode.

CREATE DB STEEL/STEELDB DESI ACCESS MULTIWRITE DBNO 901

Create multi-write Design DB STEEL/STEELDB, database number (NUMBDB attribute) 901.

CREATE DB STEEL/STEELDB DESI DBNO UNIQUE

Create Design DB STEEL/STEELDB using the next available number within the project database range.

CREATE DB TEST/TESTDESI FINO 500

Create the database TEST/TESTDESI with the given Filenumber (FINO attribute). 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.

CREATE DB TEST/TESTDESI FINO 0

Create the database TEST/TESTDESI with the Filenumber (FINO attribute) of the given database set to 0. This command can be used to update database files to the new convention, which will keep Extract filenames consistent within an Extract family.

CREATE DB PIPE/PIPEEB DESI IN AREA 501

Create Design DB PIPE/PIPEEB in area 501

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.

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

Creating Standard Extracts

CREATE EXTRACT PIPING/PIPE-X1 FROM PIPE/PIPEDB

Create an extract PIPING/PIPE-X1 from database PIPING/PIPEDB

CREATE EXTRACT ADMIN/PIPE-X1 FROM PIPE/PIPEDB

Create an extract ADMIN/PIPE-X1 from database 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

Create an extract PIPING/PIPE-X1 with extract number 100 from database PIPING/PIPEDB.

Creating a Master Database above an existing Master Database

CREATE MASTER PIPING/PIPE-X1 ABOVE PIPE/PIPEDB

Create a new master database PIPING/PIPE-X1 above existing master database 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 database that is primary at the current location.

CREATE WORKING EXTRACT FROM DB PIPING/PIPEDB FOR USERA

Create a working extract from PIPING/PIPEDB for USERA

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

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

Creating Variant Extracts

CREATE VARIANT TEST/PIPE-V1 FROM PIPING/PIPEDB

Create Design database PIPING/PIPEDB

Creating Extracts for a Satellite

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

Create an extract PIPING/PIPE-X1 from database PIPING/PIPEDB at satellite with LOCID ‘LON’

Creating Transaction Databases (Global projects only)

CREATE DB TRANSACTION/LON

Create transaction db for location with LOCID ‘LON’. Note the omission of the database type. Transaction databases have a special naming convention which associates them automatically with the location. This database is automatically created with the correct primary location. These are created as OVERWRITE databases.

Command Syntax:


>- CReate DB teamid/dbname -+- CATA -. \| \| \|- DESI -\| \| \| \|- ISOD -\| \| \| \|- PROP -\| \| \| \|- PADD -\| \| \| ‘- DICT -+- IN AREA n -. \| \| ‘-------------+--> cont cont >-- ACCess -+- UPDATE -----. \| \| +- CONTRolled -. \| \| ‘- MULTIWrite -+- CLAIM -+- EXPLicit -\| \| \| ‘- IMPLicit -+--------+-> cont cont > - PROTection -+--- ON -+----------------------\| \| \| \| \| ‘-EXPires future date -\| \| \| ‘--- 0FF------------------------+--------+-> cont cont >---+-- EXTNO n -. \| \| ‘------------+- DBNO n -. \| \| ‘----------+-- FINO n --. \| \| ‘------------+-- DESC text --. \| \| ‘---------------+--->


userid and teamid	are alpha numeric character strings up to 50 characters long. The following characters should be avoided:-\|’@$/*. passwd is an alphabetic character string up to fifteen characters long.
name	is a normal AVEVA E3D™ name consisting of a slash (/) followed by up to 31 alphanumeric characters.
dbname	is a 32-character name.


>- 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 cont >---+- IN AREA n -. \| \| ‘-------------+- CONTROL -. \| \| ‘-----------+- CLAIM -+- IMPLicit -. \| \| \| \| ‘- EXPLicit -\| \| \| ‘----------------------+--> cont Standard projects: cont >--------+- EXTNO n -. \| \| ‘-----------+- DESC text -. \| \| ‘-------------+--> Global projects: cont >-+- EXTNO n -. \| \| ‘-----------+- AT <loc>-. \| \| ‘-----------+- REFBLOCKS n -. \| \| ‘----------------+- DESC text -. \| \| ‘-------------+->

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. Refer to Using Extracts with Global Projects for further information.

The AT <loc> option allows the Hub or an administering location to create an extract database whose primary location is at the specified satellite.

Transaction Databases (Global projects only)


>- CReate DB TRANSACTION/name ------------cont > cont >--+-- EXTNO n -. \| \| ‘------------+- DBNO n -. \| \| ‘----------+-- FINO n --. \| \| ‘-------------+-- DESC text --. \| \| ‘---------------+--->

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 --->


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

Related Commands:

SET, MODULE, CHANGE, NEW, LIST AUTHUSER, USERADD TO, USERREM/OVE FROM, AUTHUSERREMOVE, AUTHENTICATION

1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.