SUBJECT: Using CCD to migrate from other CADAM-like systems to CATIA V5 on Windows NAME: Ozzie Marquez Date: April 2002

Transcription

1 SUBJECT: Using CCD to migrate from other CADAM-like systems to CATIA V5 on Windows NAME: Ozzie Marquez Date: April 2002 Page 1

2 AGENDA MIGRATION PLAN OS AND HARDWARE REQUIREMENTS CCD ENHANCEMENTS WINDOWS NT INSTALLATION AND CONFIGURATION TIPS LICENSING AND PLOTTING DATABASE MIGRATION ON-LINE DOCUMENTATION ADMINISTRATOR TIPS Page 2

3 OS and HARDWARE REQUIREMENTS CATIA-CADAM DRAFTING (CCD) SUPPORTS: CCD V424R2 CCD V5R9 Windows NT 4 SP4, SP5 or SP6a Windows NT 4 SP4, SP5 or SP6a Windows 2000 and Windows XP Windows 98, Windows 2000 and XP HARDWARE FOR A PRODUCTIVE SYSTEM: 150 MHz CPU (or faster) 128 Mb of RAM (more if working with large raster models) 2D graphics adapter with 2 Mb VRAM 2 or 3 button mouse (3 preferred) 17 inch SVGA monitor with.28 (or better) dot pitch Network adapter (required for licensing) Page 3

4 CCD ENHANCEMENTS CCD V424R2 & V5R9 Administration Windows 2000 support - LUM or above required for Windows LUM or above required for Windows XP Automatic license release - Administrators can now specify an idle time of 30 minutes or more before the session license is released. Static binding for license clients LUM or above is required on the License Server. LUM does not have to be installed on the clients. Remote Plot Mode - Drawings on remote host can now be plotted without having to file the model locally. Window Temp Plot Data - New button TPD added to Plot Current. Plots what s on the screen, like Buffer Plot Page 4

5 CCD ENHANCEMENTS CCD V424R2 & V5R9 Administration (con t) Synchronization of remote format tables with CCD-NT New character strokes Several new characters have been added to support Helix to CCD migrations. Cut/Copy/Paste between CCD sessions introduced in V5R9. Page 5

6 CCD ENHANCEMENTS CCD V424R2 & V5R9 Administration (con t) CADEX is available Requires a separate install A V4 type license is required IUE change Absoft ProFortran V6.2 is now certified (Windows only) MCX/Helix Translator is included with CCD V5 Helix Migration Package can also be downloaded from Page 6

7 INSTALLATION Remove all references to older CCD releases before installing CCD V4 or V5 Using Control Panel, remove the following environment variables: - CCD_ROOT - OPGS_RUN_TIME - DXF_TMP - PDELIB_TMP Also remove all references to the older CCD release directory from the Path variable. Use a regular user to install CCD V4 or V5 Installing CCD on Windows is very simple. Page 7

8 INSTALLATION REGISTRY ENTRIES HKEY_LOCAL_MACHINE - SOFTWARE/ - DASSAULT SYSTEMES/ - CATIA-CADAM Drafting/ - 590/ CCD_ROOT UserManuals e:\ccdraft e:\ccdraft\doc On Windows, if CCD is installed by the administrator, use Regedt32 to change access to DASSAULT SYSTEMES. Give everyone read access. Page 8

9 INSTALLATION Code-serving versus installing on each client Code-serving advantages: - Since the code is only installed on one system, code updates and administration is centralized, therefore simpler. - Ensures that everyone is running the same level of code. - Recommended if network speeds are acceptable when invoking CCD or CATIA. Code-serving disadvantages: - If the code-serving machine goes down, everyone is down. - On slow networks, for example, starting CCD (~10 Mb) or CATIA DR1 (~13 Mb) or CATIA MD2 (~67 Mb) can take some time. Page 9

10 INSTALLATION Code-serving versus installing on each client (con t) Client installation advantages: - Improves application startup time. Specifically on Wide Area Networks (WAN). - The user or administrator can run a local, customized version of CCD or CATIA. - If the workstation uses a nodelocked license, the user can continue to run locally, even if the database server is inaccessible. Client installation disadvantages: - More difficult to administer and control in large installations. Page 10

11 INSTALLATION CLIENT CCD Shortcut Create a CCD Shortcut on each NT Client with the following options: Target: ccdraft <options> -f (full screen) -m (start-up model name) Start in: Name of directory CCD should start in for File/Open. Page 11

