Licensing and Configuration

Virtuoso Software Licensing and
Configuration User Guide

Product Version 6.1.5
January 2011
© 1990–2011 Cadence Design Systems, Inc. All rights reserved.
Printed in the United States of America.

Cadence Design Systems, Inc. (Cadence), 2655 Seely Ave., San Jose, CA 95134, USA.
Open SystemC, Open SystemC Initiative, OSCI, SystemC, and SystemC Initiative are trademarks or
registered trademarks of Open SystemC Initiative, Inc. in the United States and other countries and are
used with permission.
Trademarks: Trademarks and service marks of Cadence Design Systems, Inc. contained in this document
are attributed to Cadence with the appropriate symbol. For queries regarding Cadence’s trademarks,
contact the corporate legal department at the address shown above or call 800.862.4522. All other
trademarks are the property of their respective holders.
Restricted Permission: This publication is protected by copyright law and international treaties and
contains trade secrets and proprietary information owned by Cadence. Unauthorized reproduction or
distribution of this publication, or any portion of it, may result in civil and criminal penalties. Except as
specified in this permission statement, this publication may not be copied, reproduced, modified, published,
uploaded, posted, transmitted, or distributed in any way, without prior written permission from Cadence.
Unless otherwise agreed to by Cadence in writing, this statement grants Cadence customers permission to
print one (1) hard copy of this publication subject to the following conditions:
1. The publication may be used only in accordance with a written agreement between Cadence and its
customer.
2. The publication may not be modified in any way.
3. Any authorized copy of the publication or portion thereof must include all original copyright,
trademark, and other proprietary notices and this permission statement.
4. The information contained in this document cannot be used in the development of like products or
software, whether for internal or external use, and shall not be used for the benefit of any other party,
whether or not for consideration.
Patents: Cadence Products, described in this document, are protected by U.S. Patents 5,790,436;
5,812,431; 5,859,785; 5,949,992; 6,493,849; 6,278,964; 6,300,765; 6,304,097; 6,414,498; 6,560,755;
6,618,837; 6,693,439; 6,826,736; 6,851,097; 6,711,725; 6,832,358; 6,874,133; 6,918,102; 6,954,908;
6,957,400; 7,003,745; 7,003,749.
Disclaimer: Information in this publication is subject to change without notice and does not represent a
commitment on the part of Cadence. Except as may be explicitly set forth in such agreement, Cadence does
not make, and expressly disclaims, any representations or warranties as to the completeness, accuracy or
usefulness of the information contained in this document. Cadence does not warrant that use of such
information will not infringe any third party rights, nor does Cadence assume any liability for damages or
costs of any kind that may result from use of such information.
Restricted Rights: Use, duplication, or disclosure by the Government is subject to restrictions as set forth
in FAR52.227-14 and DFAR252.227-7013 et seq. or its successor
Virtuoso Software Licensing and Configuration User Guide
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Related Documents for Virtuoso Design Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Installation, Environment, and Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Technology Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Virtuoso Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Relative Object Design and Inherited Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Typographic and Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Identifiers Used to Denote Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Configuring the Virtuoso Design Environment . . . . . . . . . . . . . . . . 11

Virtuoso Design Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Product Tiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Virtuoso Design Environment Executables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
32- and 64-Bit Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Setting the CDS_Netlisting_Mode Environment Variable . . . . . . . . . . . . . . . . . . . . . . . . 16
Launching the Virtuoso Product Family Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Types of Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
License Check Out/In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
License Failure in Design Framework II . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
License Activity Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Advanced Features and Token Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Tracking Token Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
lmstat Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
tokenPrintCapabilities() SKILL Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Software Product License Management Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Product Tier Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Hardware and Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Virtuoso Design Environment Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Virtuoso Design Environment Licensing Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
January 2011 3 Product Version 6.1.5

Setting Up the Virtuoso Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Quick Start: Common Desktop Environment
and OpenWindows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Configuration and Startup Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Setting the Installation Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Setting Up a User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Specifying Cadence Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Modifying the .rhosts File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Modifying the .Xdefaults or Equivalent File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Modifying the .cdsinit File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Verifying Your System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Distributing the User Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Configuring Remote Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Library and Tool Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Additional Virtuoso Software Licensing and Configuration

Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
X Window System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Running 64-Bit Versions of Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
TrueColor Visuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Finding Available Visuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Pseudocolor and TrueColor Visuals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Locale Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Preface
The Virtuoso Software Licensing and Configuration User Guide describes how to
configure the Virtuoso® design environment software as well as provides the following
information about the environment:
■ Executables needed to run the software - see “Virtuoso Design Environment
Executables” on page 15 and “Setting the Installation Path” on page 58 for more
information
■ Operating system requirements - see “Hardware and Software Requirements” on
page 48 and “Verifying Your System Configuration” on page 72 for more information
■ Directory hierarchy for storing executables and data files - see “Virtuoso Design
Environment Hierarchy” on page 49 and “Setting the Installation Path” on page 58 for
more information
■ Key licensing characteristics - see “Virtuoso Design Environment Licensing Setup” on
page 51 for more information
The preface describes the following topics:

■ Related Documents for Virtuoso Design Environment on page 5
■ Typographic and Syntax Conventions on page 7
■ Identifiers Used to Denote Data Types on page 8
Related Documents for Virtuoso Design Environment

The following manuals contain additional information about the Virtuoso design environment
and related Cadence products.
Installation, Environment, and Infrastructure

■ For information about Cadence licensing set up and procedures, refer to the Cadence
License Manager.
■ For information about installing Cadence products, refer to the Cadence Installation
Guide.

Preface
■ For information regarding the Virtuoso design environment, refer to the Virtuoso
Design Environment User Guide.
■ For information on database SKILL functions, including data access functions, refer to
the Virtuoso Design Environment SKILL Reference.
■ For information about the library structure, library definitions file, and name mapping for
data shared by multiple Cadence tools, refer to the Cadence Application
Infrastructure User Guide.
■ For information about migrating to the latest Virtuoso release, refer to the IC Migration
Guide.
Technology Information
■ For information on how to create and maintain a technology file and a display resource
file, refer to the Virtuoso Technology Data User Guide.
■ For information on how to access a technology file that uses SKILL functions, refer to the
Virtuoso Technology Data SKILL Reference.
Virtuoso Tools
■ For information on how to perform design tasks with the Virtuoso Layout Suite L layout
editor, refer to the Virtuoso Layout Suite L User Guide
■ For information on design rule driven editing, refer to the Virtuoso Design Rule Driven
Editing User Guide.
■ For information on a collection of general layout tools designed to streamline command
sequences and solve specific issues common to custom mask designers, refer to the
Virtuoso Toolbox User Guide.
■ For information on how to use the Virtuoso Layout Suite wire editing capability, refer to
“Interactive Wire Editing” in the Virtuoso Space-based Router User Guide.
■ For information on how to use the automatic custom digital placer to place your design
components, refer to the Virtuoso Custom Digital Placer User Guide.
■ For information on creating parameterized cells using the graphical user interface (GUI)
or low-level SKILL functions, refer to the Virtuoso Parameterized Cell Reference.
■ For information on Quick Cells, refer to the Virtuoso Quick Cells User Guide.
■ For information on component description format (CDF), refer to the Component
Description Format User Guide.

Preface
■ For information on how to route a design, refer to the Virtuoso Chip Assembly Router
Guide and the Virtuoso Space-based Router User Guide.
■ For information on how to stream mask data, refer to the Design Data Translator’s
Reference.
■ For information on custom layout SKILL functions, refer to the Virtuoso Layout Suite
SKILL Reference.
Relative Object Design and Inherited Connections

■ For information on using relative object design (ROD) functions, refer to the Virtuoso
Relative Object Design User Guide.
■ For information on connectivity and naming conventions for inherited connections, and
how to add and edit net expressions in a schematic or symbol cellview, refer to Virtuoso
Schematic Editor L User Guide.
Typographic and Syntax Conventions

The following typographic and syntax conventions are used in this manual.
text Indicates text you must type exactly as it is presented.
z_argument Indicates text that you must replace with an appropriate

argument. The prefix (in this case, z_) indicates the data type
the argument can accept. Do not type the data type or
underscore.
[ ] Denotes an optional argument. When used with vertical bars,

they enclose a list of choices from which you can choose one.
{ } Used with vertical bars, they denote a list of choices from which
you must choose one.
| Separates a choice of options.
… Indicates that you can repeat the previous argument.
=> Precedes the values returned by a Cadence® SKILL language

function.

Preface
/ Separates the possible values that can be returned by a

Cadence SKILL language function.
text Indicates names of manuals, menu commands, form buttons,

and form fields.
Identifiers Used to Denote Data Types

The Cadence SKILL language supports several data types to identify the type of value you
can assign to an argument.
Data types are identified by a single letter followed by an underscore. For example, t is the
data type in t_viewNames. Data types and the underscore symbol are used as identifiers
only and should not be typed.
Prefix Internal Name Data Type

a array array
b ddUserType Boolean
C opfcontext OPF context
d dbobject Cadence database object (CDBA)
e envobj environment
f flonum floating-point number
F opffile OPF file ID
g general any data type
G gdmSpecIlUserType gdm spec
h hdbobject hierarchical database configuration object
l list linked list
m nmpIlUserType nmpIl user type
M cdsEvalObject -
n number integer or floating-point number
o userType user-defined type (other)
p port I/O port

Preface
Prefix Internal Name Data Type

q gdmspecListIlUserType gdm spec list
r defstruct defstruct
R rodObj relative object design (ROD) object
s symbol symbol
S stringSymbol symbol or character string
t string character string (text)
u function function object, either the name of a function (symbol) or
a lambda function body (list)
U funobj function object
v hdbpath -
w wtype window type
x integer integer number
y binary binary function
& pointer pointer type
For more information about the SKILL language, refer to the Cadence SKILL Language
User Guide.

Preface

Configuring the Virtuoso Design

Environment
Important
License Update Required for IC.6.1.5
You will need to update all related licenses before using IC6.1.5.
Note: Prior to this release, IC6.1.0 licenses were used. These licenses will continue to
work with IC6.1.4 and earlier.
For more information, contact your local Cadence representative.
The following topics are discussed in this chapter:

■ Virtuoso Design Environment on page 12
■ Virtuoso Design Environment Executables on page 15
■ Launching the Virtuoso Product Family Applications on page 17
■ Advanced Features and Token Licenses on page 27
■ Tracking Token Licenses on page 31
■ Product Tier Features on page 45
■ Hardware and Software Requirements on page 48
■ Virtuoso Design Environment Hierarchy on page 49
■ Virtuoso Design Environment Licensing Setup on page 51
Use the Cadence Installation Guide and Cadence License Manager to install the
Virtuoso® design environment software and configure the licenses.

