ig51314.pdf

8/13/2019 ig51314.pdf

1/54

Installation GuideVersion 11.6Windows 2000 and Windows XP

pdms1160/PDMS Installation Guideissue 300904

8/13/2019 ig51314.pdf

2/54

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 TOTHIS DOCUMENT, INCLUDING BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULARPURPOSE.

While every effort has been made to verify the accuracy of this document, AVEVASolutions shall not be liable for errors contained herein or direct, indirect, special,incidental or consequential damages in connection with the furnishing, performance oruse of this material.

This manual provides documentation relating to products to which you may not haveaccess or which may not be licensed to you. For further information on which Productsare licensed to you please refer to your licence conditions.

Copyright 1991 through 2004 AVEVA Solutions LimitedAll rights reserved. No part of this document may be reproduced, stored in a retrievalsystem or transmitted, in any form or by any means, electronic, mechanical,photocopying, recording or otherwise, without prior written permission of AVEVASolutions.

The software programs described in this document are confidential information andproprietary products of AVEVA Solutions or its licensors.

For details of AVEVA's worldwide sales and support offices, see our website athttp://www.aveva.com

AVEVA Solutions Ltd, High Cross, Madingley Road, Cambridge CB3 0HB, UK
http://www.aveva.com/engineeringit/world/http://www.aveva.com/engineeringit/world/

8/13/2019 ig51314.pdf

3/54

CHANGE HISTORY

Issue Details

PDMS 11.6150904

Updated:Hardware recommendation; Upgrading; Licensing;AutoDRAFT chapter (versions supported)

New:Information on .NET and its effect on PDMSinstallation; Background Process Manager

Minor corrections and updates

300904 Added Section 4.7 Running PDMS in batch

pdms1160/PDMS Installation Guideissue 150904

8/13/2019 ig51314.pdf

4/54

8/13/2019 ig51314.pdf

5/54

Contents

1 Introduct ion.................................................................................................... 1-11.1 Contents of this Guide ........................................................................ 1-11.2 Associated products ............................................................................1-2

2 Hardware and Software Requirements ........................................................2-12.1 Hardware............................................................................................. 2-1

2.1.1 Graphics Cards ...................................................................... 2-12.2 Software and Configuration ...............................................................2-2

3 Installing PDMS ............................................................................................. 3-13.1 Basic Installation................................................................................ 3-1

3.1.1 .NET Framework Installation .............................................. 3-23.2 Uninstalling and Reinstalling ............................................................ 3-23.3 FLEXMAN License Manager ............................................................. 3-23.4 Remote Installation............................................................................. 3-3

4 Setting Up the Windows Environment......................................................... 4-14.1 Windows Control Panel ......................................................................4-14.2 Graphics Card Settings.......................................................................4-24.3 Setting the License File Location.......................................................4-24.4 PDMS Environment Variables ........................................................... 4-34.5 Running PDMS from a Command Prompt Window..........................4-54.6 Customising PDMS Start-Up............................................................. 4-54.7 Running PDMS in batch..................................................................... 4-64.8 Plotting ................................................................................................ 4-7

5 Language Support .........................................................................................5-15.1 Preparing Windows to use Supported Languages............................. 5-2

5.1.1 Windows 2000........................................................................ 5-25.1.2 Windows XP...........................................................................5-2

5.2 Preparing PDMS to use Latin Languages ......................................... 5-35.3 Preparing PDMS to use Far Eastern Languages ..............................5-3

6 Running PDMS under Windows ...................................................................6-16.1 Spaces in Windows pathnames .......................................................... 6-1

VANTAGE PDMS Installation Guide contents-iVersion 11.6

8/13/2019 ig51314.pdf

6/54

Contents

6.2 Linking to Microsoft Excel ................................................................. 6-16.3 Windows Parameters.......................................................................... 6-2

7 PDMS Projects............................................................................................... 7-17.1 The Sample Project............................................................................. 7-1

7.1.1 Copying Project SAM to Your User Area............................. 7-17.1.2 Users and Teams in the Sample Project.............................. 7-27.1.3 MDBs in the Sample Project ................................................ 7-3

7.2 Creating PDMS Projects .................................................................... 7-37.2.1 The Sample Project and your own Projects.......................... 7-4

8 Installing AutoDRAFT................................................................................... 8-18.1 Compatibility ...................................................................................... 8-18.2 The AutoDRAFT Software ................................................................. 8-18.3 Configuring AutoDRAFT with AutoCAD .......................................... 8-28.4 Installing and configuring AutoCAD................................................. 8-2

8.4.1 AutoCAD R2002.................................................................... 8-38.4.2 AutoCAD R2004.................................................................... 8-3

8.5 Getting Started with AutoCAD.......................................................... 8-38.6 Application Macros for use with PDMS DRAFT............................... 8-4

9 Upgrading Projects to Version 11.6............................................................. 9-110 Troubleshooting...........................................................................................10-1

10.1 General...............................................................................................10-110.2 License Manager Errors....................................................................10-110.3 Entering PDMS .................................................................................10-210.4 Problems with Graphics ....................................................................10-3

11 Structure of PDMS on .NET.........................................................................11-111.1 Overview ............................................................................................11-111.2 PDMSEXE..........................................................................................11-1 11.3 GUI module structure .......................................................................11-1

11.3.1 Wrappers ..............................................................................11-211.3.2 .NET Loading rules..............................................................11-211.3.3 Win32 DLLs .........................................................................11-3

11.4 Components .......................................................................................11-311.4.1 PDMSEXE directory ............................................................11-311.4.2 PDMSEXE/Design subdirectory..........................................11-511.4.3 PDMSEXE/Draft subdirectory ............................................11-5

contents-ii VANTAGE PDMS Installation GuideVersion 11.6

8/13/2019 ig51314.pdf

7/54

Contents

11.4.4 PDMSEXE/Monitor subdirectory........................................ 11-511.4.5 PDMSEXE/Isodraft subdirectory........................................ 11-511.4.6

PDMSEXE/Admin subdirectory..........................................11-5

11.4.7 Add-ins ................................................................................. 11-5

11.5 Forms and Menus .............................................................................11-512 Troubleshoot ing the .NET installation ....................................................... 12-1

12.1 Version Error..................................................................................... 12-112.2 Wrappers or a dependency missing.................................................. 12-112.3 Interface incompatibility ..................................................................12-212.4 Security error with thin client..........................................................12-212.5

No Add-ins.........................................................................................12-4

12.6 Window Layout ................................................................................. 12-412.7 Serialization ...................................................................................... 12-4

VANTAGE PDMS Installation Guide contents-iiiVersion 11.6

8/13/2019 ig51314.pdf

8/54

8/13/2019 ig51314.pdf

9/54

1 Introduction

This guide explains how to install and set up PDMS Version 11.6 on aworkstation running the Microsoft Windows 2000 or Windows XPoperating system (hereafter referred to jointly as 'Windows'). LocalAdministratorrights are required to perform the installation.This guide assumes you are familiar with the concepts of folder/filehierarchies for storing data on disks and with basic Windows

terminology and commands. If you are not, you may also need to refer toyour operating system documentation while you carry out theinstallation.

The guide also assumes that you have already gained access to thePDMS installation files via a CD, from the AVEVA Web site, or by someother route.

1.1 Contents of this Guide

Hardware and software requirements are described in Chapter 2.Forcompletely up-to-date information, please see the AVEVA Website athttp://www.aveva.com/engineeringitand refer to the Customer SupportHardware pages. The Web pages also give hints on ways of setting upand running PDMS on different computers in order to achieve the mostefficient performance.

Chapter 3,Installing PDMS,describes how to install PDMS 11.6 andlicense the software.

Chapter 4,Setting Up the Windows Environment,explains how toconfigure the Windows operating system before you run PDMS.