12 LICENSING LICENSING CCD Only IBM s License Use Management (LUM) is supported. The current version is 465. NT 4.0, Windows 2000, XP or UNIX (AIX, HP-UX, IRIX or Solaris) can be a license server - You must install LUM on the server and at least on one client. - After installing LUM on one client, move the Winnt\i4ls.ini file to all other clients. - Install the new ccdnls.dll with static binding support on all CCD clients. This dll is available from DSA s FTP Site. - LUM is free for all platforms and can be downloaded from: Page 12

13 LICENSING LICENSING CCD LUM V4.6.4 and are now supported and required for Windows XP. A valid CATIA V5 Configuration (DR1, MD1, ME2, etc.) must be installed to run CCD V5. IBM generates two license certificates: One for CATIA V5 and the other for CCD, even though CCD is an add-on product. Ask for product number 5691-CCD. CCD V4 offers a 30 day full-function trial license. CCD V5 offers a 45 day full-function trial license. Page 13

14 LICENSING LICENSING CCD V5 CCD V4 HRAS (Hybrid Raster) and CADEX can be used with CCD V5, but both require a V4 license. IUE and MCX are now included with Base CCD V5, therefore a separate license for these products is not required. The Markup and Annotation product is no longer available in V5. Page 14

15 ON WINDOWS, CCD SUPPORTS: CGM, HPGL, HPGL/2 and PostScript Other formats (see CCDraft\Plot\Samples\ps2tiff.bat) PLOTTING UNIX Scripts Equivalent files on Windows PLOT/plotscript_hp2 Plot\hpgl2.bat (runs the job) PLOT/backend_hp2 Plot\hpgl2.def (PHIGS config) PLOT/plotopts_hp2 Plot\hpgl2.opt (plot options) Plotting is well documented in the CADAM Drafting Plotting Installation Guide for Windows. Page 15

16 PLOTTING Buffer plotting can be done by using the new (Window TPD) button on Plot Current. You can also use the Windows screen capture tools or CCD s clipboard feature. Windows Print Driver Support If you can print to a printer/plotter from Windows, then CCD should also be able to plot to it. Just select Windows Printer as the default plotter from CCD s Plotter Setup menu. Only the plotopts file is customizable. Page 16

17 MIGRATION PATHS MICRO CADAM AutoCAD CADRA MF CADAM MCXTRAN G O O D EXCELLENT Models Data Transfer (UNIX) Symbols EXCELLENT B E S T G O O D DXF/DWG IGES NURESTOR PRO CADAM Pre-V3R5 db_update model names C_/C_/C_xxx to D_xxx Model update D_xxx to xxx.cdd Call and File models PRO CADAM V3R5 or > Model update name only D_xxx to xxx.cdd CCD -UNIX models/symbols/formats Rename EXCELLENT CCD-V4 or V5 CATIA V5 on Windows Page 17

18 MIGRATION PLAN Backup all data before any changes are made! Archive MF CADAM models in NURESTOR format. Helix models should be archived in either DMNDOS or OS File (.MCD) format. Don t forget the symbols, fonts, and formats (Helix models). It s a good idea to store these files on CD. What CADAM Tables need to be migrated? Symbols, Fonts, Special Characters, Plot Formats Plotting What plotters and plot options will be used? If migrating from UNIX, save all the plotscripts. It will help you when configuring plotting on Windows. Page 18

19 MIGRATION PLAN CCD Data exchange options on Windows Access to MF CADAM s database - ICF is the only interactive option on NT to access the MF CADAM database. - Starting with MVS OS390 V2.5, ICF will not work from Windows or UNIX to MF CADAM. A special MVS IUCV fix is available from DSA to resolve this problem. Access to CCD UNIX database - ICF (user is confined to the UNIX CADAM database, but can file to Windows. Must also file locally to plot the model accessed on remote systems.) - PCNFS (Warning: Unlike UNIX, Windows is not case sensitive) - IMPORTANT: CCD (UNIX and Windows) releases should be the same. Page 19

20 MIGRATION PLAN CCD data exchange options on Windows (con t) External File Translator (EFT) - AutoCAD DXF and DWG format support. - AutoCAD releases and 2000 are supported. - Some model touch-up may be required. NURESTOR files can be imported/exported using the CCD Data Transfer option on Windows. - Best method of transferring data from CADAM-like systems (other than Helix) into CCD % translation in most cases. Page 20

21 MIGRATION PLAN CCD data exchange options on Windows (con t) Helix Migration Package (mcxtranv4) - The recommended method if migrating from MICRO CADAM or Helix to CCD. - Included with V5R9, but also available from - Best translation method. Results are near 100%. - Unlike NURESTOR format, mcxtranv4 has no limitations such as model size or other imposed restrictions by the older NURESTOR Mainframe CADAM format. What you see in Helix is what you ll see in CCD! Page 21