Configuring the Virtuoso Design Environment
Virtuoso Design Environment

The Virtuoso platform provides a seamless transition from one Virtuoso design environment
to another as a result of the updated common user interface (UI) and automated license
checkout process.
This platform provides a unified front-to-back design environment. The front-end design
environment consists of the Virtuoso schematic editor® (VSE) and Virtuoso analog design
environment® (ADE) product families. The back-end consists of the Virtuoso layout suite®
(VLS) product family.
Each of the product families contains applications in a tiered packaging structure, and
conform to common and consistent licensing behavior and operation.
Overview
Design Environment: Virtuoso Design Environment
Product Family: VSE ADE VLS
Product Family Tier: L XL L XL GXL L XL GXL
Design Process Location: Front-End Back-End
Product Tiers
The L product tier offers basic design creation and implementation capabilities.
Product Name License Feature Name License Type

Virtuoso Layout Suite L Virtuoso_Layout_Suite_L User, host, and
display (UHD)
Virtuoso Schematic Editor L Virtuoso_Schematic_Editor_L UHD
Virtuoso ADE L Analog_Design_Environment_L UHD

The XL product tier contains IC design products that introduce new technologies and
advancements in design automation. The XL tier offers tightened linkage between design and
implementation phases in the areas of creation, analysis, implementation, and repair.

Virtuoso Layout Suite XL Virtuoso_Layout_Suite_XL UHD
Virtuoso Schematic Editor XL Virtuoso_Schematic_Editor_XL UHD
Virtuoso ADE XL Analog_Design_Environment_XL UHD
The GXL product tier incorporates advanced technology specifically needed to solve the
difficult design challenges at 90 nm and below. The GXL tier provides advanced finishing
tools suited for tackling the most difficult design problems and offers the greatest opportunity
for productivity, yield, and time-to-market improvements.

Virtuoso Layout Suite GXL Virtuoso_Layout_Suite_GXL Multi-feature,
Job Locked (J)
12 tokens.
Note: A token
is one copy of a
multi-feature
license.
Virtuoso ADE GXL Analog_Design_Environment_GXL Multi-feature,
Job Locked (J)
12 tokens.
For information on the number of tokens required for the GXL product tier, see GXL
Multi-Feature License Tokens on page 27.
The IC 6.1.x features require a 95320 product license, but also works with a 95321 product
licence, which can be considered a “super-set” of 95320.
Note: For information on the specific features in each of the product tiers, see Product Tier
Features on page 45.
Only one base license per product family tier is checked out at a time. As a result:

■ The XL tier does not require an L tier license and the GXL tier does not require the XL
tier license (features in the GXL tier can be launched in the XL tier).
■ A higher checked out license allows you to run lower tier applications. For example, you
can run L and XL in the same session with only an XL license checked out.

Virtuoso Design Environment Executables

From the IC 6.1.4 release, all Virtuoso software executables have been integrated into one
executable called virtuoso.
Note: From IC6.1.4, the icde, icds, icfb, and msfb executables will no longer work
through symlinks. The use of layout and layoutPlus is also being phased out over the
short-to-medium term. In the meantime, they will however still be supported through the use
of symlinks.
32- and 64-Bit Platforms

32- and 64-bit platform variants exist for the virtuoso workbench.

Setting the CDS_Netlisting_Mode Environment Variable

When working in ADE, you need to set the CDS_Netlisting_Mode environment variable to
Analog using one of the following methods:
■ Type the following at the command line prior to launching virtuoso
setenv CDS_Netlisting_Mode=Analog
■ Type the following SKILL in the command interpreter window (CIW)
setShellEnvVar("CDS_Netlisting_Mode=Analog")
cdsSetNetlistMode()
t
cdsGetNetlistMode()
"Analog"

Launching the Virtuoso Product Family Applications

You can start applications in each Virtuoso product family using any of the following methods:
■ File – Open and File – New from the CIW
■ Library Manager
■ Launch menu from the design windows
■ File – Open and File – New from the design windows
■ Hierarchy Editor
■ Navigator Assistant
■ History
■ Bookmarks
Note: The Task Assistant pane can be used to start advanced application features (see
“Task Assistant Interactive Commands” on page 18 for more information).
Types of Licenses
The L and XL product tiers have user, host and display (UHD) licenses. This is the same type
of license used prior to the IC 6.1 release.
The GXL tier uses job locked (J) licenses which are not shared. This is a new model for the
IC 6.1 release. Use tokens to start applications at the GXL tier. For information on the number
of tokens required for the GXL tier, see GXL Multi-Feature License Tokens on page 27.
License Check Out/In
Interactive Commands
In the L product tier, the license is checked out when a layout or schematic design is opened
for editing, or by choosing File – Make Editable in the application window.
If the layout or schematic design is opened in read-only mode or changed to read-only mode
by choosing File – Make Read Only, the license is not checked out.
Note: ADE L read-only requires a license.

The license is checked in when the last application window is closed or the mode is changed
from edit to read. When data is opened in read mode, and any edit or save operation is
performed, a license is checked out corresponding to the type of data being saved.
In the XL and GXL product tiers, the license is checked out when the layout design is opened
in either edit or read-only modes, and checked in when the last application window is closed.
Note: GXL licenses will also be checked back in when an action, such as optimization, has
been completed.
Task Assistant Interactive Commands
When the Task Assistant pane is used from the XL and GXL product tiers to launch a
feature, the following token license activities occur:
■ A token license is checked out during the execution of a command from a selected
feature menu or toolbar.
■ A token license is checked in when a selected feature is deselected from the Task
Assistant pane only if the license is still checked out.
■ A token license is checked in automatically after completion of a command for some
features (the Analog Auto Placer is one example of automatic check in).
■ A token license is not checked out when a feature is selected in the Task Assistant
pane. Selecting a feature in the Task Assistant pane turns on the menu and toolbar of
that feature only.
Note: The Context and Window – Toolbar menus do not affect the state of a token license.
These menus are navigation aids and are not linked to license activity.
For all of the Virtuoso GXL features listed in Table 1-2 on page 28 and Table 1-3 on page 29,
with the exception of the Custom Digital Placer and Floorplanning, licenses are checked in
after completion of the command. For the Custom Digital Placer and Floorplanning, the
license is checked in only when the task is turned off in the Task Assistant pane or the GXL
session is exited.
Important
There is now an enforced restriction on license check in that prevents license check
in when an application or GXL capability is still using the license.

Non-Interactive Commands
Non-interactive, lengthy, and batch commands check out the license at the beginning of the
command and automatically check in the license upon completion of the command activity.
This model applies to automatic placers, routers, and Virtuoso Layout Migrate.
License Failure in Design Framework II

In the IC 6.1.2+ release, the product 111 license must be checked out at workbench start and
while performing the following activities:
■ Starting Virtuoso applications in either graph or non-graph mode
■ Launching routines that interact with design framework II® (DFII) data (for example, CDF,
Pcells, and param)
■ Accessing Cadence data using itkDb
■ Using oa2cdb and cdb2oa data translators
■ Launching open simulation system (OSS) netlisters
In the event of a DFII license failure at startup, the Virtuoso application exits and an error
message is displayed in the CIW and a log file.
License Activity Summary

The following Licensing Check Out/In Model table on page -19 shows the licensing check
out/in activity during a single session.
Table 1-1 Licensing Check Out/In Model
Close
Open for Open for Application
Application License
Read Edit Windows1
ADE L 2 Analog_Design_Environment_L check out check out check in

ADE XL Analog_Design_Environment_XL check out check out check in
ADE GXL Analog_Design_Environment_GXL check out check out check in

Close
Open for Open for Application
Application License
Read Edit Windows1
VLS L Virtuoso_Layout_Suite_L no check out check out check in

VLS XL Virtuoso_Layout_Suite_XL check out4 check out check in
and
Virtuoso_Schematic_Editor_XL3
VLS GXL Virtuoso_Layout_Suite_GXL check out check out check in
VSE L Virtuoso_Schematic_Editor_L no check out check out check in

VSE XL Virtuoso_Schematic_Editor_XL check out check out check in
1 Close all windows running this application except the CIW.
2 VirtuosoVisualization & Analysis L and XL (called ViVA and formerly called Wavescan)
shares the ADE L and XL license.
3 If
a VSE XL license is not available, the VSE L application is used, but no license is
checked out.
4PCell Interoperability and Performance: The actions of saving, editing, or opening a
database using Core Cached Pcells capability, from either the GUI or SKILL and from any
application, causes a VLS L license to be checked out.
Process Rule Editor: The use of the Process Rule Editor, or associated SKILL function, to
save, edit, or open a techDB or design object requires a VLS XL or VSE XL license to be
checked out.
Virtuoso Visualization and Analysis XL and ADE Licenses

■ Virtuoso Visualization and Analysis tool runs only in the XL mode, which supports all the
features of Virtuoso Visualization and Analysis L and XL from previous releases.
■ If Virtuoso Visualization and Analysis XL is opened from within ADE L, XL, or GXL, it
shares the same license tokens as that of ADE L, XL, or GXL.
■ If Virtuoso Visualization and Analysis XL is opened in stand-alone mode or from
Virtuoso, it can either check out the Virtuoso Visualization and Analysis XL license or a
tier of ADE license, depending upon the preferences you set in the
VIVALicenseCheckoutOrder .cdsenv variable. By default, this variable is set to
ViVA, ADE and the tool performs the following license check out tasks:

❑ Checks out the Virtuoso Visualization and Analysis XL license.

❑ If Virtuoso Visualization and Analysis XL license check out in the previous step fails,
the tool gives you a choice to check out a tier of ADE license or two ADE GXL tokens
based on the ordering set in the ADELicenseCheckoutOrder .cdsenv variable.
The ADELicenseCheckoutOrder .cdsenv variable controls the check out
ordering of ADE license tiers.
You can also set the VIVALicenseCheckoutOrder variable to ADE, ViVA. In this
case, the tool performs the following license check out tasks:
❑ Checks out a tier of ADE license or two tokens of ADE GXL based on the ordering
set in the ADELicenseCheckoutOrder .cdsenv variable.
❑ If the license check out in the previous step fails, the tool gives you a choice to check
out the Virtuoso Visualization and Analysis XL license.
■ When Virtuoso Visualization and Analysis XL is opened in stand-alone mode or from
Virtuoso, the tool releases license when all the Virtuoso Visualization and Analysis XL
windows are closed.
■ When Virtuoso Visualization and Analysis XL is opened from within ADE XL and you
close the ADE window, the Virtuoso Visualization and Analysis XL process holds the
ADE license and continues to operate until all main windows are closed.
VLS GXL Space-based Interactive Router and Token Activity
VLS GXL Space-based Interactive Router and Token Activitity tokens check out dynamically
when analysis and optimization engines (such as EM Check), or a specialized interactive
routing command (such as EM Fix), are executed. The tokens are checked in when the
engine execution or command is complete.
The Space-based router is accessed from either VLS XL or GXL. In both cases, four tokens
(in addition to the VLS XL license or base VLS GXL cockpit tokens) are checked out during
the process that is running.

