CADAM Drafting FAQs
General CADAM Drafting Questions
releases are currently supported?
Will CCD run on Windows 10?
Yes. CADAM Drafting V5-6 R2016 (and above) has been certified on Windows 10. See the V5 System Requirements document for more information.
What about the latest 64-bit versions of Windows and associated hardware?
The currently supported versions of CADAM Drafting V5 have been tested and certified on all 64-bit editions of Windows and on Intel 64-bit processors. No additional CADAM Drafting software is required.
Is it okay to access and modify the same database with different versions of CCD?
CCD has always been upward compatible. That is, a model filed in a given release can always be called up by a later release. On the other hand, CCD has never supported backward compatibility or modifying a model on a given release after it had previously been filed on a newer release. CCD has not always enforced this non-support of backward compatibility, however. Therefore, with some releases, it was possible to modify a model on one release and still call it on an earlier release, as long as function unique to the newer release was avoided. This practice is undertaken at the user's own risk and is neither recommended nor supported by Dassault Systemes.
Occasionally a new release of CCD includes enhancements that require fundamental structural changes to the model. When this is necessary, CCD will enforce the non-support of backward compatibility. The latest release to do this is 424. Therefore, if a model is filed in 424, it will not be possible to open the model with any release of CCD that is older than 424. The message "Illegal Model" will be displayed if the user attempts to open a 424 model with a release that is older than 424.
Is it okay to access and modify the same database with CCD V4 and CCD V5? Can both releases coexist in the same network?
We recognize that a customer's migration from CCD V4 to CCD V5 might be gradual, so we do support interoperability on a limited basis. The main requirement is that the customer uses versions of CCD V4 and CCD V5 that are "current" with each other.
I can open a CCD model from CATIA V5, but when I do a "Save As", I don't see the file type for CCD (.cdd). What system setting am I missing?
Add the environment variable DRW_CCDTOV5 and set it to YES.
When I transfer models between CCD and CATIA V5, the appearance of the characters in the drawing text changes. Is there a font I can select on either side that will allow text to have the same appearance in both CATIA V5 and CCD?
Yes. The CATIA V5 SSS4 font is meant to be compatible with the CCD font. If you are using CCD and CATIA on AIX, simply use the SSS4 font on CATIA V5 and your text should appear identical. If you are using CCD and CATIA V5 on Windows, you will want to download and use the CATIA V5 SSS4 equivalent font for CCD. You can download a copy of this font from our V5 Drafting Download page. The readme file that is included in the download package will have additional information on using this font.
What compilers have been certified for developing IUE applications?
For Fortran, we have certified both Absoft ProFortran and Intel Fortran. For C and C++ development, we have certified Microsoft Visual C++ Version 6.0 (and above). Note that these are the compilers that we have certified. Certification means that we use these compilers here for our testing and can offer a higher level of support than with any other compiler. Most other Windows compilers will probably work. However, for problem reports or support, we can only address the problem or question using one of these certified compilers.
The variable geometry symbols in the symbol table that I transferred from Mainframe CADAM to CCD, come across as regular symbols. What needs to be done for these symbols to maintain their attributes?
Before you transfer the table (in UNIX using cadtran) with the variable geometry symbols, you need to include a special file in the $CCD_ROOT directory that tells the system that you have some variable geometry symbols. The file is named vargeo (no extension) and is located in $CCD_ROOT/DATATRAN. This file contains the Host symbol table number(s) that contain Variable Geometry symbols. Datatran will create the symbol table that contains Variable Geometry symbols in the $CCD_ROOT/DRAWINGS/system/symbol directory. Once this table is transferred using the UNIX cadtran utility (not available on NT), it can be copied to CCD on NT, using the CCD NT symbol table convention, of course.
I would like to grant everyone access to the drawings database in my group. Will I cause any problems if I set the file permissions to 777? I'm running CCD on AIX 5.3.
YES, you will cause problems by doing this. On UNIX (AIX and HP-UX), CCD uses the owner execute bit as a plot-data flag. Setting the permissions to 777 will turn this flag on for all the drawings, confusing CCD as to whether the file contains plot-data or not. All the models will have the P flag indicating that the model contains plot-data, which some may not. The correct file permission to grant access to everyone is 666 NOT 777.
When I start CCD on AIX it will not run and I get the message: "Unable to initialize data management, Unable to initialize proper environment." What could be wrong?
The reason you get this message is because CCD cannot find the DRAWINGS directory. Make sure that you can cd to $CCD_ROOT/DRAWINGS. If you have replaced the directory DRAWINGS with a symbolic link, check to make sure the link is still valid.
My CCD clients on Windows access the CCD database on AIX. Is there a way to prevent these users from filing local?
Yes. There is an option in CADPROF under "Drawing Management Parameters" called "Restrict Local Filing". If it is set to YES, the user can only file to the remote system selected. The "Save" and "Save As", local file options are permanently disabled, until you change the CADPROF setting back to NO. This only works with ICF, not PCNFS.
Is it possible to run different releases of CCD on the same PC?
Yes. Just make sure you install the new release/update to a different directory. Then use the Ccdraft\Bin\ccdver.exe utility to switch between releases. Note however that some combinations may not work. For example, if you use 424 and you activate the new Macro Toolbar, you will no longer be able to run previous releases of CCD on the same machine because previous releases will not know how to handle this new toolbar setting.
We still have Mainframe CADAM and plan to keep it for a few more years. Can CCD on Windows access the CADAM database?
Yes. The mechanism we use is called Interactive Call File (ICF). It allows the CCD Windows user to open and file the CADAM models, interactively. It even allows you to use the current plotters used by Mainframe CADAM. It works over TCP/IP and the only requirement is that the IBM's TCP/IP product be used. See the CCD Windows Installation Guide for more details.
I have a good TIFF file that I can open with Windows applications, but I cannot import the file into CADAM Drafting. What could be the problem?
Most likely, the problem is due to the way the drawing was scanned. It was probably scanned using true color or grayscale color options. CADAM Drafting only supports two color monochrome images.
I'm trying to run CADEX on Windows. When I open my CADEX drawing, I get a message saying "Invalid group". What does this mean?
The CADEX product was ported to Windows from the UNIX. On the UNIX platform, the "group,user" directory structure is still being used by CCD. Due to the high customer demand to have CADEX on Windows quickly, it was decided to not rewrite CADEX entirely and leave the "group,user" directory requirement in place. CADEX models can reside in any "group,user" on UNIX. On Windows, the CADEX models can reside in any "directory\subdirectory", as long as these directories are under the drawings directory defined in Cadprof's "Drawing Management Parameters". The default is $CCD_ROOT\Drawings. For example, if using the defaults:
I have very old Professional CADAM models archived on tape. The files all start with D_. What is the procedure or translator to read these models into CCD?
Professional CADAM is the predecessor to CCD. The data is binary compatible with CCD. Therefore CCD (on Windows or UNIX) can open the files, even with the older naming convention of D_XXX. Of course, though not required, it is best to rename the files to the new convention used by CCD (XXX.cdd). There is a model update tool (mdlupd) on our Tools Download page that can be used to convert large numbers of models.
Most of the drawings transferred from Helix to CCD plot out blank and only some lines are plotted in grayscale.
This is a typical problem if the drawing was transferred from MICROCADAM, Helix or DXF/DWG, especially if the default color is white. Make sure that the color_map file (also provided with the HelixMigrationPackage) is in your Ccdraft\Plot\ directory. Also, check the Ccdraft\Plot\xxxx.opt file being used with the plotter selected to make sure that the COLORMAP parameter is set to YES. This file can be used to map white to black so that the white geometry will appear on the plot. See the Plotting Installation Guide for more information.
I can see the format names in the plot data screen, but even though the drawing plots, the format does not. What am I missing?
Check to see if your format drawings exist under the directory specified in cadprof's "Drawing Management Parameters". The default directory is $CCD_ROOT\Drawings\System\format.
I have customized my plot scripts for HPGL-2 format, but I cannot get any plots out. The plot status reports no errors/warnings, yet nothing is sent to the printer queue. I send plots to the same plotter using the Windows Printer option in CCD and it works fine. What could be wrong?
By your description, it sounds like your printer queue and plotter are working fine. First check your .bat script to make sure that the copy command is sending the plot file to the desired computer and printer shared name. This copy command can be run manually from a DOS shell. Simply replace the %2 parameter with a valid HPGL-2 file name. If this works then the problem could be due to spaces in the path or plot script names. The plot scripts cannot have any spaces in the name. For example, if you install CCD into the "Program Files" directory, the space between the word Program and Files, would be enough to cause this problem.
Where does the plot output file go after it is created?
Plot output files are placed in the CCD_ROOT\Tmp directory temporarily. At the end of each plotter's .bat file there is a statement to remove this file once it has been spooled to the appropriate printer. If you want to keep the file, simply comment the delete statement. Take note, however, that plot output files can be rather large, so not deleting plot files can quickly use up a lot of space on your hard drive.
Can we create a TIFF image from a CCD model?
Yes, see the sample scripts in CCD_ROOT\Plot\Samples\Tiff\. The scripts assumed that you are using Ghostscript to produce the TIFF files, athough you could use any other converter. Ghostscript is available free of charge from www.ghostscript.com. While Dassault Systemes does not endorse or support any particular converter, we have verified that TIFF files can be obtained by using the Ghostscript converter and the sample script that we provide.
Is there a way to keep the Windows Printer from scaling the drawing to the size of the paper?
The Windows Printer Driver always scales the drawing to fit the paper size. This driver is provided to give users a way to get quick prints of their drawings. It is not intended to replace the "traditional" CCD plotting drivers as it does not offer the same level of control and customization. Customers will usually want to continue to use the traditional HPGL, HPGL2 or PostScript plot methods for production plots that must adhere to drafting conventions. (Note, however, that even the HPGL2 and PostScript plot methods will scale the plot if it is larger than the available paper.)
DSLS Licensing Questions
For more information and FAQs on DSLS licensing, please see our DSLS Information page.