22 MIGRATION PLAN UNIX CADPROF SETTINGS Document all current settings. The same settings can be used in the CCD Cadprof utility on Windows. If migrating from Helix, refer to the Helix Defaults to Cadprof Mapping document in the Helix Migration Package. MAINFRAME CADAM PRIVILEGE TABLE SETTINGS Use it as a guideline to help you design user database access permissions on Windows, once the migration is completed. Page 22

23 MIGRATION PLAN CADAM Drawing Database Migration Drawing database can reside on any disk drive that Windows can access. No more (group,user) directory structure required. This is similar to Helix s OS File Format. System directory (symbol, font, format, stdnote) can also reside anywhere, but you must define its location with cadprof. Default is CCD_ROOT\Drawings\System directory. Page 23

24 MIGRATION PLAN Decide where the CADAM database will reside On Windows or UNIX. CADAM s (group,user) database structure can be duplicated with directories/subdirectories on Windows. FAT32 File Systems are supported, but NTFS is recommended. Windows Security: directories and file access permissions NTFS formatted disk or partition is required. Use the Administration Utilities to set file access permissions on production release or shared directories, files, etc. Page 24

25 MIGRATION PLAN CADAM Drawing Database Migration to Windows From Mainframe CADAM - The Data Transfer utility of CATIA-CADAM Drafting on UNIX is required to transfer the symbol and font tables. Symbol and Font Tables: - Use the original FT05F001 index file used to create the tables on the mainframe. - If not available the index file can be created on the UNIX workstation. - For font tables you should also locate the mainframe font spacing table FT08F001, but it is not required -- the default will work. Plot Format tables (not a manual step anymore!): - As of CCD V423PTF1 and CCD V5R4 SP1, plot format tables are now synchronized automatically on on all supported platforms. Some configuration required. - For Mainframe CADAM it is still a manual process if there is no TCP/IP connection to the mainframe. Page 25

26 MIGRATION PLAN CADAM Drawing Database Migration to Windows (con t) From Helix - Symbol and Font Tables: - BULKXFER, included with the Helix Migration Package, automatically transfers all the symbol and font tables from Helix (sys,symbol) to CCD. - Plot Formats - BULKXFER transfers all the format models in (sys,format) and appends the new formats to the current CCD format table. Page 26