License Availability
Use Next License Dialog Box
In the event of a license for a requested application not being available, the Use Next License
dialog box will be displayed. From here, you are given the opprtunity to check out a higher tier
license, subject to availability. Four options are offered: Yes, No, Always, or Never.
■ If the Yes option is selected, a higher tier license is checked out, if available, for the
current session. If a higher tier license is unavailable, the Use Next License dialog will
only be displayed once.
■ If you select No, the operation completes with no license check out in the current or future
Virtuoso sessions for the requested application.
■ If the Always option is selected, a message is displayed describing how to reset the
license by removing or changing the value of the respective environment variable in the
.cdsenv file located in your home directory.
Note: A similar message is displayed when the Never option is selected.
The Always and Never options are stored in the following environment variables in
~/.cdsenv as soon as they are set.
For example,
license VLSL_UseNextLicense string "prompt"/"always"/"never"
license VLSXL_UseNextLicense string "prompt"/"always"/"never"
license VSEL_UseNextLicense string "prompt"/"always"/"never"
license ADEL_UseNextLicense string "prompt"/"always"/"never"
license ADEXL_UseNextLicense string "prompt"/"always"/"never"
If a license is not available warning messages will be displayed in the CIW.

Note: If Virtuoso is currently being run in -nograph mode, the license order mechanism
will not display the Use Next License dialog if a specific license is not available, and the
value of *_UseNextLicense is set to "prompt". Instead, a warning message will be
added to the log file.
Important
For more information see Specifying License Checkout Behavior in .cdsenv in the
Virtuoso Design Environment User Guide.

Setting License Check Environment Variables
There are a range of license check environment variables that can be used for detailed
license checkout reporting. For example, you can set an environment variable to report
whether a license check is taking too long or if a particular license or token has been checked
out.
These license environment variables, as shown in an example for each below, can be set in
one of two ways:
1. Using setenv before running Virtuoso.
Note: These environment variables can also be set when using Layout and LayoutPlus.
2. Using the SKILL function setShellEnvVar() during a Virtuoso session.
■ CDS_LIC_PRINT_FILTER
This environment variable can contain a string with the names of license features and
token capabilities, for detailed license checkout reporting using the format:
“Feature1:Token1,Token2,...:TokenN,Feature2, ...,FeatureM”
If the name of a particular feature or token is included in the CDS_LIC_PRINT_FILTER
environment variable, a warning message will be output to the CIW when that
feature/token is checked out.
If CDS_LIC_PRINT_FILTER is not defined, the license feature “111” will be the default.
Note: You can obtain a list of all registered token capabilities by examining the content
of the Token License Usage Form. For licenses, and their availability, see the
.../share/license/products.dfII file in your installation.
For example:
setenv CDS_LIC_PRINT_FILTER “111, Virtuoso_Layout_Suite_L,
Virtuoso_Layout_Suite_GXL:VLS-GXL”:virtuoso
setShellEnvVar(“CDS_LIC_PRINT_FILTER=111, Virtuoso_Layout_Suite_L,
Virtuoso_Layout_Suite_GXL:VLS-GXL:virtuoso”)

You can also use a number of aliases with the CDS_LIC_PRINT_FILTER environment
variable to cover multiple feature settings:
Environment Variable
License Tool Interprets CDS_LIC_PRINT_FILTER for
Value Alias
all All tiered licenses, including all token capabilities and
license “111”.
vlsall All licenses related to the Virtuoso Layout Suite family.
adeall All licenses related to the Analog Design Environment
family.
vseall All licenses related to the Virtuoso Schematic Editor family.
When setting the CDS_LIC_PRINT_FILTER environment variable value, you can also
combine application names and aliases, for example:
setenv CDS_LIC_PRINT_FILTER "Virtuoso_Layout_Suite_L,vseall,adeall":virtuoso
setenv CDS_LIC_PRINT_FILTER "vlsall,vseall,adeall,111":virtuoso
Note:
❑ If you set “Virtuoso_Layout_Suite_GXL:all”, the license tool will interpret
CDS_LIC_PRINT_FILTER as containing all token capabilities for the token license
“Virtuoso_Layout_Suite_GXL”.
❑ If you set “Analog_Design_Environment_GXL:all”, the license tool will
interpret CDS_LIC_PRINT_FILTER as containing all token capabilities for the token
license “Analog_Design_Environment_GXL”.
■ CDS_LIC_PRINT_TIME
This boolean environment variable can be set to output the time (in milliseconds) to the
CIW that is taken during a license check-out process. The values that can be set for
CDS_LIC_PRINT_TIME are 0 (do not print time) and 1 (print time), the default being 1.
For example:
setenv CDS_LIC_PRINT_TIME 0
or
setShellEnvVar(“CDS_LIC_PRINT_TIME=0”)
■ CDS_LIC_PRINT_ALWAYS
This boolean environment variable can be set to output messages for a particular license
feature each time that license feature is checked out. The values that can be set for

CDS_LIC_PRINT_ALWAYS are 0 (do not print each time) and 1 (print each time), the
default being 0.
Note: If CDS_LIC_PRINT_ALWAYS is not defined, or its value is 0, the message will be
output only one time to the CIW.
For example:
setenv CDS_LIC_PRINT_ALWAYS 1
or
setShellEnvVar(“CDS_LIC_PRINT_ALWAYS=1”)
■ CDS_LIC_TIMER_INTERVAL
This environment variable is used to set the number of seconds required to pass, for a
license search, before a timeout occurs. If the actual license check time exceeds the
value of CDS_LIC_TIMER_INTERVAL, a message will be output to the CIW informing
you that the check time has been exceeded. The default value is 15 seconds.
For example:
setenv CDS_LIC_TIMER_INTERVAL 10
or
setShellEnvVar(“CDS_LIC_TIMER_INTERVAL=10”)
■ CDS_LIC_PRINT_TYPE
This environment variable can be set to output all license call related messages
(information and warning) to the CIW, or only the warning messages. If the value of
CDS_LIC_PRINT_TYPE is set to “warn”, then only warning messages will be output to
the CIW. If set to “all”, both information and warning messages will be output. The
default is “warn”.
For example:
setenv CDS_LIC_PRINT_TYPE “all”
or
setShellEnvVar(“CDS_LIC_PRINT_TYPE=all”)
■ CDS_LIC_TIMEOUT_DIALOG
This environment variable is used to display the timeout dialog when the license
checkout time of a license feature, as defined by CDS_LIC_PRINT_FILTER, exceeds
the timer interval specified by CDS_LIC_TIMER_INTERVAL. The value of
CDS_LIC_TIMEOUT_DIALOG can be either “1” (which will display the dialog) or “0”
(which will not display the dialog). The default value is “0”.
Note: For the initial 111 license, the timeout dialog will be displayed even when there is
no license 111 in CDS_LIC_PRINT_FILTER and irrespective of
CDS_LIC_TIMEOUT_DIALOG being set.

Choosing Default Applications
Opening a design in a specific product family tier and keeping that setting as the default upon
startup is performed by using any of the following methods to open a design:
■ File – Open and File – New from the CIW
■ Library Manager
■ File – Open and File – New from the design windows
■ File – Set Default Application from the design windows
To set the default application using any of the methods above,

1. Choose the desired application in the Application field.
2. Select the Always use this application for this type of file option.
This field is mapped to the environment variables
❑ maskLayoutDefaultApp
❑ schematicDefaultApp
❑ schematicSymbolDefaultApp
For information on these environment variables, see Virtuoso Layout Suite L User
Guide: Environment Variables.
Note: In the event that the default application is not a base application (L tier), only the
license of the chosen application will be checked out, not the base application. Only one of
the base licenses in a given family is ever checked out at any one time.

Advanced Features and Token Licenses

The advanced technology features in the XL and GXL tiers are accessed by tokens or
multi-feature licenses which are defined by a multi-feature license model. The advanced
features can be used in both the XL and GXL tiers.
Note: See also Tracking Token Licenses.
A token is one copy of a multi-feature license. Each feature within a GXL application has a
required number of tokens. GXL applications use Job Locked (J) licenses which are not
shared between processes.
For information about the specific product family tiers, see the Documentation Launch
Menu and choose the title you need.
GXL Multi-Feature License Tokens
Table 1-2 on page 28 and Table 1-3 on page 29 lists the tokens needed for the ADE and VLS
GXL multi-feature licenses.
Note: VSE does not have a GXL product tier.
There are 12 tokens in each GXL multi-feature license. The 12 tokens can be used to access
any of the features in either of these multi-feature licenses:
■ Analog_Design_Environment_GXL
■ Virtuoso_Layout_Suite_GXL
Important
If all of your license tokens are currently in use, or you have insufficient tokens to
access a particular feature, additional tokens can be obtained by contacting your
local Cadence representative.

Table 1-2 Tokens per Feature (ADE GXL)
Tokens
Feature Version
Required
Analog_Design_Environment_GXL 2 6.1.4
Open Simulation System 2 6.1.4
DCM 1 6.1.4
MTS 2 6.1.4
MismatchAnalysis 1 6.1.4
PAD 1 6.1.4
Optimizer 6 6.1.4
YieldOptimizer 10 6.1.4
SensitivityAnalysis 2 6.1.4
YieldAnalysis 4 6.1.4
Note: All GXL applications use Job Locked (J) licenses which are not shared between
processes.

Table 1-3 Tokens per Feature (VLS GXL)
Feature Tokens Required Version
VLS_GXL 4 6.1.4
Analog_Auto_Placer 8 6.1.4
Cell_Planner 4 6.1.4
Digital_Auto_Placer 2 6.1.4
Floorplanning 4 6.1.4
Layout_CE 4 6.1.4
Module_Generator 2 6.1.4
Layout_Migrate 20 6.1.4
Layout_Yield_Optimize 8 6.1.4
VCAR 4 6.1.4
Note: If VCAR is invoked standalone it will
consume 8 GXL tokens.
Note: All GXL applications use Job Locked (J) licenses which are not shared between
processes.
Note: All of the features listed in Table 1-3 on page 29 can be started in the XL window and
do not need to be started with the GXL base capability running, with the exception of
Layout_CE which requires VLS GXL base capability (4 tokens).

