PDMS 12.0 is a major update from earlier releases of PDMS but every effort has been made to simplify the upgrade process. Most of the database updates are automatically applied when using PDMS 12. Please note that once a database has been written using PDMS 12, it will no longer be accessible by PDMS 11. Upgrade scripts are provided to upgrade projects from PDMS 11.6. It is strongly recommended that projects are backed up before commencing the upgrade process.
Global projects should be upgraded at all sites simultaneously; the recommended procedure is to consolidate them at the hub, perform the upgrade and re-distribute as required.
It should be noted that PDMS 12.0 databases will not be accessible by PDMS 11.x due to format changes. However, the inconvenience should be minimal as PDMS 12.0 can access PDMS 11.6 databases (in read mode) from a ‘foreign’ project.
Users’ own PML applications from PDMS 11.4 onwards should continue to work, after being amended to use the new application switching mechanism. Please see Chapter 23. It is possible that some form layouts will be adversely affected by the change at PDMS 11.6 to the standard Windows proportional screen fonts, though this depends on the way the forms have been defined. There is also scope for enhancement by using the new facilities offered by PML, such as toolbars and docking forms. Many of the AVEVA applications have been upgraded in this way, so users who have revised the AVEVA applications should review their changes in the light of this work.
Any Data Access Routines (DARs) programs must be re-compiled – please see note below.
2.5.1 Summary of project upgrade process *12.0.SP5*
There are major changes to PDMS databases between PDMS 11 and PDMS 12, including many extensions, more accurate (double precision) numbers and changes to Draft pens. There are also changes to the system database to enable many of the new functions in PDMS 12.
Draft Picture files are now stored in a more complex directory structure to cope better with very large volumes of drawings – for details, please see section 16.7. The Picture files also need to be upgraded to cope with the more accurate coordinates.
The upgrade to increase accuracy is performed ‘on-the-fly’ by changing data as it is updated in the normal course of design work. It is not necessary to use the database Reconfigurer function but it is necessary to perform some major upgrades on the DRAFT (Paddle) databases. A script is provided – see section 2.5.2 below.
The upgrade process is initiated by a Free User, who is allowed to enter PDMS 12 Monitor and Admin in a PDMS 11.6 Project in order to run the main script upgradeMac. Before doing this, the following actions should be performed:
• Ensure that there are no extracts on PADD databases and that they have been synchronised at the hub for Global projects
• Run the upgrade script, which works on both Global projects (see note below) and non-Global projects. Please note that it may be simpler to consolidate a project at the hub and then re-distribute after performing the upgrade.
Please note that any attempt to access a constructor module before completing the upgrade will result in an error message:
Error attempting to access a PDMS 11 project using PDMS 12
Among other things, the upgrade process will:
• Enter Admin
o Delete and re-create the COMMS elements to allow larger MDBs o Mark the project as a PDMS 12 project
o Update the module definitions, including removal of the obsolete DESCOMP module and its COMP databases
• Enter DRAFT
o Create a new DRAFT (PADD) database (MASTER/STYLWL) with a STYLWL and add it to relevant MDBs
o Read %pdmsdflts%/dra-pens and dra-lindef and create definitions of user defined pens if necessary
o Run the command UPDATE STYLEATTS on all current PADD Databases o Create a new directory structure for DRAFT Picture Files
o Optionally regenerate the picture files to cater for increased accuracy (this is the time-consuming step)
Notes:
• DRAFT databases that do not belong to an MDB will be missed, as the process upgrades each MDB containing one or more PADD databases. Users are advised to create a temporary MDB for all such ‘orphan’ databases, if any.
• For a Global project the sequence should be:-
o At the Hub (where the STYLWL should be created) go through all PADD databases (those that are primary at the Hub will be writeable, those that are non-primary at the Hub will be read-only); add all necessary pen information to the new STYLWL (which is writeable at this location)
o Propagate the db containing the STYLWL to all locations.
o At each location go to each PADD db and run the Update Style Attributes command.
• If applicable, the user should delete and re-create all Isodraft symbol files.
• TrueType fonts are available in PDMS 12 but may not be mixed with the older PDMS fonts (font families 1 to 4) in any way. If you wish to upgrade libraries or drawings, it is therefore necessary to output them to a Data Listing, edit it to change the fonts and then re-input:
libraries and then drawings. Before re-input, the receiving project should have suitable fonts created as new font families (from 5 onwards).
• It is advisable to update the spatial map after upgrading a project to PDMS12. This can be achieved using the command MAP BUILD MDB.
2.5.2 Performing the upgrade process *12.0.sp4*
Upgrade macro files
Five Macro files are included with the PDMS 12.0 DRAFT user interface (default location C:\AVEVA\plant\PDMS12.0.SP4\pdmsui\dra\upgrade)
The location of these files is referenced by a global variable in the main Upgrade macro UpgradeMac (!!upgradeDirectory = '%PDMSUI%\DRA\upgrade’)
The upgrade uses a function called tstAllocRecdPM.pmlfnc which will need to be enabled using the command:
PML REHASH ALL
As part of the upgrade process, the project is locked to prevent new users from accessing it. There is no User prompt. All Users are expunged, and all entries in the COMMS database are deleted. This is in order to increase the number of DBs in an MDB from 300 to 1000.
Non-Global projects
If the project is not Global, the process is very simple. The upgrade is initiated by running the upgradeMac macro from the Monitor command window, either by typing:
$m/C:\AVEVA\plant\PDMS12.0.SP4\pdmsui\dra\upgrade\upgradeMac or by dropping the upgrade macro on to the command pane.
The process is tracked by writing 2 files in %PDMSUSER% as it progresses:-
1. Logfile<proj code> ALPHA LOG file: echo of the console window 2. UpgradeLog<proj code> Upgrade results file reporting success/failures
If these log files show no problems, the project itself should be reviewed to check that all is well. It might also be worthwhile checking the database integrity using DICE. The project should now be ready for use with PDMS 12.
Global projects
Global projects require a little more work – it may be easier to bring all the data back to the hub for the upgrade. However, this is not always possible so the upgrade process can be carried out globally if a few additional steps are taken – note that all sites must be upgraded before the project is used.
When upgrading a Global project, the daemon must be stopped at all locations. Upgrading from an earlier release of PDMS 12.0 is straightforward; the new daemons should be installed at each location and then restarted. Upgrading from PDMS 11 needs the upgrade script to be run at the HUB and the Global database copied to all Satellite locations.
If upgrading from PDMS 11.2 or 11.3 (Global 1), the transaction database for each satellite should also be copied to the satellite. (It is not necessary to copy the transaction databases when upgrading from Global 2.1.0 or later.)
The upgrade script should then be run at each satellite. All the projects associated with the global set-up must be set-upgraded before the set-upgrade is complete. Daemons can then be restarted and you should INITIALISE each satellite.
Please see the AVEVA PDMS Installation Guide and the AVEVA Global Installation Guide.
Summary process for upgrading Global projects from PDMS 11 to PDMS 12 Preliminary checks:
Ensure that the HUB has an up-to-date view of every non-propagating PADD database which is primary elsewhere. This is necessary to gather all required pen data at the project HUB.
• This may mean issuing manual UPDATE DB commands for non-propagating PADD databases which are primary at satellites
• EXTRACT FLUSH DB for all PADD working extracts at satellites (if any)
• All locations must have their old daemons stopped, and their new Global 12.0 Daemons restarted prior to starting the upgrade process.
Make certain that the Daemons are running
• Stop any update events Upgrade process:
1. Run the upgrade at the HUB