27 MIGRATION PLAN CADAM Drawing Database Migration (con t) From PROFESSIONAL CADAM on UNIX (or IBM s old RT) - Run db_update to change the model naming convention from the C_ /C_/C_xxx to the newer D_xxx - Run mdlupd UNIX IUE utility to update and rename models to the new CCD convention: Rename all models from D_xxx to.ccd) xxx.cdd (note that is.cdd not Optionally opens and files all models (required if migrating from RT- CADAM and recommended for early versions of PRO CADAM pre-v3r5). Page 27

28 MIGRATION PLAN CADAM Drawing Database Migration (con t) Special characters in the model name Since MF CADAM, PROFESSIONAL CADAM, CCD-UNIX and Helix use their own data manager, special characters such as: * \?, could be used in the model name. These characters cannot be used in a Windows file name. - By default, these characters are mapped to underscore, even if filed back to the remote system. - Use the mapping tables under the CCD_ROOT\PROFILE\convert\tables directory to map the special characters to a valid character on Windows: For English: NAME-8859_UCS-2.map (maps from WIN) * UCS-2_NAME-8859.map (maps to WIN) ** * Only required if filing back to the remote system with the original character once a drawing has already been filed on Windows. ** Local filing should not be allowed, if mapping to the same MF character. Restrict local filing in CADPROF s Drawing Management panel. Note: ICF, MCXTRAN and Data Transfer use these tables (not PCNFS). Page 28

29 MIGRATION PLAN SYMBOL TABLE NAMING CONVENTIONS CCD or PRO CADAM CCD - WIN ( 20 characters max) FONT TABLES DRAWINGS/system/font/D_128/D_fonts \Drawings\system\font\128-fonts.cdd DRAWINGS/system/font/D_128/FSpace \Drawings\system\font\128-FSpace.bin SYMBOL TABLES DRAWINGS/system/symbol/D_001/D_symbols \Drawings\system\symbol\001-symbols.cdd FORMAT TABLES DRAWINGS/system/format/D_8009a \Drawings\system\format\8009a.cdd STDNOTE TABLES DRAWINGS/system/stdnote/D_cadam_std_mm \Drawings\systems\stdnote\cadam_std_mm.cdd Page 29

30 MIGRATION PLAN SPECIAL CHARACTERS: MF OR UNIX TO WINDOWS CCD uses the Unicode Standard character set User-defined special characters on UNIX (PRO CADAM or CCD) and MF CADAM need to be recreated on Windows. - Use CCD s fontutil (located under CCD_ROOT\gphigs) to create the new characters. - New characters must be defined in the Unicode User Define area E800-EFFF. This area allows for 1,792 new characters to be defined. - Use the cadspec utility to add the new characters to the Special Character Window. Page 30

31 MIGRATION PLAN SPECIAL CHARACTERS: MF OR UNIX TO WINDOWS (con t) Helix and MICRO CADAM A new mapping table has been added to support the Helix and older MICRO CADAM special characters: - Ccdraft\Profile\Convert\Tables\Helix-8859_ucs-2.map (non-japanese versions) - Ccdraft\Profile\Convert\Tables\Helix-932_ucs-2.map (Japanese version) ** If your models contain Japanese characters, you may need to modify the 932 table in addition to the 8859 table. Check the Migration Package on for any updates to this table. Page 31

32 MIGRATION PLAN REF-ENT IS AN EXCEPTION TO THE RULE Reference Entity models must reside in a directory\subdirectory, with a name that must match the name of the group,user where the original reference entity model was located on UNIX or MF. In addition, these directories must reside under the CCD_ROOT\Drawings directory defined in cadprof. For example, on MF or UNIX - The model eng-dwg-3 in eng,bob references the model ref3 located in eng,ref On Windows - The model eng-dwg-3 can be anywhere, but the model ref3 must be located under the CCD_ROOT\Drawings\eng\ref\ directory. - Note: If a model is created on Windows, the reference entity must reside in the same directory Page 32

33 ON-LINE DOCUMENTATION ON-LINE DOCUMENTATION On-line help is in HTML format. A browser such as Internet Explorer or Netscape is required. The full documentation, including the User Guides, can be accessed and printed from Ccdraft\En_US\Help\doc.htm Beginning with V5R9, a searchable documentation package is available under CCD_ROOT\En_US\Help. But since it runs independently from CCD, it can also be download from Page 33

34 ADMINISTRATOR TIPS Cleanup after Data Transfer Check for files under Ccdraft\datatran\temp directory - If failures occur during the data transfer process, temporary files may be left behind and some of these files can be very large. Delete them. Check Ccdraft\datatran\sysinfo\requests - Delete old request files Cleanup after the External File translator Check for files under Ccdraft\tmp and C:\tmp Cleanup after Plotting Ccdraft\tmp, Ccdraft\plot\requests, Ccdraft\plot\status Page 34

35 ADMINISTRATOR TIPS CCDVER utility has been enhanced. Starting with CCD 421R2 and CCD V5, you can change the CCD environment variables with CCD_ROOT\Bin\ccdver.exe. This will allow you to configure multiple CCD environments on the same system without conflicts. See next page for sample screen. Shows environment variable settings and detailed release level information on dll and executable files. Page 35

36 ADMINISTRATOR TIPS Page 36

37 ADMINISTRATOR TIPS Installing new releases of CCD Rename the current CCD_ROOT directory Install new releases to the previously used CCD_ROOT directory name. - Keeps registry and environment variables the same Copy customized files from previous release If problems arise you can easily go back to the old release by simply renaming the old directory back. All user modifiable installation parameters are now kept in the CCD_ROOT\Profile directory. On Windows, to eliminate zoom/pan screen flickering on large drawings, create a file called dbuf (no file extension) under CCD_ROOT\Profile\. Contents of this file are not important. Page 37

38 ADMINISTRATOR TIPS Plotting If using a NOVELL print server, the copy command in the.bat files should be replaced with: - Print %2 /d:\\hostname\printer-queue-name If drawings migrated from Helix use white for the default color, you can use the provided color_map file to map white or any other color to the desired color. The default is to map all colors to black. - Set COLORMAP parameter to YES in the plotter.opt file Page 38

39 ADMINISTRATOR TIPS CCD Service Packs for V5 and PTFs for V4 Made available as needed to resolve severe problems, usually no more than one between releases. Available only from under Software Downloads TRAINING Since Helix and CCD are so similar, training may not be necessary. The minor differences can be covered in a few hours. Current MF or UNIX CADAM users may need help using CCD s new Windows user interface and to learn productivity features that are only available with the Windows version of CCD. Schedule training to immediately follow the installation. Take a Windows NT or Windows 2000 Administration class. Page 39

40 IMPORTANT WEB SITES CADAM Web Site: with links to: CCD SOFTWARE, WHITE PAPERS, UPDATES (Service Packs & PTFs) AND GENERAL INFORMATION. IBM s SITE: CCD SALES AND GENERAL INFORMATION: Page 40