Table 1-4 Tokens Per Feature: VSR for Automatic Routing (Space_based_Router)
Number of Nets Number of Processors Number of Tokens

1 N/A VLS XL license required
2 to 9999 1 12
2 to 9999 2 to 4 24 (+12)
2 to 9999 5 to 8 36 (+12)
2 to 9999 9 to 12 48 (+12)
2 to 9999 each additional 4 processors (over 4 + 12 tokens
processors)
10,000 to 249,999 1 24
10,000 to 249,999 2 to 4 48 (+24)
10,000 to 249,999 5 to 8 72 (+24)
10,000 to 249,999 9 to 12 96 (+24)
10,000 to 249,999 each additional 4 processors (over 4 + 24 tokens
processors)
>= 250,000 1 48
>= 250,000 2 to 4 72 (+24)
>= 250,000 5 to 8 96 (+24)
>= 250,000 9 to 12 120 (+24)
>= 250,000 each additional 4 processors (over 4 + 24 tokens
processors)

Tracking Token Licenses

The following methods can be used to track token license activity.
■ lmstat Command on page 31
■ tokenPrintCapabilities() SKILL Function on page 33
■ Software Product License Management Form on page 36
lmstat Command
The lmstat command can be used to track token license activity from the command line. It
reports activity for one license server only. Use the following arguments with the lmstat
command.
Option Description
-a Display everything
-c license_file Use "license_file" as license file
-f [feature_name] List usage info about specified (or all) features
-i [feature_name] List info about specified (or all) feature(s) from the increment
line in the license file
-S [DAEMON] Display all users of DAEMON licenses
-s [server_name] Display status of all license files on server node(s)
-t timeout_value Set connection timeout to "timeout_value"
-v Display FLEXlm version, revision, and patch
-old Allow communications with an old server that uses
communications version 1.2 or earlier
-help Print this message

Example
1. Type the following in a shell window
lmstat -c <license.file> -f "<feature.name>"
For example,
lmstat -c sj234flex4 -f "Virtuoso_Layout_Suite_GXL"
2. Review the output.

In this example, designer1 on host lne2 has the VLS_GXL license checked out (4
tokens), and designer2 on host lne3 has the Layout_CE license checked out (4
tokens). Both are using version 6.1.
Users of Virtuoso_Layout_Suite_GXL:
(Total of 400 licenses issued; Total of 16 licenses in use)
“Virtuoso_Layout_Suite_GXL” v6.100, vendor: cdslmd floating license
designer1 lne2 VLS_GXL (v6.100) (server 54),start Tue 4/17 2:40, 4 licenses
designer2 lne3 Layout_CE (v6.100) (server1520), start Tue 4/17 8:35, 4 licenses
For more information about the lmstat command, see the Cadence License
Manager.

tokenPrintCapabilities() SKILL Function

tokenPrintCapabilities(
[g_general]
)
=> t | nil
Description
Outputs details of registered token licenses, including the number of tokens required for each
capability and whether or not it is in use.
The tokenPrintCapabilities function can be called with an optional input parameter or

without any parameters. If the input parameter is a string, tokenPrintCapabilities()
considers it as the name of a file and will print token usage information to it. For example:
tokenPrintCapabilities("file.txt")
If the input parameter is not a string, the tokenPrintCapabilities function prints token
usage report in CIW.
Note: The Total fields show how many tokens are needed and how many are checked out.

Output Field Descriptions
Number of tokens
Name of token license
required for each
Name of token capabilities
capabilitity
registered for this license
Total number of tokens

Total tokens License version
left available for use
available
Use status of
capability
For more information about the token capabilities, refer to the tables located in the Token
License Usage Form section of this chapter.
Note: tokenPrintCapabilities() tracks the token capabilities of regular token licenses
for ADE GXL and Virtuoso Layout Suite GXL. This function does not track the token
capabilities of other UNIX processes, such as the Virtuoso Chip Assembly Router (VCAR).
Use “lmstat Command” on page 31 or the “Software Product License Management Form” on
page 36 to track license activity for these applications.

Example
To use tokenPrintCapabilities(), do the following:

1. In the CIW type
tokenPrintCapabilities()
2. Review the output to determine which token capabilities are registered.

The output shows the regular tokens required for each capability and whether or not it is
in use. It also shows the total number of tokens needed for the capabilities that are
running and how many are checked out.

Software Product License Management Form

You can use the Software Product License Management form to track token license activity.
To open the Software Product License Management form

1. Choose Options in the CIW.
2. Choose License from the menu.
The Software Product License Management form appears.
The form is divided into Checked Out Licenses and Relevant Licenses panes. It also
provides access to the following option forms: “License Use Form” on page 39 and “Token
License Usage Form” on page 41.
Note: Selection of the Users or Token Information options in the Software Product License
Management form will cause these options to be greyed out until the appropriate forms are
displayed (License Use or Token License Usage respectively). This prevents multiple
launches of these forms from occurring from repeated option selection. The options become
active again once the selected form is displayed (this can however take some time depending
upon multiple license server checks).

Checking License Status
There are two ways to check license status:

■ Checked Out Licenses pane.
This pane lists the licenses that are currently checked out, and their count.
■ lbuiGetCheckedOutLicenses SKILL function

Use lbuiGetCheckedOutLicenses() to send license activity information to the
CDS.log file. This information can be used for creating reports to analyze license usage.
lbuiGetCheckedOutLicenses(
)
Returns a list of the licenses which appear in the Checked Out Licenses pane. The list
contains each license feature name and the number of licenses (tokens) checked out.
For example,
lbuiGetCheckedOutLicenses()
("Virtuoso_Schematic_Editor_XL" 1
"Virtuoso_Layout_Suite_GXL" 18)

Checking Relevant Licenses
This pane lists the DFII licenses used by all of the tools incorporated into the workbench.
Note: The list does not include the Assura™ physical verification or Virtuoso® simulator
licenses.
Refreshing License Status
To update the Checked Out Licenses and Relevant Licenses panes, click on the Refresh
button.
This action will update these lists to show the current list of products being run, and their
license count, along with any changes to the available license list that have been made since
the Software Product License Management form was initially accessed.

License Use Form
Choose a license from one of the lists located in the Software Product License Management
form (see “Software Product License Management Form” on page 36 for more information).
Click the Users button to open the License Use form.
The License Use form contains a list which displays usage information (for example, user,
host, display, and number of licenses) for the selected license(s), independent of the license
check out/in status. Information in this form is read from the license servers that are defined
in CDS_LIC_FILE and can display information from more than one license server. If you do
not have any licenses for a selected feature, in any license file, the License Use form will
display total and available licenses as “0”.
Note: Defining license servers in the CDS_LIC_FILE is not required (Cadence software is
able to automatically detect servers).
Notes:
■ Deselect any previously highlighted license(s) in the Software Product License
Management form before choosing a new license for viewing in the License Use form.
■ If you do not have any licenses for features selected in the Software Product License
Management form, the License Use form displayed as blank.
■ Multiple features can be selected and the corresponding license information can
displayed by clicking the Users button.

■ As well as detailing the Host machine information, Display information is also shown.
This information can be useful should you be running the software on, for example, a
VNC session.

Token License Usage Form
Click the Token Information button in the Software Product License Management form (see
“Software Product License Management Form” on page 36 for more information) to open the
Token License Usage form.
This form provides automatically updated token and license information. The following tables
describe all of the ADE and VLS GXL capabilities listed in the form.

Table 1-5 ADE GXL Capabilities
Capability Description
Analog_Design_Environment_GXL ADE GXL product which supports automated
custom IC design capabilities and is accessed
from the Open File form or Launch menu
DCM Characterization and modeling capability which is
accessed from the ADE XL introduction wizard,
Launch menu, or command interpreter window
(CIW)
MTS Multi-technology mode capability which is
accessed from the Choosing Simulators form
MismatchAnalysis View Mismatch Results capability in ADE GXL.
Open Simulation System Open simulation system (OSS) capability which
allows integration of third party netlisters and
simulators into the DFII environment using
schematic editor Integrations
PAD Parasitic Aware Design (Parasitics) capability
which is launched from the CIW or within ADE
XL/GXL
SensitivityAnalysis This feature includes the Sensitivity Analysis run
mode and View Sensitivity Results capability in
ADE GXL.
YieldAnalysis This feature is used for the high yield estimation
run mode.
YieldOptimizer This feature is used for the improved yield run
mode in ADE GXL.
Optimizer Required for optimization flows such as Local Opt,
Global Opt, Feasibility Analysis, and Size Over
Corners.

Table 1-6 VLS GXL Capabilities
Capability Description
Analog_Auto_Placer Analog placement capability which is accessed
from the Task Assistant pane by selecting the
Analog Placer task (activates Analog Placer
toolbar and menu items in Place menu)
Cell_Planner Cell planner capability which is launched from the
Constraints Editor toolbar located at the top of
the Constraint Manager pane
Digital_Auto_Placer Digital placer capability which is launched by
choosing Window – Toolbars – Custom Digital
Placer (can also be accessed from the Task
Assistant pane which updates the Place menu
with a Custom Digital selection)
Floorplanning Floor planning capability which is launched from
the Task Assistant pane
Layout_CE Layout Chip Editor capability which is launched by
choosing Layout_CE in an Open dialog box or
through the Launch menu
Layout_Migrate Layout migration capability which is launched
from the Optimize menu option in VLS.
Layout_Yield_Optimize Layout optimization capability which is launched
from the Optimize menu option in VLS.
Module_Generator Module generator capability which is launched
from the Constraints Editor toolbar located at
the top of the Constraint Manager pane
Space_based_Router Space Based router capability which is
accessed from the Task Assistant pane by
selecting the Space Based router task
VCAR Chip Assembly router capability which is
accessed from the Task Assistant pane by
selecting the Chip Assembly router task
VLS_GXL Layout GXL is launched from the Launch
menu or from the Open File form

Notes:
■ A license does not need to be pre-selected to view this information because token
license usage is always provided in the GXL product tier.
■ This is the same information as reported by the tokenPrintCapabilities() SKILL
function.
For more information about

■ Output field descriptions, such as Tokens, Version, and In Use, refer to “Output Field
Descriptions” on page 34.
■ Tokens needed for License Virtuoso_Layout_Suite_GXL capabilities, see
Table 1-2 on page 28 and Table 1-3 on page 29.

