Professional Documents
Culture Documents
ADMIN Command Reference Manual
ADMIN Command Reference Manual
PLEASE NOTE:
AVEVA Solutions has a policy of continuing product development: therefore, the
information contained in this document may be subject to change without notice.
AVEVA SOLUTIONS MAKES NO WARRANTY OF ANY KIND WITH REGARD TO
THIS DOCUMENT, INCLUDING BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE.
While every effort has been made to verify the accuracy of this document, AVEVA
Solutions shall not be liable for errors contained herein or direct, indirect, special,
incidental or consequential damages in connection with the furnishing, performance or
use of this material.
This manual provides documentation relating to products to which you may not have
access or which may not be licensed to you. For further information on which Products
are licensed to you please refer to your licence conditions.
All rights reserved. No part of this document may be reproduced, stored in a retrieval
system or transmitted, in any form or by any means, electronic, mechanical,
photocopying, recording or otherwise, without prior written permission of AVEVA
Solutions.
The software programs described in this document are confidential information and
proprietary products of AVEVA Solutions or its licensors.
For details of AVEVA's worldwide sales and support offices, see our website at
http://www.aveva.com
AVEVA Solutions Ltd, High Cross, Madingley Road, Cambridge CB3 0HB, UK
Revision History
Date
Version
Notes
March 2003
11.5
Sept 2004
11.60
June 2005
11.6.SP1
Revision History-i
Revision History
Revision History-ii
Contents
1
1.1
1.2
Macros .........................................................................................................................1-1
How to Use This Manual..............................................................................................1-2
2.1
2.2
DICE Errors..................................................................................................................2-1
DICE Commands .........................................................................................................2-2
Reconfiguration............................................................................................. 3-1
3.1
3.2
3.3
3.4
3.5
3.6
3.7
3.8
3.9
3.10
3.11
3.12
3.13
3.14
3.15
3.16
3.17
Contents-i
Contents
4.1
4.2
5.1
5.2
5.3
5.4
5.5
5.6
5.7
5.8
5.9
6.1
6.2
6.3
6.4
6.5
6.6
6.7
6.8
6.9
Contents
Contents -iii
Contents
Index ...........................................................................................................................1
Contents-iv
1 Introduction
This manual describes the PDMS ADMIN commands for Standard (non-global) and
Global projects. It is written for System Administrators who are already experienced
ADMIN users and who wish to write macros or use command input, rather than the
GUI.
The content of this manual is based on the assumption that you are already familiar
with the concepts that a PDMS System Administrator needs to understand. If you are
not familiar with these concepts, you should refer to the relevant user guide, as follows:
VANTAGE PDMS ADMIN User Guide, which tells you how to set up and
administer PDMS projects using the GUI. The User Guide also describes the
concepts that PDMS System Administrators need to understand.
Using Plant Design Global via the GUI is described in the VANTAGE Plant
Design Global User Guide, which also describes the concepts in Plant Design
Within the manual, commands that are only available in Plant Design Global are
labelled as Global Project Administration Commands. Some of these commands are
only available at the Hub of a Global Project, and this is also shown. Some options in
standard commands are only available in Global Projects and these options are also
indicated by 'Global' in associated text.
This manual also describes how to use DICE, the PDMS Data Integrity Checker, outside
PDMS, as there is no GUI for the stand-alone module. It also describes database
reconfiguration, which is also a command line or macro operation.
1.1 Macros
Most people who read this manual will be writing macros, either to run into PDMS
when required, for example, to create a new project, or as part of customising the
ADMIN interface.
There are some commands in ADMIN which automatically create simple PDMS macros.
These are command files which can be read back into PDMS. In particular, you can use
the REPLICATE command to create a macro which will replicate a project.
For information about writing more complicated macros using the PDMS Programmable
Macro Language, (PML), see the VANTAGE Plant Design Software Customisation
Guide and the VANTAGE Plant Design Software Customisation Reference Manual.
1-1
Introduction
1-2
2 Stand-Alone DICE
The PDMS Data Integrity Checker (DICE) can be run as a stand-alone program outside
PDMS. This may be necessary if the System database has been corrupted, and you
cannot enter PDMS.
Stand-alone DICE is started up using the script named dop, supplied in the PDMSEXE
directory. Give the following command, outside PDMS:
$PDMSEXE/dop
For a summary of the commands that you can use in DICE, see the Data Integrity
Checking commands in 6, Command Summary.
Commands to exit from DICE in stand-alone mode are:
STOP
FINISH
You can send the reports generated by DICE to a named file in your working directory
using the ALPHA command.
This file will contain error messages referring to the operation of DICE
itself, not any errors DICE has found during the checking process
The default name of the message file can be found from the entry for DICE in the
current version of makmac.mac, the project configuration macro.
2-1
Stand-Alone DICE
ERRORFILE
MODE
MAXERRORS
MAXWARNINGS
STATISTICS
You can send the reports generated by DICE to a named file using the ALPHA
command.
You can check one or more DB files by using the CHECK command. In this mode, you
can only refer to databases by their external filenames rather than by their internal
PDMS DB names. Up to ten files may be specified in a single command.
Note:
2-2
3 Reconfiguration
PDMS RECONFIGURER is run from within ADMIN, but only by using the command
line.
In order to understand why database reconfiguration may be necessary, and to
appreciate the steps involved, it is helpful to have some knowledge of PDMS database
structures and their management. For a summary of this information, including an
explanation of DDLs (Database Description Languages) and DABACON (the DAtaBAse
CONtrol program), read the chapter The PDMS Database Management System in the
VANTAGE PDMS ADMIN User Guide.
Only existing elements are copied to the intermediate files; deleted items and
corrupt data are ignored. The destination database created from these files is
therefore both compact and uncorrupted.
The reference and non-reference attributes of the elements are held in different
intermediate files. The method of transfer of data to the destination database
ensures that all referencing is complete and consistent.
The source and destination databases may have different DDLs. This enables
existing data to be restructured to conform to a new database structure and so, for
example, to be used with a new version of PDMS.
A similar technique is used to convert whole projects to new versions of PDMS, though
in this case the intermediate files need not be decoded.
3-1
Reconfiguration
3-2
Reconfiguration
PASS 2 - Phase 1
PASS 2 - Phase 2
The second intermediate file is read and its contents used to set
all reference attributes in the destination DB and to perform
insertion operations.
The reason for the two phases is that references in the source DB may refer to elements
lower down in the hierarchy. It is necessary, therefore, to create all elements in the
destination DB before trying to set references to any of them.
Since the two passes perform independent and consecutive operations, the process can
be interrupted after Pass 1 has been completed, with Pass 2 being run later.
Reconfiguration has four basic steps:
1.
2.
3.
Specify which parts of the source data are to be copied to the destination.
4.
3-3
Reconfiguration
3-4
Reconfiguration
Note that you must use RCFCOPY ALL if you intend to use the RECONFIGURE
SESSIONS command at the next step, as the SESSIONS option is not valid if you only
carry out partial reconfiguration.
Use the SAMEREF option to ensure that the same reference numbers are maintained
after reconfiguration. See Section 3.5, Using the SAMEREF Option, for details.
Use the SESSIONS option to ensure that the session information stays the same
after reconfiguration. See Section 3.6, Using the SESSIONS Option for details.
The following messages are typical of the output during a completely successful
reconfiguration:
3-5
Reconfiguration
3-6
Reconfiguration
session number, username and original date stays the same after reconfiguration, you
can use the command:
RECONFIGURE SESSIONS
The option is not valid for SYSTEM, or GLOBAL DBs, and is not available for a partial
reconfiguration.
The following example illustrates the use of the SESSIONS option:
FROM DB CTBATEST/DESI
TO FILE /A /B
RCFCOPY ALL
RECONFIG SESSIONS
After reconfiguration, data can be read back in from the file using the existing
commands, replacing the original DB data. When reading in data, the DB number and
extract number must be the same as the originating DB number and extract number.
For example:
FROM FILE /A /B
TO DB CTBATEST/DESI
RECONFIG
The SAMEREF option is assumed when reading the data. If errors occur, the data is not
saved. If you want the data saved even if errors occur, use the FORCE option. For
example:
FROM FILE /A /B
TO DB CTBATEST/DESI
RECONFIG FORCE
=42/205
3-7
Reconfiguration
For a Satellite System database, the primary location may be at the Satellite itself,
or it may be at another Satellite, or at the Hub. The RECONFIGURE command
reconfigures the currently open System database. At a Satellite, the command can
therefore operate either on the local System database, or on another Satellites
System database which is primary at the local Satellite.
BRIEF
FULL
In VB (Very Brief) mode, a message is output as each element in the copy list is
successfully created. If the copy command was RCFCOPY ALL, then a message is output
for each element successfully copied into the World of the destination DB.
In BRIEF mode, all information output in VB mode is given, plus messages describing
any errors that have occurred due to DDL changes.
In FULL mode, all information output in BRIEF mode is given, plus a log of all elements
successfully created and named. Note that FULL mode is very verbose and its use is not
generally recommended.
The default is BRIEF mode.
An upper limit may be set on the number of errors that are acceptable during Pass 2 of a
reconfiguration using the ERRORS command. For example:
ERRORS 50
3-8
Reconfiguration
-1
3.10.1
Copies..
A copy of a DB can be made by using the RCFCOPY command. For example the
following command: will create a copy of the existing DB PIPEA/PIPEA in the new DB
ADMIN/TEST.
RCFCOPY PIPEA/PIPEA ADMIN/TEST
The key features of copies are:
All copies of DBs have the same DB number. This may be seen by using the LIST
FILES command. For example:
MASTER/DES
DESI
NUMBER 14
PIPEA/PIPEA DESI
NUMBER
ADMIN/TEST
DESI
NUMBER
USER/DRAFT
PADD
NUMBER
The contents of all copies are identical with respect to both data and structure.
Any given element has the same reference number in each copy.
A DB may have any number of copies, but copies may not exist in the same MDB.
3.10.2
Reconfigured Copies
3-9
Reconfiguration
A reconfigured copy has a different DB number from that of the source DB.
In the reconfiguration process, the destination DB becomes a reconfigured
copy of the source DB, but the reverse is not true. The relationship exists in
one direction only.
The contents of a reconfigured copy are an edited version of those of the
source DB.
Any given element will have a different reference number in the reconfigured
copy from its reference number in the original DB (unless you use the same
SAMEREF option).
3.11.1
A DB often contains elements which have reference or reference array attributes which
point into other DBs. For example, one Design DB could contain a Branch connected to a
Nozzle in another Design DB. The HREF (or TREF) attribute of the Branch would point
into the second DB and the CREF attribute of the Nozzle would point back into the first
DB. See example below:
HREF /E1-N2
Branch /150-B1
DESIGN DB 1
CREF /150-B1
Nozz /E1-N2
DESIGN DB 2
3-10
Reconfiguration
Similarly, references can exist from Design DBs into Catalogue DBs (the SPREF
attribute of a piping component pointing to an SPCOM, for example), but references
cannot exist from a Catalogue DB back into a Design DB.
When a DB is reconfigured without the SAMEREF option, most of the reference numbers
of its elements will change. To maintain the integrity of pointers into the DB from other
DBs, the contents of any DB which might point to elements in the reconfigured DB are
scanned and the reference or reference array attributes are changed to point to the
correct element once more.
For example, assume that the reference number of an SPCOM in a Catalogue DB
changes from =17/3108 in the original DB to =49/2014 in the reconfigured copy. All
piping components whose SPREF attribute was previously set to =17/3108 must have
SPREF reset to =49/2014. Such components might exist in several DBs.
Reference resetting is performed by the RCFUPDATE command described in the next
section.
3.11.2
3-11
Reconfiguration
Old reference
New reference
/VESS1
=123/456
=123/457
/VESS2
=123/457
=123/458
Thus, giving the RCFUPDATE command twice results in the reference =123/456
being reset to =123/458.
RECONFIGURER knows which types of DB can be pointed to by reference attributes in
other types of DB, and so does not attempt to update DBs which could not possibly point
to the latest reconfigured copy. A report is output which lists which DBs were and which
were not updated.
The table of references is maintained across multiple reconfigurations, as long as you do
not exit from ADMIN.
3.11.3
The RCFUPDATE command is usually given immediately after databases have been
reconfigured. The index can be saved to a file when the reconfiguration has been
completed; to be used at a later date.
The commands are DUMP to save to a file, and LOAD to load a file. For example:
LOAD /DUMP1
FROM DB MASTER/DESIGN
TO DB MASTER/DESNEW
RCFCOPY ALL
RECONFIGURE
DUMP /DUMP2
These commands will read an existing reference number index from file /DUMP1, add
the reference number pairs from the specified reconfiguration to it, and then write the
index out again to the file /DUMP2.
If a number of databases have been reconfigured, the dump file will record the crossreference index for all of them.
The LOAD command replaces the current index. The command LOAD APPEND appends
the table to the current index.
3.11.4
The RCFCOPY ALL command copies all the elements in the source DB World into the
destination DB World. If the World of the destination DB already contains members,
then the elements from the source DB are added to these.
The RCFCOPY command can be used to define the root elements to be copied. A root
element is any element owned by the World, that is:
BLTA
GPWL
3-12
Reconfiguration
When a root element is copied, all elements owned by it are also copied. A maximum of
300 root elements may be specified in a single copy list.
The selective commands RCFCOPY CATALOGUE and RCFCOPY SPECIFICATIONS
cause the first root elements of type CATA and SPWL, respectively, to be copied from
the list part of the World in the source DB.
To copy only part of a DB, one or more root elements must be specified (by name or
reference number) in a RCFCOPY command. For example:
RCFCOPY /SITE-A SITE-7
Elements of any other types will be copied into the destination DB as NULL elements,
that is they will be created as floating elements, not owned by any higher-level element.
This does not mean that they are inaccessible. As long as such an element is named (or
you know its new reference number) it can be incorporated as a member of any suitable
parent element by using the INCLUDE command.
If you are not at a top level element, there must be an existing element in the
destination DB into whose list part you wish to incorporate the element being copied.
This is done using the INTO option of the RCFCOPY command. For example:
RCFCOPY /ZONE5A INTO /SITE-3
would copy the Zone /ZONE5A and make it the last member of the Site /SITE-3.
If the intended owning element does not already exist in the destination DB at the
beginning of Pass 2, the listed root element will not be copied. For example:
RCFCOPY /SITE-3 /ZONE5A INTO /SITE-3
is not allowed.
INTO cannot be used when the destination is FILES rather then a DB. The word AND
and the comma (,) may be used as separators to improve readability, thus:
RCFCOPY /SITE-5, /ZONE5A INTO /SITE-3, /SITE-6 AND /SITE-12
Several RCFCOPY commands can be given in sequence to add elements to the copy list.
For example, the sequence
RCFCOPY /SITE-5
RCFCOPY /ZONE5A INTO /SITE-3
RCFCOPY /SITE-6, /SITE-12
is exactly equivalent to the RCFCOPY command in the previous example.
If an element is quoted in the copy list but does not exist in the source DB, an error
message is output and the element is not copied. Since RCFCOPY commands are
additive, a correcting command may be given on the next line. For example:
RCFCOPY /SITE1 /SITE2 /SITR3 /SITE4
(24,16) /SITR3 not found
(error message)
Since SITE1, SITE2 and SITE4 are already in the copy list, all that is needed to add
SITE3 is:
RCFCOPY /SITE3
3-13
Reconfiguration
Note:
3.11.4.1
Partial reconfiguration of PADD DBs is only allowed for picture elements (i.e.
SHEE, BACK, OVER, SYLB, LALB) and above.
Setting External References
In cases where you have made a partial copy of a database, sometimes it is necessary for
you to ensure the external references are correct in the copied elements.
For example, if you moved a piping zone to a different database while maintaining the
references to an equipment zone which was to remain it the original database, the
copied piping zone could have unset external references and the equipment zone would
remain connected to the original piping zone.
In these cases you can use the ALLCONnections option to set the external references for
the reconfigurered elements:
RCFCOPY /SITE1 INTO /SITE2 ALLCONNECTIONS
This will set all references including those within the original database not in the list of
copied elements.
To update the references of the original database to point to the new copied elements
use the RCFUPDATE INTERNAL command described in Section 3.11.2.
3.11.5
Copying Groups
If a Group World is specified in a RCFCOPY command, only the Group World and its
owned Groups are copied. Errors will occur in Phase 2 if the Group members have not be
copied as well.
It is meaningless to try to reconfigure a group on its own.
3-14
Reconfiguration
RCFCOPY ALL
RECONFIGURE
and in the destination project:
FROM FILES /TEMP1 /TEMP2
TO DB /CATNEW
RCFCOPY ALL
RECONFIGURE
Note:
Elements Transferred
Destination DB
CIVIL/STRUC4
ANSI/MASCAT
SITE-A
Whole Design DB
Whole Catalogue DB
One Site
STEEL/MAIN
CATAL/MAIN
EQUIP/MAIN
FROM DB CIVIL/STRUC4
TO FILES /REC2A /REC2B
RCFCOPY ALL
RECONFIGURE
FROM DB VESSEL/V25CT
TO FILES /REC3A /REC3B
RCFCOPY /SITE-A
RECONFIGURE
Creates Catalogue DB
3-15
Reconfiguration
Creates Design DB
RCFUPDATE DB STEEL/MAIN
RCFUPDATE DB EQUIP/MAIN
3-16
Reconfiguration
Note:
The XREF file only indicates those elements which need to be updated. The
DUMP files are still required in order to match the old and new reference
numbers correctly.
When reconfiguring a whole project, it is impossible to order databases of the same type
so that all references are resolved as the reconfiguration proceeds. The XREF and
RESETXREFS commands are needed to tidy up the references.
Note:
3-17
Reconfiguration
Xref /REC5X
Reconfigure
Reset with /REC1X
Resolve db STANA/SAPROP
Reset with /REC2X
Resolve db DEREKF/DFPROP
Reset with /REC3X
Resolve db ALANC/ACPROP
Reset with /REC4X
Resolve db TAMH/THPROP
Reset with /REC5X
Resolve db TAMH/PROP_ATEST
Finish
Output macro
Write Upgrading project CJB
Write From PDMS10 to PDMS11
Write Output phase
$R6
UPGRADE ON
From db STANA/SAPROP
To files /REC1A /REC1B
Copy all
Reconfigure
From db DEREKF/DFPROP
To files /REC2A /REC2B
Copy all
Reconfigure
From db ALANC/ACPROP
To files /REC3A /REC3B
Copy all
Reconfigure
From db TAMH/THPROP
To files /REC4A /REC4B
Copy all
Reconfigure
From db TAMH/PROP_ATEST
To files /REC5A /REC5B
Copy all
Reconfigure
Reconfiguration
complex case it is probable that a number of error messages will also be output,
indicating potential problems in building up an unambiguous structure in the new DB.
3-19
Reconfiguration
3.14.1
The progress-monitoring messages, which indicate the stages reached during the
reconfiguration, are self-explanatory. They are:
*** Pass one initiated ***
*** Pass one completed ***
*** Pass two initiated ***
:
*** Pass two completed ***
***Reconfiguration Completed
After the reconfiguration has been completed, a summary of any problems found during
Pass 2. This will contain zero values where no problems were found.
The format of this report is:
integer
integer
integer
integer
integer
3.14.2
CODE:
TYPE:
OLDREF
The reference number of the element in the source DB (starting with #).
NEWREF:
NAME:
The name given to the element. This applies only if the message is coded
EN to indicate that the element has been named (see next section).
3-20
Reconfiguration
3.14.3
The coded prefix to each message comprises two parts. The first character is one of the
following:
The remaining characters, which give more explicit meaning to the message, are
explained in the following subsections.
Element Created
EN
Element Named
These are output as the reconfiguration proceeds and each message ends with the name
of the copied element.
The element could not, therefore, be created. This can occur when the element type is
not permitted in the list part of the element above it in the DB hierarchy, for example, if
an attempt is made to reconfigure FROM FILES into a DB of the wrong type.
*ENI
An attempt was made to insert the element into a list where it is no longer permitted.
*EL
Element Lost
Elements in the list part of ones that cannot be created are lost, since they cannot be
created either.
followed by one or more other messages giving more information about the error.
RECONFIGURER can be used for the transfer of PDMS DBs between different
computers, which may be of different types. Because reconfiguration is a two-pass
operation, the data can be copied from one computer and read back into a different one.
VANTAGE PDMS ADMIN
Command Reference Manual
Version 11.6SP1
3-21
Reconfiguration
The transfer operation is essentially an extension of the procedure for copying data
between projects, described in Section 3.12. RECONFIGURER makes provision for
translating the coding of the intermediate files to ensure compatibility between the
language requirements of different computers.
An alternative method of transferring data between different computers is to use the
OUTPUT command in Design, Draft, Paragon or Lexicon. For details of other data
transfer methods, see the VANTAGE PDMS DESIGN Reference Manual Part 1
(OUTPUT command).
Binary files are in a compact machine-readable form, but are generally specific to a
particular type of computer.
Character files (which are usually in ASCII code) generally have to be much larger
to hold the same amount of information, but are human-readable. Character files
can be transferred relatively easily between different types of computers.
PDMS DBs are stored as binary files so that large amounts of data can be held
efficiently. RECONFIGURER provides a means to convert PDMS DBs from binary files
into character files and vice versa.
On source machine:
FROM DB MASTER/DESI
TO FORM /F1 /F2
RCFCOPY ALL
RECONFIG
On destination machine:
FROM FORM /F1 /F2
TO DB MASTER/DESI
RECONFIG
3-22
Reconfiguration
The default for reconfiguration is that, when reconfiguring an extract, only changes
made in the extract are output. To output all elements, as in normal reconfiguration, the
keyword FULL must be added to the RECONFIGURE command line. For example:
RECONFIG FULL
3.19.2
The SAMEREF option is always used for extracts. You need not to enter the SAMEREF
option; it is assumed.
This means that you can not reconfigure to DBs of a different DB number.
3.19.3
The SESSIONS option is always used for extracts. You need not enter the SESSIONS
option; it is assumed.
3-23
Reconfiguration
3.19.4
The MERGE CHANGES command will leave sessions referred to by child extracts.
Thus, the resultant file will be larger than it would have been had there been no
extract children.
The alternative approach of deleting and recreating the extract is not possible
unless all child extracts are also deleted and recreated.
3.19.5
Reconfiguring back from files to databases must also be done top-down, and you
must complete the reconfiguration for the whole extract. For example, if you
reconfigure all three database levels of a three level extract to files but only
reconfigure the top two file levels back to databases, the third database will be
corrupted due to the reconfiguration of the other two. For further details, see
section 3.19.7 below.
Before reconfiguring in from a file, the extract must be refreshed from its parent.
3-24
Reconfiguration
1. Refresh TEAMA/EXTRACT.
2. Reconfigure TEAMA/MASTER to file /A, /B.
3. Reconfigure TEAMA/EXTRACT to file /C, /D.
4. REVERT TEAMA/EXTRACT to Session 1.
5. MERGE CHANGES on TEAMA/EXTRACT.
6. REVERT TEAMA/MASTER to Session 2.
7. MERGE CHANGES on TEAMA/MASTER.
8. Reconfigure from file /A, /B to TEAMA/MASTER.
9. Refresh TEAMA/EXTRACT (to pick up changes made in Step 8).
3.19.6
When the RCFUPDATE command is used on an extract, all affected attributes will be
updated regardless of whether or not the element has been claimed to the extract. This
means that, if many extracts of the same extract family are updated, the same changes
will be made to each of the extracts.
3.19.7
3-25
Reconfiguration
FROM DB CTBATEST/MASTER
TO FILE /MASTERA /MASTERB
RCFCOPY ALL
RECONFIG SESSIONS
FROM DB CTBATEST/EXT
TO FILE /EXTA /EXTB
RCFCOPY ALL
RECONFIG SESSIONS
FROM DB CTBATEST/EXTBOT
TO FILE /EXTBOTA /EXTBOTB
RCFCOPY ALL
RECONFIG SESSIONS
FROM FILE MASTERA /MASTERB
TO DB CTBATEST/MASTER
RECONFIG
FROM FILE EXTA /EXTB
TO DB CTBATEST/EXT
RECONFIG
FROM FILE EXTBOTA /EXTBOTB
TO DB CTBATEST/EXTBOT
RECONFIG
It is not necessary for the reconfiguration back from file to be done within the same
session of RECONFIGURER. For example, in a global project where MASTER, EXT
and EXTBOT are primary at different locations, then the following sequence could be
followed:
1. At location A (primary location for MASTER):
FROM DB CTBATEST/MASTER
TO FILE /MASTERA /MASTERB
RCFCOPY ALL
RECONFIG SESSIONS
2. At location B (primary location for EXT):
FROM DB CTBATEST/EXT
TO FILE /EXTA /EXTB
RCFCOPY ALL
RECONFIG SESSIONS
3. At location C (primary location for EXTBOT):
FROM DB CTBATEST/EXTBOT
TO FILE /EXTBOTA /EXTBOTB
RCFCOPY ALL
RECONFIG SESSIONS
Steps 1 to 3, reconfiguring from databases to files, can be done in parallel.
3-26
Reconfiguration
3.19.8
Reconfiguring the Transaction Database in a Global
Project
The Global Daemon stores most of the commands that it is asked to perform at a
location in a transaction database. Each location has its own transaction database. For
details, see Chapter 5, The Transaction Database.
3-27
Reconfiguration
3-28
4-1
/*
WORLD
World
/*S
STAT
Status World
RFWL
Module
World
RUNF
Modules
/*T
TMWL
/*DS
DBSTWL
DBSET
User World
MDB World
TEAM
USER
MDB
Font
World
Font
Files
/*M
MDBW
Team World
FTWL
FNTF
/*U
USWL
Teams
DBLI
DB
Lists
DB
DBs
USLI
User
Lists
MDBs
Users
TMLI
Team
Lists
EXTLI
Extract
Lists
DB
DBs
DB Set
World
DB Sets
DBSTL
DBL
DB List
/*RO
ROWL
/*SC
SCOW
Role
World
Scope
World
ROLE
SCOPE
Roles
PEROP
Perops
Scopes
/*ST
STWLD
/*ACR
ACRW
Stamp
World
STAMP
Stamps
ACR
World
ACR
ACRs
STLST
Stamp List
ACRST
ACR
Groups
ACRL
ACR Lists
DB
DBs
Figure 4-1
The names of the top-level elements (for example, /*S,) are shown, followed by the element type and a short explanation.
4-2
Prjlck false
Prjdesc
unset Project description
Infa unset Project name
Infb unset Project message
Charset
0
Locrf nulref in a non-global project
Hccnt
Extract list changes count
16 character text
Integer =< 999999
120 character text
120 character text
120 character text
Multibyte character set
Integer =< 999999
4-3
4-4
Name /name
Lock false
Owner /name
The User World (USWL)
Attributes
Name /*U
Lock false
Owner /*
/name
false
/*U
/name
General
unset
unset
4-5
4-6
/*
Sets Data Access Control on or off (Standard projects only)
/name
ignore
ignore
ignore
ignore
ignore
ignore
Element Class
Attribute Class
unset
unset
4-7
For example:
ECLASS BRANCH HIERARCHY EQUI HIERARCHY STRU
will include Branch and Equi members, but only STRUs themselves.
4-8
4-9
The Global Locations world element GLOCW, which will own GRPLI elements
which in turn own GRP elements
The Global Stamp World element GSTWLD. If stamps exist in the System
database, they are all copied to the Global Stamp World element and deleted from
the System database.
The attributes of these elements and their members, and the changes to other ADMIN
database elements which occur when a Project is made Global, are described in the
following pages.
The Global database contains information that is common to all Locations running a
Global project. The Global database is readable at all locations but is it can only be
written to at the Hub. Changes to the Global database are propagated to all the other
Locations. This means that the Global database is the same at every Location, except
during the short time changes are being propagated.
Each local System Database contains project information that is specific to the Location.
The local administrator can write to the local system Database. A local System database
is similar to the System database in a non-global Project. The main difference is that
some of the standard ADMIN elements will be redundant. The differences are described
below.
Session information is stored separately in the COMMs database; and the MISC
database stores inter-db macros and messages. The Comms and Misc databases are
local to each Location.
4-10
/*
WORLD
World
/*S
STAT
Status World
RFWL
Modules
World
RUNF
Modules
FTWL
Fonts
World
FNTF
Font
Families
/*DS
DBSTWL
User World
/*M
MDBW
MDB World
USER
MDB
DBSET
/*U
USWL
Users
TMLI
Team
Lists
MDBs
EXTLI
Extract
Lists
DB Set
World
DB Sets
/*RO
ROWL
Role
World
(empty)
/*SC
SCOW
Scope
World
SCOPE
Scopes
/*ACR
ACRW
ACR
World
ACR
ACRs
/*T
TMWL
Team
World
(empty)
ACRST
ACR Sets
/*LC
LCOMW
Comms
World
LCTIML
Event
Timer
LCOMC
LCOML
Daemon
config
Comms
Links
Li
ACRL
DB
DBs
DBSTL
DBL
DB List
LCOMD
Scheduled
Updates
DB
DBs
Figure 4-2
The names of the top-level elements (for example, /*S,) are shown, followed by the element type (for example, STAT) and a short
description, (for example, Status World)
VANTAGE PDMS ADMIN
Command Reference Manual
Version 11.6SP1
4-11
The communications world element in the COMMs database contains the project lock
and isolation flags. The project lock may be set or cleared using LOCK and UNLOCK;
and the Isolation flag may be set true or false using ISOLATION syntax. Both lock and
isolation may be set or queried remotely by the Hub or an administering location.
This means that a report of all Users at every Location in the Project can only
be obtained by combining reports from each Location.
The TMLI list in the USER element in the Local System database will continue to
provide a list of teams to which a user at a particular location belongs.
In the same way that a TEAM element no longer maintains a list of users in that team,
a DB element in a team does not maintain a list of MDBs to which the DB belongs. The
MDB element, in the Local System database keeps a list of DBs belonging to it.
The detailed changes to the elements and attributes are described below.
STAT Element
This element already exists in the Local System database, but certain attributes have
been relocated to the Global System database. The attributes are the same as in a
Standard Project with the addition of:
Locrf text(120)
Note:
When a location is created, the LOCRF attribute in its local system DB will be
set to the reference of its LOC location element in the global system database.
4-12
LCOML Element
The LCOML element contains a list of LCOMD elements, each of which specifies details
about the communications link between the current site and one other site, as described
below.
Attributes:
Name /name
Type LCOML
Lock false
Owner /*LC
LCOMD Element
The LCOMD element contains specific details about the communications link between
the current site and one other site, and controls scheduled updates. There will be one
LCOMD element for each location, which has a communications link with the current
location.
Attributes:
Name
Lock
Owner
Description
Locrf
Timer
Times
Timee
Timei
Timeo
Execb
/name
false
/name
unset
/name
4-13
Execa
unset 120 character text: name of script to be run after updates
are transferred (optional)
The Timer values are:
Minutes past the hour
Hours
Days
Months
Days of the week
0 - 59
0 - 23
1 - 31
1 - 12
0 (Sunday) - 6
For example:
Timer '0,30 * * * *'
LCTIML Element
The LCTIML element is present in a Global project only and has the following functions:
It contains a LEVENL attribute, which sets the time interval for the event loop
for all locations, in seconds.
It contains a list of LCTIMD elements, each of which specifies details about the
event timings between the current site and one other site, as described below.
Attributes:
Levenl
Lmerti
4-14
Lmerfa 3
Lmerdl false
LCTIMD Element
The LCTIMD element contains details about the event timings between the current site
and one other site. There will be one LCTIMD element for each location that
communicates with the current location.
Attributes:
Name
Description
Locrf
Lendti
Lmaxtr
Ltimei
/name
unset
/name
4-15
WORLD
World
/*GS
GSTAT
Global Status
World
GRPLI
Group List
GRP
Groups
LOCLI
Location
List
/*GT
GTMWL
Global
Team World
/*GST
GSTWLD
Global
Stamp
World
ROLE
Roles
TEAM
Teams
STAMP
Stamps
PEROP
Perops
DBLI
DB List
STLST
Stamp
List
/*GRO
GROLW
Global
Role World
/*GL
GLOCWL
Location World
LNKLI
Links List
LOC
Locations
LNK
Links
DB
DBs
DBLOC
Figure 4-3
/*GS
/*
unset Project number:
999999
unset Project description
-370086
Extract list changes count
17 character text
120 character text
Integer =< 999999
GTMWL Element
The Global Team World element GTMWL is named /*GT. Only one /*GT element can
exist in the database. It is the same as the TMWL element, except that:
4-16
Attributes
Name /*GT
Lock false
Owner /*
TEAM Element
Attributes
Name /name
Lock false
Owner
/*GT
Description unset
DB Element
The DB element owns the list element DBLOC which holds four additional attributes
(see DBLOC element, page 4-18). These attributes are attached to the DBLOC element
to facilitate separate claiming of both this element and the owning DB element. This
scheme reduces the contention between the PDMS ADMIN module and the Plant
Design Global daemon.
Attributes
Name /name
Type DB
Lock false
Owner
/name
Stype DESI
File number
Fino n
Area 0
Area number
Daccess
Update
Claimdb
Explicit or Implicit if Daccess is Multiwrite
Description unset
Proj unset (except for Foreign DBs, where it is set to the project code)
Fcpyref
Nulref
Bcpyref
Nulref
n
Extractno
Variant
false
Controlled
false
4-17
DBLOC Element
Attributes
Name /name
Type DBLOC
Lock false
/name DB element
Owner
Locrf /name Name of Primary Location
Prvrf
Name of previous
Primary Location (normally unset)
Propg true Propagation flag
Picfd false Picture file propagation flag
DEALDB Ref Array Indicates locations where db is being de-allocated
4-18
/name
ignore
ignore
ignore
ignore
ignore
ignore
Element Class
Attribute Class
unset
unset
GLOCWL Element
The Global Location World element GLOCWL specifies information about Locations,
Groups and Communications (Links). It is named /*GL and only one /*GL element can
exist in the database. The GLOCWL element consists of the three list elements GRPLI
for groups, LOCLI for locations and LNKLI for links. It has the following attributes:
Attributes
Name /*GL
Lock false
Owner /*
text
Aduuid
Hubrf /name
Prvrf Nulref
NxtHb Nulref
text
Newuid
GRPLI Element
The GRPLI element contains a list of Group elements GRP. A Group is a fully connected
local network of Locations which conceptually form a single node in the Plant Design
Globaltree structure of Locations.
Attributes
Name /name
Lock false
Owner /*GL
GRP Element
The characteristics of each group are defined by a GRP element which has the following
attributes:
Attributes
Name /name
Lock false
Owner
/name
Description unset
Membership of a group is indicated by the attribute GRPRF in each location element
LOC, as described below. The location elements LOC are themselves listed in the LOCLI
element.
4-19
LOCLI Element
The LOCLI element contains a list of all Location elements LOC, including offline
Locations and those which belong to Groups.
Attributes
Name /name
Lock false
Owner /*GL
LOC Element
The characteristics of each Location are defined by a LOC element which has a set of
attributes and a secondary list element DBALL. The DBALL element is a complete list
of all Databases allocated to the Location. It is implemented as a Dabacon secondary list
of DB reference numbers which refer to DB elements under the DBLI list element of
TEAM elements.
Locations which belong to a Group have an attribute GRPRF holding the reference
number of the Group. If this attribute is null then the Location does not belong to a
group. LOC elements also possess a LOCRF attribute which points to the parent of the
Location. This attribute is used to determine paths between Locations in the proposed
tree structure for connecting Locations.
In a future implementation, based on a more general graph structure, the LOCRF
attribute might either be dropped or used for another purpose. A Location is only
recognised as fully initialised when the logical attribute LINIT is true. Other attributes
of a Location are described in the following table.
The LOC element has the following attributes:
Attributes
Name /name
Lock false
Owner
/name
Description unset 120 character text
Locid XXX 3-letter identifier
Rhost rhost name host name
Iconn 1
Connection type:
1 = on-line
0 = off-line
Linit false Initialisation flag
Grprf Nulref Group reference set if
Location is added to a Group
Locrf /name Parent Location
PRMRF
Primary location of system Database. If unset,
(and PRVRF is unset) the Satellite will be
administered locally
PRVRF
Nulref Old primary location (normally unset)
DEALAL
false Indicates that ALL DBs are currently being
de-allocated from this location
4-20
CURLOC
ADMLOC
DBPRIMARY
LOCPRIMARY
Note:
DBALL Element
Attributes
Lock false
Owner /name
LNKLI Element
The LNKLI element contains a list of link elements LNK which specify the connections
between pairs of Locations. Not used at this release.
Attributes
Name /name
Type LNKLI
Lock false
Owner /*GL
LNK Element
Not used at this release.
Attributes
Name /name
Descriptions unset 120 character text
LNKRX
LINKRY
LINKWV
GSTWLD Element
Any existing stamps in the standard System database are copied to the Global Stamp
World element and deleted from the System database.
Attributes
Name /*GST
Lock false
Owner /*
4-21
STAMP Element
Attributes
Name /name
Lock false
Owner /*ST
Desc unset
Func unset
Purp unset
Setdat unset
STLST Element
Attributes
Name /name
Lock false
Owner /name
Stlsf Nulref DB reference
Stsess 0
Session number for DB
4-22
5-1
%TRMSG
%TRYEAR
%TRMONT
%TRDAY
%TRUSER
%TRLOC
%TRINCO
%TROPER
%TROUCO
%TRSLST
%TRFLST
%TRSUCC
%TRFAIL
%TRSUCC
Figure 5-1
5-2
%TRMLST
%TRMESS
%TRFAIL
/*MS
Logical Controls whether Local claim commands are stored
Name of %TRMONT as for year, then slash and month. For example, /2001/MAY
Name of %TRDAY as for TRMONT, followed by slash then date. For example,
/2001/MAY/21
TRYEARs own TRMONTs, TRMONTs own TRDAYs and TRDAYs own TRUSERs.
5-3
The final system TRUSER element is named /TIMEDUPDATES with a single TRLOC
of the local site. This contains commands issued to process the regular timed updates.
TRDAY
TRUSER
TRLOC
/2002/MAR/25 /2002/MAR/25/LOCALDAEMON
../CAM
/2002/MAR/25/REMOTEDAEMON ../OXF
../LON
../HOU
/2002/MAR/25/TIMEDUPDATES ../CAM
/2002/MAR/25/SYSTEM
../CAM
/2002/MAR/25/FRED
../CAM
/2002/MAR/25/ROSE
../CAM
etc
etc
TRINCO
CLAIMetc
CLAIMetc
CLAIMetc
CLAIMetc
UPDATE ALLetc
CLAIMetc
CLAIMetc
CLAIMetc
etc
5-4
NAME
text
TRCNUM
int
Command number
INCSTA
int
COMUID
ref
TRMODU
int
TRLOCL
log
COMSTR
text
ORILOC[3]
text
DESLOC3]
text
PRVLOC[3]
text
AUXLOC[3]
text
SYSLOC[3]
text
DEPCOU
int
DEPEND[*]
ref
DEPTYP[*]
log
DATECR
date
DATEAK
date
NACKN
int
EXTIME[4]
text
DATERD
date
DATECM
date
DATERP
date
NREPLY
int
MSTEXT
text
TRPASS
log
DATEND
date
NREPAK
int
USERST
text
TRDBRF
ref
of Database DB element
TRFINO
int
5-5
TREXTN
int
TRAREA
int
TRSTYP
int
filetype of DB element
TRDBNO
int
dbnumber of DB element
TRDACC
int
INARCO
int
INTARG[*]
int
TRCARG[*]
text
TRVISI
log
Visible or not
DESC[256]
text
User description
5-6
RECEIVED
ACKNOWLEDGED
STALLED
READY
COMPLETE
REPLIED
PROCESSED
REDUNDANT
CANCELLED
TIMEDOUT
text
TRCNUM
int
OUTSTA
int
COMREF
ref
ORILOC[3]
text
DESLOC3]
text
PRVLOC[3]
text
AUXLOC[3]
text
SYSLOC[3]
text
NXTARL[3]-
text
DEPCOU
int
DEPEND[*]
ref
DEPTYP[*]
log
PREOP
ref
DATECR
date
5-7
DATERD
date
DATESN
date
NRETRY
int
MAXTRY
int
WAITIM
int
ENDTIM
date
DATEAK
date
NACKN
int
DATERP
date
DATERK
date
NREPLY
int
MSTEXT
text
TRPASS
log
POPCOD
int
DATEND
date
NREPAK
int
USERST
text
TRDBRF
ref
TRFINO
int
TREXTN
int
TRAREA
int
TRSTYP
int
Filetype of DB element.
TRDBNO
int
Dbnumber of DB element.
TRDACC
int
INARCO
int
5-8
INTARG[*]
int
TRCARG[*]
text
TRVISI
log
Visible or not
DESC[256]
text
User description
READY
STALLED
SENT
ACKNOWLEDGED
REPLIED
COMPLETE
STALLED_POSTOP Post operations could not be created. State will later return
to COMPLETE ready for retry, or to TIMEDOUT.
PROCESSED
REDUNDANT
CANCELLED
TIMEDOUT
5-9
5-10
NAME
text
TRONUM
int
OPSTAT
int
DEPCOU
int
DEPEND[*]
ref
DEPTYP[*]
log
PREOP
ref
DATECR
date
DATERD
date
DATERN
date
NRETRY
int
MAXTRY
int
WAITIM
int
ENDTIM
date
DATESL
date
DATECM
date
MSTEXT
text
TRPASS
log
POPCOD
int
DATEND
date
USERST
text
TRVISI
log
Visible or not.
DESC[256]
text
User description.
READY
STALLED
RUNNING
COMPLETE
STALLED_POSTOP Post operations could not be created. State will later return
to COMPLETE ready for retry, or to TIMEDOUT.
PROCESSED
REDUNDANT
CANCELLED
TIMEDOUT
Successes (TRSUCC) are grouped under Success Lists (TRSLST) and TRMLST.
Failures (TRFAIL) are grouped under Failure Lists (TRFLST) and TRMLST.
5-11
Failures and Successes are propagated back to the originating location as messages as
soon as they are generated and before the full result is handed back. These are finally
stored under TRMLST as TRSUCC and TRFAIL elements.
All the list elements have no user attributes.
A double integer code relating to a PDMS message or error (0,0 if not known or
relevant)
The result of a command (TROUCO) is the sum of all TRSUCC and TRFAIL elements
owned by its operations and output commands. All of these are communicated back to
either the user (if it is a local command) or propagated to the originating site (if it is a
foreign command). In the latter case the compounded errors will appear under the
relevant originating TROUCO operation and hence onwards and upwards.
Whether a TROPER itself is classed as a success is determined by its execute method.
Input Commands are successes if all its operations AND output commands are
successes. An output Command is a success if the input command it spawned returns a
success. Results are only passed on to the generating TROUCO when the input
command is totally finished.
Messages are sent immediately they are generated before waiting for operation or
command conclusion. They go the same route as the result, being compounded by a
5-12
TROUCO and transmitted to other site TROPER elements. They are only stored under
the final TRINCO generated from a USER command.
Attributes for elements %TRSUCC and %TRFAIL
DATEMS
date
MESNUM[2]
int[2]
MSTEXT
text
MSTYPE
int
MESQUA
int
Data qualifier.
MESREF
ref
MSDTXT
text
MSLOC
text
TRCNUM
int
TRONUM
int
TRTYPE
text
5-13
5-14
DATEMS
Date
MESNUM[2]
int[2]
MSTEXT
Text
Message text.
MSLOC
text
MSSENT
log
Unused.
TRCNUM
int
TRONUM
int
TRTYPE
text
6 Command Summary
This chapter lists the ADMIN commands in functional groups. Details of the commands
are given in Chapter 7 in alphabetical order of command name.
ACRADD
ACRREM
ADD
CHANGE
CDESC
CNAME
COPY
CREATE
CURRENT
DADD
DEFER
Makes a DB non-current.
DELETE
DREMOVE
EXCHANGE
EXCLUDE
INCLUDE
NEW
PROJECT
6-1
Command Summary
REPLICATE
REMOVE
SET
TADD
TREMOVE
EXPUNGE
EXTRACT
LOCK
MAXUSERS
MERGE CHANGES
MESSAGE
MOVE
NEW STAMP
REVERT
UNLOCK
6-2
ADMINISTER
ALLOCATE
DEALLOCATE
DUPLICATENAMES
GENERATE
HUBLOCATION
INITIALISE
ISOLATION
MAKE GLOBAL
NEW
Command Summary
PING
PREVOWNER
PURGE
RECOVER
REMOTE
REMOTEMESSAGE
RENEW
REORDER
SET
SYNCHRONISE
SYSTEMLOCATION
TRANSFER
UPDATE
MODULE
FONTFAMILY
6.6 Querying
LIST
QUERY
STATUSSESSION
SYSTAT
6-3
Command Summary
FINISH
GETWORK
SAVEWORK
TERM
CHECKOPTION
Stand-alone:
CHECK
ERRORFILE
Specifies the name of the file containing the error and warning
messages when DICE is used in stand-alone mode.
EXTERNAL
MAXERRORS
MAXWARNINGS
MODE
STATISTICS
STOP
6.9 Reconfiguration
6-4
BRIEF
DUMP
ERRORS
FILE
Command Summary
FROM
FULL
LOAD
RCFCOPY
RCFUPDATE
RCFUPGRADE
RECONFIGURE
Starts reconfiguration.
REINIT
RESETXREFS
TO
UPGRADE
VB
XREF
6-5
Command Summary
6-6
7 Command Details
The commands are described in this chapter in alphabetical order of command names.
The descriptions are usually under subheadings of Function, Description, Examples,
Command Syntax, and Related Commands. The syntax of commands is shown by syntax
graphs. These are discussed in the first two sections. The third section contains the
command descriptions.
Command arguments are shown in lowercase letters. These are just descriptions of
what you need to enter. For example:
FONTDirectory name
means that to set the name of the Font Directory to newfonts, you enter:
FONTD newfonts
Syntax graphs are read from top left to bottom right. The start point is shown by >,
and you can follow any path through the graph until the exit point, shown by >, is
reached.
Points marked with a plus sign (+) are option junctions which allow you to input
any one of the commands to the right of the junction. For example:
7-1
Command Details
means you can type in ABC or PQR or just press Enter to get the default
option.
Text in angle brackets <. . . > is the name of another syntax graph. This convention
is used for syntax which occurs in many places. The graphs referred to are
described at the end of this section. For example:
>----+--- ABC -----.
|
|
|--- PQR -----|
|
|
|--- <dia> ---|
|
|
-------------+--->
means you can type in ABC or PQR or any command allowed by the
syntax given in diagram <dia> or just press Enter to get the default
option.
Points marked with an asterisk (*) are loop back junctions. Command options
following these may be repeated as required. For example:
.-----<-------.
/
|
>---*--- option1 ---|
|
|
|--- option2 ---|
|
|
--- option3 ---+--->
means that you can enter any combination of option1 and/or option2
and/or option3, where the options can be commands, other syntax
diagrams, or command arguments.
The simplified format:
.----<------.
/
|
>---*--- name ----+--->
means that you may type in a list of PDMS names, separated by at least one
space.
7-2
Command Details
A three-letter Word. For example: CAM, the LOCID of a LOC element, where the
LOCID is 3 capital letters.
A PDMS general identifier <gid> which points to a LOC element. For example:
/LOCATION_AAA
<when>
>--+-- BEFORE --.
|
|
`-- AFTER ---+------ <date> --------.
|
|
|------ SESS n --------|
|
|
-- STAMP stampname ---+--->
<date>
>--- time --- day --- month --- year
time is in the format hh:mm where hhx is the hour and mm the minutes. If not given
then the default of 23:59 is taken. There must not be any spaces around the colon.
day will be an integer. If not specified, the current day is taken. The day must be given
if no time was specified.
month can be entered as a word, or as a number separated by a slash. If not given the
year will default to the current year. It may be entered as two or four figures.
Examples:
12:00 21 January 2002
9:30 11 / 1 / 02
10:30
21 / 1 / 2002
21 January
7-3
Command Details
larger typeface.
7-4
Command Details
ACCESS
(Project definition)
Function:
Examples:
ACCESS ADMINUSER FREE DRAFTUSER GEN
Give user ADMINUSER FREE access, user DRAFTUSER GENERAL
access
Command Syntax:
.-------------<-------------.
/
|
>--- ACcess --*-- userid ---*--- FRee ------|
|
|
`--- GEneral ---+--->
7-5
Command Details
ACRADD
(Project definition)
Function:
Description:
The ACR and the ACR Group must already exist, and the ACR
Group must be the current element.
You can then give a list of ACR names to be added to the Group.
Note that ACR Groups cannot contain other ACR Groups.
Examples:
ACRADD /ACR1 /ACR22 /ACR24
Adds the ACRs /ACR1, /ACR22 and /ACR24 to the current ACR Group.
Command Syntax:
.----<-------.
/
|
>-- ACRADD --*--- acrname ---'
|
`--------------------->
7-6
Command Details
ACRREM
(Project definition)
Function:
Description:
The ACR Group must be the current element. You can then give a
list of ACR names to be removed from the Group.
Examples:
ACRREM /ACR1 /ACR22 /ACR24
Removes the ACRs /ACR1, /ACR22 and /ACR24 from the current ACR
Group.
Command Syntax:
.----<-------.
/
|
>-- ACRREM --*--- acrname ---'
|
`--------------------->
7-7
Command Details
ADD
(Project definition)
Function:
Description:
Examples:
ADD STEELN/STEELN 1
Place DB STEELN/STEELN at the head of the current MDB list
Command Syntax:
.-------------<--------------.
/
|
>-- ADD ---*--- dbname ---+--- integer ---|
|
|
---------------+--->
7-8
Command Details
ADMINISTER
Function:
Description:
The Location must have been created using the NEW LOC
command, and its Location identifier must have been set.
For example:
Locid 'AAA'
where /AAA is the identifier of the new Location, and /BBB is the
identifier of the Administering Location, that is, the location
where the System database for the Location will be Primary.
The NEWSYSTEM option is only available at the Hub. It creates a
system database for a new location in the transfer area. (This is
similar to the GENERATE LOCATION command.)
The system database created is a copy of the Hub system
database without MDBs and with only a SYSTEM user. The
Administrator at the Hub can then create Users and MDBs (as
well as Teams and Databases) for the Location before it is set up.
The SYSTEM option is available at the Administering Location,
that is, the location where the System database for the Location is
Primary. This may be the Hub or another Satellite. This
command will close the local system database and open the
appropriate satellite system database. The database will be
opened with Write access unless the READONLY keyword is used.
7-9
Command Details
ADMINISTER (continued)
After the SYSTEM or NEWSYSTEM commands have been given, you
will be able to carry out administration tasks for the remote
location. To return to administering your own (current) Location,
give the command ADMINISTER LOCAL. To return to administering
the last system database which was open, give the command
ADMINISTER SAME.
Any location may issue an ADMINISTER command for another other
locations system database. If the system database is not Primary,
then the system database will be opened READONLY.
Once you have selected a remote system database, you can give
most ADMIN commands, which will operate on the remote
Location. In particular, the following commands can be used for
housekeeping tasks on the remote System Database:
EXPUNGE SYSTEM
MERGE CHANGES SYSTEM
CHECK SYSTEM
RECONFIGURE SYSTEM
The Hub will not be allowed to REPLICATE the project when it is
administering a remote location, since the wrong system database
will be replicated. However REPLICATE SYSTEM commands (which
generate macros to replicate the project structure) will still be
valid.
The administered location will still be able to lock or isolate the
project locally. It will also be able to administer its primary
constructor databases by using the REMOTE <loc> command,
where <loc> is its own location identifier, followed by one of the
normal commands:
EXPUNGE
BACKTRACK
MERGE CHANGES
REVERT
CHECK
Reconfiguration will also be possible provided that suitable
databases are primary at the location.
7-10
Command Details
ADMINISTER (continued)
Examples:
ADMINISTER NEWSYSTEM /Cambridge
ADMINISTER NEWSYSTEM 'CAM'
Allows the Hub Administrator to create data (Users, MDBs etc) for a
Location in the transfer directory.
ADMINISTER SYSTEM /Cambridge
ADMINISTER SYSTEM 'CAM'
Allows any System Administrator to read the System Database for
Cambridge. Only the Administrator at the Location where the
Cambridge System Database is Primary will have write access to it.
ADMINISTER SYSTEM SAME
Allows a System Administrator who is administering other Locations
to open the last System database opened.
ADMINISTER SYSTEM LOCAL
Allows a System Administrator who is administering other Locations
to open the local System database.
ADMINISTER SYSTEM AT /Cambridge
ADMINISTER SYSTEM LOCAL READONLY
This is equivalent to entering the ADMIN module as ADMIN
READONLY.
Command Syntax:
>-- ADMINISTER --+--- NEWSYSTEM <loc> -----------------------------.
|
|
`--- SYSTEM ------+-- AT <loc> ---.
|
|
|
|
|--- SAME -------|
|
|
|
|
`--- LOCAL ------+--- READONLY --|
|
|
`---------------+--->
Querying:
7-11
Command Details
ALLOCATE
Function:
Description:
Each Location has a list of databases that are allocated to it. The
ALLOCATE command adds a database to this list. A named
database or all databases can be specified. The allocation can be
deferred until a given time. The databases must already exist at
the Hub.
The Hub sends its own copy of the database, or that of the
Locations parent, to the Location. This is not necessarily the most
up-to-date copy. Note that the Database will also be allocated to
all ancestors of the Location, if it is not already allocated to them.
When a DRAFT Database is allocated, the picture files are not
automatically copied with it. They will arrive with the next
update.
By default, the allocated databases will be Secondary, but you can
specify that they will be Primary. If a database already exists at a
location, you can change its Primary/Secondary status using the
CHANGE command.
Several Databases can be allocated in the same operation using
the ALLOCATE command.
In order for an extract database to be used at a satellite, all
owning extracts must also have been allocated there.
Offline Locations
The ALLOCATE PRIMARY option cannot be used. Use
ALLOCATE followed by CHANGE PRIMARY. The date option is
not allowed.
Note that ALLOCATE should be followed by a TRANSFER
command to copy the database to the location. The CHANGE
PRIMARY command should not be issued until this has been
done.
Using macros to Allocate Databases
You will probably use a macro for long lists of databases
allocations, for example, when a project is first set up.
The allocation process may take some time if there is a slow link
between Hub and Satellite and/or if databases sizes are large.
Note that if a de-allocation is in progress, then the allocation will
stall until the de-allocation is complete before commencing.
7-12
Command Details
ALLOCATE (continued)
Make sure that you do not try to allocate a database to the same
location twice. If the allocation appears to have failed, check the
transaction databases at both the Hub and the Satellite before
attempting to repeat the command.
To check that the allocation has been successful, GETWORK and
then navigate to the LOC element. Navigate to its DBALL
(allocation list) member, and query its members. Wait until the
DBALL element at both the Hub and the Satellite lists all the
allocated databases before continuing.
Note: If the transaction database for a location is being allocated,
this command is not recorded in the transaction database. It is
not normally necessary to allocate it or change its primary
location explicitly.
Note: The OVERRIDE PROPG option cannot be used with a
deferred time.
Examples:
ALLOCATE PIPE/PIPE PRIMARY AT CAM
Copies database PIPE/PIPE from the current Location to Location
CAM, making it Primary
ALLOCATE ALL AT LON AT 23:30
Copies all databases which exist at the current Location but do not
exist at Location LON, from the current Location to Location LON, at
2330 hrs. The Primary/Secondary status will not be changed.
ALLOCATE ALL AT OXF OVERRIDE PROPG
Copies all databases, including non-propagating databases, which exist
at the current Location but do not exist at Location OXF, from the
current Location to Location OXF. The Primary/Secondary status will
not be changed. Transaction databases will not actually be copied, but
empty database files will be created at secondary locations. This
command is useful when changing the Hub location, since it ensures
that the DB allocation lists of the old and new Hub locations match.
7-13
Command Details
ALLOCATE (continued)
Command Syntax:
>-ALLOCate -+- teamid -.
|
|
|----------+- dbname -+-------------.
|
|
|
|
|- PRIMary ---|
|
|
|
|
`- SECOndary -+-AT loc-+-AT <time>----.
|
|
|
|
`--------------+->
|
`- ALL ----------------------------AT loc-+-AT <time>-------.
|
|
`-OVERride PROPG -+->
Related Commands:
Querying:
7-14
Command Details
ALPHA
Function:
Examples:
ALPHA LOG /LOG OVERWRITE
Sends all information displayed in the Command Input and Output
window to a file named log.
ALPHA FILE /LOG
Sends reports to a file named log, for example, a DICE report.
ALPHA LOG END
Ends recording.
Command Syntax:
>-- ALPha ---*--- LOG ---+--- filename ---+--- OVERwrite -------------------|
|
|
|
|
|
|
|--- APPend ----------------------|
|
|
|
|
|
|
`-----------------+-- COMMands ---|
|
|
|
|
|
|
|-- REQuests ---|
|
|
|
|
|
|
`---------------|
|
|
|
|
`--- END ------------------------------------------|
|
|
`--- FILE ---+--- filename ---+--- OVERwrite ------------------|
|
|
|
|
|--- APPend ---------------------|
|
|
|
|
`--------------------------------|
|
|
`--- END -----------------------------------------+-->
7-15
Command Details
BACKTRACK
(Project Administration)
Function:
Description:
Examples:
BACKTRACK HANGERS/PADD TO SESSION 4
Backtracks the HANGERS/PADD database to Session 4. The team id
(HANGERS) and TO can be omitted.
BACKTRACK HANGERS/PADD TO STAMP /stamp_007
Backtracks the HANGERS/PADD database to the session that has the
stamp stamp_007. The team id (HANGERS) and TO can be omitted.
BACKTRACK /HVAC 10:30 31 / 8 / 96
BACKTRACK /HVAC 10:30 31 AUGUST 1999
Backtracks the HVAC database to10.30 am on the 31 August 1999. If
the time is omitted, 11.59 p.m. is assumed. If the month is not given,
7-16
Command Details
the current month is assumed. If the year is not given, the current year
is assumed. This example assumes that the team name has been
specified using the SET command.
7-17
Command Details
BACKTRACK (continued)
BACKTRACK PIPE/PIPE-A AT OXF TO SESSION 4
In a Global project, backtracks the PIPE/PIPE-A database at Location
OXF to Session 4. The team id (PIPE) and TO can be omitted. (The
database PIPE/PIPE-A must be Primary at the Location OXF,) and the
System Database for OXF must be Primary at the current Location.
See the ADMINISTER SYSTEM command.
Command Syntax:
>- BACKTrack -+- teamid -.
|
|
----------+- dbname TO <when> --->
Querying:
Q SESSION
7-18
Command Details
BRIEF
(Reconfiguration)
Function:
Examples:
LIBY
#92/842
=16/2404
(24,90)
Warning! library number 242 already exists in the
project.
Duplicate libraries should not be used in the same MDB
EC
DEPT
#16/805 =16/2408
Phase one complete - starting phase two
#EAE SHEE
#88/842 =16/2417 /DR1/S5
IDLN: The head of the current element does not contain
the attribute given
#EAE SHEE
#69/808 =18/2408 /DR1/S4
IDLN: The head of the current element does not contain
the attribute given
#EAE SHEE
#53/819 =22/2402 /DR1/S3
IDLN: The head of the current element does not contain
the attribute given
***Reconfiguration Completed
0 Elements were not defined in DDL
0 Elements have been lost
0 Elements are no longer named
3 Attributes were incorrectly defined
0 Elements were not inserted.
Command Syntax:
>--- Brief --->
7-19
Command Details
CANCELCOMMAND
Function:
Description:
Examples:
CANCELCommand TRINCO1 OF /2002/APR/23/USERA/LON
Command Syntax:
>--- CANCELCommand <gid> --->
7-20
Command Details
CDESC
(Project definition)
Function:
Description:
Examples:
CDESC USER TEST/TEST This is a test user
CDESC TEAM TEST This is the test team
CDESC DB TEST/DESI The test design database
CDESC MDB TEST This is the test MDB
Command Syntax:
>--- CDesc ---+--|
|--|
|--|
---
7-21
Command Details
CHANGE
Function:
(Project definition)
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.
Description:
7-22
Command Details
CHANGE (continued)
In a Global Project, the CHANGE command can be used at the
7-23
Command Details
CHANGE (continued)
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 introduced at PDMS 11.3, 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.
Notes on the following Change...Primary Commands
The new Primary Location will receive all outstanding updates of
the database from the current Primary Location.
Offline Locations: Note that the Primary Location of a Database
cannot be changed directly between an off-line satellite and an online 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.
7-24
Command Details
CHANGE (continued)
Command Syntax:
>- CHange -+- dbname -+--- ACCess ---+--- MULTIWrite ----.
|
|
|
|
|
|
|--- CONTRolled ----|
|
|
|
|
|
|
--- UPDAte --------|
|
|
|
|
|--- CLAIM ----+--- IMPLicit ------|
|
|
|
|
|
|
|--- EXPLicit ------|
|
|
|
|
|
|
--- OFF -----------|
|
|
|
|
|--- FINO -----+--- n -------------|
|
|
|
|
|
|
--- 0 -------------|
|
|
|
|
--- CONTROL --+--- ON ------------|
|
|
|
|
--- OFF -----------|
|
|
`- FOREIGN dbname RESET ----------------------+--->
Note:
Querying:
7-25
Command Details
CHECK
Function:
Description:
Using the CHECK command from within a PDMS project, you can
check:
7-26
Command Details
CHECK (continued)
CHECK PROJECT
Checks the integrity of all DBs in a project, including the System DB,
Comms DB and Misc DB (but not the virgin DBs). The DBs are checked
automatically by DICE in the following order:
The System DB
The Comms DB
The Misc DB
Command Syntax:
From a PDMS module:
.------<----.
/
|
DBs --*-- dbname ---+-----------------------------------.
|
SYStemdb -----------------------------------------------|
|
GLOBaldb -----------------------------------------------|
|
COMMdb -------------------------------------------------|
|
MISCdb -------------------------------------------------|
|
PROject ------------------------------------------------+-->
7-27
Command Details
CHECK (continued)
Note:
In stand-alone mode:
.-------<------.
/
|
>--- CHEck --- FIles --*--- filename ---+--->
Related Commands:
7-28
CHECKOPTION
Command Details
CHECKOPTION
Function:
Description:
7-29
Command Details
CHECKOPTION (continued)
An example of the output from DICE when statistics are
requested is as follows:
OVERALL STATISTICS
==================
Total no. of entries in Name Table = 111
Total no. of elements checked = 782
Total no. of ref attributes found = 726
Total no. of external references = 0
7-30
Command Details
CHECKOPTION (continued)
Once set, the preference MDB remains current until another
EXTERNAL CHECK PREFERENCE command is entered to set a
new MDB, or to specify that none is to be used, (though the
setting will become irrelevant if EXTERNAL NOCHECK or
EXTERNAL REJECT is entered). Using just EXTERNAL CHECK to
switch external setting back on will not affect the current
preference MDB.
The EXTERNAL REJECT option should normally be chosen only
when you are certain that the DB which is being checked should
not contain any external references. If this setting is used, any
external reference found in the DB will be reported as a fatal
error and further checking will be abandoned.
Note that when the CHECK FILES option is used, no external
reference checking can be done for that file and EXTERNAL
NOCHECK will be assumed.
The CLAIM options are only relevant to extracts.
Extract Claimlists
The CLAIM ON option (the default) will check that the claim list in
an extract corresponds with the claim list in its master database.
The following error messages may be produced:
Element ref/ref is not in parent extract claim list
Element ref/ref is claimed to another user/extract
Element ref/ref needs claiming to child extract in
parent extract
Element ref/ref needs clearing in parent extract
claim list
700:
702:
703:
704:
For case 704, the patch attempts to release the element from the
parent extract. If successful, the following message will be
written:
7-31
Command Details
CHECKOPTION (continued)
704:
7-32
Command Details
CNAME
(Project definition)
Function:
Description:
7-33
Command Details
CNAME (continued)
Command Syntax:
>-- CName --+-- USer --- username username ---+--- /password---.
|
|
|
|
----------------|
|
|
|--- DB --- dbname dbname ---+--- OVER ------------|
|
|
|
|
---------------------|
|
|
|--- MDB --- mdbname mdbname ----------------------|
|
|
--- TEam -- teamname teamname --------------------+->
Related Commands: CHANGE, EXCLUDE, INCLUDE, MOVE, CDESC
7-34
Command Details
COPY
(Project definition)
Function:
Description:
7-35
Command Details
COPY (continued)
Command Syntax:
>- COpy -+- DB dbname -+- FROM PROject projid USer id pass -.
|
|
------------------------------------+---> continued
7-36
Command Details
CREATE
(Project definition)
Function:
Description:
7-37
Command Details
CREATE (continued)
In a Global Project, you can only create Teams and Master
Databases at the Hub. Extracts can be created at any 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.
Examples:
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.
7-38
Command Details
CREATE (continued)
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 introduced at PDMS 11.3,
which will keep Extract filenames consistent within an Extract family.
CREATE DB PIPE/PIPEEB DESI IN AREA 501
Create Design DB PIPE/PIPEDB in area 501
7-39
Command Details
CREATE (continued)
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
Databases
>- CReate DB
teamid/dbname -+|
||
||
||
||
-
CATA -.
|
DESI -|
|
ISOD -|
|
PROP -|
|
PADD -|
|
DICT -+- IN AREA n -.
|
|
-------------+--->
cont
7-40
Command Details
CREATE (continued)
cont >---+-- EXTNO n -.
|
|
`-----------+- DBNO n -.
|
|
`----------+-- FINO n --.
|
|
`-------------+-- DESC text --.
|
|
`---------------+--->
name
dbname
is a 32-character name
Extracts
>-- CReate MASTER team/db ABOVE team/db ---->
cont
cont
cont
cont
---------->
7-41
Command Details
CREATE (continued)
Standard projects:
cont >--------+- EXTNO n -.
|
|
`-----------+- DESC text -.
|
|
`-------------+-->
Global projects:
cont >-+- EXTNO n -.
|
|
`-----------+- REFBLOCKS n -.
|
|
---------------+- AT <loc> -.
|
|
`------------+- DESC text -.
|
|
`-------------+-->
The REFBLOCKS option is used to allocate a block of reference numbers. See Running
The AT <loc> option allows the Hub or an administering location to create an extract
database whose primary location is at the specified satellite.
7-42
Command Details
CREATE (continued)
Users, Teams and MDBs
>- CReate -+- USer userid passwd -+--- FRee ------.
|
|
|
|
`--- GEneral ---|
|
|
|- TEam teamid ------------------------+-- DESC text ---.
|
|
|
|
----------------|
|
|
- MDB name---------------------------------------------+-->
Querying:
>--- Query --+-|
|-|
|-|
--
7-43
Command Details
CURRENT
(Project definition)
Function:
Description:
Examples:
CURRENT MASTER/AREA-D 2
Move DB MASTER/AREA-D to be at position 2 in the current MDB list
Command Syntax:
.------------<----------.
/
|
>-- CUrrent ---+--- dbname ---*--- integer -- dbname ---
|
|
--- integer --+-- integer -------------------->
7-44
Command Details
DADD
(Project definition)
Function:
Description:
Examples:
The following example assumes that both the Team and the DB
Set have been set using the SET command.
DADD DB /STEELN /STEELS DBSET /ASET DB /PIPEN
Adds the databases /STEELN, /STEELS and /PIPEN, and all the
Databases in the DB Set /ASET, to the current DB Set.
Command Syntax:
.----------------<------------.--<---.
|
|
/
.----<-------.
|
|
/
/
|
|
|
>-- DADD --*--- DB -------*--- dbname ---+---'
|
|
|
|
.-------------------<------------.
|
| /
|
|
| /
.-------<-------.
|
|
|/
/
|
|
|
*--- DBSET ----*--- dbsetname ---+---+---+--->
/
Querying:
Q SET DBSET
7-45
Command Details
DEALLOCATE
Function:
Description:
Examples:
DEALLOCATE PIPE/PIPE AT CAM
Removes the database PIPE/PIPE from Location CAM. The database
must not exist at any Locations which are descendants of CAM.
DEALLOCATE HVAC/HVAC AT OXF INCLUDING DESCENDANTS
Removes the database HVAC/HVAC from Location OXF and all
descendants of OXF.
DEALLOCATE ALL AT LON
Removes all databases which exist at Location LON. Note that you
cannot use the INCLUDING DESCENDANTS option with ALL.
7-46
Command Details
DEALLOCATE (continued)
Command Syntax:
>- DEALLOCate -+- teamid -.
|
|
|----------+- dbname -+- INCluding DESCENDants -.
|
|
|
|
`-------------------------|
|
|
`- ALL -----------------------------------------+-- AT <loc> -->
At a location:
>--- Q DBALL
At a Database:
>--- Q DBLC --->
7-47
Command Details
DEFER
(Project definition)
Function:
Description:
Moves a DB from the current list of an MDB into the deferred list
of an MDB. You can specify the position in the list by giving an
integer.
Examples:
DEFER MASTER/AREA-D
Make DB MASTER/AREA-D non-current.
Command Syntax:
.------<------.
/
|
>-- DEfer ---+--- dbname ---*--- dbname ---
|
|
--- integer --+----------------->
7-48
Command Details
DELETE
(Project definition)
Function:
Description:
7-49
Command Details
DELETE (continued)
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.
7-50
Command Details
DELETE (continued)
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 --+---------------+-->
7-51
Command Details
DREMOVE
(Project definition)
Function:
Description:
Examples:
The following example assumes that both the Team and the DB
Set have been set using the SET command.
DREM DB /STEELN /STEELS DBSET /ASET DB /PIPEN
Removes the databases /STEELN, /STEELS and /PIPEN, and all the
Databases in the DB Set /ASET, from the current DB Set.
Command Syntax:
.----------------<------------+--<---.
|
|
/
.----<-------.
|
|
/
/
|
|
|
>-- DREMove --*--- DB -------*--- dbname ---+---'
|
|
|
|
.-------------------<------------.
|
| /
|
|
| /
.-------<-------.
|
|
|/
/
|
|
|
*--- DBSET ----*--- dbsetname ---+---+---+--->
/
Querying:
Q SET DBSET
7-52
Command Details
DUMP
(Reconfiguration)
Function:
Description:
Examples:
DUMP /DUMP1
Write reference number index to named file.
Command Syntax:
>--- DUmp filename --->
7-53
Command Details
DUPLICATENAMES
Function:
Description:
7-54
Command Details
DUPLICATENAMES (continued)
The output reports the element name and the DB reference
number and DB number for each of the duplicates, for example:
/00NEB0SED =15196/3964, 7004, =15192/24230, 7000
/00NEB0SFD =15196/3965, 7004, =15192/24231, 7000
/00NEB0SFE =15196/3966, 7004, =15192/24232, 7000
If both MASTER and COPY DBs occur in the list then the DB refs
and nos will be identical. If necessary, use the LIST DBS
command to associate a DB name with a DB number.
Command Syntax:
>--- DUPLICatenames START --->
>--- DUPLICatenames FIle filename --->
>--- DUPLICatenames INclude ---+--|
|
|
|--|
|--|
`---
ALL ---------------------.
|
.----<-------.
|
/
|
|
DB ---*--- dbname ---+---|
|
LIST --------------------|
|
CLEAR -------------------+--->
.----<-----------.
/
|
>--- DUPLICatenames EXclude ---+--- DB ---*--- dbname -------+
|
|
|--- LIST --------------------|
|
|
`--- CLEAR -------------------+--->
>--- DUPLICatenames CHECK --->
7-55
Command Details
EDIT
(Module definition)
Function:
Description:
Examples:
EDIT MODU ADMIN IMACRO /START
Enter EDIT mode and edits module ADMIN to add the macro /START
as an initialisation macro.
EDIT MODU 77 SECU FR
Enter EDIT mode and edits module 77 to make it a FREE module
MODU 77 MODE CATA RW
In Edit mode, change module 77 to CATA db with read/write mode.
EDIT MODU DESIGN RES /%PDMSEXE%/DES
Change resume file name for DESIGN module entry
EDIT MODU ADMIN IMACRO DELETE
Edits the ADMIN module definition and deletes the Imacro entry.
7-56
Command Details
EDIT (continued)
Command Syntax:
.----------------------------------------------------------------------------.
/
|
>- EDit -*- MODule -+- number --.
|
|
|
|
|
|
- modname -+- NUmber number ---------------------------------------|
|
|
|
|
|- NAme name -------------------------------------------|
|
|
|
|
|- Security -+- FRee ------------------------.
|
|
|
|
|
|
|
|
`- GENeral ---------------------|
|
|
|
|
|
|
|- Mode file -+- RW -------------------------|
|
|
|
|
|
|
|
|
|- Read -----------------------|
|
|
|
|
|
|
|
|
|- None -----------------------|
|
|
|
|
|
|
|
|
- DEFault --------------------|
|
|
|
|
|
|
|- Open -+- SYMBOLFILE --.
|
|
|
|
|
|
|
|
|
|
|- ATTlibfile --|
|
|
|
|
|
|
|
|
|
|
- MESSagefile -+- name -.
|
|
|
|
|
|
|
|
|
|
--------+- DELETE -|
|
|
|
|
|
|
|
|
----------|
|
|
|
|
|
|
|- Resume file ------------------------------|
|
|
|
|
|
|
|- Buffer -+- integer -----------------------|
|
|
|
|
|
|
|
|
- DEFault -----------------------|
|
|
|
|
|
|
|- Imacro -+- name ---.
|
|
|
|
|
|
|
|
|
|
- DELETE -+----------------------+- newline-
|
|
----------------------+--------------------------------------------------------->
7-57
Command Details
ERRORFILE
Function:
Specifies the name of the file containing the error and warning
messages when DICE is used in stand-alone mode.
Description:
PDMS obtains the text of all its user messages from an external
file. When DICE is used from within a PDMS project, this file is
available automatically, but this is not the case in stand-alone
mode. Hence the first command you must give in stand-alone
mode is the ERRORFILE command, followed by the name of the
error message file.
The name of the message file can be found from the entry for
DICE in the current version of makemac.mac, the project
configuration macro.
Examples:
ERRORFILE /%PDMSEXE%/MESSAGE.DAT
Command Syntax:
>--- ERRORfile filename --->
Related Commands: MODULE, LIST MODULES
7-58
Command Details
ERRORS
(Reconfiguration)
Function:
Description:
Command Syntax:
>--- ERRors number --->
7-59
Command Details
EXCHANGE
(Project definition)
Function:
Description:
Examples:
EXCHANGE PIPING/AREA-A SERV/AREA-D SERV/AREA-E PIPING/AREA-B
PIPING/AREA-A and PIPING/AREA-B are the current DBs. They
will be replaced by the DBs SERV/AREA-D and SERV/AREA-E
respectively, even though they are listed out of sequence.
Command Syntax:
.--------<----------.
/
|
>-- EXchange ---*--- dbname dbname ---
|
|-----------------------.
|
|
--- integer integer ---+--->
Related Commands: ADD, REMOVE, CURRENT, DEFER
7-60
Command Details
EXCLUDE
(Project definition)
Function:
7-61
Command Details
EXPUNGE
(Project administration)
Function:
Description:
7-62
Command Details
EXPUNGE (continued)
Command Syntax:
.-----<--------------------------------.
/
|
>-- EXPUNGE --*-- process_id --------------------------|
|
|
|-- DB dbname ----+-- USER usernumber ---|
|
|
|
|
`----------------------'
|
|--- DB SYSTEM ---.
|
|
-----------------+------------------>
Note:
Querying:
Q ACTIVE
Related Commands:
SYSTAT,
For Global projects - REMOTE, REMOTE EXPUNGE
7-63
Command Details
EXTERNAL
Function:
Description:
7-64
Command Details
EXTERNAL (continued)
Examples:
EXTERNAL CHECK
EXTERNAL NOCHECK
EXTERNAL REJECT
An example of the output when EXTERNAL CHECK is specified:
External databases referenced
_____________________________
Number
______
8
31
Name
____
GLB/DESI
TECHP/TPDESI
No of references
________________
41
4
Command Syntax:
>--- EXTernal ---+--- NOCHeck* ---.
|
|
|--- CHECK ------+-- PREFERENCE
|
|
--- REject -----+--->
The default is NOCHECK.
7-65
Command Details
EXTRACT
(Project administration)
Function:
Description:
FLUSH RESET
Resets the database after a failed EXTRACT FLUSH
command. If more than one user is issuing the same
database extract, then flush and release commands
can be processed in the wrong order, causing a flush to
fail and preventing subsequent refreshes of the
extract. This command can be used to undo the failed
flush.
FLUSHW
REFRESH
FULLREFRESH
Refreshes an extract and all its parent extracts its
ancestors. A full refresh takes place from the top of the
database hierarchy downwards, ending with a refresh
of the extract itself. Each extract is refreshed with
changes that have been made to its parent extract.
7-66
ISSUE
RELEASE
DROP
Command Details
EXTRACT (continued)
Note that unlike the constructor modules, you can only perform
these operations on a complete database in ADMIN, and so
claiming has no meaning in ADMIN. For general information
about using extracts in projects, see the VANTAGE PDMS
ADMIN User Guide. For information about using extracts in
Global projects, see Running Global Projects with VANTAGE
PDMS.
7-67
Command Details
EXTRACT (continued)
EXTRACT FLUSH RESET DB PIPE/PIPE-X1
Undoes a failed flush on this database.
Command Syntax:
>-- EXTRACT -+|
|
||
||
||
||
||
`-
Note:
7-68
FLUSH --+------------.
|
|
`--- RESET --|
FLUSHWithoutrefresh -|
|
RELEASE -------------|
|
ISSUE ---------------|
|
DROP ----------------|
|
FULLREFRESH ---------|
|
REFRESH -------------+- DB - dbname -->
In ADMIN, you cannot carry out partial operations as you can in the
constructor modules. The commands can only be applied to entire DBs.
Command Details
FINISH
Function:
Examples:
FINISH
Command Syntax:
>--- FINISH --->
Related Commands: SAVEWORK
7-69
Command Details
FONTDIRECTORY
(Font definition)
Function:
Description:
The font directory stores the font families for use in DESIGN and
DRAFT. Font families are defined by the FONTFAMILY
command. The FONTDIRECTORY command can be given in
ADMIN or used in the make macro. In the make.mac macro
supplied the font directory is defined as %PDMSEXE%. If the font
directory is unset, PDMS will search for the fonts in the users
current directory.
Examples:
FONTD /%PDMSEXE%
Command Syntax:
>--- FONTDirectory name --->
Querying:
7-70
Command Details
FONTFAMILY
(Font definition)
Function:
Description:
1 UK STYLE
2 UK STYLE
3 UK STYLE
4 UK STYLE
/%PDMSEXE%
1
2
3
4
For each font family, you can define an angle of slope between -85
and +85 degrees inclusive. The text can be sloped forwards
(positive angles) and backwards (negative angles).
Examples:
FONTFAMILY font_no IR ir_no STYLE style_no ANGLE angle
FONTFAMILY font_no FILE /abc BOLD /def ANGLE angle
PROJECT MBCHARSET JAPAN ANGLE angle
FONTFAMILY 1 IR 4 STYLE 1
FONTF 2 UK ITALIC
FONTF 3 UK BLOCK
FONTF 4 GREEK STYLE 1
7-71
Command Details
FONTFAMILY (continued)
Command Syntax:
.-------------------------<------------------------------.
/
|
>-- FONTFamily ---*--- n ---*- IR number --.
|
|
|
|
|- UK ---------|
|
|
|
|
|- US ---------|
|
|
|
|
|- GREEk ------|
|
|
|
|
|- CYRIllic ---|
|
|
|
|
|- LATIn 1 ----|
|
|
|
|
|- LATIn 2 ----+-- STYle n ---------.
|
|
|
|
|
|
|-- LIne ------------|
|
|
|
|
|
|
|-- BLock -----------|
|
|
|
|
|
|
|-- SErif -----------|
|
|
|
|
|
|
|-- ITalic ----------|
|
|
|
|
|
|
|-- SCript ----------|
|
|
|
|
|
|
|-- TYpewriter ------|
|
|
|
|
|
|
-- UWLIne ----------|
|
|
|
|
- FILE filename -- BOLD filename --+- ANGLE n --|
|
|
`------------+-->
Notes:
The IR number is the International Registration Number of the
font. See ISO 8859.
The font family number must be in the range 1-4
The style n must be in the range 1-7.
The angle n must be in the range -85 to + 85 degrees. Negative
angles slope the text backwards.
Related Commands: FONTDIRECTORY
Querying:
7-72
Command Details
FROM
Function:
(Reconfiguration)
Specifies the source database for reconfiguration.
Examples:
FROM DB MASTER/DESIGN
Source data is in database MASTER/DESIGN in current project
FROM DBFILE /des016
Source data is in specified file (assumes project directory is current
directory)
FROM PROJECT des MASTER/DESIGN
Source data is in specified DB within project des
FROM FORMATTEDFILES /F1 /F2
Source data is in named character-format intermediate files (used
when transferring data between computers).
FROM SYSTEM
This command is used to reconfigure the System database. It is
followed by the command RECONFIGURE. For more information, see
Section 3. In a Global Project, this command is only available at the
primary location of the System DB (the administering location).
FROM GLOBAL
7-73
Command Details
FULL
(Reconfiguration)
Function:
Description:
Command Syntax:
>--- FUll --->
7-74
Command Details
GENERATE
Function:
Description:
All the Project files are copied to a transfer directory at the Hub,
ready for transmission to the new satellite. The transfer directory
is specified by the environment variable
project_locid
where project is the 3-character project code and locid is the 3-
7-75
Command Details
GENERATE (continued)
Examples:
GENERATE LOCATION LON
Generates a location with identifier LON. By default, all Databases at
the Hub will be allocated to LON.
GENERATE LOCATION /LONDON
Generates a location /LONDON, allocating all databases.
GENERATE LOCATION LON NOALLOCate
Generates a location with identifier LON. No Databases will be
allocated.
Note:
Command Syntax:
>-- GENerate LOCation <loc> --+--- ALLOCate -----.
|
|
`--- NOALLOCate ---+-->
7-76
Command Details
GETWORK
Function:
VANTAGE PDMS.
Command Syntax:
>--- GETWORK --->
7-77
Command Details
HUBLOCATION
Function:
Description:
Examples:
HUBLOCATION LON
Relocates the Hub to location with identifier LON.
HUBLOCATION LON AT 20:00
Relocates the Hub to location with identifier LON at 2000 hrs.
7-78
Command Details
7-79
Command Details
INCLUDE
(Project definition)
Function:
Examples:
INCLUDE DB MASTER/PIPECATA FROM PROJ MAS USER USERA/A
The database MASTER/PIPECATA from project MAS will be included
in the current project. The user/password (USERA/A in this example)
must be a FREE user in the source project.
Command Syntax:
>--- INCLude DB dbname FROM PROject projectid USer username/password --->
7-80
Command Details
INITIALISE
Function:
Description:
Examples:
INITIALISE
Command Syntax:
>--- INITIALise --->
Q LINIT
7-81
Command Details
ISOLATION
Function:
Description:
Examples:
ISOLATION TRUE
Isolates the current Location.
ISOLATION FALSE
Connects the current Location.
ISOLATION TRUE AT LON
Isolates the remote Location LON. This command is only available at
the Hub or at the administering location (in this example, that for
LON).
the Hub or at the administering location (in this example, that for
LON).
Command Syntax:
>--- ISOLATion ---+--- TRUE ----.
|
|
`--- FALSE ---+--- AT <loc> ---.
|
|
`----------------+--->
Querying:
7-82
Command Details
LIST
(Querying)
Function:
Examples:
LIST
Outputs date and time.
LIST USERS
Lists the Users in a project.
LIST MDBS
Lists the Multiple Databases in a project.
LIST DBS
Lists the Databases in a project.
LIST DBS OF TYPE DESI
Lists all the Databases of type DESI in a project.
LIST TEAMS
Lists the Teams in a project.
LIST COPIES
Lists the DBs in a project which have been copied and the filenames of
the copies.
LIST ALL
Lists the Users, Teams, Databases and MDBs in a project.
LIST FILES
Lists the DBs in a project and their corresponding filenames in the
Project directory.
LIST MESSAGES
Lists inter-user messages.
LIST MODULES
Produces information on all the PDMS modules used by the project.
LIST MODULES 5
Produces information on module 5.
LIST MODULES DESIGN
Produces information on module DESIGN.
LIST MESSAGES
Lists inter-user messages.
LIST PASSWORDS
Lists users ids and passwords.
LIST TYPES
Lists the types of DB currently permissible.
7-83
Command Details
LIST (continued)
LIST SIZES
Gives the sizes of all the DBs in a project.
LIST EXTERNAL
Lists DBs which are being shared with another project.
LIST MACROS
Lists inter-db connection macros.
LIST AREA 51
Lists DBs in Project Area 51.
LIST WORKing EXTracts
Lists the working extracts.
LIST WORKing EXTracts FOR user
Lists the working extracts for the specified user.
LIST WORKing EXTracts dbname
Lists the working extracts for the specified DB.
7-84
Command Details
LIST (continued)
Command Syntax:
.----------------------<----------- ----------.
/
|
>--- LIst ---*-----------------------------------------------|
|
|
|--- USers -------------------------------------|
|
|
|--- MDBs --------------------------------------|
|
|
|--- DBs ---+--- OF TYPE type ------------------|
|
|
|
|
-----------------------------------|
|
|
|--- TEams -------------------------------------|
|
|
|--- FIles -------------------------------------|
|
|
|--- COpies ------------------------------------|
|
|
|
.-------<---------.
|
|
/
|
|
|--- MOdules ---*--- integer -------|
|
|
|
|
|
|
|--- module_name ---
|
|
|
|
|
-------------------------------|
|
|
|--- MESSages ----------------------------------|
|
|
|--- ALL ---------------------------------------|
|
|
|--- PASSwords ---------------------------------|
|
|
|--- TYpes -------------------------------------|
|
|
|--- SIZes -------------------------------------|
|
|
|--- MACRos ------------------------------------|
|
|
|--- AREA --- integer --------------------------|
|
|
|--- EXTernal ----------------------------------|
|
|
--- WORKing EXTracts -+----------.- FOR user -+--->
|
|
- dbname
7-85
Command Details
LOAD
(Reconfiguration)
Function:
Examples:
LOAD /DUMP1
Read reference number index from named file and replace current
index.
LOAD /DUMP1 APPEND
Read reference number index from named file and
append to current index.
Command Syntax:
>--- LOad ---+--- APPEND ---.
|
|
--------------+--- filename --->
Related Commands: DUMP, REINIT, XREF
7-86
Command Details
LOCK
(Project administration)
Function:
Locks the Project Database and prevents any other user from
entering the database until the project is unlocked.
Examples:
LOCK
Locks the Project database.
LOCK AT LON
Locks the Project database at the remote Location LON. Only available
Command Syntax:
>--- LOCK ------>
7-87
Command Details
MAKE GLOBAL
Function:
Description:
7-88
Command Details
MAXERRORS
Function:
Description:
Examples:
MAXERRORS 100
Related Commands: MODE, MAXWARNINGS
Command Syntax:
>--- MAXErrors
integer --->
7-89
Command Details
MAXUSERS
(Project Administration)
Function:
Sets the maximum number of users for a project. Note that there
is no theoretical limit to the number of simultaneous users, but a
limit may be set by the current licence restrictions.
Examples:
MAXUSERS 10
Command Syntax:
>--- MAXUSers integer --->
7-90
Command Details
MAXWARNINGS
Function:
Description:
Example:
MAXWARNINGS 100
Related Commands: MODE, MAXERRORS
Command Syntax:
>--- MAXWarnings
integer --->
7-91
Command Details
MERGE CHANGES
Function:
(Project Administration)
Note:
Examples:
MERGE CHANGES HVAC/PADD AFTER SESSION 4 BEFORE SESSION 10
Merges all the changes to the HVAC/PADD database after session 4
and before session 10, that is all changes made in sessions 5 to 9 will be
combined. If there are any stamped sessions in sessions 5 to 9, they
will be kept. The team id (HVAC) can be omitted if a current team is
set.
MERGE CHANGES HVAC/PADD AFTER STAMP /
stamp_012 BEFORE STAMP /stamp_016
Merges all the changes to the HVAC/PADD database for sessions that
are after the session stamped with stamp_012 and before the session
stamped with stamp_016. All changes made in stamped sessions that
are between the sessions stamped with stamp_012 and stamp_016 will
be combined. If there are any other stamped sessions, they will be kept.
The team id (HVAC) can be omitted if a current team is set.
7-92
Command Details
Note:
<BEFORE/AFTER>
7-93
Command Details
where when can be given in the form of a date or a session number, or, if the
required sessions have been stamped, a stamp, as shown in the examples. See
Section 7.2, for the full syntax of <when>.
Note:
7-94
Q SESSION
Command Details
MESSAGE
(Project administration)
Function:
Description:
text ----------.
|
text ----------|
|
text ----------|
|
text ----------|
|
text ----------|
|
text ----------+-->
LIST MESSAGE
7-95
Command Details
MODE
Function:
Description:
MAXERRORS
Command Syntax:
>--- MOde ---+--- BRief ---.
|
|
--- FUll ----+--->
7-96
Command Details
MODULE
(Module Definition)
Function:
Description:
Examples:
Module 78
DESIGN
Security Free
Mode DESI Default
Mode PROP R
Mode CATA R
Mode DESI RW
Resume /%PDMSEXE%/des
Command Syntax:
>- MODule -+--- integer module_name -.
|
|
--- module_name integer -+- newline <runf> -->
VANTAGE PDMS ADMIN
Command Reference Manual
Version 11.6SP1
7-97
Command Details
RW --------.
|
Read ------|
|
None ------|
|
DEFault ---+--->
7-98
Command Details
MOVE
(Project administration)
Function:
Description:
xxxnnn
set to
pathname
where xxx is the Project Code, for example, abc, and nnn is a
number, for example, 001. When the database is created, the area
number of the database must then be set to the corresponding
value, in this example, 1.
Example:
MOVE DB HVAC/HVAC TO AREA 051
Command Syntax:
>--- MOve DB dbname TO AREA integer --->
7-99
Command Details
NEW
Function:
Description:
global database.
7-100
Command Details
NEW (continued)
Command Syntax (any Project):
>--- NEW ---+--|
|--|
|--|
|--|
|--|
|--|
|--|
`---
7-101
Command Details
NEW STAMP
(Project administration)
Function:
Description:
|
|
|
-- STAMP /stampname ------------------------------------+--->
7-102
Command Details
7-103
Command Details
PING
Function:
Description:
Example:
PING LON
Checks that communications link to Location LON exists.
Command Syntax:
>- PING <loc> --->
7-104
Command Details
PREVOWNER
Function:
Description:
7-105
Command Details
PREVOWNER (continued)
Examples:
PREVOWNER HUB
PREVOWNER dbname
PREVOWNER SYSTEM AT <loc>
Command Syntax:
>--- PREVOwner ---+--- HUB ---------------.
|
|
|--- SYSTEM AT <loc> ---|
|
|
`--- dbname ------------+--->
Related Commands:
Querying:
7-106
Command Details
PROJECT
(Project definition)
Function:
119 characters
119 characters
119 characters
16 characters
7-107
Command Details
PROJECT (continued)
Command Syntax:
>- PROJect -+-- NUMber text ------------------------------------------------.
|
|
|-- NAMe text --------------------------------------------------|
|
|
|-- DEScription text -------------------------------------------|
|
|
|-- MESsage text -----------------------------------------------|
|
|
|- MBCHARset -+- integer --.
|
|
|
|
|
|
|- JAPanese -|
|
|
|
|
|
|
|- CHInese --|
|
|
|
|
|
|
|- LATIN ----+- FILE -+- name -+- BOLD name -.
|
|
|
|
|
|
|
|
|
|
|
|
-------------|
|
|
|
|
- DEFAULT ------------|
|
|
|
-------------------------------|
|
|
|
|
|
|
|
.-------<------'
|
|
|
|
|
|
-+- KORean ---.
|
|
|
|
|
|
|
|
- TCHINese -+--FILE name --+- ANGLE integer ---|
|
|
|
|
-------------------+->
- CHARset -+- IR integer ---------.
|
|
- LATIN -+- integer --|
|
|
|- CYRIllic -|
|
|
------------+->
Querying:
>--- Q PROject --+-|
|-|
|-|
|-|
|-|
|-|
--
7-108
NUMber -------.
|
NAMe ---------|
|
DEScription --|
|
MESsage ------|
|
CODe ---------|
|
MBCHARset ----|
|
CHARset ------+-->
Command Details
PURGE
Function:
Description:
Examples:
PURGE OLD FILES
Deletes all files in the Project with the suffix .admold.
PURGE OLD FILES DB
Deletes all database files in the Project with the suffix .admold.
PURGE OLD FILES PICTURE
Deletes all picture files in the Project with the suffix .admold.
Command Syntax:
>--- PURGE ---+--- OLDfiles ---+----------------.
|
|
|
|
|--- DB ---------|
|
|
|
|
`--- PICture ----|
|
|
`--- DB dbname -------------------+--->
7-109
Command Details
QUERY
Function:
(Querying)
Used to output a wide variety of information. In general, querying
options are documented with the commands which they relate to.
Some options which do not fit into this category are listed here.
Note that general PDMS commands for querying elements and
attributes are also available.
Examples:
Q COPIES PIPING/AREA-A
List the copies of DB PIPING/AREA-A
Q SET MDB
Q SET TEAM
Q SET DBSET
Query the set (i.e. current) Team, MDB or DB Set
Q MOD DESIGN DRAFT 33
Query module entries for DESIGN, DRAFT and module 33
Q DDL
Gives version number of System DDL (Design Data Language)
Q CLAIM SAMPLE/DESI
Outputs information about claimed databases
Q NEWREF old-ref
Gives the new reference corresponding to the given old reference
Q SESSION LAST
Outputs the date, user, and any comments saved with the given
session
Q SESSIONS ON date dbname
Q SESSIONS SINCE n dbname
Q SESSIONS LAST n dbname
Query session information on a specified database
Q SESSIONS SINCE n
Q SESSIONS LAST n
Q SESSIONS ON date
Query session information on the current database (i.e. System or
Global database)
Q ACTIVE
Gives the active session number
7-110
Command Details
QUERY (continued)
Q NACCNT
At a DB element, gives the non-additive changes count. This value
increases when a database is merged, backtracked or reconfigured.
This attribute will return the value for the system database if used at
STAT /*S, or in a Global project, for the global database if used at
GSTAT /*GS.
Q HCCNTAt a DB element, gives the extract list changes count. This value
increases when extracts are inserted or removed.
Note: The superseded ELCCNT pseudo-attribute is retained as a
synonym for HCCNT. HCCNT is available at /*S and /*GS elements as
well as at DB elements.
Q CLCCNT
At a DB element, gives the claim list changes count. This value
increases when elements are claimed or dropped without other changes
to the database.
Note: In a Global project, the above three attributes together with session
information can be used to compare the state of the database at different
locations. For information about this, see Running Global Projects with
VANTAGE PDMS.
Querying extracts
Q DBNAME
Gives the name of the database you are actually writing to.
Q CLAIMLIST
Gives a list of user claims in your current database.
Q CLAIMLIST EXTRACT
Tells you what you can flush.
Q CLAIMLIST OTHERS
Tells you what you can't claim, including user claims and extract
claims.
7-111
Command Details
QUERY (continued)
Q COMMS LON INPUTRequests
Q COMMS LON OUTPUTRequests
Query data from comms link to named location: Input or Output
Requests.
Q COMMS TO LON PATH
Query Comms routing to location LON.
Q CURLOC
Returns the true current location. This command is useful when you
are remotely administering another location: it returns the name of the
actual location where you are working.
Q ISOLAT AT LON
Returns TRUE if the location LON is isolated.
Q LOCK AT LON
Returns the lock at location LON.
The following options are only available in a Global Project at the Hub.
The daemons must be running.
Q READERS HVAC/HVAC AT CAM
Outputs a list of readers of database HVAC/HVAC at Location CAM.
Q READERS HVAC/HVAC AT CAM COUNT
Outputs a count of readers of database HVAC/HVAC at Location CAM.
Q WRITERS HVAC/HVAC AT CAM
Outputs a list of writers to database HVAC/HVAC at Location CAM.
Q WRITERS HVAC/HVAC AT CAM COUNT
Outputs a count of writers to database HVAC/HVAC at Location CAM.
7-112
Command Details
QUERY (continued)
Command Syntax:
>- Q --+--|
|--|
|--|
|--|
|--|
|--|
|
|
|--|
|
|
|--|
|--|
|--|
|
|
|
|
|--|
|--|
|
|
|
|
|--|
|--|
|--|
|--|
|--|
---
USer ----.
|
TEam ----+--- word -----------------------.
|
DB -------.
|
|
|
COpies ---+--- dbname --------------------|
|
DBNO dbno --------------------------------|
|
MDB name ---------------------------------|
|
.-------<-----.
|
/
|
|
MOdule ---*--- integer ---|
|
|
|
|
--- word ------+---------------|
|
LOck -------------------------------------|
|
DDL --------------------------------------|
|
SET ---+--- TEam -------------------------|
|
|
|--- DBSet ------------------------|
|
|
--- MDB --------------------------|
|
PROject ----------------------------------|
|
SESSIONS --+-- SINCE --.
|
|
|
|
|-- LAST ---+- n --+-----------|
|
|
|
- ON <date> -----+-dbname ---|
|
CLAIM dbname -----------------------------|
|
NEWREF oldref ----------------------------|
|
MAXUSers ---------------------------------|
|
ACTIVE -----------------------------------|
|
MACRO n ----------------------------------|
|
INFOrmation --+--- dbname ----------------|
|
|
--- SYSTEM ----------------+--->
7-113
Command Details
QUERY (continued)
The following options are only available in a Global Project.
>--- Q COMMS ---+--- TO ---.
|
|
`----------+--- <loc> ---+--- INPUTPackets ----.
|
|
|--- OUTPUTPackets ---|
|
|
|--- INPUTRequests ---|
|
|
|--- OUTPUTRequest ---|
|
|
|--- PATH ------------|
|
|
`---------------------+-->
>--- Q ADMLOC --->
>--- Q CURLOC --->
>--- Q ISOLAT AT <loc> --->
>--- Q LOCK AT <loc> --->
>--- Q --+-- READERS --.
|
|
`-- WRITERS --+- <dbname> --.
|
|
`-------------+--- AT <loc> --.
|
|
`---------------+-- COUNT --.
|
|
`-----------+-->
7-114
Command Details
RCFCOPY
(Reconfiguration)
Function:
Description:
Examples:
RCFCOPY ALL
Copies all of the elements in the list part of WORLD in the source DB
into the list part of WORLD in the destination DB
RCFCOPY CATA
Copies the first root elements of type CATA to be copied from the list
part of the WORLD in the source DB.
RCFCOPY SPEC
Copies the first root elements of type SPWL to be copied from the list
part of the WORLD in the source DB.
RCFCOPY /SITE5A /SITE7
Copies just the named elements.
RCFCOPY <SITEA> INTO <SITEB> ALLCONNECTIONS
Sets all references, including those in the original database that are
not in the list of copied elements.
7-115
Command Details
Command Syntax:
/
>- RCFCopy ---*|
||
||
||
`-
Querying:
.-------------<-----------------.
|
ALL ------------.
|
|
|
CATalogue ------|
|
|
|
SPECifications -|
|
|
|
name -----------|
|
|
|
refno ----------+--- AND ------|
|
|
|--- comma ---
|
`--- INto -+- name --+-ALLCONnections -.
|
|
|
- refno -+-----------------+->
Q COPIES
7-116
Command Details
RCFUPDATE
Function:
(Reconfiguration)
Updates reference pointers into reconfigured databases.
Examples:
RCFUPDATE DB MASTER/DESIGN
Updates references to the reconfigured DB from DB
MASTER/DESIGN.
RCFUPDATE DB MASTER/DESIGN INTERNAL
Updates references in DB MASTER/DESIGN for any elements that
have been copied with RCFCOPY. Use this option with care because it
is possible to update a reference that has already been changed by the
RECONFIGURE command.
RCFUPDATE MDB /USERA
Updates references to the reconfigured DB from all appropriate DBs in
MDB /USERA
RCFUPDATE TEAM STEEL
Updates references to the reconfigured DB from all appropriate DBs
owned by team STEEL.
RCFUPDATE ALL
Updates references to the reconfigured DB from all databases in
current project.
Command Syntax:
>--- RCFUPdate ---+--- DB dbname -+--------------.
|
`-- INTERNAL --|
|
|
|--- MDB mdbname --------------|
|
---------|
|--- TEam teamname ------------|
|
|
|--- ALL ----------------------|
|
|
------------------------------+-->
7-117
Command Details
RCFUPGRADE
Function:
(Reconfiguration)
Command Syntax:
>-- RCFUPGRADE --+-- ON ----.
|
|
-- OFF ---+-->
7-118
Command Details
RECONFIGURE
(Reconfiguration)
Function:
Description:
You can specify that the reference numbers stay the same in the
reconfigured database. The SAMEREF option will fail if:
You can specify that session information stays the same in the
reconfigured database by using the SESSIONS option:
7-119
Command Details
RECONFIGURE (continued)
3. Reconfigure from the file to the new database.
For Global projects, note the following:
Examples:
RECONFIGURE
Command Syntax:
>--- RECONfigure ---+---- FORCE ----.
|
|
|--- SESSIONS --|
|
|
`--- SAMEREF ---+--->
Related Commands:
7-120
Command Details
RECOVER
Function:
Description:
7-121
Command Details
RECOVER (continued)
Examples:
AAA
BBB
EEE
You are here
CCC
You are
administering
DDD from CCC
STEELN/STEEL
N is Primary at
EEE
PIPEN/PIPEN is
Primary at CCC
DDD
7-122
Command Details
RECOVER (continued)
System DBs
RECOVER SYSTEM FOR EEE FROM BBB
Recovers System database for EEE from the copy at BBB.
RECOVER SYSTEM FROM BBB
Recovers System database for the true current location from BBB.
Remote recovery of System DBs
(available at the Hub or the administering location of the
satellite)
RECOVER SYSTEM FOR EEE AT AAA FROM BBB
Recovers AAA's copy of the System database for EEE from the copy at
BBB.
Command Syntax:
>--- RECOVer -+-- SYSTEM --+-- FOR <loc> --.
|
|
|
|
`---------------|
|
|
`-- dbname ------------------+-- AT <loc> --.
|
|
`--------------+-- FROM <loc> --.
|
|
`----------------+--->
7-123
Command Details
REINIT
(Reconfiguration)
Function:
Description:
Command Syntax:
>--- REinit --->
7-124
Command Details
REMOTE
Function:
7-125
Command Details
REMOTE (continued)
7-126
Command Details
REMOTE (continued)
Examples:
For details of time and date syntax, see Section 7.2.
BACKTRACK
REMOTE <loc> BACKTRACK dbname TO 14:30
REMOTE <loc> BACKTRACK dbname TO SESS 17
Backtracks changes to the given database, which must be Primary at
the named location. A database cannot be backtracked through a
stamp.
REVERT
REMOTE <loc> REVERT dbname TO 14:30
REMOTE <loc> REVERT dbname TO SESS 17
Adds a session reverting to the data at the specified session or date.
The database must be Primary at the named location.
MERGE CHANGES
REMOTE <loc> MERGE CHANGES dbname BEFORE 31 MARCH
REMOTE <loc> MERGE CHANGES dbname BEFORE SESSION 9 AFTER SESSION 4
Merges changes to the given database, which must be Primary at the named
location. Stamped sessions will not be removed by the merge.
REMOTE <loc> MERGE CHANGES SYSTEM
Merges changes to the system database for the location <loc>.
REMOTE <loc> MERGE CHANGES SYSTEM FOR <loc2>
Merges changes to the system database for <loc2>, which must be
administered by <loc>.
EXPUNGE
REMOTE <loc> EXPUNGE
REMOTE <loc> EXPUNGE username
Expunges all users or the given user from the communications
database at the given Location. username is the PDMS username.
REMOTE <loc> EXPUNGE DB dbname
REMOTE <loc> EXPUNGE DB dbname USER username
REMOTE <loc> EXPUNGE DB SYSTEM
REMOTE <loc> EXPUNGE DB SYSTEM FOR <loc2>
Expunges all users or the given user from the given database at the
given Location. The database must be primary at the given Location.
Username can be the PDMS username or a session number.
7-127
Command Details
REMOTE (continued)
DICE Checking
REMOTE <loc> CHECK SYSTEM
REMOTE <loc> CHECK DB dbname
REMOTE <loc> CHECK MISCDB dbname
REMOTE <loc> CHECK COMMDB
REMOTE <loc> CHECK SYSTEMDB FOR <loc2>
Performs a standalone DICE check on the given database at the given
Location. The database does not need to be primary at the given
Location. The check uses the current MODE, STATISTICS,
MAXERRORS and MAXWARNINGS settings.
Cancelling commands
REMOTE <loc> CANCEL <gid>
Allows an Admin user to cancel a command at another Location <loc>,
where <gid> is a TRINCO in the transaction database for the given
Location (this is not the current Location, unless <loc> is the current
Location). This command requires an up-to-date version of the
transaction database for Location <loc> to be available at the current
Location. (The transaction database is not normally propagated. It is
best to RECOVER this database from the primary location rather than
to SYNCHRONISE it.)
Command Syntax:
7-128
Command Details
REMOTE (continued)
>- REMOTE <loc> EXPUNGE -+- USER username ----------------------.
|
|
|--------------------------------------|
|
|
`- DB --+- dbname -+-- USER username --|
|
|
|
|
`-------------------|
|
|
`- SYSTEM -+-- FOR <loc2> -----|
|
|
`-------------------+-->
Related Commands:
DB dbname ------------------------.
|
MISCDB --------------------------|
|
COMMDB --------------------------|
|
SYSTEMDB dbname -+- FOR <loc2> ---.
|
|
`----------------|
|
GLOBALDB -------------------------+-->
7-129
Command Details
REMOTE (continued)
Querying:
Remote database session information can only be queried by
looking at the secondary database at the current location, which
may not be up-to-date.
Information about remote users of PDMS may be queried using
remote session objects. For example
!p = current project
!l = !p.locations()
!r = !l[2].sessions()
q var !r[1]
q var !r[1].module()
q var !r[1].user()
q var !r[1].mdb().
7-130
Command Details
REMOTEMESSAGE
Function:
Examples:
REMOTEMessage <loc> ALL text
Send message to all users at named location
REMOTEMessage <loc> TEAM teamid text
Send message to all members of a team at named location
REMOTEMessage <loc> FREEUSER text
Send message to administrator at a named location
Command Syntax:
>--- REMOTEMessage <loc> ---+--- ALL -----------.
|
|
|--- FREEuser --------|
|
|
`--- TEam teamid -----+--- text --->
7-131
Command Details
REMOVE
(Project definition)
Function:
Examples:
REMOVE SERV/AREA-D
Command Syntax:
.------------.
/
|
>-- REMove dbname ---*--- dbname ---
|
-------------------->
7-132
Command Details
RENEW
Function:
Description:
7-133
Command Details
RENEW (continued)
Examples:
RENEW DELETE <db>
Renews the transaction DB at the current location
RENEW TRANSACTION/LON AT LON
Renews the transaction DB for London at location London
Command Syntax:
>--- RENEW ---+-- DELETE ----- dbname -----.
|
|
`-- dbname --- AT <loc> -----+--- >
7-134
Command Details
REORDER
Function:
7-135
Command Details
REPAIR
Function:
Examples:
Q REPAIRREQUIRED
REPAIR
REPAIR CHECKONLY
REPAIR NOCHECK
Command Syntax:
>-- REPAIR ---+-----------------.
|
|
+--- NOcheck -----+
|
|
----CHECKonly----+----->
7-136
Command Details
REPLICATE
(Project definition)
Function:
Description:
7-137
Command Details
REPLICATE (continued)
Before you run the macro to recreate the project structure, you
must create the new project-related directories. In a Global
project, this must include transfer directories for each satellite
(for more details, see the TRANSFER command).
Note:
Examples:
REPLICATE XYZ
Copies all data from the current project directories into directories for a
project named XYZ. In a Global project, a new UUID value for the
Project is set (stored in ADUUID of /*GL; this is because each project
requires a unique value of this attribute. This is used by Global
daemons to distinguish between projects at the same location).
Notes: A new UUID value may be queried at /*GL using Q NEWUID.
The administrator may use this value to set ADUUID manually
if a Global project has been copied externally to PDMS.
If ADUUID is left unchanged, there may be data corruption
since daemons may send data to the wrong project.
The ADUUID attribute is essential to distinguish between
Global projects. Each project should have a unique value of
ADUUID. This value is what the Global daemon uses to select
the correct project.
For example if the user copies a project using the file system,
rather than by using the REPLICATE command, then the
ADUUID attribute in both projects will be the same, and this
may cause commands from one Global project to be received by
the wrong Global project.
It is therefore essential that the PDMS Administrator resets the
ADUUID attribute of the project. The NEWUID attribute
provides a way to get a new value, since it makes a 'uuidgen'
query. The Administrator can then use the result of the
NEWUID attribute query to set the ADUUID attribute. Note
that NEWUID is not an attribute of the database. It is a pseudoattribute provided for the purpose of generating a new uid
value for ADUUID.
7-138
Command Details
7-139
Command Details
RESETXREFS
Function:
(Reconfiguration)
Description:
Examples:
RESETXREFS WITH /REFFILE RESOLVE DB MASTER/DESNEW
where /REFFILE is the name of the file generated by the XREF
command and MASTER/DESNEW is the corresponding DB to be updated.
Command Syntax:
>-- RESETxrefs --+-- WIth --.
|
|
----------+-- name --*-- RESOLve --+-- DB --.
|
|
|
|
--------+-- dbname --.
|
|
-- END ----------------------------+-->
7-140
Command Details
REVERT
(Project administration)
Function:
Description:
Examples:
REVERT PIPE/PIPE to 10:30
Reverts database to the session current at 10:30.
REVERT PIPE/PIPE to 31 MAY
Reverts database to the session current on 31st May.
REVERT PIPE/PIPE to SESS 10
Reverts database to the session 10.
REVERT PIPE/PIPE to STAMP /stamp_012
Reverts database PIPE/PIPE to the session that has the stamp
/stamp_012.
Command Syntax:
>-- REVERT dbname to <when> --->
Related Commands:
7-141
Command Details
SAVEWORK
Function:
Description:
Command Syntax:
>--- SAVEWORK --->
7-142
Command Details
SET
Function:
Description:
Set the specified MDB, DB Set or Team as the current one for the
addition or removal of DBs or users, respectively.
Once a team has been set, DBs owned by that team can be
referred to by using the database part of the name only.
Examples:
SET MDB /RAB
Sets current MDB as RAB.
SET DBSET /ASET
Sets current DB Set as ASET.
SET TEAM PIPING
Sets current team as PIPING. Abbreviated references to the DBs
/AREA-A, /AREA-B etc. will automatically be taken as references to the
actual DBs PIPING/AREA-A, PIPING/AREA-B etc.
Command Syntax:
>--- SET ----+--- MDB name ------.
|
|
|--- DBSET name ----|
|
|
`--- TEAm name -----+--->
Querying:
>--- Query SET --+--- MDB ----.
|
|
|--- DBSET --|
|
|
`--- TEAM ---+--->
7-143
Command Details
STATISTICS
Function:
Description:
Examples:
An example of the output from DICE when statistics are
requested is as follows:
OVERALL STATISTICS
==================
Total no. of entries in Name Table = 111
Total no. of elements checked = 782
Total no. of ref attributes found = 726
Total no. of external references = 0
Command Syntax:
>--- STATistics ---+--- OFF ----.
|
|
--- ON -----+--->
7-144
Command Details
STATUSSESSION
Function:
(Querying)
Examples:
An example of output is shown below.
Project:
User: HVAC (75dws52)
Teams: HVAC
MDB: /HVAC
Command Syntax:
>--- STATUSSession -->
7-145
Command Details
STOP
Function:
Examples:
STOP
Related Commands:
FINISH has the same effect
Command Syntax:
>--- STOP --->
7-146
Command Details
SYNCHRONISE
Function:
Description:
7-147
Command Details
SYNCHRONISE (continued)
SYNCHRONISE ALL WITH LON
Synchronise all databases at current location with location LON.
SYNCHRONISE STEELN/STEELN AT LON WITH CAM
Synchronise single database at location LON with location CAM.
Examples of synchronisation of system databases:
SYNCHRONISE SYSTEM WITH CAM
Synchronise the System Database for the current Location with
location CAM
SYNCHRONISE SYSTEM AT LON WITH CAM
Synchronise the System Database for the current location at location
LON with location CAM
SYNCHRONISE SYSTEM FOR OXF AT LON WITH CAM
Synchronise the System Database for OXF at location LON with
location CAM
Examples of synchronisation of the global database:
SYNCHRONISE GLOBAL WITH CAM
Synchronise the Global Database at the current Location with location
CAM
SYNCHRONISE GLOBAL AT LON WITH CAM
Synchronise the Global Database at location LON with location CAM
SYNCHRONISE GLOBAL AT OXF
Synchronise the Global Database at OXF with the current location
Command Syntax:
>- SYNCHronise -+|
||
|
|
|
|
||
`-
dbname --------------------.
|
SYSTEM -+- FOR -+-- LOCAL -|
|
|
|
|
`-- <loc> -|
|
|
`------------------|
|
GLOBAL --------------------|
|
ALL -----------------------+- AT <loc> --.
|
|
`-------------+- WITH <loc> -.
|
|
`--------------+--->
7-148
Command Details
SYSTAT
(Querying)
Function:
Description:
Lists all users who are accessing the project, the modules and
databases which they are using, and whether they have Read-only
or Read/Write access to the database. It also gives the login id and
workstation identifier. You can select what information you want
output: see the following examples.
Examples:
MODE
RW
R
R
R
R
R
R
R
R
R
7-149
Command Details
SYSTAT (continued)
DB
HANGERS/DESI
HANGERS/PADD
HANGERS/CATA
MASTER/PIPECATA
MASTER/STLCATA
MASTER/HVACCATA
MASTER/SUPPCATA
MASTER/PADD
MASTER/DICT
MASTER/PROP
MODE
R
RW
R
R
R
R
R
R
R
R
2 user(s) listed
This shows that two users are using Project SAM:
User HANGER who is using DRAFT, and has Read/Write
access to the Draft database HANGERS/PADD.
User HVAC who is using DESIGN, and has Read/Write
access to the Design database HVAC/DESI.
In a Global project, there may also be a SYSTEM user running
the Globaldaemon module. This shows that the daemon is
running.
You can restrict the output to information about the user, host,
module or MDB as shown in the following examples:
SYS USER HVAC
Lists the information for the user HVAC
SYS NAME an
Lists the information for the user id an
SYS HOST sg107
Lists the information for the workstation sg107
SYS MODULE DRAFT
Lists the information for any users of DRAFT
SYS MDB HVAC
Lists the information for any users of the MDB HVAC
7-150
Command Details
SYSTAT (continued)
Command Syntax:
>--- SYStat ---+----------------------.
|
|
|--- USER username ----|
|
|
|--- NAME loginid ---|
|
|
|--- HOST hostid ----|
|
|
|--- MODUle module ----|
|
|
--- MDB name ---------+--->
7-151
Command Details
SYSTEMLOCATION
Function:
Description:
7-152
Command Details
SYSTEMLOCATION (continued)
Command Syntax:
>-- SYSTEMLOCation <loc> --+-- PRIMARY AT <loc> --.
|
|
|-- LOCAL -------------|
|
|
`-- HUB ---------------+-->
7-153
Command Details
TADD
(Project definition)
Function:
Examples:
TADD SJC
Add user SJC to the current Team.
Command Syntax:
.------<-----.
/
|
>--- TADD userid ---*--- userid ---
|
----------------->
7-154
Command Details
TERM
Function:
Examples:
TERM
Terminates alpha file and outputs reports to screen. This syntax is
equivalent to ALPHA FILE END
Command Syntax:
>--- TERM ----->
7-155
Command Details
TO
(Reconfiguration)
Function:
7-156
Command Details
TO (continued)
Command Syntax:
>- To -+|
||
||
||
||
-
7-157
Command Details
TRANSFER
Function:
Description:
project_loc
where project is the 3-character project code and loc is the 3-
ABC_SYD
ABC_CAM
7-158
Command Details
TRANSFER (continued)
Examples:
TRANSFER TO loc
Copies all database files at the current location, together with
appropriate inter-db macro files etc. to the transfer directory specified
by the project_loc variable.
TRANSFER FROM loc
Updates the current location with the files transferred from Location
loc. Only databases that are allocated at the current location will be
read in.
Related Commands: GENERATE LOCATION
Command Syntax:
>--- TRANSFer ---+--- TO pathname <loc> ---.
|
|
`--- FROM pathname -------+--->
7-159
Command Details
TREMOVE
Function:
(Project definition)
Removes users from the Set (i.e. Current) team.
Examples:
TREM SJC
Removes user SJC from the current Team.
Command Syntax:
.-----<------.
/
|
---*--- userid ---
|
-------------------->
7-160
Command Details
UNLOCK
(Project administration)
Function:
Examples:
UNLOCK
Unlocks all locked databases
7-161
Command Details
UPDATE
Function:
Description:
Database.
Files such as Isodraft files and external plot files are not
propagated automatically by the global daemon. However, there is
a mechanism in the daemon to allow such files to be transferred
to and from neighbouring locations, during scheduled updates or
the UPDATE ALL command. The directory to receive transferred
files is defined by the environment variable %IMPORT%. Each
location to which files are to be transferred requires its own
transfer directory - %EXP_ABC% for location ABC. Transfer of
other data is described more fully in the Global Management User
Guide.
Both Locations must be on-line.
Examples of updating constructor databases:
UPDATE ALL WITH LON
All databases at the current location and all databases at Location
LON will be compared, and updated so that all have the most recent
data.
UPDATE PIPES/PIPES WITH CAM
The PIPES/PIPES database at the current location will be compared
with the PIPES/PIPES database at Location CAM. Updates will be
transferred from the most up-to-date database to the other.
7-162
Command Details
UPDATE (continued)
Examples of updating system databases:
UPDATE SYSTEM WITH CAM
The System database for the current location, at the current location,
will be compared with the System database for the current Location at
Location CAM. Updates will be transferred from the most up-to-date
database to the other.
UPDATE SYSTEM FOR OXF WITH CAM
The System database for location OXF at the current Location will be
compared with the System database for location OXF at Location CAM.
Updates will be transferred from the most up-to-date database to the
other.
Examples of updating the global database:
UPDATE GLOBAL WITH CAM
The Global database at the current location will be compared with the
Global database at Location CAM. Updates will be transferred from
the most up-to-date database to the other.
Command Syntax:
>--- UPDATE ---+--|
|--|
|--|
`---
dbname ---.
|
SYSTEM ---|
|
ALL ------|
|
GLOBAL ---+--- WITH <loc> --->
7-163
Command Details
UPGRADE
Function:
(Reconfiguration)
Produces macros to upgrade a project to a new version of PDMS.
Examples:
UPGRADE /OUTMACRO /INMACRO
This will produce two macro files, OUTMACRO and INMACRO.
OUTMACRO will be used in the old PDMS version to dump the
contents of all DBs in the project to intermediate files. INMACRO will
be used in the new PDMS version to load the intermediate files and
recreate the complete project.
UPGRADE /OUTMACRO /INMACRO FOREIGN db1 db2 ...
All databases, including the list of foreign databases specified by the
FOREIGN option will be upgraded.
UPGRADE /OUTMACRO /INMACRO FOREIGN ALL
All databases, including all foreign databases will upgraded.
Command Syntax:
.---<------.
/
|
>--- UPGrade macro1 macro2 ---+-- FOReign --*-- dbname --
|
|
-------------+--- ALL -----.
|
|
`-------------+--->
7-164
Command Details
VB
(Reconfiguration)
Function:
Examples:
LIBY
#92/842
=16/2404
(24,90)
Warning! library number 242 already exists in the
project.
Duplicate libraries should not be used in the same MDB
EC
DEPT
#16/805 =16/2408
Phase one complete - starting phase two
*** Pass two completed ***
***Reconfiguration Completed
0 Elements were not defined in DDL
0 Elements have been lost
0 Elements are no longer named
3 Attributes were incorrectly defined
0 Elements were not inserted.
Command Syntax:
>--- VB --->
7-165
Command Details
XREF
(Reconfiguration)
Function:
Examples:
XREF /REFFILE
Reference number list to be written to file /REFFILE.
Command Syntax:
>--- XRef filename --->
7-166
Index
Attributes
non-reference
handling of during reconfiguration,
3-1, 3-3
reference
handling of during reconfiguration,
3-1, 3-3
Binary-format files, 3-22
BRIEF command, 3-8
Brief output mode, 3-8
Character-format files, 3-22
Commands
Detailed Descriptions, 7-4
Reconfiguration, 3-2
Summary in Functional Groups, 6-1
Syntax Graphs, 7-1, 7-3
Communications elements
LCOMC (Admin Daemon Config), 4-13
LCOMD (Comms Link Details), 4-13
LCOML (LCOMD Elements List), 4-13
LCTIMD (Event Timings), 4-15
LCTIML (Event Timer), 4-14
LEVENL (Time Interval), 4-14
Copies of databases, 3-9
Copy list (for reconfiguration), 3-3, 3-5, 3-13
DAtaBAse CONtrol program (DABACON),
3-1
Database Structure
index-i
Index
Output
controlling, 3-8
PADD databases
treatment of when reconfiguring, 3-14
Picture files
Projects
upgrading, 3-16
Errors
reconfiguration
controlling limit of for output, 3-9
Extracts, 3-23
Groups
RECONFIGURER, 3-1
reconfiguring, 3-14
INCLUDE command, 3-13
Index
of reference numbers, 3-11
Intermediate files, 3-1, 3-3
Isodraft files, 4-14, 7-165
LOAD command, 3-12
Manual Content, 1-1, 1-2
Messages, 3-19
Index
Source database
for reconfigure operation, 3-1, 3-3
VB Command, 3-8
Very Brief output mode, 3-8
World, 4-8
Transaction elements
World elements
index-iii