![]() |
This task shows how to export your V4 catalog parts to V5. | |
![]() |
This process will
migrate the parts geometry and parts attributes from your V4 library to
V5. Before you perform this procedure you should export project
registration and standards data, which is explained elsewhere in this
section.
The process described here is the preferred method of exporting parts. However, if for some reason you do not want to export the V4 library, or you do not have access to it, you can export parts directly from a V4 model. The procedure is described in Exporting Parts from a V4 Model. |
|
![]() |
1. | Parts in
compressed form cannot be migrated. If your catalog is in compressed form
then you must re-create it in uncompressed form using standard V4
procedures. This
requires adding to your DCLS file following declarative:
CATAEC.SETUP.PRO.CATALOG_COMPRESSION=FALSE; You may also need to set the
MAXTIM variable appropriately, such as: catia.MAXTIM_CPU=150000;.
The uncompressed parts geometry will be placed inside "timestamp" details (*.library files) in the following directory: ...setup\PRO\APD\lib. The catalog file will be placed in the following directory: ...setup\PRO\catlg. |
2. | In the same ...\catlg directory,
create an index type file and name it PRTMGXXX, where XXX is your catalog
number. The V4 sample catalog number is frequently 005 and that is the
number that will be used in this document. You need to create a special
file - you can name it migrateXXX - which will be used to create the index
file. You can create this input file by copying an existing file (convert1_catalog_parts,
which is in the same directory) and editing it. Enter the following in the
file:
/* */ *TYPE create_CCAPS_index *INPUT /aecsite424/setup/PRO/catlg/PRTDA005 *OUTPUT /aecsite424/setup/PRO/catlg/PRTMG005 *KEYS PARTDEF CATEGORY 8 PARTDEF PARTTYPE 8 PARTNUM PARTNO 40 PIPESIZE SIZE 40 ELCATLOG ELTIME 16 STANDATA STANDARD 8 VNDRCODE VNDRCOD 40 PARTNAME PARTNAME 40 PIPESPEC ENDS 40 ENDSPEC ENDS 40 ENDSPEC RATG 40 See ...MigrationDirectory\Piping Systems\V4_CatalogMainFile\migrate999 for an example. |
|
3. | Also in the ...\catlg directory
enter at a prompt: run catutil -l RF0CPT -i migrate005 -o
migrationindex.out
This will create the file PRTMG005 in the ...\catlg directory. Ignore error messages "Undefined Attribute Group Name". This only indicates that pipes do not have part end styles and parts do not have pipe end styles. |
|
4. | Move the the PRTMG005 file to its V5 location, in the directory: ...intel_a\startup\EquipmentAndSystems\MigrationDirectory\PipingSystems\ V4_CatalogMainFile | |
5. | Move all the <timestamp> files that were
created when you uncompressed your V4 catalog to their V5 location:
...intel_a\startup\EquipmentAndSystems\MigrationDirectory\PipingSystems\
V4_Catalog_Details. They are called timestamp files because
each file will have a date and time stamp for a file name as shown below:
2001248204613737.library 2001248204623132.library 2001248204625529.library 2001248204627914.library 2001248204630318.library |
|
6. | You must migrate the standard encode/decode tables from V4 using CATAecV4ToV5PipingTables before you start the migration of piping parts. The migrated tables must reside in ...MigrationDirectory\Piping Systems\V5_Migrated_Tables\ASTL (or another directory with your standard's name). | |
7. | In V5, open a command prompt window and change
directories to ...intel_a\code\command. Type in the following and hit
Enter: CATAecV4ToV5PipingCatalog.bat 005 (replace the numerals 005 with
your catalog number). This will create your V4 parts in V5, placing them
in ...intel_a\startup\EquipmentAndSystems\MigrationDirectory\PipingSystems\
V5_Generated_CATParts (unless you set the AECMIGR_DIRECTORYPATH
variable to a different location). Each part will have a unique, generic
part name.
For Unix execute the script CATAecV4ToV5PipingCatalog.sh 005 (replace 005 with your catalog number). |
|
8. | Create a parts catalog, a suggested name being PipingParts005.catalog, and place the parts in it. See ...MigrationDirectory\Piping\Piping Design\ComponentCatalogs for an example. | |
|