Product Tier Features

The following table shows the feature details included in each application.
VSE ADE VLS ADE VLS

Feature VSE L ADE L VLS L
XL XL XL GXL GXL
New Common Environment X X X X X X X X
New Icon Style X X X X X X X X
Multi-Tab Support X X X X X X X X
Updated Pulldown Menus X X X X X X X X
Bookmarks & History X X X X X X X
Window Config Support X X X X X X X
World View Assistant X X X X X X X
Search Assistant X X X X X X X
Property Editor Assistant X X X X X X X
Navigator Assistant X X X X X X X
Task Assistant X X X X
Basic Polygon Editing X X X
Q-Cells X X X
Abstract Generation X
DRD Editing X X X
Constraint Browser X X X X X
Design Explorer X X X X X
Single Test-bench X X X
Simple Parametric Analysis X X X
Device Checking X X X
Global Variable Support X X X
Updated Wavescan X X X
New Calculator X X X

VSE ADE VLS ADE VLS

XL XL XL GXL GXL
Simulation Support: Virtuoso X X X
Multi-mode Simulation,
HSPICE
Circuit Optimization X
Behavioral Model Generation X
Parasitic Resimulation X X
Yield Analysis X
Mismatch/Sensitivity X
Analysis
SiP Support X
Native interactive wire editing X X
Point-to-point routing X X
Finish wire X X
Push in interactive wire X X
editing
Advanced DRD rule checks X X
in interactive routing/wire
editing
Advanced rule checks in X X
batch checking
Interactive bus routing X X
Interactive special signal wire X X
editing
A & D Device Placer X* X
Modgens X* X
Cell Planning X* X
Chip Assembly Router X* X
Floorplanning X* X
Custom Digital Placer X* X

VSE ADE VLS ADE VLS

XL XL XL GXL GXL
Spaced-Based Auto Router, X* X
Version 6.1.2
Spaced-Based Interactive X* X
Router, Version 6.1.2
Spaced-Based Chip X* X
Optimizer, Version 6.1.2
Layout Yield Optimize, X*1 X
Version 6.1
Layout Migrate, Version 6.1.2 X*1 X
1 With 5100 license

* Features available in XL but require GXL tokens.
Note: Unless otherwise stated, all products are version 6.1.

Hardware and Software Requirements

For hardware and software requirements needed to run the Virtuoso design environment
software, see Hardware and Software Requirements on Cadence Online Support.
Software Layers
The figure below shows how the Virtuoso design environment software resides on top of
several layers of software (bottom layer is your hardware platform).
User Interface
Cadence Tools Customer Tools
Virtuoso Design Environment
Qt Library
Motif
Xt Library
X Window System
Operating System
Hardware Platform
(Sun, IBM, Linux)
For More Information Refer to

Installation Cadence Installation Guide
Licensing Cadence License Manager
File locking Cadence Application Infrastructure User Guide
Plotting Plotter Configuration User Guide
Design flow Your Cadence applications engineer (AE)

Virtuoso Design Environment Hierarchy

The software uses the following directory hierarchy to store executables and data files.
your_install_dir /
bin.xxx /
install/ softload
tools.xxx /
Link Application directories, plus bin/ dfII/

… various files, bin/virtuoso
cdnshelp/ including: executables
include/ cdsIdent cdsuser/
plot/ cds_plat etc/tools
samples/ cds_root include/
… cdnshelp lib/
local/
samples/
tools/
src/
…
share/
bin/ cdssetup/
… cdsinfo.tag.sample
doc/ setup.loc
doc/ examples/ …
… registry/
license/ data/
etc/ oa/ dfII/
… toolbars/
workspaces/
logs/ icons

The your_install_dir/tools/dfII directory includes the directories listed below.

The files in these directories depend on which Cadence® products are installed.
bin Virtuoso design environment software executables for your platform.

bin.xxx Link to bin directory.
cdsuser Sample home directory environment setup files such as .Xdefaults,
.cdsinit, .cshrc, .mwmrc, .simrc, .xinitrc, and arrowKeys.map.
etc/tools Directories corresponding to particular applications or core pieces of
infrastructure such as layout, schematic, and cdba. Each directory
contains a default .cdsenv file and might also contain other sample files.
include C header files to go with licensed Cadence products.
local CAD group customization files and site-specific configuration files.
Note: Installing new software does not overwrite this directory.
lib Programming libraries.
samples Sample user files. Some of the samples include the following:
.cdsenv Sample environment variable file
local Sample customization files
plot Schematic plotting files
techfile Technology files and libraries
tutorials Tutorials for various products
script Configuration scripts.
src More customization files.

Virtuoso Design Environment Licensing Setup

The key licensing characteristics of the Virtuoso design environment are outlined in the
following table.
Licensing Characteristic Virtuoso Design Environment

Licensing software SoftShare
Licensing DAEMON cdslmd
License file license.HOSTID
Path to DFII your_install_dir/tools/dfII
Path to the license directory your_install_dir/share/license
Variable for license file See the Cadence License Manager
File locking CLS
Note: Licenses from several license servers can be used if there are multiple independent
license servers configured.
Important
All Cadence software requires Cadence licenses. To specify your license file, set the
CDS_LIC_FILE. If a license cannot be found on any of the servers specified in the
CDS_LIC_FILE, the license search will continue to look through the
LM_LICENSE_FILE. If you do not want a license search to continue beyond the
CDS_LIC_FILE, you need to set the CDS_LIC_ONLY environment variable which
will instruct Virtuoso to ignore the LM_LICENSE_FILE.
For more information about license files and variables, see the Cadence Installation Guide
and Cadence License Manager.

The following table answers frequently asked licensing questions:
Question Answer
In interactive mode, when are licenses checked in? Licenses are checked in automatically
when you exit an application.
Do all Cadence products support global TIMEOUT? Yes.
TIMEOUT sets the time after which an
inactive license is reclaimed by the
vendor daemon. You can amend the
default TIMEOUT setting in the
options file to specify how long it is
before a product license times out.
The value entered will be valid as long
as it exceeds the minimum setting
(3600 secs).
Note: TIMEOUTALL, which applies a
timeout to all features is also
supported in DFII products.
e.g.
TIMEOUT featurename seconds
TIMEOUTALL seconds
What happens to my work and any open windows When you execute the next
when products lose their licenses? command, it will re-check out the
license automatically.
Note: You will only notice an issue if
the license you need (the license that
timed out) is no longer available.
After startup, how often does a product check for a The license-checking interval
valid license? depends on the product. In general,
interactive products (for editing) check
at the start of every editing command
and batch-mode products check
every five minutes.
Can I wait for a license? No.

Question Answer
If prolonged batch jobs require multiple licenses, This depends on the application.
are all licenses reserved or checked out up front?


Setting Up the Virtuoso Software
This chapter contains the following startup information:

■ Quick Start: Common Desktop Environment and OpenWindows on page 56
■ Configuration and Startup Procedures on page 58
Each time the application software runs, the application loads variables in this order:
1. Resources in the resource database
The resources are taken directly from the .Xdefaults file only if the res.db file does
not exist. It is created automatically by common desktop environment (CDE) after login
and incorporates your .Xdefaults file at that time.
2. Variables in the app_defaults file
3. Variables set by the application
4. Variables set by the your_install_dir/tools/app_dir/local/.cdsenv file
❑ your_install_dir is the directory that contains the software
❑ app_dir is the directory containing the Cadence® application files
5. Environment variables
6. Program loads all .cdsenv files in the following order if the CDS_LOAD_ENV
environment variable is not set:
❑ your_install_dir/tools/dfII/etc/tools/application/.cdsenv
❑ your_install_dir/tools/dfII/local/.cdsenv
❑ $HOME/.cdsenv
7. Program searches the following locations in order and loads variables from the first
.cdsinit file encountered:
❑ your_install_dir/tools/dfII/local
❑ current working directory: .
❑ your home directory

Individual user settings override the variables set by the application and any group
customization. You can copy the .cdsenv site file to your local directory and customize it or
choose Options – Save Defaults in the Command Interpreter Window (CIW) to save
variable settings to a .cdsenv file (see “Saving New Default Values” in the Virtuoso Design
Environment User Guide for more information).
Quick Start: Common Desktop Environment

and OpenWindows
This section outlines the quick start procedure for the CDE, which works on all platforms, and
OpenWindows (SUN Solaris only) window managers running X-Windows graphics software.
Important
You may need to use a root login to modify files or change permissions.
1. Set up a user account.
Note: You can refer to “Setting Up a User Account” on page 60 for more details.
2. Modify and apply your search path as follows:
If you are running the csh shell:

Modify your search path in your .cshrc as follows:
set path = (. your_install_dir/tools/bin \
your_install_dir/tools/dfII/bin $path)
Then, either log out and back in again or type the following commands:
source .cshrc
rehash
If you are running sh or ksh shells:

Modify your search path in your .profile as follows:
PATH=your_install_dir/tools/bin:your_install_dir/tools/dfII/bin:$PATH;
export PATH
Then, either log out and back in again or type the following command:
. .profile
Note: If an incorrect path message appears, you need to correct any errors in your path
statement (.cshrc or .profile) and re-apply the changes.
no programName in path path

3. Start the software by typing

executable &
where executable is the executable you want to run (for example, virtuoso).
The splash screen appears and is followed by the CIW.
Note: You must set up plotters before you can plot a design (see the Plotter Configuration
User Guide for details).

Configuration and Startup Procedures

The tasks below provide a guide to the full configuration and startup procedure for your
software. This document assumes you have copies of the default initialization files from
your_install_dir/tools/dfII/cdsuser/.* in a local directory and that you are
logging in through dtlogin (perhaps from /usr/dt/bin).
■ Setting the Installation Path on page 58
■ Setting Up a User Account on page 60
■ Specifying Cadence Environment Variables on page 62
■ Modifying the .rhosts File on page 66
■ Modifying the .Xdefaults or Equivalent File on page 67
■ Modifying the .cdsinit File on page 70
■ Verifying Your System Configuration on page 72
■ Distributing the User Files on page 73
■ Configuring Remote Displays on page 73
■ Library and Tool Issues on page 74
Setting the Installation Path

Before starting the software, set a path to the executables and components.
For example,
setenv CDSHOME /yourInstallDirPath
set path = ( $CDSHOME/tools/bin $CDSHOME/tools/dfII/bin )
Note: The $CDS_INST_DIR environment variable is no longer used by Cadence

