Allegro® User Guide: Getting Started with Physical Design Product Version 16.6 October 2012 A Configuration This appendix explains how to configure the Allegro layout editors after you install the Cadence software For additional information, see the "What's New" document UNIX-Based Installation Directory Information and Troubleshooting Files That Reference the Installation Directory Checking File References to the Installation Directory Automatically Correcting Installation Directory References Windows-Based Installation Directory Information Licensing Issues Compatibility for Libraries and Designs IBM DFS UNIX-Based Installation Directory Information and Troubleshooting After you install Cadence software, configuration files are modified to reference the installation directories you specified during installation This section describes: The files that reference installation directories include How to verify the files are edited correctly A sample cshrc file A sample profile file How to automatically edit incorrect references Files That Reference the Installation Directory When you install the layout editor using softload, the following files are automatically edited to reference the installation directory you specified during softload: /tools/pcb/bin/cshrc /tools/pcb/bin/profile where is the actual installation directory you specified during softload For example, could be /usr/cds, as in the following example: Checking File References to the Installation Directory If you have problems running the layout editor after installation, verify that the following variables correctly reference the installation directory: In the /tools/pcb/bin/cshrc file set CDS_ROOT = In the /tools/pcb/bin/profile file CDS_ROOT= In the /tools/pcb/text/Allegro/APDHelp file, many variables reference the installation directory If the cshrc, profile, and Allegro/APDHelp files contain incorrect references to the installation directory, you can edit them individually, or run the setup_Allegro/APD script to automatically correct all three files, as described in the following section Automatically Correcting Installation Directory References During installation, the setup_Allegro script saves the original versions of the cshrc, profile, and Allegro/APDHelp files in their respective directories These original files have the extension fcs /tools/pcb/bin/cshrc.fcs /tools/pcb/text/profile.fcs /tools/pcb/text/Allegro/APDHelp.fcs The setup_Allegro/APD script edits these original versions to create the following files: tools/pcb/bin/cshrc tools/pcb/text/profile tools/pcb/text/Allegro/APDHelp Do not edit the original fcs files.The setup_Allegro/APD script does not run correctly if these files have been modified You can, however, edit the resulting cshrc, profile or Allegro/APDHelp files To use setup_Allegro/APD to place the correct install_dir directory references in the cshrc, profile and Allegro/APDHelp files: Change directories to the installation directory: cd The installation directory is the directory immediately above the tools directory Type tools/pcb/bin/setup_Allegro/APD [] where platform is one of the following platform specifications: sun4v hppa ibmrs wint Sun Sparc running Solaris HP Precision Architecture running HP-UX IBM rs6000 running AIX Windows NT (Intel) path Is the path to the specified install directory, install_dir This enables you to run the layout editor from a directory other than the one where the layout editor is installed If not specified, install_dir defaults to the current working directory For example, if your administrator installed the layout editor on AServer:/cds/9504 and you have Network Filesystem (NFS) mounted the installation directory on your workstation as Yourworkstation:/usr/cds the paths in the installation directory references the path /cds/9402 rather than your local path of /usr/cds Portions of the Allegro software not run correctly unless your local path to the software matches the path specified in the configuration files To resolve this, one of the following: Mount the server directories on your workstation just as they are installed on the server mount AServer:/cds/9504 /cds/9504 Create a symbolic link on your workstation that points from the installation directory to your local NFS mount point ln -s /usr/cds /cds/9504 Have your administrator modify the configuration files on the server to match the directory paths on your workstation On the host where the software is installed (AServer), change directories to /cds/9504 and enter the following command: The default working directory for the install_dir becomes /usr/cds Example cshrc File The following is a sample of the tools/pcb/bin/cshrc file configured for an install_dir specified as /usr/cds set CDS_ROOT = /usr/cds set TOOLSDIR = $CDS_ROOT/tools setenv ALGROPATH set path = ( $TOOLSDIR/pcb/bin $TOOLSDIR/bin \ $ALGROPATH \ $path ) Example profile File To use a sample local profile file (~/.profile) At the Korn Shell command line, type CDS_ROOT=/usr/cds TOOLSDIR=$CDS_ROOT/tools ALGROPATH=$TOOLSDIR/pcb/bin PATH=$TOOLSDIR/bin:$ALGROPATH:$PATH; export PATH Note: Do not set the TELENV variable if you use the standard Cadence installation hierarchy Displaying UI Dialog Boxes Correctly If the secondary (child) dialog boxes disappear behind the main UI of the layout editor, you need to modify the window manager to keep child windows on top For HP and AIX The typical window manager default configuration is secondariesOnTop:True For Solaris The typical window manager default configuration is secondariesOnTop:False If you run CDE, add the following to your ~/ Xdefaults file DTwm*secondariesOnTop:True If you want to restrict this behavior to certain programs, add the following to your ~/ Xdefaults file DTwm**secondariesOnTop:True For example: DTwm*Allegro*secondariesOnTop:True Add an entry to the file for each program When finished, restart the window manager Windows-Based Installation Directory Information The Allegro software directory structure for Windows is identical to that on UNIX platforms However, Windows does not install chsrc or profile files Licensing Issues For detailed information on licensing Cadence products for Unix and Windows environments, see the installation manual that accompanies the CD-ROM Compatibility for Libraries and Designs Symbol Library and Padstacks All library symbols created with previous releases of Allegro software are compatible with this release Before loading the generic library, be sure that customized component symbols are not in the same directory in which you load the layout editor Loading this generic the layout editor library overwrites the symbol library The CAE libraries will not be affected Before using any the layout editor library symbols, carefully review them to ensure that they meet your physical design criteria IBM DFS Distributed File System (DFS) is an IBM networking protocol Before Release 10.0, databases could become corrupted if the volume that contained the database became full during the database save This corruption was due to a deficiency in DFS, not the layout editor Starting in Release 10.0, the editor detects that a volume is DFS and takes appropriate action to ensure the database is written correctly Unfortunately, this means that writing databases across the network takes about twice as long as in pre-10.0 versions because the editor verifies the data as it is written to disk Database reads are not affected You can disable this DFS safety feature by setting the afs_nosync environment variable With this variable set, databases save as fast as in previous releases, but the file write safety check is not performed By default, this additional checking takes place automatically as long as the system uses the standard "/dfs" naming convention Return to top of page For support, see Cadence Online Support service Copyright © 2012, Cadence Design Systems, Inc All rights reserved ... top For HP and AIX The typical window manager default configuration is secondariesOnTop:True For Solaris The typical window manager default configuration is secondariesOnTop:False If you run CDE,... directory to your local NFS mount point ln -s /usr/cds /cds/9504 Have your administrator modify the configuration files on the server to match the directory paths on your workstation On the host where... software not run correctly unless your local path to the software matches the path specified in the configuration files To resolve this, one of the following: Mount the server directories on your