Chapter 5,Language Support,describes how to set up the WindowsEnvironment to use PDMS with different Language options.

Chapter 6,Running PDMS under Windows,gives some advice on usingPDMS in a Windows environment.

Chapter 7,PDMS Projects,describes the sample project that is suppliedas part of PDMS, and how to set up your own projects.

Chapter 8,Installing AutoDRAFT,describes how to install and configurePDMS AutoDRAFT.

VANTAGE PDMS Installation Guide 1-1Version 11.6
http://www.aveva.com/engineeringithttp://www.aveva.com/engineeringithttp://www.aveva.com/engineeringit

8/13/2019 ig51314.pdf

10/54

Introduction

Chapter 9,Upgrading Projects to Version 11.6, describes how to upgradeyour projects from PDMS 11.5, PDMS 11.5SP1, or earlier releases, for

use with PDMS 11.6.Chapter 10,Troubleshooting,describes solutions for some of the errorsthat you could encounter when running PDMS.

Chapter 11, Structure of PDMS on .NET, outlines the way in whichPDMS in installed and configured in a Microsoft .NET environment.

Chapter 12,Troubleshooting the .NET installation, describes solutions tosome of the .NET related issues you might encounter.

1.2 Associated products

There are various other VANTAGE products that may be used inconjunction with PDMS. You may wish to consider installing these atthe same time. Those closely associated with PDMS include thefollowing VANTAGE Plant Design products:

Router for automatic rule-based pipe routing withinPDMS

Global for synchronisation of PDMS projects betweenworld-wide sites

Model Management for change & status control of engineeringobjects (e.g. pipes, welds, ) from systemdesign through detailing and into deliverableproduction

And newat PDMS 11.6: Final Designer AutoCAD editing of PDMS DRAFT drawings,

including final detailing

For details of the installation of these add-on products, please refer to

the relevant installation guide. If they are required, it may be advisableto read these before installing PDMS.

1-2 VANTAGE PDMS Installation GuideVersion 11.6

8/13/2019 ig51314.pdf

11/54

2 Hardware and Software Requirements

This section describes the hardware and software configurations thatPDMS requires to run under Windows.

2.1 Hardware

The following list gives a minimum specification for your computer.

Processor Intel IA-32 architecture, e.g. Pentium- at least 1 GHz.

Memory 256 MB minimum,512 MB or more highly recommended.

Graphics Card High performance card recommended- see below.

Display A resolution of at least 1024x768 (XGA) isstrongly recommended

Storage Approximately 670 MB- see AVEVA web-site for details.

CD drive CD-ROM will be used for media distribution.

Mouse 3-Button mouse required;Mouse with wheel strongly recommended.

2.1.1 Graphics Cards

PDMS uses standard OpenGL for its 3D graphics.