applications. For more information, see “$CDS_INST_DIR” under “Search Mechanism” in
Chapter 3 of the Cadence Application Infrastructure User Guide.
Setting an environment variable (such as CDSHOME) allows consistency when setting paths
to additional components or libraries. However, you do not need to set library hierarchy
directories using the LD_LIBRARY_PATH environment variable or to set library paths using
an environment variable in your library definitions file. See the Virtuoso Design
Environment User Guide for more information.

The LD_LIBRARY_PATH UNIX environment variable is used for special library modules (.so)
that tools might need. It is not necessary to add hierarchy library directories to the
LD_LIBRARY_PATH because the executable scripts add the appropriate information.
The library definitions file (an ASCII text file that defines which libraries are accessible and
where they are located in the installation hierarchy) uses root expressions to refer to
installation paths. For information about how to refer to the root of Cadence installation
hierarchies in your library definitions file without using environment variables, see “Installation
Root Expressions” in Chapter 5 of the Cadence Application Infrastructure User Guide.
Cadence tools are typically installed in their own directory hierarchy. You should use different
UNIX environment variables to represent each release hierarchy. The following example
shows how to set installation paths in a .cshrc file (you must modify these paths to match
your installation).
Note: For information regarding setting environment variables for specific tools, refer to the
documentation for that particular tool.
#*********************************************************************#
# Set path to DFII install directory
set CDSHOME = /cdsIntall/cds/IC541
#
# Set path to ICC install directory
setenv ICCHOME /cdsInstall/cds/iccraft112
#
# Set path to Assura install directory
setenv ASSURAHOME /cdsInstall/cds/Assura312
#
# Set path to Encounter install directory
setenv ENCOUNTERHOME /dsmInstall/cds/SOCE41
#
#*********************************************************************#
#
# Set paths to Cadence executables
#(In this example, variable names are assigned for each tool path,
# then set in the set path statement)
#
set dfiiPath = ( $CDSHOME/tools/bin $CDSHOME/tools/dfII/bin )
set iccPath = ( $ICCHOME/tools/iccraft/bin )
set assuraPath = ( $ASSURAHOME/tools/bin $ASSURAHOME/tools/dfII/bin )
set encounterPath = ( $ENCOUNTERHOME/tools/bin $ENCOUNTERHOME/tools/fe/bin
ENCOUNTERHOME/sun4v/tools/fe/bin )
#
set path = (. ~/bin \
/usr/local \
/opt/netscape \
/usr/local/bin \
/usr/openwin/bin/xview \
/usr/openwin/bin \
/usr/bin /usr/sbin /bin /etc /usr/etc \
$dfiiPath \
$iccPath \
$assuraPath \
$encounterPath \
)

#*********************************************************************#
# Set paths to license files
setenv LM_LICENSE_FILE $CDSHOME/cdsbin/lmtools/license.dat/licence.dat
#*********************************************************************#
# Set LD_LIBRARY_PATH
setenv LD_LIBRARY_PATH /usr/dt/lib:/usr/lib/X11:$OPENWINHOME/lib:/usr/lib:
#*********************************************************************#
# END of the .cshrc file
#*********************************************************************#
Note: The library path environment variable you use depends on your operating system:
■ For Sun Solaris, Linux, and UNIX, use LD_LIBRARY_PATH.
■ For HP, use SHLIB_PATH.
■ For IBM, use LIBPATH.
Setting Up a User Account

In order to set up accounts for new users, you must already have created a login and home
directory for each user. The home directory must include .cshrc and .login files for the
csh shell, or a .profile file for the sh or ksh shells. The
your_install_dir/tools/dfII/cdsuser directory contains sample home directory
environment setup files (see “Virtuoso Design Environment Hierarchy” on page 49).
You can set up a user account by running the Cadence-provided setup.sys script (see
“Using setup.sys” on page 60). If you choose not to run setup.sys to set up your user
account, you will need to follow the steps outlined in “Copying Sample Files to Your Home
Directory” on page 61.
Once you have set up a user account, you can modify your search path and run the software
as described in “Quick Start: Common Desktop Environment and OpenWindows” on
page 56.
Using setup.sys
You can use setup.sys to set up your user account. This utility helps you add a fictitious
user, cdsuser, with the user ID, group ID, and cdsuser home directory you specify to the
end of the /etc/passwd file on your local workstation. The user directory contains the
necessary startup files (.cshrc, .Xdefaults, .cdsinit, and so on) configured to run
Cadence software.

Caution
Creating cdsuser modifies your password file.
1. As root, run your_install_dir/tools/dfII/bin/setup.sys.
The SYSTEM SETUP MENU appears.
2. Type 1 to choose Create a cdsuser and click Enter.
This option modifies /etc/passwd (to add cdsuser; if you already have cdsuser on
your workstation, this option uses the existing account).
3. Log out as root and change to cdsmgr.
You can use cdsuser as a template for creating and modifying your own setup files. Before
you can run Cadence software as cdsuser, change the password for cdsuser.
Copying Sample Files to Your Home Directory
If you do not use setup.sys to set up your user account, you will need to do the following:
1. Copy the sample files to your home directory.
You can use commands similar to the following:
cd
cp your_install_dir/tools/dfII/samples/.??* .
cp your_install_dir/tools/dfII/cdsuser/.??* .
Caution
The copy command (cp) will overwrite any existing files of the same name
in your directory.
2. Go through each section of the sample files and customize them for your site. Be sure to
replace /cdsdir with your_install_dir.

Specifying Cadence Environment Variables

You can specify any number of the following environment variables.
Cadence Environment Variables
Variable What You Can Specify

CDS_LOG_PATH A colon-separated path of directories (ordered by
preference) in which to put the log file. If none of these
directories exist or they are all not writable, the default
$HOME directory is used.
CDS_LOAD_ENV A customized search order for .cdsenv using one of the
following keywords:
■ False loads neither ~/.cdsenv or CWD/.cdsenv
■ CWD loads only CWD/.cdsenv
■ addCWD loads ~/.cdsenv and then loads
CWD/.cdsenv
■ CWDElseHome loads CWD/.cdsenv if it exists, or
~/.cdsenv, if it exists
■ CSF uses the Cadence Setup Search File
mechanism to find the .cdsenv files to load
For more information, see “Specifying a Search Order for
.cdsenv“ in the Virtuoso Design Environment User
Guide.

Cadence Environment Variables, continued

CDS_PROMPT_CKOUT Whether the Auto Checkout form automatically appears
when you open data files using a product that has a
graphical user interface (GUI) and automatic check-out
capability using one of the following keywords:
all prompts for all autocheckout requests and is the
default. Causes all tools that have a GUI and perform
autocheckout operations to prompt you to check out
data before performing an autocheckout. A prompt is
issued regardless of the values of the other variables
controlling check in/out behavior. This action lets you set
up an environment that prompts for checkout wherever
possible. Tools that cannot prompt cannot automatically
check out data unless you also set the
CDS_AUTO_CKOUT variable.
■ none does not prompt for any autocheckout
requests.
■ views prompts for autocheckout requests of
cellview data.
■ files prompts for autocheckout requests of
non-cellview data.


CDS_AUTO_CKOUT Whether the software automatically checks out a file
when you open it with a product using one of the
following keywords:
■ all checks out all autocheckout requests and is
the default.
■ none does not check out any autocheckout
requests.
■ views checks out autocheckout requests of
cellview data.
■ files checks out autocheckout requests of
non-cellview data.
If a tool has a GUI and CDS_PROMPT_CKOUT is set to
all, CDS_AUTO_CKOUT has no effect. Otherwise,
when set to all, it causes all tools that have an
autocheckout capability to automatically check out a file
as needed.


CDS_PROMPT_CKIN Whether the Auto Checkin form appears when you close
properties or files that were automatically checked out.
Or if you try to exit a session without closing properties
or files that were automatically checked out, while using
a Cadence product that has both a GUI and automatic
check-in capability using one of the following keywords:
■ files prompts you before performing an
autocheckin of non-cellview data (default). It
overrides CDS_AUTO_CKIN and applies to
interactive tools only.
all prompts for all autocheckin requests. Causes all
tools that have a GUI and perform check in operations to
prompt you whether or not to check in data before
performing an autocheckin. Tools that do not have a
GUI are not affected by this variable.
■ none does not prompt for any autocheckin
requests.
■ views prompts for autocheckin requests of
cellview data.
CDS_AUTO_CKIN Whether the software automatically checks in data files
when you close properties or files that were
automatically checked out or when you exit a session
without closing properties or files that were automatically
checked out using one of the following keywords:
■ files file is autocheckin if it was automatically
checked out during this session and is the default.
■ all checks in all autocheckin requests.
■ none does not check in any autocheckin requests.
■ views checks in autocheckin requests of cellview
data.
If the tool has a GUI and CDS_PROMPT_CKIN is set to
all, CDS_AUTO_CKIN has no effect. When this
variable is set to all, all tools automatically check in any
file they automatically checked out.


CDS_IBM_FULLDUMP Whether to dump the core with full traceback and data
sections (IBM only). When an IBM workstation dumps its
core, the core contains a full traceback section but no
data section. Debugging typically requires the data
section.
CDS_LICENSE_DIR Alternate SoftShare license directory used.
CDS_LOG_VERSION Naming convention for preserving multiple log files using
one of the following keywords:
■ sequential adds a sequential number to the name
of the log file, such as CDS.log.1 or CDS.log.2.
■ pid adds the number of the UNIX process to the
name of the log file, such as CDS.log.1719 or
CDS.log.2250.
Note: If you do not specify CDS_LOG_VERSION, each
session overwrites the log file from the previous one.
CDS_SHM_ADDR The address to use for shared memory.
Note: Set this variable only when you do not have shared
memory.
Setting this variable turns off VO fasttime. If you set

CDS_SHM_ADDR to a non-zero hex number, the software
uses that address instead of the default address for
shared memory.
CDS_AUTO_64BIT Which applications to run using the 64-bit version (see
“Running 64-Bit Versions of Applications” on page 77).
Modifying the .rhosts File

Note: Modifying the .rhosts file is optional.
If you are going to run a remote simulation or remote shmd, your network must be properly
configured. You must create a .rhosts file in your home directory or edit the
rhosts.equiv file in the /etc directory of each workstation on the network for which you
want to run a remote simulation or shmd process. If you do not create a .rhosts file, any

attempt to run a simulation or shmd on the remote workstation gives you a “permission
denied” error.
Modifying the .Xdefaults or Equivalent File

