Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Module 25
Basic Administration
Training Manual
PLEASE NOTE: AVEVA has a policy of continuing product development: therefore, the information contained in this document may be subject to change without notice. AVEVA 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 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 that you may not have access to 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.
The software programs described in this document are confidential information and proprietary products of AVEVA Ltd or its licensors.
Visit our website at http://www.aveva.com
Contents
Session 1 ...................................................................... 1-1
Project Access.............................................................................................. 1-1 Objectives .................................................................................................. 1-1 Must Know Points ...................................................................................... 1-1 Project Access ........................................................................................... 1-2 Adding Project Environment Variables to the Batch File ............................ 1-5 Starting PDMS ........................................................................................... 1-6
Contents-i
Contents
Contents-ii
Contents
Replicating a Project ................................................................................ 7-17 Deleting Phantom Users/Claim Lists ........................................................ 7-20 The Data Options ..................................................................................... 7-21 Merging Sessions..................................................................................... 7-21 Backtracking Session .............................................................................. 7-24 Inter-DB Macros ....................................................................................... 7-25
Contents-iii
Contents
Contents-iv
Project Access
Session
Project Access
bao qut
Vantage PDMS makes extensive use of Environment Variables they are used to define the location of the PDMS software and Projects. In this section we are going to investigate the setting and the location of PDMS Projects
nghien cuu
bien
Objectives
At the end of this session you will be able to: Add Project Environment Variables Start PDMS and access the AVEVAs SAM Project
1-1
Project Access
Project Access
PDMS requires four Project Environment Variables pointing at four directories, these are set for each project. Project names are made up using 3 Characters. For example, for a Project ABC ABC000 ABCISO ABCMAC ABCPIC Project database directory. Project Isodraft Options directory. Project Inter-DB connection macro directory. Project Draft Picture File directory.
AVEVA supplies three projects on the PDMS CD. SAM IMP MAS Sample Project (Metric) Sample Project (Imperial) He Anh Master Catalogue
We are going to test our PDMS installation using the SAM project. The environment variables for the SAM project have been set up in a batch file called EVAR.BAT which is held in the PDMS executables Directory. All Catalogue information for the SAM project is held in the MAS project so the environment variables for MAS have also been set. We will check the settings of SAM000, SAMPIC, SAMISO, SAMMAC, MAS000 and MASPIC. Normally the MASMAC and MASISO will never be required as no Design or Isometrics will be produced from this project By default the supplied PDMS projects are held in a project directory under the PDMS executables directory.
dieu hanh
co the thuc hien dc
Navigate using the File Manager or My Computer to the Project directory, in this example c:\AVEVA\pdms11.6\project
1-2
Project Access
1-3
Project Access
The evars batch file checks to see if the variables are set and if they are not set they are set to the default location.
1-4
Project Access
PDMS makes extensive use of environment variables and more of these are explained in Session 8.
1-5
Project Access
Always make modifications to environment variables in the batch file, do not include them as system variables as this may create conflicts between PDMS versions.
Starting PDMS
Double click on the Run PDMS Shortcut Or Start > Programs > AVEVA > VANTAGE PDMS 11.6 > Run PDMS
1-6
Session
Creating a new Project
Objectives
At the end of this session, you will able to: Creating a new Project Creating Teams Creating Users Creating Databases Creating Catalogue, Dictionary and Properties databases. Copying Databases Including and Copying Foreign Databases. Multiple Databases (MDBs)
2-1
6. FINISH The new PDMS database directory TAD000 will now contain three system databases, TADSYS, TADCOM, and TADMIS. At versions of PDMS prior to PDMS 11.4.SP1 virgin databases would have been copied from the %pdmsexe% directory this practice has stopped and the virgin databases are used directly from the %pdmsexe% directory. Note : The variable %pdmsexe% will have been set to point at c:\AVEVA when we installed PDMS.
2-2
It would be normal practice at this point to change the system password (SYSTEM/XXXXXX) to a new one for security reasons. For the purposes of this Training Manual we will be changing it later during User Modification.
2-3
STEELN STEELN/STEELN STEELS STEELS/STEELS DRAFT ISO ADMIN DRAFT/DRAFT ISO/ISO ADMIN/ADMIN
In addition, the following Teams and Users will be needed for the administrative functions:
Team PARAGONADMIN DESIGNADMIN DRAFTADMIN ISOADMIN User/Password PARADM/PARADM DESADM/DESADM DRAADM/DRAADM ISOADM/ISOADM
2-4
Creating Teams
1.
On the Admin Elements Form Select Elements Teams Select the Create Button
2.
3. 4. 5. 6.
Type the Team Name CATA Description Team for Project Catalogue Select Apply Continue to create all the Teams as described above.
7. 8.
Modify the description of team MASTER by selecting Modify and then select Team master on the Admin Elements Form Dismiss the Modify Team Form
2-5
Creating Users
1.
On the Admin Elements Form Select Elements USER Select the Create Button
2.
2-6
3. 4. 5. 6. 7.
Type the User Name CATA Password CATA Security Select GENERAL (see note below) Description User for Project Catalogue Select Project Team CATA and add to Membership Using the Arrow. Select Apply
8.
Note: The use and setting up of User Access Control Rights is covered on the Advanced System Administrators Course and will be left Blank. 9. 10. Continue to create the Users ADMIN, DRAFT, PIPEN, PIPES, STEELN and STEELS as described above. Remember to select the appropriate Team Modify the description and the password of the User SYSTEM by selecting Modify and then select <User> SYSTEM on the Admin Elements Form. Form this exercise change the SYSTEM password to TAD Dismiss the Modify User Form
11.
You should now have the Users as shown below: Database access depends on attributes of the User and of the Database Users can be: FREE Users May enter all modules. May update any databases. GENERAL Users May not enter the Restricted modules, which are usually the administration modules of ADMIN and LEXICON. May only modify databases for teams of which they are members. Note: User privileges also control access to modules.
2-7
Creating Databases
1.
On the Admin Elements Form Select Elements Databases & Extracts Select the Create Button
2.
Note: The use and creation of Extract Databases is covered on the Advanced System Administrators Course.
3.
We will first create a Design Database for PIPEN. 4. Select Team PIPEN 5. Name DESIGN 6. Description North Area Pipes 7. Select Database Type Design (The explination of Database Types is described Below) 8. Access Mode Update, Implicit Claim.
(The explanation of Access Modes is described Below) 9. Area Number, DB Number and File Number for this example should be left at System.
2-8
10. Select Apply 11. Continue to Create Databases for Teams PIPES, STEELN, STEELS. 12. Create a Draft database for Team DRAFT, remember to change the database type to DRAFT.
Database Types
A PDMS project can contain the following types of database: Administration databases The SYSTEM database itself, which holds the access control data for the model data and modules. The COMMS database, which stores information about who is using which module and which model databases are available. The MISC database which stores inter-user messages, and inter-database macros. Model Databases DESIGN databases which contain all the design information for the project. CATALOGUE databases which contain the project catalogue and specifications. PADD databases which contain data about drawings produced by DRAFT. ISOD databases which contain spool drawings produced by SPOOLER. PROPERTIES databases which can contain material properties, and can be referenced by the catalogue. DICTIONARY databases which contain the definitions of user-defined attributes (UDAs), as set up in LEXICON. COMPARATOR databases which are used by Design Manager. (You may not be licensed to use this product, in which case this type of database will never be used.) Databases can be: UPDATE CONTROLLED MULTIWRITE Allow one writer and n readers. Allow one writer and n readers, the same as UPDATE. Write access is controlled externally to PDMS. Allow n writers and m readers.
2-9
MULTIWRITE databases
The use of Multiwrite databases is explained later in Session 6.
2-10
1. On the Admin Elements Form Select Elements Databases 2. Select the Create Button 3. Select Team CATA 4. Name PIPE 5. Description Project Pipe Catalogue 6. Database type Select Catalogue 7. Access Mode Update, Implicit Claim. 8. Area Number and File Number for this example should be left at System. 9. Set DB Number 5050 10. Select Apply 11. Create databases CATA/STEEL (5051) Catalogue, ADMIN/DICT (5052) Dictionary, ADMIN/PROP (5053) Properties.
2-11
You can use the Modify button to change the database names should you require.
Database access is controlled by the Team so by changing the Team of a database user access can be changed.
2-12
Copying Databases
Copied databases can be used for: Copying a template project Merging projects
Copying included databases before archiving Databases can be copied by selecting Database from the Element option button on the Admin Elements form, selecting the element you want to copy from the scrolling list, and then pressing the Copy button. The Copy Database form will be displayed. Note that you cannot change the Database number of the copied database. This will be same as the original. You cannot have more than one database with the same database number in the same MDB. Note: To avoid the risk of database corruption, all copying of databases (i.e. the files inside the Project directory) must be done from the ADMIN module and not by using operating system utilities or commands.
Teams must exist for all databases that are to be shared. Databases in the source project that will be shared must NOT be given a database number that will clash with a database number that already exists in the destination project.
Note that Foreign Databases are marked with * in the database list. You can exclude foreign Databases by pressing the Exclude DB button on the Admin Element form. The ExcludeDb form will be displayed
2-13
You can also include databases from the sample project, Using the options under Install on the main menu These options are as follows:
Sample Project > Foreign Master dbs
copies all the MAS databases in the Sample project to the local directory
Foreign Master dbs
The options allow you to set pointers to individual databases in the MAS project.
Local Master dbs
The options allow you to copy individual databases in the MAS project to the local directory Deleting Databases Databases can be deleted by selecting the element from the scrolling list on the Admin Elements form and then pressing. Note: To avoid the risk of database corruption, all deletion of databases (i.e. the files inside the Project directory) must be done from ADMIN and not by using operating system utilities or commands. Using Different Areas The Area Number will accept values in the range 1 to 9. If the value is set to System (using the button next to the gadget) then the database area will be set to the system default (0). Note: The environment variable for a databases area must exist when the database is created or moved. To complete the database additions on our example project we are going to include all the databases for the MAS project and copy a database from the SAM project.
2-14
To include all the databases from MAS Select INSTALL > Foreign Master DBs > All
This command will have included most of the databases from MAS the rest will need to be included manually. You can see on the form below that all foreign databases are indicated with an asterisk * To include additional databases from MAS 1 On the Admin Elements Form Select Elements Databases 2 Select the Include Button
2-15
3. 4. 5. 6. 7.
Select MAS project Username SYSTEM Password XXXXXX Select the foreign Databases MASTER/COMP Select Apply
8.
2-16
9. Select Apply 10. You should now have the following databases defined: -
2-17
You may now wish to resize the Admin Elements From Select Settings > Display Mode > Resize Admin Elements Form
2-18
The Admin Elements Form will now look like this. It may also require stretching by dragging the bottom right corner hand corner of the form.
2-19
2-20
For the Training exercise we are going to create six MDBs, PIPEN, PIPES, STEELN, STEELS, DRAFT and CATA. These MDB will be used by each of the associated users as described earlyier. 1. On the Admin Elements Form Select Elements MDBs 2. Select the Create Button
3. Enter the name of our first Pipe user PIPEN 4. Description North Pipes MDB 5. Sort By Number 6. Select Project Database PIPEN/DESIGN 7. Use the down arrow to move PIPEN/DESIGN to the Current Databases field. 8. Select Insert AFTER 9. Highlight PIPEN/DESIGN in the Current Databases
2-21
10. Select all the Project databases (RH mouse button in Project Database window ) 11. Change Insert from Before to After and press the down arrow. 12. Select Apply 13. Continue to create MDBs for the other users. (remember you could use copy)
The order in which the databases are included is very important, the users write access database should be the first in the list and the rest should follow in the order that they will be accessed. Frequently used databases should be near the top of the list.
2-22
At this point we will go into PDMS Design as different users and check that we can create items and see items created in other databases.
2-23
Session
Testing PDMS Access
This session tests that you are able to create Equipment and Pipes in PDMS using multiple User Names.
Objectives
At the end of this session, you will able to: Create Equipment as PDMS User PIPES and create Pipes as PDMS User PIPEN
3-1
An Inter database macro will have been created as the Pipe is in a different database to the equipment.
3-2
Session
References Between Databases
This module explains the relationship between databases and the use of Inter database connection macros.
Objectives
At the end of this session, you will able to:
4-1
When you connect Branches PDMS sets the Head Reference (HREF) or the Tail Reference (TREF) to the Item it is connected to, for example a Nozzle or a Tee Name. It also sets the Connection Reference (CREF ) of that item to point at the Branch that has been connected. If you have write access to the connected component it just connects and sets the relevant connection references. If you dont have write access an Inter-database connection macro is created.
4-2
If you have any Inter-database macros to run there will be a message in Monitor highlighted in red: You have Inter-DB Macros to run To find out there names Select Project > Inter-DB Macros
As you can see we have one macro to run, make a note of the name and enter Design.
4-3
Before we run the Inter-DB macro go to one of the Nozzles we build earlier and query the CREF, it should be Nulref (=0/0). The Inter-database macros are run via the command line. Display the Command Line Display > Command Line
The variable %tadmac% points to the Inter-database macro directory that we set up earlier. The CREF attribute of both Nozzles will now have been set.
4-4
Session
Objectives
At the end of this session, you will become familiar with:
5-1
Introduction
If you have more than one user who wishes to access PDMS it will be necessary to share PDMS and the databases across a Network of computers. The Installation of PDMS can be performed in two ways: 1. A full version of PDMS on each PC 2. A client version of PDMS on each PC For the purposes of this training we are going to assume that the required version has been installed on the PCs.
1.
Navigate to the c:\ drive using the file manager or My Computer Select the AVEVA Directory using the RH Mouse Button. Select Sharing
2.
3.
5-2
You will now be able to see the AVEVA directory via Network Neighbourhood. (Network Neighbourhood on NT or by using My Network Places on W2000) In the following example the PC name is PC517. Navigate to Network Neighbourhood using the File Manager or Network Neighbourhood.
The network name of this directory will be \\pc517\AVEVA. We will now need to modify the PDMS batch file and replace any references to the c: drive with pc517.
5-3
Creating Shortcuts
For the purposes of this Training move to another PC, Login and navigate to the PDMS executable directory using Network Neighbourhood or the File Manager. Select PDMS.bat with the RH Mouse Button and Select Create Shortcut.
Drag this Shortcut to the Desktop. The Start in: directory should be changed to point to a User Directory as this is the place that PDMS will place output files. I should not be left as the PDMS executables directory. Modify the Properties of the Shortcut by selecting Properties via the RH Mouse Button To change the icon to the PDMS Logo 1. Modify the Properties of the Shortcut by selecting Properties via the RH Mouse Button 2. Select Change Icon
5-4
Browse the network and Select des.exe from the PDMS executable directory 3. OK all the forms and you will now have the new Icon. 4. Modify the Start up directory to point to a local drive for example c:\userdata or c:\temp 5. Rename the shortcut via the RH Mouse Button to say PDMS 11.6 You can now test this shortcut.
Modify the Shortcut and add PROJECT USER/PASSWORD MDB Module. The module name could be replaced by a macro $m/start.mac etc. You may wish to rename the Shortcut to reflect the Project and user.
5-5
Session
MULTIWRITE Databases
This module explains the use and creation of Multiwrite databases.
Objectives
At the end of this session, you will able to:
Understand the use of MULTIWRITE Databases Create Multiwrite databases Modifying Items in a Multiwrite database Claim Lists
The following points need to be understood by the trainees. How to Create Multiwrite databases.
6-1
MULTIWRITE Databases
MULTIWRITE Databases
DESIGN, CATALOGUE, DRAFT (PADD) and ISODRAFT databases can be multiwrite. The SYSTEM database is always multiwrite. For multiwrite databases, it is better to split the database content according to the different team responsibility. This will normally be determined by: The physical layout of the plant. The different engineering disciplines involved.
Databases may be switched between UPDATE and MULTIWRITE at any time. One recommended way of working is to start with an UPDATE database for each user. This keeps a tight control on the write access. Then if a particular database requires intensive work at some stage in the project, the database can be switched to multiwrite to allow several users to make the required changes simultaneously. For multiwrite databases, it may be more appropriate to add several databases to the same team, and allow several users to belong to that team.
6-2
MULTIWRITE Databases
1. 2.
Enter PDMS Admin On the Admin Elements Form Select Databases Select PIPEN/DESIGN Select Modify
3. 4.
5.
Change Access Mode to Multiwrite, Implicit Claim Select Apply Select Dismiss
6. 7.
When you use Implicit Claim if you modify an item you claim the Item for modification. This mode must be used as some applications may not be set up to claim items before modification.
6-3
MULTIWRITE Databases
6-4
MULTIWRITE Databases
As the database containing the pipe is in a Multiwrite database we are able to modify it.
6-5
MULTIWRITE Databases
Claim Lists
Select Utilities > Claim Lists
When working in Implicit Claim mode, each time you modify an item in Design the significant Item, Bran, Equip etc is added to the Claim List. For standard Multiwrite databases Claims can be release manually using Unclaim and are released automatically when the Designer leaves PDMS. If the designer leaves PDMS abnormally the items will remain claimed.
6-6
Session
Project Administration
This module is an overview of the options on the main ADMIN menu. They are described in the order in which they appear on the menu, reading from left to right. Some of the simpler options are described in full, and some of them have references to other modules, where they are described in more detail.
Objectives
At the end of this session, you will be familiar with:
Locking/Unlocking the Project Database Admin Options Display Options Query Options Settings Options Utilities Options Project Information Understand the use of Fonts in PDMS Set Up Font Families How Modules are Defined The Module Definition Form Setting the DABACON Buffer Size Replicating a Project Deleting Phantom Users / Claim Lists Merging Sessions Backtracking Sessions Inter-DB Macros
7-1
Project Administration
Locking/ Unlocking the Project Database How to set the Imacro Deleting Phantom Users / Claim Lists Merging Sessions Backtracking Sessions
7-2
Project Administration
Project Administration
This Chapter is an overview of the options on the main ADMIN menu. They are described in the order in which they appear on the menu, reading from left to right. Some of the simpler options are described in full, and some of them have references to other chapters, where they are described in more detail.
You should always Lock the project before carrying out database modifications.
7-3
Project Administration
Note: You cannot QUIT (that is, exit without saving changes) from ADMIN. This is to ensure that there are no inconsistencies between the actual database files and the record of the databases in the Project stored in the System database.
7-4
Project Administration
Abnormal Exits
If you exit abnormally from ADMIN, for example because of a power failure or system crash, and you list the database files in the operating system, you may see files with a .deleted extension. This is because when you do any task that involves deleting a database file in ADMIN, PDMS copies the file to be deleted to a new file with the .deleted extension. When you SAVEWORK, or exit normally which automatically does a SAVEWORK, the .deleted files are removed. However, if there is a problem which results in database files being deleted, and an exit occurs before the System database can be updated with the changes, PDMS will rename the .deleted files, removing the extension, so that the files will still be available.
Display
Selecting Display > Admin Elements will display the Admin Elements form, if it has been closed. Selecting Display > Command Line will display the Command Input and Output window.
7-5
Project Administration
See the online help if you need further information about these forms.
7-6
Project Administration
The Settings > Change Password option allow you to set whether or not users can change their passwords. If you select Enabled, users will see a Change Password option on the menu on the main Session Manager window, which will allow them to change their passwords. Otherwise, a password can only be changed within ADMIN.
7-7
Project Administration
An individual user All members of a specified team All active project users
The message will be displayed only to users already in PDMS when the command is given, and then only when they change modules or leave PDMS. You can list messages. A message is automatically deleted once it has been displayed. (Messages are only displayed in a System Command Window and could be missed, this is an old feature, it may be better to use e-mail)
7-8
Project Administration
Information allows you to add descriptive information about the project. Font Families allows you to set the fonts used in DESIGN and DRAFT. Module Definitions allows you to change the PDMS module definitions. Replicate allows you to replicate the project structure. See later in this Module. Expunge allows you to remove phantom users from the Project after an abnormal
exit.
Data Access Control allows you to turn on Data Access Control this is covered on Advanced System Administrators Course. Turning on DAC by default will remove all access to PDMS
Project Information
You can add descriptive information about the Project by selecting Project > Information from the Main Menu. The PROJECT Information form will be displayed. You can set the Name, Description, Message and Number. The maximum numbers of characters are 119 for Name, Description, and Message, and 16 for Number. If set, these details are displayed each time the PDMS project is entered. They can be reset in ADMIN at any time.
7-9
Project Administration
Change the Project information as Indicated above, and go into Monitor to see the effects. You could also query the Project information Q PROJ Q PROJ Num
7-10
Project Administration
Font Families
The System database stores details of four font families, numbered 1-4. These families may be defined using ADMIN itself, or the commands can be included in the makemac.mac macro used to create the project. All four families are used by DRAFT, but only the first is used by the other graphical modules. Note that all PDMS font files have the suffix .gfb.
Character Sets
A character set is specified by name or by a CADC code number derived from its International Registration (ISO-IR) number or from its ISO 8859 part number. The available character sets are: Name Latin 1 Latin 2 Latin Cyrillic UK US Greek Cyrillic Code 885901 885902 885905 4 6 18 37 Description ISO 8859-1 Latin alphabet No. 1 ISO 8859-2 Latin alphabet No. 2 ISO 8859-5 Latin/Cyrillic alphabet Standard UK ASCII (ISO 646 Reg 4) Standard US ASCII (ISO 646 Reg 6) ISO 2375 Registration 18 ISO 2375 Registration 37
The ISO 8859 sets contain all the characters of the standard US ASCII set plus ranges of extra punctuation marks, symbols, accents, accented characters, and combined characters. Latin-1 provides additional characters for the following languages: Danish French German Italian Albanian Rumanian Dutch Icelandic Norwegian Faroese Finnish Irish Spanish Portuguese Swedish.
Latin-2 provides additional characters for the following languages: Czech Serbo-Croat German Slovak Hungarian Slovene Polish
7-11
Project Administration
Latin/Cyrillic provides additional characters for the following languages: Bulgarian Serbo-Croatian Byelorussian Ukrainian Macedonian Russian
Character Styles
The character styles are also specified by name or code number. The available styles are: Name Line Block Serif Italic Script Typewriter UWLine Code 1 2 3 4 5 6 7 (Uniform Width Line)
Styles 1 to 5 are proportionally spaced, that is the spacing of the characters varies depending on the characters. Styles 6 and 7 have fixed spacing and so are better for the construction of lists or tables where items must line up vertically. Not all styles are available for every character set. An error will be output if a specified combination is not available.
7-12
Project Administration
User-defined Fonts
A font family may also be defined by two user-supplied font files. One file is used to define the standard character set and the second (optional) file to define a bold version of it. These user-supplied files must be in PDMS font-file format and have the suffix .gfb. AutoCAD character shape files (.shp format) can be converted to .gfb format using the Font Converter supplied as part of the PDMS Software Developer's Kit. For details contact your local AVEVA Support office, listed on the copyright page of this manual.
Sloping Fonts
For each font family, you can define an angle of slope between -85 and +85 degrees inclusive. This will cause the text to be sloped forwards (positive angles) or backwards (negative angles).
7-13
Project Administration
The Font Directory sets the directory where the font files are stored. The Current Font Settings show the four fonts that are available. It shows whether they are System-defined or User-defined, the character set (Type) and style. You can change the definition of the font selected in the list by changing the settings on the rest of the form.
Modules
The modules are set up in the supplied product, and you will not normally need to create or edit module definitions in order to run PDMS. The only part of the definition that you may wish to change is the initialisation macro (imacro), which is run on entry to the module. The initialisation macro typically contains module-specific commands to set up the screen display, including loading application macros.
7-14
Project Administration
The Settings window displays the settings for the Module selected in the modules List. You can change all of these except the Number and Name. Security can be set to Restricted, General or Free. Runfile sets the file used to start up the Module. The defaults are supplied in the %PDMSEXE% directory. Imacro sets the file used to start up the GUI for the Module. A typical value as used in the Design Module would be %PDMSUI%/des/ADMIN/START. The Advanced button displays the Advanced Module Settings form. This form allows you to set the buffer size (see next section), the default database type and access for the Module. Note: Changing the options on this form may cause serious problems when using PDMS. The form is for expert use only.
7-15
Project Administration
7-16
Project Administration
Replicating a Project
The Project > Replicate options enable you to replicate the whole project, including all the data, or just the structure of the project. The Project Data option copies the current Project to a new Project. Before you use this option, you must create the project directories and set the environment variables for the copied project. Then enter the new project code on the Replicate Project form. Note: A project must not be replicated outside PDMS by copying the whole of the Project directory to another Project directory. This is because information about the project name is stored inside the DBs themselves. Before you can use this option it will be necessary to create the four environment variables and the project directories as described earlier. For the exercise, create a PDMS Project called TCP. Remember to create the project variables and associated directories for TCP000, TCPPIC, TCPMAC and TCPISO adding them to the PDMS batch file. 1. Select Project > Replicate > Project Data
7-17
Project Administration
The Project Structure option creates a macro which can be run into PDMS to replicates the structure of the current project. No data is copied. When you select this option, a file browser is displayed so that you can give the pathname for the macro. ADMIN scans the System database and outputs to the file all the commands necessary to recreate the project structure, in the following order: Create users, Create teams, Add users to teams, Create DBs, Make Copy DBs, Create MDBs, Add DBs to MDBs and make them current if appropriate In this example we are going to create a macro to replicate the project structure. 1. Select Project > Replicate > Project Structure
This macro is often used as the basis for creating all new projects and is customised by each company to suit their requirements.
7-18
Project Administration
It may be necessary to edit this file to modify User Name and Passwords.
7-19
Project Administration
The Project > Expunge > All Users option will remove all phantom users from the system. You will be prompted to confirm that this is what you want to do.
The Project > Expunge > User Processes option will display the Expunge form. The current process is shown by an asterisk. ADMIN will not let the Current User be expunged.
7-20
Project Administration
The Project > Expunge > Claimlist option will display the Expunge Database Claim List form.
The Data options on the main menu are as follows: The Data >Change Management options allow you merge and backtrack PDMS sessions. The Data >Inter Db Macros option allows you to manage the macros generated by PDMS when a User needs to write to a database to which the User does not have access. The Data > Extract Databases Control this is covered on Advanced System Administrators Course.
Merging Sessions
PDMS sessions enable a history of changes to the database to be recorded. When a new session is made, the changed data is appended to the end of the database file. Appending updated data to files will increase the disk space required. If the history information is not required, and to save disk space, you can compact a database by merging sessions. You can specify that the changes before or after a given date or session number will be merged.
7-21
Project Administration
For example, there may be a session, which corresponds to a project milestone, which you need to keep, in which case you can merge the sessions around this. In other cases you may wish to merge all sessions before a given date or within a given week. Merging the database sessions has no effect on any database references into that database from other databases. To merge sessions, select Data >Change Management > Merge Changes from the main ADMIN menu. The Merge Changes form will be displayed.
You can merge the changes to All Project Databases, the System databases, or the Single Project database selected in the list. If you choose All Project databases, you can merge all changes, or changes before or after a given time, date or session number. If you choose System Database, you can merge changes before or after a given time, date or session number.
7-22
Project Administration
If you choose Single Project database, choose a database from the list. Note that the More button is now available. This will display the Database Sessions form, which lists information about the existing sessions for the database.
As you can see all the sessions have been merged and the database size will have been reduced. This would normally only be done after getting a project archive. The Rebuild list button is used to update the list of databases. For example, if a new database has been created while the form is displayed, the list will not be updated until the form is closed and re-displayed, or the Rebuild list button is pressed.
7-23
Project Administration
Backtracking Sessions
You can return a database to the state it was in at a previous session, you can backtrack using the Data > Change Management > Backtrack Changes option on the main ADMIN menu. The Backtrack Changes form will be displayed. Select the database required from the list. You can backtrack changes by specifying a time, date or session number. Note: Subsequent sessions will be lost, and so you may wish to copy a database before backtracking. You can backtrack to the date or session number required.
The Rebuild list button is used to update the list of databases. For example, if a new database has been created while the form is displayed, the list will not be updated until the form is closed and re-displayed, or the Rebuild list button is pressed.
7-24
Project Administration
Inter-DB Macros
Any Inter-DB macros can be displayed by selecting Data > Inter-db Macros from the Main ADMIN menu. The Inter-db Macro form will be displayed. A macro can be deleted by selecting it in the scrolling list and pressing Delete. This
allows the Administrator to delete any macros, not just the macros for the current Team. Remember Inter-DB macros are created in the following situations:
A user in DESIGN attempts to make a connection to an element which is in a Design database to which the user does not have write access, A user in DESIGN attempts to make a connection to an element which is in a Multiwrite Design database to which the user has write access, but the element is claimed by another user. A user in ISODRAFT updates REVISION and DETAIL attributes, which need to be stored in the Design database, to which the user has no access. The Administrator would normally check the project users before deleting Inter-DB macros.
7-25
Session
PDMS Environment Variables
We have seen the use of Project Environment Variables ABC000, ABCPIC, ABCISO and ABCMAC that are used to point at out projects. PDMS make extensive use of these variables. The PDMS installation guide has a full list of these variable and there uses. The following section describes the use and modification of some of these variables
Objectives
At the end of this session, you will able to:
8-1
8-2
In our example this would be c:\AVEVA\pdms11.6\pdmsui If you have a look in this directory you will see a structure where Des holds the Design Interface, Dra holds the Draft Interface, Iso holds the Isometric interface etc. For the purposes of this training we are going to load CATVIEW 11.3 (This is the current version). CATVIEW is used by the Cats and Specs people to help them create Piping Specifications.
Loading CATVIEW
1. 2. Locate CATVIEW on the PDMS CD. Install CATVIEW to the AVEVA directory. e.g. c:\AVEVA (or \\pc517\AVEVA for server installation) A batch file is provided to point PDMS at this extra User Interface, this batch file will require modification to suit your system. 3. Navigate to the CATVIEW directory you have just installed.
4.
Edit the file evars.bat Make sure that the catview variable points to the correct location of Catview. For example set catview=c:\AVEVA\catview11.6
8-3
Modify the PDMS.BAT file and include the line call c:\AVEVA\catview11.6\evars.bat after the line call %pdms_installed_dir%\evars %pdms_installed_dir% The modified section of the file would now look like this.
8-4
Testing CATVIEW
Enter PDMS Module PARAGON and enter the Pipework application Select Utilities > Catview
Display one of the Components. Cats and Specs are the subject of a separate course.
8-5
Session
Data Integrity Checking
This chapter describes the PDMS Data Integrity checker known as DICE. DICE checks the internal structure of a database.
Objectives
At the end of this session, you will able to:
Use DICE Use FULL and BRIEF Modes and Maximum Errors Producing Statistics Checking External References Format DICE Output
9-1
Is the complete data hierarchy intact? For example, do all lists contain all of the members that they should contain? Are all element names correctly stored and accessible? Are references to other databases valid? If not, a warning will be output. The most likely cause is a deleted database. If the answer to any of these questions is no, a message will be output, either to your screen or to a named ASCII file in your working directory. DICE also tells you how many elements are stored. An error in the network, resulting in loss or nonarrival of data. An error on copying databases. In particular, this can lead to truncated databases. Insufficient disk space or storage quota, so that the project area fills up while a database is being updated. Deletion of a DB which is referenced from another DB. Reconfiguration of a DB without a corresponding update of all DBs which have references pointing into it. An undetected fault in the PDMS Database Management software
It is important that any corruption which does occur is detected as quickly as possible, so that the System Administrator can replace the faulty database by a backup copy. For this reason, DICE is designed to operate as fast as possible, using relatively little computer resource, so that it is economic and practical to check the whole of the project database on a regular basis, and not just when an immediate need arises, such as after a computer failure. It is recommended that DICE checks should be run frequently, for example, before a daily backup is taken. DICE should be run at least once a week.
The total number of elements in the DB The number of referenced names in the DB
9-2
Preparatory Steps before Checking Starts A summary of most of the project information stored in the System DB can be obtained by using the Query options. This may be helpful when deciding which DBs need a detailed check. Although DICE can never alter the contents of a DB which it is checking, it always accesses the DB in Read/Write mode, to prevent anyone using the database while it is being checked. You cannot, therefore, check any DB which is in use elsewhere. You can use the Query options to see which other users are currently accessing the project, which DBs they are using, and what their access mode is to each. You may wish to lock the project by pressing the Lock button on the main menu. Locking prevents any more users from entering the project, although current users will be able to continue working.
Using DICE
Select Utilities > Integrity Checking from the main menu and the Data Integrity Check form will be displayed.
9-3
The Check options at the top of the form allow you to choose which databases you want to check. If the option button is set to Selection, you can pick the databases you want from the list. All selects all the databases in the list, and Clear clears the selection. The other options under Selection allow you to check the Project database or the System database. The Settings options control the types of check carried out, and they are described in the following sections.
Producing Statistics
STATISTICS OFF specifies that no statistics will be generated. STATISTICS ON causes DICE to produce a statistical summary of the DB, including its size, the number of elements contained within it, etc. See Section for an example of the type of output produced.
9-4
Is the referenced DB a valid type? For example, a reference attribute in a Design DB which points to a DRAFT DB must be illegal. Is the position pointed to within the limits of the referenced DB? Note that for a copied DB, DICE only checks that the reference is within the limits of the largest copy. A non-fatal error message is produced for each invalid external reference found. The REJECT option should normally only be used when you are certain that the database which is being checked should not contain any external references, for example, to a Dictionary database. If this command is used any external reference found in the database will be reported as a fatal error and further checking will be abandoned. If databases have been copied, the references will be checked against the first copy found.
Macros
Normally the System Administrator will set up standard macros for the regular use of DICE. DICE has two modes of operation: From within PDMS. This is the normal way of using DICE. You can use it to check a single DB, several DBs or a whole PDMS project. You can use the Database Integrity Check form for a quick interactive check, or you can write a macro. As a stand-alone program. This is useful, for example, when the System DB has been corrupted. DICE can be used to check the System DB from outside the PDMS project. In stand-alone mode, DICE can only check database files one at a time. The commands needed to write DICE macros, or to run DICE as a stand-alone program, are described in the PDMS ADMIN Reference Manual. Some of the commands in DICE can only be used from within PDMS, some can only be used in stand-alone mode and the rest is available in either mode. DICE detects which mode it is operating in and rejects any inappropriate commands.
9-5
DICE Output
As each DB or file is checked, a report is sent to the screen or a file. The basic report, produced in response to any CHECK command, consists of three sections: A report header, which includes information about the date and time of the check, the general details of the DB which is to be checked (DB name, DB number, filename, size, etc), and the options selected. An error report, which lists details of any errors encountered during the checking process. This will contain just one error and any number of warnings in BRIEF mode, but up to the number of errors and warnings specified by if FULL has been specified. A report summary, which tells you whether the DB is free from structural faults, suspect or definitely corrupt. Other output sections, which will be appended to the basic report if they have been requested, are:
All the information which DICE can determine about a DB before starting its detailed checks is presented in the report header. If any particular item of information cannot be determined (for example, the project name when running in standalone mode), it is presented in the header as
*UNKNOWN*
The format of the header is as follows: ***************************** * DATABASE INTEGRITY REPORT * *****************************
Date TAD Oct 96 Time 16.02 Project Database TAD SYSTEM Filename /%TAD000%/tad000 DB number 1 DB type SYSTEM DB size 133 Pages (0.272 Million bytes) Maximum size 2000 Pages DB is 0.% full Page size 2048 bytes
9-6
Options requested
STATISTICS OFF CHECK EXTERNAL REFERENCES LIST REFERENCED DATABASES FULL CHECK DDL version 10.0 8/10/92
Database has no structural errors DICE Banner. This is repeated at the beginning of each report, in addition to its display when first entering the module. It confirms the particular version of DICE which produced the report. Date and Time. The date and time at which the check was started for that particular DB or file. Project. The three-character PDMS project code. Database. The name by which the DB is known within the PDMS project. Filename. The name of the external file containing the DB. DB number. The DB identification number, as it appears in the output from the LIST FILES command. DB type. Design, Catalogue, Drawing etc. DB size. The amount of space, in pages and megabytes, currently used by the DB in its file. Also shown are the maximum size (in pages) and the percentage of space filled. Note that if the database is more than 90% full, the space filled is output as a warning. Page size. The number of bytes per file page. Options requested. Confirms the settings of the checking options: STATISTICS OFF or BRIEF STATISTICS or STATISTICS ON CHECK EXTERNAL REFERENCES LIST REFERENCED DATABASES BRIEF CHECK or FULL CHECK Finally the report summary and the error report will be given, as described in the following sections.
9-7
9-8
Session
Reconfigure
10
The Reconfigure Module has been withdrawn at PDMS 11.2 the functionality has been included in Admin. Reconfigure is not used as much as it was at earlier releases, this is because it is now not used to compress databases. Database compression is not done by Merging Sessions as described earlier. You can use Reconfigure to Upgrade Projects, Move data between databases or projects.
Objectives
At the end of this session, you will able to:
Understand Basic Reconfigure Command Understand the use of Intermediate / Dump Files Perform a Simple Reconfigure Perform a Partial Reconfigure Perform a Reconfigure using the SAMEREF option
10-1
Reconfigure
Reconfigure
The Reconfigure Module has been withdrawn at PDMS 11.2 the functionality has been included in Admin. Reconfigure is not used as much as it was at earlier releases, this is because it is now not used to compress databases. Database compression is not done by Merging Sessions as described earlier. You can use Reconfigure to Upgrade Projects, Move data between databases or projects. The process of Reconfiguring can be roughly split into five commands : FROM TO RCFCOPY RECON RCFUPDATE The Database of file where the information is coming from. The Database or file where the information is going to. The data you wish to copy. The reconfigure command. When you create a new database the reference numbers used by PDMS will change. It would be correct to deduce that databases using this information must be changed to point at the new references. We will need to update all databases which point to it to the new database.
10-2
Reconfigure
Reconfigurer Commands:
The FROM Command Although, the syntax graph for FROM offers several options, the one normally used is: FROM DB dbname
FROM PROJECT projectid dbname - should be used with great care. A DB can be transferred from another project, but it must be completely independent of other DBs, i.e. it must be self-sufficient with no pointers to other DBs.
>------FROM----+----FIles-----file 1-----file 2----. | | |----SYStem-------------------------| | | |----DBFile--------name-------------| | | |----PROJect---projectid----dbname--| | | ----DB------------dbname-----------+---->
The only safe use of this command would be to transfer the catalogue database of an old project into a new project. The old database would be left untouched in the old project as UPDATE will not scan outside the current project. The new reconfigured database in the current (new) project would be the same as if the old project catalogue had been DATALed across to the new one. FROM SYSTEM applies to the reconfiguration of the system database. Tthis action will normally be necessary when a project is being converted to a new version of PDMS. In this case a TO destination is not stated as the database is reconfigured into itself. The TO Command This has a similar form to the FROM command, except that we have the option of sending the reconfigured information to an existing database or a new one. TO DB dbname dbname refers to an existing database. will create a new DB of the correct type provided that an existing TEAM name has been used TO NEW
.NOTE: If any other command than TO NEW dbname or TO DB dbname is used, then the RCFUPDATE command will have no effect.
10-3
Reconfigure
The RCFCOPY Command This specified exactly what we wish to copy. Normally COPY ALL is used, as the whole database is being transferred. The option to copy parts of DBs into other parts of existing DBs can become a hazardous operation if the whole process is not thought out carefully by the System Administrator.
.-----------------------------------------. / | >-----RCFCopy---+------------CATa------------------------. | | | | |------------SPEC------------------------| | | | | |------------ALL-------------------------| | | | | |------------name--+---------------------| | | | | | | | +--name--+ | | | --INTO--| |--| | | --refno-- | | ------------------+---------------------|--| | +--name--+ | | --INTO--| | | | --refno----+--+-->
The COPY command does not actually perform the copying function, it merely defines the information to be transferred.
10-4
Reconfigure
The RECONFIGURE Command This is the final simple command that sets everything in motion. During the time that the RECONFIGURE is running, information on PASS1 and PASS2 will be output on the screen. This serves as some indication of the rate of progress, in that the completion of PASS1 can broadly be taken as the halfway mark. At the end of the RECONFIGURE, a summary of errors similar in appearance to that seen in CLASHER is given. It is essential that if any errors have occurred that the RECONFIGURER process is considered as having failed. The RECONFIGURER is a very general application and as such will try to complete any task given to it. If errors have occurred it is almost certain that the TO DB contains only some of the information which was supposed to be transferred. The safest course is to delete this DB before any attempt is made to repeat the RECONFIGURE. If all the rules are obeyed then the message that the System Administrator will expect to see every time will be: ***PASS 2 COMPLETED RECONFIGURATION COMPLETE 0 ELEMENTS WERE NOT DEFINED IN DDL 0 ELEMENTS HAVE BEEN LOST 0 ELEMENTS ARE NO LONGER NAMED 0 ATTRIBUTES WERE WRONGLY DEFINED The RCFUPDATE Command The UPDATE process scans the DBs specified for any pointers which refer to the old DB and changes them to references to the new reconfigured one. For this task, it of course requires the dumptable. If the user had left the module since the RECONFIGURE was performed, he should have saved the dumptable; DUMP /filename Having returned to RECONFIGURER, he must now reactivate this table: LOAD /filename If the UPDATE follows on immediately after the RECONFIGURE then this is not necessary.
>-RCFUPdate----+----DB----dbname----. | | |----MDB---mdbname---| | | ----TEam--teamid-------->
The UPDATE command may be given as many times as necessary to define all the MDBs Teams or individual DBs that are used to point to the old DB.
10-5
Reconfigure
There is not an UPDATE PROJECT command as this would demand that the system scans every single DB in the project. This would be wasteful, as it is unlikely that all the databases in a project have pointers to one particular DB, except perhaps the catalogue.
10-6
Reconfigure
The equipment /VESS-1 will exist twice with the same name, but only the one in database PIPEN/DESIGN is correct. The Equipment should be deleted from PIPES/DESIGN.
10-7
Reconfigure
Backtrack the Database to session number 2 Reconfigure SAMEREF from files to the Data base you have just Backtracked.
10-8
Reconfigure
10-9
Reconfigure
Make a note of the DB number using Modify Database. Delete the db and create one using the same name, DB and File Number. Reconfigure SAMEREF from files to the new Data base you have just created.
You will now need to add this new database to every MDB as required.
10-10
Reconfigure
10-11
Session
Backing up Data
11
It is essential that good backups are produced of your data. Companies will have invested a lot of money and man hours into producing the PDMS data so it is very important that data is not lost due to hardware failure, fire or user error.
Objectives
At the end of this session, you will able to:
11-1
Backing up Data
Daily Backups
It is essential that good backups are produced of your data. Companies will have invested a lot of money and man hours into producing the PDMS data so it is very important that data is not lost due to hardware failure, fire or user error. Backups are normally produced each night when there is no one using the system and are normally automated. Now that magnetic tapes can store vast amounts of data and operate very quickly it is normal practice to backup all files on the Server each night. The local PC files are not normally backed up. If your tape deck does not have the capacity to save all the data then you can just save the project data. For example PDMS Project PDMS Options PDMS Macro (TAD000) (TADISO) (TADMAC)
The PDMS picture files (TADPIC) need not be saved as they can be regenerated by using the Draft Update commands. You must make sure that anything that has been modified has been backed up. I you have done any customisation then these files should be backed up.
11-2
Backing up Data
A typical tape backup sequence for the server could be as follows you will require Three Monthly Tapes (MONTH 1 , 2 and 3), Three Weekly Tapes (Week 1, 2 and 3) and Four Daily Tapes (MON, TUES, THU and FRI). Week No 1 2 3 4 5 6 7 8 9 Monday MON MON MON MON MON MON MON MON MON Tuesday TUE TUE TUE TUE TUE TUE TUE TUE TUE Wednesday WEEK 1 WEEK 2 WEEK 3 MONTH 1 WEEK 1 WEEK 2 WEEK 3 MONTH 2 WEEK 1 Thursday THU THU THU THU THU THU THU THU THU Friday FRI FRI FRI FRI FRI FRI FRI FRI FRI
Using the backup system shown in the worst case you could loose a days work, but by taking out a Weekly / Monthly tape you would be able to get items back up to 4 months ago that may have been deleted in error. Backing up Data
Project Backups
Once a Project is completed it would be normal practice to save the Project including all Reports etc. and a copy of the PDMS version. It is always best to create two copies of the data so if the cd or tape gets lost or damaged there is still another copy.
11-3