Multi-Discipline Supports Administrator Guide

Project Upgrade for MDS Defaults : Details of the Utility
Some of the contents of MDS Defaults Files are combined into common PARAGON CATALOGUE elements, so that the default data extracted from one or more MDS default files for the same MDS Ancillary or Framework Standard etc. is stored in the same PARAGON CATALOGUE element.
For a comparison of which MDS Defaults File is stored in which PARAGON CATALOGUE element see the breakdown in the following tables.
Note:
The MDS12 Application default values converted and upgraded from the six MDS 11.6 defaults files are all in DATA elements in their own DATASET element.
Shown below is a table depicting which MDS12 PARAGON CATALOGUE element is partially or wholly created from which MDS default file.
MDS Application Default File Name
MDS12 PARAGONPARAGON CATALOGUE Element Name
CATA /MDS/OPTION/DEFAULTS
CATA /MDS/STRUCTURE/DEFAULTS
CATA /MDS/HANGER/DEFAULTS
CATA /MDS TRUNNION/DEFAULTS
CATA /MDS/PRELIMINARY/DEFAULTS
CATA /MDS/ANCILLARY/DEFAULTS
CATA /MDS/TRUNNION/DEFAULTS
CATA /MDS/STRUCTURE/DEFAULTS
CATA /MDS/HANGER/DEFAULTS
CATA /MDS/STRUCTURE/DEFAULTS
CATA /MDS/ZONEID/DEFAULTS
CATA /MDS/ICON/DEFAULTS
Shown below is a table depicting which MDS default file is partially or wholly transferred into which MDS12 PARAGON CATALOGUE element.
MDS12 PARAGON CATALOGUE Element Name
MDS Application Default File Name
CATA /MDS/OPTION/DEFAULTS
CATA /MDS/STRUCTURE/DEFAULTS
CATA /MDS/ANCILLARY/DEFAULTS
CATA /MDS/TRUNNION/DEFAULTS
CATA /MDS/HANGER/DEFAULTS
CATA /MDS/PRELIMINARY/DEFAULTS
CATA /MDS/ZONEID/DEFAULTS
CATA /MDS/ICON/DEFAULTS

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