The your_install_dir/tools/dfII/cdsuser directory contains a .Xdefaults file.
Both the X Window System and OpenWindows software normally use the resources in the X
resources database that is loaded upon login from your local .Xdefaults file.
You can copy the Cadence-provided .Xdefaults file to your local directory and modify it to
contain the settings you want.
1. Copy Cadence .Xdefaults file to your local directory:
cd
cp your_install_dir/tools/dfII/cdsuser/.Xdefaults .
2. Modify the settings you want and save the file.
The software reads in X resources when you start your application. If you make changes to
your .Xdefaults file after the software is running, these changes do not take effect until you
read the resources into the X server and restart your application. You must force the server
and window manager to see the file changes.
1. Read in the .Xdefaults file.
xrdb -merge .Xdefaults
Note: The -merge option prevents deleting desired settings that are not in the
.Xdefaults file.
2. Restart your window manager using one of the following methods:
❑ Access the menu selections from your desktop. For example, if you are running CDE
and using dtwm, you can right-click in a blank area on your desktop to open the
Workspace menu and choose Windows – Restart Workspace Manager.
❑ Exit the CDE and login again.

Cadence Resources
The following table identifies some of the resources that you can modify in your local
.Xdefaults file. You can find examples of these resource settings in
your_install_dir/tools/dfII/cdsuser/.Xdefaults.
Important
Cadence resources use tight bindings with a period (.) instead of the usual loose
bindings with an asterisk (*). The period cannot be replaced by an asterisk.
Wildcard resources produce unpredictable effects on dialog boxes and menus.
Cadence recommends that you restrict your resources to the list shown in the
resource list above to prevent X resources from clashing with SKILL descriptions for
forms and menus.
Cadence Resource Description

Opus.activeBannerColor Color of the active window banner.
Opus.attentionTextColor Color of text in dialog boxes.
Opus.background Color of the background for everything except
graphics windows.
Opus.beepDialog Beeps when warning or dialog boxes appear.
Opus.borderColor Color of field borders if hiShowFieldBorders(t)
has been called.
Opus.bottomShadowColor Color for the bottom shadow of three-dimensional
widgets.
Opus.buttonColor Color of button and label text.
Opus.dragColor Color of the selection box you draw around objects;
the zoom box you draw to zoom in or out; the
outlines of objects you move, copy, or reshape; and
the outlines of edges you stretch.
dragColor controls the highlight that appears
before you select objects. Objects and edges are
highlighted as you move the cursor over them.
Opus.editorBackground Color of design window background.
Opus.flashColor Color of flashing box drawn around error fields in
forms.


Opus.flashColor Color of flashing box drawn around error fields in
forms.
Opus.foreground Color of menu and listbox text and selected radio
and toggle buttons.
Opus.formPlacement Location of form (top, bottom, left, right, or
center).
Opus.formRelativeTo Location of form relative to screen, window
(currentWindow), or CIW.
Opus.geometry Location and size of CIW (overrides Opus.x,
Opus.y, Opus.height, and opus.width).
Opus.height Height of CIW (Opus.geometry overrides this
setting).
Opus.inactiveBannerColor Color of the inactive window banner.
Opus.labelFont Font used for form labels, button text, and menu
text.
Opus.optionFormPlacement Placement of option form (top, bottom, left, right,
or center).
Opus.optionFormRelativeTo Placement of option form relative to screen,
current window (currentWindow), or CIW.
Opus.recessColor Color of uneditable text fields and depressed
buttons.
Opus.selectionColor Controls the highlight that appears around selected
objects when Opus.selectionPlane is True,
otherwise it uses the grid color.
Opus.showPromptLines Display prompt line on graphics windows.
Opus.showScrollBars Display scroll bars on graphics windows.
Opus.showStatusLines Display status line on graphics windows.
Opus.textColor Color of text in type-in fields, ShowFile windows,
and CIW input and output areas.
Opus.textEditor Text editor.
Opus.textFont Font for text in fields, ShowFile windows, and CIW
input and output areas.


Opus.topShadowColor Color of top shadow of three-dimensional widgets.
Opus.warpPointer Automatically moves cursor to OK in dialog boxes
and to current value on pop-up menus.
Opus.width Width of the CIW (Opus.geometry overrides this
setting).
Opus.x Horizontal position (X axis) of the CIW
(Opus.geometry overrides this setting).
Opus.y Vertical position (Y axis) of the CIW
(Opus.geometry overrides this setting).
Window Manager Resources
If you are using CDE, you can edit your window manager resources. Cadence recommends
using the following settings:
Dtwm*clientAutoPlace: False
Dtwm*colormapFocusPolicy: pointer
Dtwm*keyboardFocusPolicy: pointer
Dtwm*interactivePlacement: False
Dtwm*positionIsFrame: True
Dtwm*saveUnder: True
You can turn off the Dtwm*client features tool by tool. For example, XClock does not have
decorations when using these resources:
Dtwm*XClock.clientDecoration:none
Dtwm*XClock.clientFunctions:none
You can copy your site-specific dtwmrc to $HOME/.dt/user.dtwmrc.
Modifying the .cdsinit File

Before you set up users, decide whether you want them to use the same .cdsinit file. The
program uses the first .cdsinit file that it finds in the following order:
1. your_install_dir/tools/dfII/local/.cdsinit
2. Current directory (.)
3. Your home directory (~)
You can customize the .cdsinit file after you copy it into the current directory or the user
home directory. Use the following guidelines when modifying the .cdsinit file:

Tip
You can find a sample .cdsinit file at
your_install_dir/tools/dfII/samples/local/cdsinit.
■ Group the information in the file according to the application and clearly label the
application name using comment lines.
■ For each setting, use comment lines to specify what the normal defaults are and to what
they might be changed. Specify what you normally use.
■ Warn about any settings that lead to undesirable results.
■ Set the option to your normal value or to the normal default value.
■ Read several files if necessary, such as
❑ your_install_dir/tools/dfII/local/.cdsinit
❑ A project’s ./.cdsinit
❑ Each user’s personal ~/.cdsinit
To create a site-specific file, follow these steps:

1. Copy the default file to another directory.
Type the following to copy the default file to a local directory:
cp your_install_dir/tools/dfII/cdsuser/.cdsinit
your_install_dir/tools/dfII/local
2. Edit the last line of the (system) .cdsinit file to read.

