1

---

Cadence Application Infrastructure

---

This section describes a set of mechanisms common to Cadence® applications.

The following mechanisms support consistent operations between applications.

• Name mapping between applications: The Cadence approach to name mapping, applied when applications use data from other applications with non-compatible naming conventions. Each Cadence application interprets names according to a consistent set of rules. Data is interoperable across many applications and data formats. Also, data is interoperable between UNIX and NT operating systems.
• Generic Design Management (GDM) facility: It is an interface between Cadence applications and any design management system. This facility implements an interface that CAD applications, which make direct DM system calls, can use so that they can work with many different design management systems without having any special knowledge of those systems. Part of the GDM facility is a set of shell commands that can be used in running design management operations. These commands are also used by some Cadence applications that perform these operations from shell scripts.
• Copying Libraries: Cadence provides the cdsCopy system to help you copy, merge, or rename libraries. A cdsCopyShell, a set of SKILL functions, and a cross-reference updater system are part of cdsCopy.
• Cadence Locking System (CLS): It is the mechanism used by Cadence applications to lock files on all platforms. A Lock-Stake file (fileName.cdslck) in the same directory as a file indicates that the file is locked. Applications release locks when they no longer need them. CLS also provides an administrative tool that lets you view and release any locks.
• Occurrence property dictionary: It is a central repository for simulation-control property definitions.
• Cadence Library Structure: It uses your computer directory structure to organize data. Data is stored in files in a directory hierarchy. Most Cadence applications use the same library model. The library structure provides data interoperability and consistent behavior among applications—a common library model using common file-naming conventions.

Related Topics

Name Mapping

Generic Design Management (GDM) Commands

cdsCopy

Occurrence Property Dictionary

Cadence Locking System

Cadence Library Structure

Cadence Application Infrastructure Files

Various configuration mechanisms are used in Cadence application, such as defining data types, locating libraries, configuring key capabilities. These configuration mechanisms are controlled by specific file formats and associated utilities.

• The Cadence Setup Search File (setup.loc)
• The Cadence System Information File (cdsinfo.tag)
• The Cadence Library Definition File (cds.lib)
• The Cadence Data Registry File (*.reg)

The Cadence Setup Search File

This file supports a configuration to search for application setup and configuration information.

The Cadence System Information File

This file supports configuration of several key capabilities, including the type of design management system used to manage a library and whether a more strict library checking mechanism should be used to identify Cadence libraries.

The Cadence Library Definition File

This file supports defining the locations of Cadence libraries and models related to organizing library definition files so that teams of users can consistently share such definitions.

The Cadence Data Registry File

This file supports defining various data types (especially views), associating default editors with data, and is also a general registry facility.

Related Topics

Cadence Setup Search File: setup.loc

Cadence System Information File: cdsinfo.tag

Cadence Library Definition File

Cadence Data Registry File: data.reg

Cadence Application Infrastructure Commands

The following commands are useful in configuring data files, debugging files, and in reporting the status of the Cadence application infrastructure.

Command	Usage
cdswhich	A command available as a test, debug, and administration tool for use in managing the search mechanism.
cdsinfo	A command used as a test, debug, and administration tool for the system information file mechanism.
nmp	A command that assists you in determining the difference in a name as it is mapped to different name spaces.
cds_root	A utility, typically used in startup scripts, for identifying the location of Cadence installation hierarchies.
dregprint	A command that displays the contents of the data registry.
cdsLibDebug	A command that helps you to test and debug your library definition files. cdsLibDebug is only available with Virtuoso Studio design environment applications.
clsAdminTool	An administrative tool for viewing and releasing file locks.

Related Topics

The cdswhich Command

The cdsinfo command

The nmp Command

The cds_root Utility

The dregprint Command

The cdsLibDebug Command

CLS Administrative Tool

Return to top