Due to the continuously and rapidly changing list of hardwareaccelerated OpenGL graphics cards commercially available, an up-to-date list of supported graphics cards cannot be included in thisdocument. However, the AVEVA Web pages(http://www.aveva.com/engineeringit) contain a current list of both testedand supported graphics cards in the Support section.

Other graphics cards which fully support the OpenGL standard shouldalso work, but AVEVA cannot offer assistance in configuring these. Youmay also find some problems, for example, when picking items in PDMS.


8/13/2019 ig51314.pdf

12/54

Hardware and Software Requirements

2.2 Software and Configuration

The following software should be installed and configured on yourcomputer to enable PDMS 11.6 to run.

PDMS 11.6 is fully supported under:

Windows 2000 Professional with Service Pack 4

Windows XP Professional with Service Pack 11

Notethat Windows 2000 and Windows XP Service Packs and HotFixes from Microsoft are required for PDMS to run effectively.Please refer to the AVEVA Support web site, or contact the AVEVASupport team for details of the latest recommended Windows 2000and Windows XP environment for PDMS.

PDMS 11.6 databases mustbe on an NTFS File System: FATCpartitions are notsupported.

The license manager must have a drive called C: available forwriting temporary information. In the case of double boot machines,where D: is the system disk for Windows XP/2000 and C: is used foran earlier version of Windows, the license manager will still work,since it does not require NTFS.

PDMS 11.6 requires Microsofts .NET Framework: it will beinstalled from the CD if necessary.

Optionally, you can have Microsoft Excel installed for outputtingreports.

1PDMS 11.6 will run on Windows XP SP2, but requires changes to the default settings. The Internet

Connection Firewall (ICF) should be turned off or configured to ensure access to the database server.In addition, Group Policy changes (which alter the registry) are required for VANTAGE Plant DesignGlobal to ensure that RPC requests do not require authentication. Details are given in the Global

Installation Guide.


8/13/2019 ig51314.pdf

13/54

3 Installing PDMS

3.1 Basic Installation

Local Administrator rights are normally required to install PDMS.

1. To install PDMS from CD Insert the CD into your CD-ROM drive.If you have AutoPlay enabled for the drive, the installation startsautomatically. Otherwise, run Start.htmon the CD.If you are installing PDMS from the network Click Start>Runonthe Windows taskbar and type the path to the Start.htmfile on yournetwork.

2. Click on CD CONTENTSand select the product which you want toinstall (in this case PDMS Version 11.6), then click INSTALL. ClickOKon any confirmation forms which appear.

3. On the File Downloadform, selectRun this program from its currentlocation(IE 5.0) or Open(IE 5.5 or later) to install the program filesdirectly from their current location onto your hard disk. Select Yeson the Security Warning query about an Authenticode signature.

4. This starts the InstallShieldWizard, which will lead you throughthe rest of the installation process.

During the installation sequence, follow the on-screen instructions asthey appear. You will be given a choice between two levels of installation:

Full installation: Installs all available product components(recommended for a new installation unless there are good reasonsfor restricting the options available to end users).

Custom installation: Presents you with a list of all available productcomponents from which you can select those to be installed.

It is recommended that you use the default settings for folder paths etc.unless you have good reasons for doing otherwise. You must not useembedded spaces in folder path names.The process needs at least 670MB of free disk space for a full installationof all options. InstallShield checks that there is enough space availablebefore it starts, and warns you if there is not.


8/13/2019 ig51314.pdf

14/54

Installing PDMS

When the process is complete, select Start>Programs/AVEVA/VANTAGEPDMS 11.6to reach the Run PDMS, Make PDMS project, Run Background

Process Managerand PDMS manualsoptions.

3.1.1 .NET Framework Installation

The new graphical user interface included in PDMS 11.6 requires thatMicrosofts .NET Framework 1.1 be installed. The .NET Framework issupplied on the installation CD, and is installed automatically if it is notalready installed.

3.2 Uninstalling and Reinstalling

If InstallShield detects an existing PDMS installation, it will display theoptions for modifying/repairing/removing the files rather than simplyoffering the standard installation options.

To remove installed components from your hard disk, or to add additionalcomponents to an existing installation, select Start>Settings>Control Paneland use theAdd/Remove Programstool.

As an alternative procedure, repeat Steps 1 to 4 of the installation

sequence detailed above. The InstallShield Wizard will detect yourexisting installation and will give you the following options:

Modify: Displays the same list of options as the Custominstallation.Select new components to be added and/or deselect any currentlyinstalled components to be removed.

Repair: Reinstalls all currently installed components (to correct anycorrupted files etc.).

Remove: Removes all currently installed components.

NOTE:

Uninstalling PDMS will not uninstall Microsofts .NET Framework:this must be removed separately if required.

3.3 FLEXMAN License Manager

You must install and set up the FLEXMAN license system before PDMScan be used. This will usually be done only on the server. Please see theFLEXMAN Installation Guide. News and update information is alsoavailable for FLEXMAN on the AVEVA support web-site.


8/13/2019 ig51314.pdf

15/54

Installing PDMS

3.4 Remote Installation

If you wish to have one server installation of PDMS accessed from remoteworkstations, you must ensure that the Windows system DLLs on eachremote workstation are upgraded to a suitable version for running thePDMS 11.6 application programs. You can achieve this by installingPDMS 11.6 itself in minimal form; that is, select the Custom Installationtype and then deselect everything except 'PDMS Core Components'.

In addition, this release includes a stand-alone 'Thin Client' installerwhich can be used on individual workstations to update the necessaryWindows system DLLs, and which also provides start menu shortcuts tothe main PDMS installation.

The Thin Client installer is a self-extracting InstallShield executablewhich is held in the C:\AVEVA\PDMS11.6\thin_client_installer\subfolder. It is applicable when the main PDMS 11.6 product is installedeither from the 'Full Installation' option or the 'Custom Installation'option with the 'Thin Client Installer' component selected.


8/13/2019 ig51314.pdf

16/54

Installing PDMS


8/13/2019 ig51314.pdf

17/54

4 Setting Up the Windows Environment

This chapter describes how to configure the Windows operating systembefore you run PDMS. Following installation of PDMS, you shouldperform the following steps:

Check the settings for your graphics board: See Section 4.2.

Ensure the FLEXMAN License Manager daemon is running, andset environment variables relating to FLEXMAN: See Section 4.3.

Configure Windows parameters for PDMS: see Section 4.4.

You can then run PDMS by clicking on the PDMS shortcut or icon,which will set up the remaining environment variables required.

Note: In the following instructions it is assumed that PDMS 11.6 hasbeen installed in folder C:\AVEVA.If it has been installedelsewhere, substitute C:\AVEVAwith the name of the installationfolder.

4.1 Windows Control Panel

The Windows Control Panel contains tools that are used to change theway Windows looks and behaves. This Install Guide describes how to useControl Panel tools to configure Windows to run PDMS.

Open the Control Panel as follows:

Windows 2000ClickStart, point to Settings, and then click Control Panel

Windows XPIf your computer is set up with the Classic Start menu, click Start,point to Settings, and then click Control Panel.

If your computer is set up with the standard Start menu, click Startand then click Control Panel.


8/13/2019 ig51314.pdf

18/54

Setting Up the Windows Environment

4.2 Graphics Card Settings

You should set your display to a resolution of at least 1024 x 768 and thecolour depth to True colour or 16.7 million colours.

This can be set by opening the Control Panel.SelectDisplayand select theSettingstab. Make the appropriate selections on the form for yourgraphics card.

Due to the rapidly changing list of hardware accelerated OpenGLgraphics cards commercially available, an up-to-date list of supportedgraphics cards, graphics device drivers and recommended device driverconfiguration cannotbe included in this document. However, the AVEVA

Support Web pages (http://www.aveva.com/engineeringit) contain acurrent list of both tested and supported graphics cards, along withadvice on configuration of graphics device drivers.

4.3 Setting the License File Location

Before you can use PDMS, you must set up the FLEXMAN licensesystem and connect to the FLEXMAN License Manager daemon (see theFLEXMAN Installation Guide).

Each User needs to set a license path that defines the location of thelicense file or service. For earlier versions of FLEXMAN, setting theenvironment variable LM_LICENSE_FILE did this. However, thisapplied to all software using FLEXlm. You can now setCADCENTRE_LICENSE_FILE instead that applies only to softwareusing our Vendor License Manager Daemon.

To avoid users having to repeatedly set such an environment variable,FLEXlm itself now remembers the current setting in the WindowsRegistry. This Registry setting will initially come from the value of thecorresponding environment variable, but cannot then be modified by

changing the environment variable you must use the FLEXlm utilitylmtoolsor the new command-line lmpathto query or set the license path.These utilities are installed with FLEXMAN.

The environment variable can be set in one of three ways, either in thePDMS entry script, as a User Environment Variable in the Control Panelor manually in a command window.

To set manually or in the PDMS entry script, type the following in acommand window or in the entry script before starting PDMS:

set CADCENTRE_LI CENSE_FI LE=Por t @Comput er name


8/13/2019 ig51314.pdf

19/54


To set automatically:Windows 2000 and Windows XP Open the Control Panel.

Select System, and pick theAdvanced tab

Click on the Environment Variablesbutton

Set the CADCENTRE_LICENSE_FILE user environment variableto the location of the license obtained from AVEVA(Port@Computername). For example:

CADCENTRE_LI CENSE_FI LE744@licserv

To confirm the licence environment variable setting, open a commandwindow and type the command SET. You should see a list of environmentvariables, including:

CADCENTRE_LI CENSE_FI LE=Por t @Comput er name

To check the Registry setting, you will need to use the FLEXMAN utility

l mpath st atus

You should see an output including the following:

l mpat h - Copyri ght ( C) 1989- 2002 Gl obet r ott er Sof t war e, I nc.

Known Vendor s:

cadcent r e: 744@l i cserv

4.4 PDMS Environment Variables

PDMS uses Windows Environment variables to locate folders containingPDMS system files and users project data. This allows you to locate thesefolders anywhere on the file system. The default location for PDMSsystem files is C:\AVEVA\PDMS11.6, but the location of the pdms11.6folder can be changed if desired when PDMS is installed.

PDMS is supplied with a file evars.batin the PDMS executables folder(C:\AVEVA\pdms11.6) which sets default values for the environmentvariables so that they point to the folder structure as installed. It alsosets the PATHvariable to include the PDMSEXE folder containing PDMSexecutables.

You may need to modify this file to reflect the folder structure of yourown installation. The following is a list of the variables you may need to

reset, with a brief description of each one and the default setting.


8/13/2019 ig51314.pdf

20/54


Note that all environment variables must be UPPERCASE.

It is recommended that users should not write to the pdms11.6

installation folder or any of its contents:

PDMS System Environment Variables

The following environment variables refer to the location of PDMSsystem files.

PDMSEXE Executable folderC: \ AVEVA\ pdms11. 6

PDMSEXEMAI N Copy of PDMSEXE, but can be a search pathC: \ AVEVA\ pdms11. 6

CADCENTRE_LI CENSE_FI LE License fileNote that this variable relates to AVEVAs former namefor historical reasons!See section 4.3,Setting the License File Location

PDMSUI Application User Interface folder (PML 1)C: \ AVEVA\pdms11. 6\ pdmsui

PMLLI B Application User Interface folder (PML 2)C: \ AVEVA\pdms11. 6\ pml l i b

PDMSDFLTS Applications defaults folderC: \ AVEVA\pdms11. 6\ pdmsui \ df l t s

PDMSPLOTS Applications PLOTS folderC: \ AVEVA\ pdms11. 6\ pdmsui \ pl ot s

PLOTCADC Pointer to the PLOT executable.C: \ AVEVA\pdms11. 6\ pl ot \ pl ot . exe

PDMSHELPDI R Online help data files.C: \ AVEVA\ pdms11. 6\ onl i nehel p

PDMS User Environment Variables

The following environment variables refer to the location of users PDMS

folders. Users must have write permission to these folders.PDMSWK Temporary PDMS work file folder

C: \ t emp

PDMSUSER Application Users save/restore setup area (or the users'home' folder)C: \ AVEVA\pdms11. 6\ pdmsuser

PDMSREPDI R PDMS Applicationware Report Input and Output folder.C: \ AVEVA\pdms11. 6\ pdmsui \ r epor t s

PDMSDFLTS Applications defaults folder. Note that individual usersmay not have permission to change PDMS System

defaults in C: \ AVEVA\pdms11. 6\ pdmsui \ df l t s , but


8/13/2019 ig51314.pdf

21/54


they should have their own local defaults area. This isachieved by setting a PDMSDFLTS search path, e.g. C: \ USERDFLTS C: \ AVEVA\pdms11. 6\ pdmsui \ df l t s

Project Environment Variables

For each PDMS project, four more environment variables must be set.For example, for a project ABC:

ABC000 Project database folder

ABCI SO Project ISODRAFT options folder

ABCMAC Project Inter-DB connection macro folder

ABCPI C Project DRAFT picture file folder

PDMS is installed with sample project data (See Chapter 7 PDMSProjects). PDMS Project Environment variables for these projects are setin evars.bat.

4.5 Running PDMS from a Command Prompt Window

You can run PDMS from a Command Prompt window rather than usingthe Start/Programs menu. To do this you must set your PATHvariable toinclude the folder where PDMS is installed.

Windows 2000 and Windows XP Open the Control Panel.

Select System, and pick theAdvanced tab.

Click on the Environment Variablesbutton.

Edit the system variable Pathto add the PDMS folder (for example,C:\AVEVA\pdms11.6) to the list of folders in the Path variable.

Once the Path variable includes the pdms11.6 folder, you can run PDMSby typing pdms at a command prompt.

4.6 Customising PDMS Start-Up

There is a batch (.bat) file supplied in C: \ AVEVA\pdms11. 6calledpdms.batwhich allows entry into PDMS.

You can run PDMS using this batch file in any of the following ways:

Use the shortcut in the Windows Start menu,Start>Programs>AVEVA>VANTAGE PDMS 11.6>Run PDMS


8/13/2019 ig51314.pdf

22/54


You can create a shortcut on your desktop to run your batch file.With the cursor in the desktop area, click with the right-hand

button and select New>Shortcut. This shows a sequence of dialogs tohelp you create the shortcut. Type in the location of pdms.bat, forexample:C: \ AVEVA\pdms11. 6\ pdms. bat

then press Nextand give the shortcut a name.Press Finish.

You should now be able to double-click on the shortcut icon to enterPDMS.

If you have C: \ AVEVA\pdms11. 6( the path name for the pdms.batfile) in your PATH environment variable, just type pdmsin a

command window to execute the batch file. Otherwise, navigate to the folder where the batch file is stored and

typepdmsor pdms.bat.

You can set up your own batch files to run PDMS. For example, you maywish to run design checking utilities every night, or update batches ofdrawings overnight.

Begin by creating a batch file, for example, runpdmsmacro.bat .

Type the following line into this file:

C: \ AVEVA\ pdms11. 6\ pdms. bat TTY SAM SYSTEM/ XXXXXX / STRUC $M/ mymacr of i l e

Where:

TTYtells PDMS not to start the PDMS GUI. This gives command lineonly operation.

SAM is the project name. SYSTEM/XXXXXX is the PDMS username/passwordto be used when

running the command macro

/STRUC selects the required MDB

mymacrofileis the pathname of a PDMS command macro, containingthe commands that you want to execute in PDMS.

In this example, running runpdmsmacro.bat will enter PDMS in projectSAM, as user SYSTEM/XXXXXX, in MDB /STRUC, and run the PDMScommand macro mymacrofile.

4.7 Running PDMS in batch

PDMS creates a separate PDMSConsole process to manage the

command-line input/output for all modules. When PDMS is invoked


8/13/2019 ig51314.pdf

23/54


from a .bat file, processing of this file resumes as soon as you leaveMonitor even though you are still using PDMS.

To help manage this situation, PDMSWait.exe is distributed as part ofPDMS and can be used to make a PDMS script wait for PDMS tocomplete before continuing.

PDMSWait uses Windows facilities to wait for an event triggered byPDMSConsole when PDMS finishes. Because you can be running morethan one PDMS session on any one computer, both PDMSWait andPDMSConsole look for an environment variablePDMS_CONSOLE_ I DENTI FI ERbefore doing this. You can setPDMS_CONSOLE_ I DENTI FI ERto any unique string. In a .bat file you canuse the %RANDOM%or %TI ME%values provided by Windows; in a Perl script,

you can use the process number, accessible as $$.

Example:

echo St ar t PDMS at %TI ME%

set PDMS_CONSOLE_I DENTI FI ER=%RANDOM%

cal l %PDMSEXE%\ pdms

cal l %PDMSEXE%\ pdmswai t

echo Returned t o . bat at %TI ME%

This will start PDMS, then wait until it has finished before resuming thescript.

The VANTAGE PDMS MONITOR Reference Manualprovides moredetails on running PDMS batch programs.

4.8 Plotting

To plot in a Windows environment, we recommend that you use theplotcadc.batfile supplied in the pdms11.6 folder. Note that you may haveto modify the plotcadc.batfile to suit your local printer installation.

The Network Plotter must be mapped using the NET USEcommand. Seeyour network documentation for more information.

To run the plotcadc.batfile, give a command in the format:

C: \ AVEVA\pdms11. 6\ pl otcadc. bat plotfile format printer options

Where options are the AVEVA PLOT utility options, and may be omitted.See the PLOT User Guide for more information. Note that the optionsmust be enclosed in quotes.

For example:

pl ot cadc. bat c: \ pdms\ pl ot 1 ps \ \ nt ser ver \ NTPost Scri pt

pl ot cadc. bat c: \ pdms\ pl ot 1 hpgl \ \ nt ser ver \ NThpgl ' CE=Y'


8/13/2019 ig51314.pdf

24/54

8/13/2019 ig51314.pdf

25/54

5 Language Support

By default, your PDMS project can use any language whose charactersare contained within the Latin 1 character set. The Languages coveredby the Latin-1 character set a listed in the table below. If you want to useany of the other, non-Latin-1 languages supported by PDMS, it isnecessary to configure your PDMS project and the Windows operatingsystem. This chapter describes how to use PDMS on Windows 2000 andWindows XP Professional in each of the supported language groups:

Latin-1

Latin-2

Latin-Cyrillic

Far Eastern

Supported languages

Name Description Languages covered

Latin 1 ISO 8859-1 Latin alphabet 1 Danish, Dutch, English, Faroese,

Finnish, French, German,

Icelandic, Irish, Italian,

Norwegian, Portuguese,

Spanish, Swedish,

Latin 2 ISO 8859-2 Latin alphabet 2 Albanian, Czech, English,

German, Hungarian, Polish,

Rumanian, Serbo-Croat, Slovak,

Slovene

Latin Cyrillic ISO 8859-5 Latin/Cyrillicalphabet

Bulgarian, Byelorussian,English, Macedonian, Serbo-

Croatian, Ukrainian, Russian

Far Eastern Japanese, Korean, Simplified

Chinese, Traditional Chinese

PDMS does not support any other language character set, nor does itsupport the mixing of any of the above, except for mixing one FarEastern language with English.


8/13/2019 ig51314.pdf

26/54

Language Support

5.1 Preparing Windows to use Supported Languages

5.1.1 Windows 2000

To add an additional language in Windows 2000, follow these steps:

1. Open the Control Panel.

2. Double-click Regional Optionsto show the Regional Options dialog.

3. Click the Input Localestab.

4. In the Input Localesbox, click the required language, and then

click Properties.5. In the Keyboard Layoutbox, click the required keyboard layout,

click OK, and then click OK.

6. Click the Generaltab. Click to select the check box next to thelanguage group you wish to install, and then clickApply. Thesystem will either prompt for a Windows 2000 CD-ROM or accessthe system files across the network. Once the language isinstalled, Windows 2000 will prompt you to restart the computer.

5.1.2 Windows XP

To add an additional language in Windows XP, follow these steps:

1. Open the Control Panel.

2. Double-click Regional and Language Options.

3. On the Regional optionstab, under Standards and formats,select the required language from the list.

4. Click the Languagestab, and then click Detailsunder "Textservices and input languages".

5. Under Default input language, select the required language. Ifthe required language appears in the list, click OK.If it does not appear in the list, then click Addunder "InstalledServices", and then click the language you want to add and thekeyboard layout you want to use for that language.To configure the settings for the Language bar, click Language Barunder "Preferences". The Language bar is used to switch betweenlanguages while you are using PDMS. Click OK to close theLanguage Bar Settings dialog.Click OK to close the Text Services and Input Languages dialog.


8/13/2019 ig51314.pdf

27/54

Language Support

6. Click theAdvanced tab. Under Languages for non-Unicodeprograms, select the required language. ClickApply. It may be

necessary to install new code page conversion tables. Only memberof the Administrators group can install code page conversiontables. The system will either prompt for a Windows XP CD-ROMor access the system files across the network. Once the language isinstalled, Windows XP will prompt you to restart the computer.

Note: For Far Eastern language support, it is necessary have the EastAsian support option installed.

5.2 Preparing PDMS to use Latin Languages

In PDMS ADMIN, you must specify a character set for each project byusing one of the following commands on the PDMS ADMIN commandline:

Command Languages covered

PROJECT CHARSET LATIN 1

(default)

Danish, Dutch, English, Faroese,

Finnish, French, German, Icelandic,

Irish, Italian, Norwegian, Portuguese,

Spanish, Swedish,

PROJECT CHARSET LATIN 2 Albanian, Czech, English, German,

Hungarian, Polish, Rumanian, Serbo-

Croat, Slovak, Slovene

PROJECT CHARSET LATIN CYRILLIC Bulgarian, Byelorussian, English,

Macedonian, Serbo-Croatian,

Ukrainian, Russian

The corresponding font family must be selected for Draft and Isodraftdrawings. Use Project>Font Familiesand select the Font Type appropriate

for you chosen language.For details, see the VANTAGEPDMS ADMIN User GuideandVANTAGEPDMS ADMIN Command Reference Manual.

5.3 Preparing PDMS to use Far Eastern Languages

You must ensure that your licence file is for the language version yourequire.


8/13/2019 ig51314.pdf

28/54

Language Support

Before you use PDMS, you must set the environment variableCADC_LANG as follows:

CADC_LANG=Japanese Kanji

CADC_LANG=Korean

CADC_LANG=Chinese Simplified Chinese

CADC_LANG= TChinese Traditional Chinese

In PDMS ADMIN, you must specify the multibyte character set for eachproject by using the command corresponding to your required language:

PROJECT MBCHARSET JAP

PROJECT MBCHARSET KOR FILE /

PROJECT MBCHARSET CHI Simplified Chinese

PROJECT MBCHARSET TCHIN FILE /Traditional Chinese

For details, see the VANTAGE PDMS ADMIN User Guide andVANTAGE PDMS ADMIN Command Reference Manual.


8/13/2019 ig51314.pdf

29/54

6 Running PDMS under Windows

6.1 Spaces in Windows pathnames

To run macros with spaces in the filenames, you must enclose thefilename in quotes, without a leading slash. For example:

$m' c: \ Pr ogr am Fi l es\ Macr os\ space. mac' ar g1 ar g2

Due to the way in which PDMS parses its command lines, this format isalso recommended for use with filenames containing Asian characters.

6.2 Linking to Microsoft Excel

You can make your reports load directly into a Microsoft Excelspreadsheet, as comma-separated files:

Select Utilities>Reports>Modifyfrom the PDMS main menu bar.

Pick a report template.

Click on OK: the Modify Template form is displayed.

Select Options>Other Formats...from the Modify Template form menubar. This displays the Report Formatform. From this form:

Choose the CSVoption from the Formatdrop-down list.

Click on OK: this returns you to the Modify Templateform.

Select the Overwriteradio button

For the filename enter %PDMSUSER%/ f name. csv (the . csvextension is important).

In the System command text box enter

'cmd/cC:\\excel.exe %PDMSUSER%\fname.csv'whereC: \ is the location of Excel on your system.Note that it is necessary to enclose Windows command argumentsin double quotation marks if the argument contains embeddedspaces. : \ \


8/13/2019 ig51314.pdf

30/54

Running PDMS under Windows

6.3 Windows Parameters

The following setting can be used to improve performance whenrepositioning forms in PDMS. These are optional Windows Parametersettings.

Windows 2000Open the Control Panel.SelectDisplayand select the Effectstab. On theform,uncheckShow Window Contents While Dragging.Windows XPOpen the Control Panel.SelectDisplay, then select theAppearancetab andclick on the Effectsbutton. On the form,uncheckShow Window ContentsWhile Draggingand Show shadows under menus.


8/13/2019 ig51314.pdf

31/54

7 PDMS Projects

7.1 The Sample Project

PDMS is supplied with a sample project, which can be used in severalways:

It provides you with examples of the use of PDMS.

It provides you with sample libraries, catalogues and specificationswhich enable you to use PDMS before you set up your own, and canbe used as starting points when you do start to create your own.

It provides you with starting points for the tutorials in the followingmanuals:

Pipework Design Using PDMS

Pipework Spooling Using PDMS

Structural Design Using PDMS

Industrial Building Design Using PDMS

Support Design Using PDMS

HVAC Design Using PDMS

Reporting from PDMS

Drawing Production Using PDMS

It provides an example of how to set up your own projects.

The sample project is actually two projects in PDMS terms:

MAS (Master) provides data in read-only databases. This data

should not be deleted or changed in any way, or the rest of thesample project will become unusable.

SAM (Sample) contains several MDBs which can be modified, andso they can be used for training,

7.1.1 Copying Project SAM to Your User Area

The sample project is loaded automatically when you install PDMS. Youshould copy the sample project to your user area and run it as supplied.


8/13/2019 ig51314.pdf

32/54

PDMS Projects

The project files are held in two directories: sam000 holds all designdata and catalogue data; sampicholds the DRAFT picture libraries.

7.1.2 Users and Teams in the Sample Project

Free User

The Free user has username/password SYSTEM/XXXXXX.

General Users

Team Username/password

CATS CATS/CATS

DEMO DEMO/DEMOEQUI EQUI/EQUIHANGER HANGER/HANGERHVAC HVAC/HVACPIPE PIPE/PIPESAMPLE SAMPLE/SAMPLESTRUC STRUC/STRUCUSERA USERA/AUSERB USERB/BUSERC USERCCUSERD USERD/DUSERE USERE/EUSERF USERF/FUSERG USERG/G

General User with Administ ration Rights

There is a user named ADMIN who is a member of all teams exceptMASTER. In particular, ADMIN is a member of the following teams:

CATADMINDRAFTADMINHSADMINISOADMIN

Membership of these teams gives special administration rights withinthe corresponding constructor module.

Each MDB contains databases with appropriate access rights. There arealso teams and users associated with each MDB with appropriate accessrights.


8/13/2019 ig51314.pdf

33/54

PDMS Projects

7.1.3 MDBs in the Sample Project

This section assumes that you are already familiar with PDMSdatabases.

The sample project contains the following MDBs which can be used fordemonstration or training purposes:

CATS An MDB for practising using Catalogues andSpecifications.

DEMO A demonstration MDB.

EQUI An MDB for the Equipment tutorials.

HANGER An MDB for the Support Designtutorial. This MDBcontains suitable pipework, steelwork and civils as astarting point.

HVAC An MDB for the HVAC Designtutorial. This MDBcontains suitable steelwork and civils as a startingpoint.

MASTER An MDB containing the master Catalogues andSpecifications, Lexicon Dictionaries etc.

MASTERCAT An MDB used for practising the use of Catalogues andSpecifications.

PIPE An MDB for thePipework Designand PipeworkSpooling tutorials.

SAMPLE An MDB for the Reporting from PDMSand DrawingProductiontutorials. This MDB contains design datafrom which reports and drawings can be produced. Youcan also produce isometrics.

STRUC An MDB for theStructural Design tutorial.

TRAINA to

TRAING Additional MDBs available for training purposes.

7.2 Creating PDMS Projects

For full information on setting up your own projects, see the VANTAGEPDMS ADMIN User Guide.

You will need to create project folders for each project; for example, for aproject xyz:


8/13/2019 ig51314.pdf

34/54

PDMS Projects

md xyz000md xyzpi cmd xyzi somd xyzmac

Set the corresponding environment variables that point to thesedirectories. You can do this by setting Environment Variables using theControl Panel, or by modifying the evars.batfile used to configure yourPDMS Windows installation. (see Chapter 4,Setting Up the WindowsEnvironment,for further details). Alternatively, type the following in anMS-DOS window:

set XYZ000=pathname\xyz000set XYZPI C=pathname\xyzpi c

set XYZI SO=pathname\xyzi soset XYZMAC=pathname\xyzmac

Note: Users converting from UNIX should note that there is no directequivalent of the . cshr cfile in which these variables can be set.

Use the 'Make PDMS project' icon supplied to start the PDMS Makeprogram, then enter:

XYZ$m/ %PDMSEXE%/ makemac. macFI NI SH

Note: Users converting from UNIX should note that the makemac. macfile is the same as on UNIX. The executable for each module isalso named identically to that on UNIX, e.g. DESIGN runs%PDMSEXE%/ des. The extension ' . exe' needed by Windows isadded automatically.

7.2.1 The Sample Project and your own Projects

You can add databases from the sample projects SAM and MAS to yourown projects from within PDMS ADMIN, using the Installoptions on the

main menu bar. Note that these options are only available if you havethe project environment variables for SAM and MAS set.

Note on DRAFT Libraries:You must have DRAFT libraries available in your current project beforeyou can enter the module. You may find it convenient to install thelibraries supplied by AVEVA in the MAS project (using the Installoptions), even if you wish to create your own libraries for the project.


8/13/2019 ig51314.pdf

35/54

8 Installing AutoDRAFT

This chapter explains the steps needed to install and configureAutoDRAFT.

AutoDRAFT may be run in stand-alone mode or it may be run fromPDMS DRAFT or ISODRAFT. You can use the adraftde, adraftbeandadraftsescripts as described in the VANTAGE PDMS AutoDRAFT UserGuide. The DRAFT and ISODRAFT applicationware generates interface

files for AutoCAD, which are then used by the scripts.AutoDRAFT generates interface files for DRAFT, which can be importedusing the DRAFT applicationware.

8.1 Compatibility

The version of AutoDRAFT released with PDMS 11.6 is compatible withAutoCAD Releases 2002 and 2004.

8.2 The AutoDRAFT Software

AutoDRAFT software consists of three AutoCAD applications that runwith AutoCAD Releases 2002 and 2004, and PDMS application macros tolink these AutoDRAFT applications with PDMS DRAFT and ISODRAFT.

The three AutoCAD applications are:

AutoDRAFT Drawing Editor

AutoDRAFT Frame Editor

AutoDRAFT Symbol Editor

The Drawing Editor is used to modify drawings transferred from DRAFTor ISODRAFT. Please note that the new Final Designer product providesmuch closer integration between DRAFT and AutoCAD.

The Frame Editor is used to transfer AutoCAD drawings into backingsheets or overlay sheets in DRAFT.

The Symbol Editor is used to convert AutoCAD graphics into symboltemplates within DRAFT symbol libraries.


8/13/2019 ig51314.pdf

36/54

Installing AutoDRAFT

8.3 Configuring AutoDRAFT with AutoCAD

The AutoDRAFT 11.6 software is installed under the PDMS executablesfolder:

autodraftACAD

pdms11.6

autodraftfonts autodraftACADsource

The autodraftACADfolder contains .bat files, AutoDRAFT scripts,AutoLISP programs, binary DRAFT menu files and an AutoCADlinestyle file.

The autodraftfontsfolder contains AutoCAD font files. All of theseare needed to run AutoDRAFT programs in AutoCAD.

In addition to the AutoDRAFT binary menu files, text versions arealso provided. These are supplied in the autodraftACADsourcefolderfor reference/customisation. This folder should not be visible by

AutoCAD.

Note: The AutoDRAFT software will operate properly only if AutoCADcan be run using the acadcommand. AutoDRAFT may not work ifthe AutoCAD executable acadhas been renamed, or if the acadcommand runs a user-supplied file which itself runs AutoCAD.

8.4 Installing and configuring AutoCAD

In order to use AutoDRAFT, AutoCAD must be installed and configuredfor each computer where AutoDRAFT will be used. TheAutoCADInstallation and Performance Guidesupplied with AutoCAD describes

how to do this.

AutoCAD should be configured to locate the extra menus and fonts usedin AutoDRAFT: the method depends on the AutoCAD version, typically:

Add the appropriate paths to the autodraftACAD,autodraftACADsourceand autodraftfontsdirectories to the>Tools>Options>Support File Search Pathfield.

The AutoDRAFT environment variable setting commands applicable toeach release of AutoCAD are listed in the following sections. Theenvironment variables are set within the supplied pdms.batfile. Theseshould be edited to suit the installed version of AutoCAD.


8/13/2019 ig51314.pdf

37/54


8.4.1 AutoCAD R2002

set PDMS_ACAD=2002set PDMS_ACAD_PATH=pathname for AutoCAD R2002 filese.g. C:\Program Files\Acad2002;C:\Program Files\Common

Files\Autodesk Sharedset ACAD_VERSION=%PDMS_ACAD%set path=location of autodraftACAD directory;%PDMS_ACAD_PATH%;

%path%

Before running AutoDRAFT, you need to run AutoCAD R2002 and addthe following as file paths:

Location of autodraftACAD directory

Location of autodraftACADsource directoryLocation of autodraftfonts directory

8.4.2 AutoCAD R2004

set PDMS_ACAD=2004set PDMS_ACAD_PATH=pathname for AutoCAD R2004 files

e.g. C:\Program Files\Acad2004;C:\Program Files\CommonFiles\Autodesk Shared

set ACAD_VERSION=%PDMS_ACAD%set path=location of autodraftACAD directory;%PDMS_ACAD_PATH%;

%path%

Before running AutoDRAFT, you need to run AutoCAD R2004 and addthe following as file paths:

Location of autodraftACAD directoryLocation of autodraftACADsource directoryLocation of autodraftfonts directory

8.5 Getting Started with AutoCAD

Before using the Drawing Editor make sure that AutoCAD has beencorrectly installed and configured by entering the command acad at theoperating system command prompt.


8/13/2019 ig51314.pdf

38/54


8.6 Application Macros for use with PDMS DRAFT

The applicationware provides the additional menus and forms requiredto run the AutoDRAFT editors in AutoCAD directly from DRAFT andISODRAFT.


8/13/2019 ig51314.pdf

39/54

9 Upgrading Projects to Version 11.6

It is necessary to upgrade your PDMS projects by using the appropriateupgrade procedure. The procedure supplied with PDMS 11.6 will workwith all releases from PDMS 11.2 onwards. If you are upgrading from anearlier version of PDMS, it is necessary to upgrade from each PDMSversion to the next by using the upgrade procedure supplied with theappropriate version of PDMS.

For example, to upgrade a project from PDMS 10.5 to PDMS 11.6, it isnecessary first to load the PDMS 11.2 product, and use its upgradeprocedure to create a PDMS 11.2 version of your project, before using theupgrade scripts supplied with 11.6.

No database upgrade is necessary for PDMS 11.4 or 11.5 projects. Theonly action of the upgrade in this case is to remove the *vir.dat files fromthe project if you say yes to the prompt. These files are now stored inPDMSEXE to simplify the upgrade process: the change was made atPDMS 11.4sp1.


8/13/2019 ig51314.pdf

40/54

Upgrading Projects to Version 11.6


8/13/2019 ig51314.pdf

41/54

10 Troubleshooting

Here are some suggestions about solving some problems you mayencounter when using PDMS under Windows.

10.1 General

Error: The dynamic link library DFORMD.dll could not be found in thespecified path.

Explanation: This is supplied with PDMS. Perhaps you have not set your PATHvariable. The PATH setting must include C:\AVEVA\pdms11.6.

Error: STOP. The application failed to initialise properly (0xc0000135). Clickon OK to terminate the application.

Explanation: This occurs after a number of other errors. The most likely reason is aproblem with the PATH variable.

10.2 License Manager Errors

Error: When you start up lmgrd it says (lmgrd) Can't make folderC:\FLEXlm, errno: 2 No such file or folder, etc.

Solution: There is no C: drive for the license manager to write to. As the SystemAdministrator or a Power User, you need to make a shared disk calledC:. This can be done on a networked or non-networked computer.

Within the Windows Explorers Filemenu, create a new folder (e.g.D: \ C_dr i ve) and make it current. Select File>Propertiesand selectthe Sharetab. Click on the Shared As:radio button and then click OK.

Then from the Tools menu select Map Network Drive. Select C: fromthe Drive: drop-down list in the displayed form and type

\\hostname\C_drive

in the Path box. Then click on OK. (C:) should now appear in the list ofavailable drives in Explorer.

Error: (lmgrd) "": Not a valid server hostname, exiting.Explanation: The hostname used by AVEVA to create the license file does not

correspond with the computer on which you are running PDMS. Thehostname comes from the variable COMPUTERNAME, which you can


8/13/2019 ig51314.pdf

42/54

Troubleshooting

obtain by typing 'env| f i ndst r COMPUTERNAME' in a CommandPrompt window. Compare this with the license file contents, andresubmit if necessary.

Pop up Mess.: FLEXlm: checkout failed: Cannot connect to license server (-15,10:10061) WinSock error code.

Explanation: lmgrd has not been started up - see above for details.

Pop up Mess.: FlexLM: checkout failed: Cannot find license file (-1,73:2) No such fileor folder.

Explanation: lmgrd has not been started up - see above for details.

Pop up Mess.: FlexLM: checkout failed: Licensed number of users already reached(-4,132).

Explanation: You have exceeded the permitted number of users specified in yourlicense file.

10.3 Entering PDMS

Error: (43,9) Environment Variable not defined for project name.Explanation: You have not set the environment variable for the project, e.g. XYZ000.Error: (43,1) Project not available!

Error 7 allocating system database.

Explanation: The environment variable for the project does not point to the correctlocation. Either the disk and/or folder do not exist or are not readable.

Error: not found.orBad password.

Explanation: You are trying to enter PDMS without a valid PDMS username and/orpassword.

Error: PDMSWK environment variable not set.Solution: Set PDMSWK to c:\temp or some other folder where PDMS can create

temporary files.

Error: Error 34 opening variables file.Explanation: You cannot create a file in the location pointed to by environment

variable PDMSWK.


8/13/2019 ig51314.pdf

43/54

Troubleshooting

Error: Project is pre version 8.Explanation: This can happen if you have transferred the project from UNIX using

FTP in ASCII rather than Binary format.

10.4 Problems with Graphics

Error: Cannot pick certain items in DESIGN 3D shaded views.Solution: There is probably a problem with the display driver for the graphics

board that you are using. Make sure you have the version of the displaydriver recommended on our supported display drivers Web page.

Error: Incorrect colours.Solution: Check the setting of your Display. The colour resolution should be set to

True Colour or 16.7 million colours.

Error: Graphics speed (for example in 3D views) is poor.Solution: Check the setting of your Display.


8/13/2019 ig51314.pdf

44/54

Troubleshooting


8/13/2019 ig51314.pdf

45/54

11 Structure of PDMS on .NET

From PDMS 11.6, the GUI uses the Microsoft .NET environment including thelatest WinForms based user interface components. Using this state-of-the-arttechnology enables docking forms and toolbars in PDMS and provides a robustfoundation for the future provision of standard application programminginterfaces.

This does affect the way PDMS is installed: this section gives a brief overview

and the following one outlines how to troubleshoot the installation.

11.1 Overview

This section describes the overall structure and components of the PDMS .NETinstallation, and the environment necessary to run it. Each PDMS GUI modulenow consists of a thin .NET exe, a .NET Wrapper DLL and a Win32 DLL plussome other shared components including 3rd party controls from Infragistics.The .NET components are private assemblies installed under the root directory%PDMSEXE%.

11.2 PDMSEXE

The environment variable %PDMSEXE% is used to locate the executable onmodule switch. It is also used to locate attlib.dat (attribute and noun definitions),message.dat (message definitions), desvir.dat (schema definition) etc. NormallyPDMS is started from pdms.bat which is located in your %PATH%. Both%PDMSEXE% and %PATH% should include the install directory.

11.3 GUI module structure

Each GUI module is structured in the same way. For Design the structure lookslike this


8/13/2019 ig51314.pdf

46/54

Structure of PDMS on .NET

des.exe

Wrappers.dll

des.dll

where des.exe and des.dll live in the directory %PDMSEXE% and Wrappers.dlllives in the Design subdirectory below %PDMSEXE%. So, when running a PDMSGUI module %PDMSEXE% is used to locate the executable, .NET loading rulesare used to load Wrappers.dll and Win32 DLL loading rules are used to loaddes.dll (and other Win32 DLLs on which des.dll depends).

11.3.1 Wrappers

For each GUI module (Design, Draft, Admin, Isodraft and Monitor) there is aWrappers.dll in a subdirectory with the same name as the module. EachWrapper.dll has a dynamic link to the appropriate Win32 DLL for that module.

.NET loading rules are used to load the appropriate Wrappers.dll for a givenmodule. So, when running des.exe, the version of Wrappers.dll linked withdes.dll will be loaded. Design and Draft subdirectories also contain adrawlistWrapper dll which is used by the Drawlist add-in.

11.3.2 .NET Loading rules

All the .NET assemblies are Private assemblies and are installed under%PDMSEXE% (Assembly Base directory) or a subdirectory below. .NET loadsprivate assemblies from the base directory of the application. If it cant find the

private assembly here it uses the applications configuration file called.exe.config to see whether it contains any path hints. Path hints arestored in the element. So, for example, des.exe.config has thefollowing probing path . This means thatWrappers.dll is loaded from the subdirectory Design below the applicationdirectory.


8/13/2019 ig51314.pdf

47/54


11.3.3 Win32 DLLs

Each Wrappers.dll depends on the given modules Win32 DLL, e.g. DesignsWrappers.dll found in the Design subdirectory depends on des.dll. Win32 DLLloading rules apply here. These are:

The directory from which the importing component loaded. (e.g. theDesign subdirectory where Wrappers.dll is loaded)

The (application's) current directory (where its run from)

The Windows directory (default: C:\Windows) (we dont install anythinghere)

The directories that are listed in the PATH environment variable

Since the module DLL does not live in the same directory as the Wrappers.dllthen unless you are running from %PDMSEXE%, your %PATH% will be used tolocate the module DLL. (The Wrappers.dll subdirectory is the directory which isfirst searched for all the Win32 DLLs on which Wrappers depends i.e..dll, sglNet.dll, udDNet.dll, )

11.4 Components

The following components will be installed under %PDMSEXE% or one of itssubdirectories. This is not a complete list but a list of all .NET related files forGUI modules (Design, Draft, Isodraft, Admin and Monitor). Each module has an.exe and corresponding dll e.g. des.exe and des.dll, a config file, a manifest fileand an Addins file. The config file is used to specify the location of the Wrappersdlls for each application, the manifest file is used to set the visual style of theapplication and the Addins file defines which add-ins the application will load(e.g. Explorer, Drawlist, ).

11.4.1 PDMSEXE directory

Design/Spooler

des.exe, des.dll, des.exe.config, des.exe.manifest, DesignAddins.xml,SpoolerAddins.xml

Draft

dra.exe, dra.dll, dra.exe.config, dra.exe.manifest, DraftAddins.xml


8/13/2019 ig51314.pdf

48/54


Monitor

mon.exe, mon.dll, mon.exe.config, mon.exe.manifest

Isodraft

iss.exe, iss.dll, iss.exe.config, iss.exe.manifest, IsodraftAddins.xml

Admin

adm.exe, adm.dll, adm.exe.config, adm.exe.manifest

Shared

Depends.dll, DrawList.dll, DrawListAddin.dll, ExplorerAddin.dll,ExplorerControl.dll, ForeignLanguage.dll, HistoryAddIn.dll, MyDataAddIn.dll,ReferenceListAddin.dll, PDMSCommands.dll, PDMSFilters.dll,PDMSResources.dll, PDMSResources.resources, StartUp.dll,

ApplicationFramework.dll, udNet.dll, DruidNet.dll

Infragistics

This is a third-party GUI tool-kit:

Infragistics.Shared.v3.dll, Infragistics.Win.UltraWinDock.v3.dll,Infragistics.Win.UltraWinExplorerBar.v3.dll,Infragistics.Win.UltraWinGrid.v3.dll,Infragistics.Win.UltraWinStatusBar.v3.dll,Infragistics.Win.UltraWinTabbedMdi.v3.dll,Infragistics.Win.UltraWinTabControl.v3.dll,Infragistics.Win.UltraWinToolbars.v3.dll, Infragistics.Win.UltraWinTree.v3.dll,Infragistics.Win.v3.dll, Infragistics.Win.Misc.v3.dll

System

msvcp71.dll, msvcr71.dll

Other DLLs required by DRAFT

These DLLs are loaded as required by specific DRAFT commands:

Draft_DXF_LI.dll, Draft_DGN_LI.dll, Draft_Test_LI.dll, Draft_SVG_LI.dll

Other DLLs required by DESIGN

sgl5NET.dll


8/13/2019 ig51314.pdf

49/54


11.4.2 PDMSEXE/Design subdirectory

drawlistWrappers.dll, Wrappers.dll

11.4.3 PDMSEXE/Draft subdirectory


11.4.4 PDMSEXE/Monitor subdirectory

Wrappers.dll

11.4.5 PDMSEXE/Isodraft subdirectory


11.4.6 PDMSEXE/Admin subdirectory

Wrappers.dll

11.4.7 Add-ins

These new user interface .NET components are loaded by the ApplicationFramework. Each module has an addin file which defines the set of add-ins itwill load, e.g. for Design this file is DesignAddins.xml. The toolbar entries toshow and hide each add-in are defined in PML.

11.5 Forms and Menus

Most of the User Interface is still defined in PML located in %PMLLIB% and%PDMSUI%.


8/13/2019 ig51314.pdf

50/54


8/13/2019 ig51314.pdf

51/54

12 Troubleshooting the .NET installation

12.1 Version Error

Error: System.IO.FileLoadException: The located assembly's manifestdefinition with name 'PDMSResources' does not match the assembly reference.

Solution: All .Net assemblies must be the same version. CheckFile>Properties>Version Assembly Version on all assemblies is 11.6.0.0 or whateverthe current version is.

12.2 Wrappers or a dependency missing

Error: An exception System.IO.FileNotFoundException has occurred inmon.exe.

Additional information: File or assembly name Wrappers, or one of its dependencies,was not found.

Solution: All the .NET assemblies are Private assemblies and are installed under%PDMSEXE% (Assembly Base directory) or a subdirectory below. .NET loadsprivate assemblies from the base directory of the application. If it cant find theprivate assembly here, it uses the applications configuration file called.exe.config to see whether it contains any path hints. Path hints are storedin the element. So, for example, des.exe.config has the following probingpath . This means that Wrappers.dll is loadedfrom the subdirectory Design below the application directory. Each Wrappers.dlldepends on the given modules Win32 DLL e.g. Designs Wrappers.dll found in theDesign subdirectory depends on des.dll. Win32 DLL loading rules apply here. Theseare

The directory from which the importing component loaded. (i.e. the Designsubdirectory where Wrappers.dll is loaded in the case of Design)

The (application's) current directory (where its run from)

The Windows directory (default: C:\Windows) (we dont install anything here)

The directories that are listed in the PATH environment variable

Since the module DLL does not live in the same directory as the Wrappers.dll then

unless PDMS is running from %PDMSEXE% the %PATH% will be used to locate


8/13/2019 ig51314.pdf

52/54

Troubleshooting the .NET installation

the module DLL. (The Wrappers.dll subdirectory is effectively is the directory whichis first looked in for all the Win32 DLLs which Wrappers depends on i.e..dll, sglNet.dll, udDNet.dll, )

Make sure that both %PDMSEXE% and %PATH% point to the root directory inwhich PDMS is installed.

12.3 Interface incompatibil ity

Error:An exception System.MissingMethodException has occurred in mon.exe

Or

An exception System.IO.FileNotFoundException has occurred in mon.exe

Additional information: A procedure imported by 'Wrappers' could not be loaded.

Solution: The interfaces between components are not compatible. CheckFile>Properties>Version Assembly Version on all assemblies is 11.6.0.0 or whateverthe current version is.

12.4 Security error with thin client

Error: An unhandled exception of type 'System.IO.FileLoadException' occurredin Unknown Module.

Additional information: Unverifiable assembly 'Wrappers' failed policy check.

Solution:.NET security gets in the way when running PDMS across the networkwhere the assemblies reside on a different machine to the .NET runtime. Thedefault security level for the local intranet is not set to Full Trust which means thatprograms may not be able to access resources on the local machine. To overcome

this, the intranet security may be set to Full Trust. However this means that any.NET assembly may run. Alternatively, Full Trust may be given to a specified groupof strongly named assemblies. This is done using the code access security policy toolcaspol. This should be run on each client machine to add all the assemblies on agiven server directory to a group and give Full Trust to this group.

Use Administrative Tools>.Net Configuration 1.1>My Computer>Runtime SecurityPolicy>Machine>Code Groups>All Code>LocalIntranet_Zone to check the groupproperties.

If the security Policy has not been set, this can be done by hand using:


8/13/2019 ig51314.pdf

53/54


caspol -m -ag LocalIntranet_Zone -url\\\\* FullTrust -n "" -d ""

where is the UNC (Uniform Naming Convention)- the format of aUNC path is: \\\\

Or

If you are not concerned about other .NET remote assemblies running on yourmachine, this can be set for the entire intranet using:

Control Panel>Administrative Tools>Microsoft .Net Framework 1.1Configuration>Configure Code Access Security Policy>Adjust Zone Security>Makechanges to this computer

Then change Local Intranetto Full Trust

http://%3Cservername%3E/%3Csharename%3E/%3Cdirectoryhttp://%3Cservername%3E/%3Csharename%3E/%3Cdirectory

8/13/2019 ig51314.pdf

54/54


12.5 No Add-ins

Problem: Add-ins missing from moduleSolution:

Add-ins loaded by each module are defined in the following xml files:

DesignAddins.xml

DraftAddins.xml

IsodraftAddins.xml

SpoolerAddins.xml

If Add-ins are missing, check that these files exist in %PDMSEXE%

12.6 Window Layout

Problem: Window layout is not restored e.g. Add-ins position and/or dockedstate,

Solution: The file WindowLayout.xml in the %PDMSUSER%directory stores this information for the each GUI module. If this file is deleted thenthe window layout will return to its default.

12.7 Serialization

Serialization is the process used to store the data e.g. history stacks, toolbar state for the GUI in a .NET environment.

Problem: Information is stored per project and per module in the following filesin the %PDMSUSER% directory:

Settings.binSettings.bin.

Solution: These files may be deleted or transferred between users working on thesame project.

ig51314.pdf

Documents