if(isFile("./.cdsinit")
then load("./.cdsinit")
else when(isFile("~/.cdsinit")
load("~/.cdsinit)
)
)
3. Save and close the file.
This allows you to customize their own .cdsinit files. Some customizations may include
the following:
■ You can specify the library search path for the site-specific libraries. See the Virtuoso
Design Environment User Guide for more information.
■ You can define key bindings.

■ You can set up the environment for SKILL programming (see the Cadence SKILL
Language Reference and the Cadence SKILL Language User Guide).
❑ Set the log filter to display user and program results in the output area of the CIW:
hiSetFilterOptions( t t t t t t t )
❑ Turn the writeProtect switch off:

sstatus( writeProtect nil )
This switch affects only procedures loaded after the software starts running.
❑ Turn on the debugger:
installDebugger()
■ If you have your own SKILL files, you can include one or more locations in the SKILL
search path by adding a setSkillPath function with a list of space-separated path
strings such as one of the following:
setSkillPath(". skill_path")
setSkillPath(strcat(". your_install_dir/etc skill_path"))
setSkillPath(strcat(". " prependInstallPath("/etc ") "skill_path"))
Verifying Your System Configuration

The system configuration checker (your_install_dir/tools/bin/checkSysConf) verifies
that the operating system level, system configuration, and patch level of your machines match
Cadence software requirements. To run the system configuration checker, do the following:
1. In an xterm window, type the following command to get a list of valid release names:
checkSysConf -r
Valid release names appear on your screen.

2. Run the system configuration checker using a valid release name as follows:
checkSysConf validReleaseName
For example,
checkSysConf IC5.2 | more
The system configuration checker reports system information (such as Host Name and
Hostid) and verifies whether system requirements are met (such as MEMORY, SWAP,
DISPLAY, PACKAGE, and PATCH requirements). Any failures to comply with system
requirements for the specified release stream appear at the end of the report. For example,
you might need to find out which products require a missing patch by running checkSysConf
with the -p option:
checkSysConf IC5.2 -p patch

For more information about the system configuration checker, refer to the Cadence Cadence
Online Support web site:
http://support.cadence.com/docs/files/releases/sys_conf_check/welcome.html.
Distributing the User Files
Caution
Do not overwrite existing user files.
➤ Copy the files to the new user home directory.
Include the following default or site-specific files:
.cshrc or .profile
.Xdefaults
Configuring Remote Displays

Normally, only specified workstations can access the X server, but you can change the
access by typing one of the following commands:
Important
Contact your system administrator before using this command as it overrides more
stringent security schemes.
Command Description
xhost + All hosts can access the X server.
xhost + hostname Add hostname to access list.
xhost - hostname Remove hostname from access list.
xhost - Only those workstations listed in the access list,
/etc/X*.hosts, can access the X server.

Library and Tool Issues

You might want to also consider the following library and tool issues:
■ Converting existing libraries (see the Conversion Tool Box User Guide)
■ Creating new libraries
■ Integrating other tools
■ Creating menus for tools (see the Virtuoso Design Environment User Guide.
■ Locale Settings

Additional Virtuoso Software Licensing

and Configuration Information
The administration of the software is summarized below.
Fulfill requirements
Disk requirements
Memory requirements
Installation
License setup
Third-party software
Ongoing support
Plotting
Library management
Technology file
Customization License management
New user setup User tailoring of software
Environment setup Network access
Hand over to users
Plotter definitions File sharing
Library setup Support on other platforms
Regular backups
Note: This document assumes that your operating system and the X Window System are
installed and that each user has an account (user name, home directory, .cshrc, and
.login file or .profile file). The Virtuoso Design Environment User Guide provides
more information about customizing these files.
The following information is described in this chapter:

■ X Window System on page 76
■ Running 64-Bit Versions of Applications on page 77
■ TrueColor Visuals on page 80
■ Locale Settings on page 82
If you need information about NFS mounting, see “Advanced Installation Topics” in the
Cadence Installation Guide.

Additional Virtuoso Software Licensing and Configuration Information
X Window System
You can find server-dependent directories and files in the following location:
X_install_dir/etc/*
where X_install_dir is the directory where your X Window system software is installed.
You can start X in one of the following ways:

1. The workstation runs X all the time (X is running even before you log in). You are using
dtlogin.
Note: This document assumes that you are using dtlogin.
Important
The dtterm -C option on some platforms makes the dtterm window act as the
console, whereas on other platforms, dtterm -C quits with an error.
2. The workstation comes up in text or a proprietary graphics mode. You start X after you
log in (without xdm).

Running 64-Bit Versions of Applications

Most Cadence® applications have both 32- and 64-bit versions. The 64-bit versions of
applications are installed in the same tools hierarchy as the 32-bit versions. A wrapper for
each application determines which version of the application is run.
Note: The default setting is to run applications in 32-bit unless the CDS_AUTO_64BIT
environment variable is set to ALL (see below for more information).
To run the 64-bit version of a Cadence application, do the following:

1. Verify that your operating system supports 64-bit applications.
Note: You should have a minimum of 4GB of RAM to run Cadence 64-bit applications.
2. Verify that a 64-bit version of the application is installed.
The 64-bit version of an application is located in the 64bit directory in the standard
installation location of the application.
For example,
your_install_dir/tools/bin/64bit/cdsHierEditor
your_install_dir/tools/dfII/bin/64bit/virtuoso

3. Set the following environment variable:

CDS_AUTO_64BIT { ALL | NONE | list | INCLUDE:list | EXCLUDE:list }
ALL All applications are run as 64-bit.

NONE All applications are run as 32-bit.
list Only the applications specified are run as 64-bit.
Specify list as a list of case-sensitive application names,
separated by a colon, comma, or semi-colon. If you use a
semi-colon, enclose the list in quotation marks.
INCLUDE:list Only the applications specified are run as 64-bit.
EXCLUDE:list Only the applications specified are run as 32-bit; all other
applications are run as 64-bit.
For example, if you have virtuoso and libManager installed:
CDS_AUTO_64BIT is ... The following versions are run ...

ALL virtuoso: 64-bit; libManager: 64-bit
virtuoso virtuoso: 64-bit; libManager: 32-bit
INCLUDE:virtuoso virtuoso: 64-bit; libManager: 32-bit
EXCLUDE:virtuoso virtuoso: 32-bit; libManager: 64-bit
NONE virtuoso: 32-bit; libManager: 32-bit
Important
Setting CDS_AUTO_64BIT does not guarantee that you will run the 64-bit version of
an application. The wrapper runs the 64-bit version of the application only if all the
following conditions are true:

❑ The operating system supports 64-bit applications.

❑ A 64-bit version of the application is installed.
❑ You choose to run the 64-bit version by setting the CDS_AUTO_64BIT environment
variable.
Note: Applications can override the CDS_AUTO_64BIT variable with an
application-specific variable. See the application’s documentation for more
information.
Otherwise, the 32-bit version of the application is run.
4. Start the Cadence application from its standard location.
For example, for the virtuoso executable,
your_install_dir/tools/dfII/bin/virtuoso.
or for the Cadence Hierarchy Editor
your_install_dir/tools/bin/64bit/cdsHierEditor
The wrapper for the application assess whether to run the 32- or 64-bit version of the
application based on the value of CDS_AUTO_64BIT.
The actual versions of the applications reside in subdirectories of the bin directory. For
example, the 32-bit version of appName is in
your_install_dir/tools/bin/32bit/appName.
Caution
Do not run the executables in the 32bit or 64bit directories directly
(always run the application through its wrapper).
Note: See your application documentation for more information. In some cases, you
might need to start appName.exe instead of appName to run the application through
its wrapper.
Tip
When you start an application, you can use the -debug3264 option to assess
whether you are running the 32- or 64-bit version. Diagnostic information is
displayed before the program starts.
In the following example, the 32-bit version of the libManager executable was run even
though CDS_AUTO_64BIT was set to ALL. The output of the -debug3264 option

indicates that the 32-bit version was run because the 64-bit version of the application was
not installed.
% setenv CDS_AUTO_64BIT ALL
% libManager.exe -debug3264
-------- 32/64 bit wrapper diagnostics -------------
App name: libManager.exe
App path: /net/machine/cds/5.0.0/tools/dfII/bin
OS is 64-bit capable.
The user has selected 64-bit operation via the environment variables.
No 64-bit version of the application exists.
A 32-bit version of the application exists.
----------------------------------------------------
PATH :
/net/ansbk/usr/SoftWindows.solaris/bin:/mnt3/ns/bin:/usr/bin/X11:/usr/openwin
/bin:.:/usr/ucb:/bin:/mnt3/ns/bin:/usr/local/bin:/usr/bin:/usr/etc:/usr/local
:/usr/lang/v3:/net/machine/cds/5.0.0/tools/bin:/net/machine/cds/5.0.0/tools/d
fII/bin:/net/machine/cds/5.0.0/tools/lib:/opt/SUNWdtpcv/bin:/usr/local/pvt
LD_LIBRARY_PATH :
/net/machine/cds/5.0.0/tools/lib:/usr/lib:/usr/openwin/lib:/usr/lib/X11:/usr/
dt/lib
CDS_AUTO_64BIT : ALL
Launching "/net/machine/cds/5.0.0/tools/dfII/bin/32bit/libManager.exe"
------------------------------------------------------
TrueColor Visuals
The software defaults to a 24-planes TrueColor visual. If a 24-planes visual is not available,
the software will first search for a 16-planes TrueColor visual, then a 15-planes TrueColor
visual.
Note: One of these graphics display visuals must be available in order to run TrueColor
visuals.
Finding Available Visuals

To check for available graphics display visuals, do the following.
➤ At the system prompt, type xdpyinfo
The following shows the results of xdpyinfo for a typical 24-planes TrueColor visual:
visual:
visual id: 0x2e
class: TrueColor

depth: 24 planes
available colormap entries: 256 per subfield
red, green, blue masks: 0xff, 0xff00, 0xff0000
significant bits in color specification: 8 bits
Pseudocolor and TrueColor Visuals

In previous releases, the software supported Pseudocolor visuals. Pseudocolor visuals
allowed color mapping (mapping between the pixels used to define the colors and the actual
colors displayed). In the IC 6.1 release, only TrueColor visuals are supported. TrueColor
provide a full palette of colors which increase with larger numbers of planes (bits). In other
words, the incremental difference between each color is smaller with the more planes you
have.
A 15-plane TrueColor visual provides 32,768 colors and uses 5 bits each to describe the red
component, green component, and blue components. A 16-plane TrueColor visual provides
65,535 colors and uses 6 bits to describe the red component, 5 bits to describe the green
component, and 5 bits to describe the blue component. The 24-plane TrueColor visual
provides 16,777,216 colors and uses 8 bits to describe each component of the red, green,
and blue.

The following table shows how the total number of planes (or bits) are used to describe each
of the components; red, green, and blue for TrueColor visuals.
15 Planes Color Depth

Color r r r r r g g g g g b b b b b
Bits 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

Color r r r r r r g g g g g b b b b b
Bits 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

Color r r r r r r r r g g g g g g g g b b b b b b b b
Bits 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Locale Settings
Virtuoso software requires locale settings to be set to C in order to work properly. When you
run Virtuoso software on any platform, the software sets the locale to C automatically. Your
original locale settings are ignored.
This also means that for a script, shell, or other tool that is run from a Virtuoso application (for
example, a shell invoked from the CIW), the locale setting that is used is always C, regardless
of any locale variables set in your environment.
If you want to restore your original locale settings for a script, shell, or tool that is invoked from
a Virtuoso application, source one of the following scripts first:
For Bourne shells:

your_install_dir/tools/dfII/samples/local/cdsOrigLocale.sh
For C shells:

your_install_dir/tools/dfII/samples/local/cdsOrigLocale.csh
For example,
source your_install_dir/tools/dfII/samples/local/cdsOrigLocale.csh
or
. your_install_dir/tools/dfII/samples/local/cdsOrigLocale.sh
You can also do this from the system command. For example, to run dtpad, you could use
the following command:
system( strcat( ". " prependInstallPath( "samples/local/cdsOrigLocale.sh" )
"; /usr/dt/bin/dtpad -standAlone" ) )


Licensing and Configuration

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Licensing and Configuration

Caricato da

Copyright:

Formati disponibili

Virtuoso Software Licensing and

Configuration User Guide

Printed in the United States of America.

Configuring the Virtuoso Design Environment . . . . . . . . . . . . . . . . 11

January 2011 3 Product Version 6.1.5

Setting Up the Virtuoso Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Additional Virtuoso Software Licensing and Configuration

January 2011 4 Product Version 6.1.5

The preface describes the following topics:

Related Documents for Virtuoso Design Environment

Installation, Environment, and Infrastructure

January 2011 5 Product Version 6.1.5

January 2011 6 Product Version 6.1.5

Relative Object Design and Inherited Connections

Typographic and Syntax Conventions

text Indicates text you must type exactly as it is presented.

z_argument Indicates text that you must replace with an appropriate

[ ] Denotes an optional argument. When used with vertical bars,

| Separates a choice of options.

… Indicates that you can repeat the previous argument.

=> Precedes the values returned by a Cadence® SKILL language

January 2011 7 Product Version 6.1.5

/ Separates the possible values that can be returned by a

text Indicates names of manuals, menu commands, form buttons,

Identifiers Used to Denote Data Types

Prefix Internal Name Data Type

January 2011 8 Product Version 6.1.5

Prefix Internal Name Data Type

January 2011 9 Product Version 6.1.5

January 2011 10 Product Version 6.1.5

Configuring the Virtuoso Design

The following topics are discussed in this chapter:

January 2011 11 Product Version 6.1.5

Virtuoso Design Environment

Design Environment: Virtuoso Design Environment

Product Family: VSE ADE VLS

Product Family Tier: L XL L XL GXL L XL GXL

Design Process Location: Front-End Back-End

Product Name License Feature Name License Type

January 2011 12 Product Version 6.1.5

Product Name License Feature Name License Type

Product Name License Feature Name License Type

January 2011 13 Product Version 6.1.5

January 2011 14 Product Version 6.1.5

Virtuoso Design Environment Executables

32- and 64-Bit Platforms

January 2011 15 Product Version 6.1.5

Setting the CDS_Netlisting_Mode Environment Variable

January 2011 16 Product Version 6.1.5

Launching the Virtuoso Product Family Applications

License Check Out/In

January 2011 17 Product Version 6.1.5

Task Assistant Interactive Commands

January 2011 18 Product Version 6.1.5

License Failure in Design Framework II

License Activity Summary

Table 1-1 Licensing Check Out/In Model

ADE L 2 Analog_Design_Environment_L check out check out check in

January 2011 19 Product Version 6.1.5

VLS L Virtuoso_Layout_Suite_L no check out check out check in

VSE L Virtuoso_Schematic_Editor_L no check out check out check in

1 Close all windows running this application except the CIW.

Virtuoso Visualization and Analysis XL and ADE Licenses

January 2011 20 Product Version 6.1.5