8 Generic Design Management (GDM) Commands

Cadence provides a facility known as Generic Design Management (GDM). 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 to perform design management operations. These commands are also used by some Cadence^® applications that perform these operations from shell scripts.

GDM is designed to support data stored in Cadence Library Structure libraries, including properly handling co-managed sets and other data that must be accessed in a synchronized fashion. By using GDM, you avoid the need to understand the Cadence library structure when using any design management system.

GDM recognizes data formats defined in multiple installation hierarchies.

GDM Concepts

GDM is based on a simple DM system model, which defines 12 operations or commands based on the following concepts:

Concept	Description
workarea	A directory hierarchy in the file system, where a related set of designs and other data including Cadence design libraries are stored.
version	A design management system–specific identifier of an instance of a file, which GDM handles in an opaque manner, expecting the users and underlying design management systems to understand the meaning of the identifier.
repository	Associated with each design management system installation. The repository knows what files are managed, where they are stored, and what versions of those files exist and are accessible by users.
wrapping	Integrates your chosen design management system into GDM. It consists of a shared library that is dynamically loaded and a set of design management–specific commands that GDM executes. The Cadence Services organization offers a service for implementing a wrapping of a specific design management system.

Using Third-Party GDM Integrations

If you are using a third-party GDM integration (or wrapping), such as Synchronicity, Inc. DesignSync, and you cannot copy the shared libraries into the Cadence installation hierarchy, do the following:

Set the following environment variable that enables GDM to look for third-party shared libraries outside the Cadence installation hierarchy:
```
setenv GDM_USE_SHLIB_ENVVAR yes
```
You can also use the CDS_GDM_SHLIB_LOCATION environment variable to set the path to where the DM library can be found. Multiple paths can be set and GDM will investigate each of them until the DM shared library is found. For example:
CDS_GDM_SHLIB_LOCATION=/tools/icmanage/gdm/lib64:/tools/icmanage/gdm/lib
Add the location of the shared libraries to the platform-specific library path environment variable. The library path environment variable is

LD_LIBRARY_PATH

on Sun

LIBPATH

on IBM RS

LD_LIBRARY_PATH

on Linux

If both 32-bit and 64-bit program versions are used, both library locations should be specified. The 32-bit directories are located in <path>/lib, while the 64-bit libraries can be found in <path>/lib/64bit.
GDM then looks for shared libraries in the locations specified by the platform-specific library path environment variable.

GDM Environment Variables

The following environment variables are used by GDM:

Environment Variables	Description
`GDMNOTLOADLIB`	Specifies that no design management system be used. When this variable is set, no DM operation will be executed and no shared library will be loaded.
`GDM_USE_SHLIB_ENVVAR`	Enables GDM to look for shared libraries outside the Cadence installation hierarchy. If you set this variable, you must also add the location of the shared libraries to the platform-specific library path environment variable (such as `LD_LIBRARY_PATH)`.

Common Arguments for GDM Commands

All gdm commands, except gdmimport, support the following arguments:

-lib and -file
-recurse
-cdslib
-xtra
-help

If you use a gdmxxx command that the specific design management wrapping does not support, the system generates an error message. All gdmxxx commands have a nonzero exit status if the command fails or if any file operated on generates an error.

The -lib and -file Arguments

Specify items in libraries by using the argument -lib followed by a library name, using the following syntax:

lib.cell:view/file

Library, cell, and view names in this syntax are always in the library namespace (LibraryNT or LibraryUnix), which means that cell and view names appear just as an ls command shows them. The -lib argument need appear only once to determine how the system parses multiple specifications.

For example, everything in the cell MUX2 in library gates is identified as:

-lib gates.MUX2

The Verilog source file in the hdl view of cell cpu in the system library is identified as:

-lib system.cpu:hdl/verilog.v

When you use the library syntax, all items appropriate to the level being used must be present. To specify a file in a view, you must specify all four items lib.cell:view/file. If a file is named, the forward slash ( / ) must be present. The remaining punctuation is optional if there is no name following these items. The following example specifies a cell-level file, delay.tla in cell aoi3, and a library level-file, template.usr.

-lib asic.aoi3/delay.tla asic/template.usr

You can give file specifications, which are not library references, with no arguments. If there is a need to specify both files and library references to a single command, use -file to change back to file specifications from library specifications. The following example refers to the entire contents of two cells, mpeg and frame, in library video, and the nonlibrary file synth.cmd, where -lib applies to all the arguments after the -lib argument until any following the -file argument. If -file is present, it applies to all the arguments until any following the -lib argument. No other arguments are positional. They have the same effect no matter where they appear in the command line.

% gdmcmd -lib 'video.mp*g'  video.frame  'video/index.htm*' -file ../synth.*

For GDM (Unix shell) commands, you can use wildcard characters, * and ?, and letter range characters, [ ], while specifying library, cell, view, and file names.

The * character matches zero or more characters of the library, cell, or cellview name. For example, if you specify –lib 'S7E100A_*.*:s*', it extracts all the elements where the library name starts with S7E100A_, such as S7E100A_XU, and the view name starts with s, such as schematic or symbol.
The ? character matches one character in the library, cell, or cellview name. For example, if you specify -lib 'S7E100?.Cell??:layout', it extracts all the elements where the library name starts with S7E100 and matches one character following it, such as S7E100X or S7E100Y; and extracts all the elements where the cell name starts with Cell and matches two characters following it, such as Cell01 or Cell02, and the view name is layout.
The letter range [a-z] matches one character in the given range in the library, cell, or cellview name. For example, if you specify -lib 'S7E100[A-C].*:symbol', it extracts all the elements where the library names are S7E100A, S7E100B, and S7E100C, and the view name is symbol.

Important Points to Note

The wildcard characters do not work when specified for the filenames starting with a dot (.). For example, if you specify -lib 'lib/*', it will not extract the elements, such as lib/.oalib. In such cases, you need to specify the pattern as -lib 'lib/.*'.
When you run the gdmDelete command, a prompt is displayed for confirmation before deleting the library elements only if wildcard characters are specified in the -lib argument.
When using wildcard characters for the values specified for the -lib argument, ensure that those values are enclosed within single quotes. However, do not enclose values with single quotes when using the -file argument because the operating system shell needs to process those wildcard characters.

The -recurse Argument

If a nonlibrary specification is a directory name, by default it refers only to the files immediately below that directory. If the argument -recurse is present anywhere on the command line, it refers to the entire tree of files under that directory.

The -cdslib Argument

This argument specifies the library definition file to be used for mapping library names to library directories. If this argument is not specified, gdm looks for cds.lib files.

The -xtra Argument

GDM commands that run design management–specific commands take an argument of -xtra . This enables the GDM command to take additional arguments that are specific to the design management command so that it can pass them to the design management command.

The -help Argument

This argument prints out a brief message that describes the available arguments.

Common Arguments for DM Commands

GDM commands call the design management–specific commands that constitute the wrapping of a design management system. For example, gdmexport calls xxxexport, where xxxexport is the wrap around the design management system export command. These design management-specific wraps must accept the following arguments, which are passed to them by the corresponding GDM commands:

Argument	Description
`-gdm`	Forces the command to follow GDM requirements.
`-u` file	Precedes files in the file list that are not managed but exist in the file system.
`-setstart` file1 file2 `...` `-setend`
	`-setstart` marks the beginning of a list of files that are to be treated as a set. `-setend` marks the end of the set.
`-xtra` arguments	Precedes arguments specific to the design management system.

GDM Commands

Designers can use Generic Design Management (GDM) shell commands to perform operations without using a graphical user interface. These commands are as follows:

If you use a gdm command that the specific design management wrapping does not support, the system generates an error message. All gdm commands have a nonzero exit status if the command fails or if any file operated on generates an error.

Case Sensitivity

All arguments are case insensitive. Therefore, -lib, -Lib, and -LIB are equal. The variables that follow the arguments are case sensitive; for example, gdmci lib ABCLibrary is not the same as gdmci -lib abcLibrary.

gdmcancel

gdmcancel [-cdslib file] [-recurse] [-xtra str] [-optimize] [-help] 
[-lib lib.cell:view/file] [-file file] ...

Description

Cancels the checked-out status of files in the workarea. Co-managed files are always canceled as a group. Co-managed set behavior applies only to views when the view is specified as a library entry, such as -lib lib.cell:view.

Arguments

`-cdslib` file	Specifies the library definition file to be used for mapping library names to library directories.
`-recurse`	If a nonlibrary specification is a directory name, by default it refers only to the files immediately below that directory. If the argument -recurse is present anywhere on the command line, it refers to the entire tree of files under that directory.
`-xtra` str	Allows additional arguments, specific to the design management cancel command, to be passed through `gdmcancel` to that command.
`-optimize`	Skips some calls to the design management system to improve performance. Specifically, when you cancel a checkout, GDM first obtains the status of the files from the design managment system and removes any files that are not checked out from the file list. With the `-optimize` argument, GDM will skip the extra call to get status and just provide the list of files to the DM system. The DM system will then issue an error if a file has not been checked out.
`-help`	Displays information about this command and its arguments.
`-lib` lib`.`cell`:`view`/`file
	Library elements for which the cancel checkout task needs to be performed. Names listed without `-lib` or `-file` are treated as `-file` arguments.
`-file` file	Files and directories (nonlibrary elements) for which to cancel checkout. Names listed without `-lib` or `-file` are treated as `-file` arguments.

gdmci

gdmci [-cdslib file] [-recurse] [-xtra str] [-initial] [-description des_str]
[-dfile file] [-optimize] [-help] [-lib lib.cell:view/file] [-file file] ...

Description

Checks in specified files and registers files that were previously unmanaged. Gives checked-out and previously unmanaged files to the repository so the files can be shared. Co-managed files in a view are always checked in as a group. Co-managed set behavior applies only when directories or files are specified as library elements; that is, with the -lib argument.

When you specify a library or cell, all the managed files in the library or cell are checked in, but only the co-managed files in the views are checked in.

Arguments

`-cdslib` file	Specifies the library definition file to be used for mapping library names to library directories.
`-recurse`	If a nonlibrary specification is a directory name, by default it refers only to the files immediately below that directory. If the argument -recurse is present anywhere on the command line, it refers to the entire tree of files under that directory.
`-xtra` str	Allows additional arguments, specific to the design management checkin command, to be passed through `gdmci` to that command.
`-initial`	Checks in all specified files and registers files that were previously unmanaged. If it is not used, new or unmanaged files that are members of a registered co-managed set will be checked in. All arguments are case insensitive and can be shortened to any abbreviation that is unique across all `gdm` command arguments. Hence, -initial can be specified as -Ini .
`-description` des_str
	Cannot be used with `-dfile.` The string `"str"` is used as the description for the `checkin` operation.
`-dfile` file	Cannot be used with `-description`. Use `-dfile` to enter a multiline description. The contents of the file named are used as the description for the `checkin` operation.
`-optimize`	Skips some calls to the design management system to improve performance. Specifically, when you check in library elements or files, GDM first obtains the status of the files from the design managment system and removes any files that have already been checked in from the file list. With the `-optimize` argument, GDM will skip the extra call to get status and just provide the list of files to the DM system. The DM system will then issue an error if a file has already been checked in.
`-help`	Displays information about this command and its arguments.
`-lib` lib.cell:view/file
	Library elements to check in. Names listed without `-lib` or `-file` are treated as `-file` arguments.
`-file` file	Files and directories (nonlibrary elements) to check in. Names listed without `-lib` or `-file` are treated as `-file` arguments.

gdmco

gdmco [-cdslib file] [-recurse] [-xtra str] [-version version] [-name <tagname>] [-optimize] [-help] [-lib lib.cell:view/file] [-file file] ...

Description

Checks out specified files. Makes files in the workarea available for editing. Co-managed files are checked out in the same grouping in which they were checked in. Co-managed set behavior applies only when directories or files are specified as library elements; that is, with the -lib argument.

Arguments

`-cdslib` file	Specifies the library definition file to be used for mapping library names to library directories.
`-recurse`	If a nonlibrary specification is a directory name, by default it refers only to the files immediately below that directory. If the argument -recurse is present anywhere on the command line, it refers to the entire tree of files under that directory.
`-xtra` str	Allows additional arguments, specific to the design management checkout command, to be passed through `gdmco` to that command.
`-version` version	Value is a specific design management string representing the version from which this file is derived.
`-name <tagname>`	Allows you to check out the file from the `version` with the given tagname.
`-optimize`	Skips some calls to the design management system to improve performance. Specifically, when you check out library elements or files, GDM first asks the DM system to expand the library element or directory and return the status of the files to the server. With the `-optimize` argument, GDM expands the library element or directory on the client side and sends the list to the server, thus skipping the extra call to the DM system.
`-help`	Displays information about this command and its arguments.
`-lib` lib.cell:view/file
	Library elements to check out. Names listed without `-lib` or `-file` are treated as `-file` arguments.
`-file` file	Files and directories (nonlibrary elements) to check out. Names listed without `-lib` or `-file` are treated as `-file` arguments.

gdmdelete

gdmdelete [-cdslib file] [-xtra str] [-local] [-help][-recurse]
[-lib lib.cell:view/file] [-file file] ...

Description

Deletes files both from the work area and from the default configuration. If deleted from the default configuration, gdmupdate does not place the file in your workarea. The file is hidden from future use.

Arguments

`-cdslib` file	Specifies the library definition file to be used for mapping library names to library directories.
`-xtra` str	Allows additional arguments, specific to the design management delete command, to be passed through `gdmdelete` to that command.
`-local`	Deletes files from your work area. Files in the repository are not deleted.
`-help`	Displays information about this command and its arguments.
`-recurse`	If a nonlibrary specification is a directory name, by default it refers only to the files immediately below that directory. If the argument -recurse is present anywhere on the command line, it refers to the entire tree of files under that directory.
`-lib` lib.cell:view/file
	Library elements to delete. Names listed without `-lib` or `-file` are treated as `-file` arguments.
`-file` file	Files and directories (nonlibrary elements) to delete. Names listed without `-lib` or `-file` are treated as `-file` arguments.

gdmexport

gdmexport [-cdslib file] [-recurse] [-xtra str] 
[-lib lib.cell:view/file | -file file] ... -destination path 
[-version identifier] [-complete] [-exportpaths] [-help]

Description

Exports files from the design management system data repository to the destination you specify. The destination can be a directory or a file; it can be a filename only if the file already exists and if you are exporting only one file.

When you export a library or cell directory, all the managed files in the library or cell are exported. When you export a view directory, only the co-managed files in the view are exported. Co-managed files are exported in the same grouping in which they were checked in. To export all the managed files in a view directory, use the -complete argument.

When you a export a directory that is not a Cadence library element, only the files in the directory are exported. Files in subdirectories are not exported unless you use the -recurse argument.

The gdmexport command does not affect the data in the design management system.

The gdmexport command calls the xxxexport command, which implements your design management system’s export of data. The xxxexport command should take the following arguments:

xxxexport -destination path [-version identifier] [-exportpaths]

Arguments

`-cdslib` file	The library definition file to be used for mapping library names to library directories.
`-recurse`	Exports the entire tree of files under the source directory. The files are copied to the destination directory. The source directory tree structure is not created in the destination directory unless you also specify the `-exportpaths` argument. If you do not use the `-recurse` argument, only the files in the top directory are exported; files in subdirectories are not exported. When you export a Cadence library element (such as a library or cell), the entire tree of files under the directory is exported, even if you do not use the `-recurse` argument
`-xtra` str	Allows additional arguments, specific to the xxx`export` command, to be passed through `gdmexport` to that command.
`-lib` lib.cell:view/file `\|` `-file` file
	`-lib:` Library elements to export. All names that follow `-lib` and are before the next `-`argument are assumed to be library elements. `-file`: Files and directories (nonlibrary elements) to export. All names that follow `-file` and are before the next `-`argument are assumed to be files. All the files in the directory you specify are exported. Files in subdirectories are not exported unless you specify the `-recurse` option. The source directory tree structure is not created in the destination directory unless you also specify the `-exportpaths` argument.
`-destination` path	The location to which you want to export the files. You must specify this argument. If the path you specify does not exist, GDM creates the missing directories. You can specify a directory or a file as the destination. The destination can be a file only if it already exists and if you are exporting only one file. If the destination is an existing file, `gdmexport` overwrites its contents.
`-version` identifier
	A string representing the version of the files to be exported. The value of `version` depends on the design management system you are using. For example, if you use Team Design Manager, the value of `version` would be one of the following: a version number, the string `current`, or the string `local`. If a file does not have the version you specify, it is not exported.
`-complete`	Specifies that all managed files in view directories should be exported, instead of only the co-managed set of files.
`-exportpaths`	Creates the directory tree structure of the source directory in the destination directory. If you do not use `-exportpaths`, all the files are copied in the destination directory but subdirectories are not created. See also the descriptions for `-recurse` and
`-help`	Displays information about this command and its arguments.

Examples

gdmexport -lib LIB1.cell1:schematic -destination /tmp/tmplib/cell1/schematic

Exports the current version of the schematic to the directory /tmp/tmplib/cell1/schematic.

gdmexport -file myfile -version 3 -destination /tmp/

Exports version 3 of myfile to /tmp/.

gdmexport -lib LIB1.cell1 -version 7 -destination /tmp/tmplib/ 
           -exportpaths -recurse

Exports all the files in cell1, including the files in subdirectories under cell1, that have a version 7.

gdmhistory

gdmhistory [-cdslib <filename>] [-lib lib.cell:view/file] [-file <file>] [-xtra <str>] [-full] [-author] [-size] [-last nn|-all] [-header] [-status] [-parent] [-long] [-labels]

Description

Returns information about the version history of a file. The library and file arguments must specify only one file.

Arguments

`-cdslib` <filename>	Specifies the library definition file to be used for mapping library names to library directories.
`-lib` lib.cell:view/file
	Library elements for which to get their histories. Names listed without `-lib` or `-file` are treated as `-file` arguments.
`-file <`file>	Files and directories (nonlibrary elements) for which to get their histories. Names listed without `-lib` or `-file` are treated as `-file` arguments.
`-xtra <`str>	Allows additional arguments, specific to the design management history command, to be passed through `gdmhistory` to that command.
`-full`	Full description is printed on separate lines from the other information.
`-author`	Name of the author of the file.
`-size`	Size of the file.
`-last` nn\|-all	Takes a numeric option. Prints each version number and date and the first several characters of the history up to the given number of versions.
`-header`	Header of the history output.
`-status`	Status of the file.
`-parent`	Returns the version from where the current version is derived from. For example, if the current version is 1.5 and it is derived from 1.4, then `-parent` will display the version as 1.4 in the `gdmhistory` command line. The `-parent` argument is always on by default, so that the returned data of version, date, and description will be displayed.
`-long`	Ignores any given options, but will return all the options on the list.
`-labels`	Will return any labels/names attached to the version by calling the `gdmsetname` API.

Examples

gdmhistory -file my_lib/my_cell/schematic/sch.oa -author -header

=> ${CWD}/my_lib/my_cell/schematic/sch.oa

Derived       Version        From Date                                Author          Desc

1.2                1.1        Mon Nov 11 14:30:32 GMT 2019 userA  [NO_COMMENT]

The output shows information about version 1.2 that was derived from version 1.1 (for example, the checked out version) created by the user userA on the listed date. No check in comment is included.

This information is according to the expected output of the example. However, the availability of the information is dependent on a DM system’s support for GDM features.

When the -file filePath option is used with gdmhistory, the data is examined as a relatively located file, and there is no name mapping. This distinction is important because when you specify a file inside a library, the mapped names for the library, cell, or view required by the -lib option might differ from the non-mapped names required by the -file option.

gdmimport

gdmimport srcLib targetPath [-help]

Description

Copies a Cadence library (srcLib) into the current workarea (targetPath).

Arguments

srcLib	The source library.
targetPath	The workarea path to which you want to copy the library.
`-help`	Displays information about this command and its arguments.

gdmregprint

gdmregprint [-help] [-version] [-indexName index_name]
  [-dataFormat] [-library] [-cell]

Description

Examines the registry entries that are design management related and visible to the Cadence tool.

The gdmregprint command must run from the same directory where the Cadence tool is executed because files in the current working directory can affect the registry entries.

When no arguments are specified, the help information is displayed.

Arguments

`-help`	Displays information about this command and its arguments.
`-version`	Displays version information for the `gdmregprint` command.
`-indexName` index_name	Contains statements to use instead of the `.reg` files content, which is available in the same directory. If the index file is not found, content from the `.reg` files is read. To create an index file, add the`.idx` suffix to the specified name.
`-dataFormat`	Displays the pattern property and property information for the `dataFormat` entries that contain one or both of the following properties: `Co_Managed` `Also_Managed`
`-library`	Displays the `Also_Managed` property information for the library entry. If the property is not defined, library information is not displayed.
`-cell`	Displays the `Also_Managed` property information for the cell entry. If the property is not defined, cell information is not displayed.

gdmsetdefver

gdmsetdefver -version version [-cdslib file] [-xtra str] [-name tag] [-help]
[-lib lib.cell:view/file] [-file file] ...

Description

Associates the given version to the specified set of files currently in the workarea. Action is DM system specific. For TDM, this command sets the specified version as the default version.

Arguments

`-version` version	Gives the version of the file. Value is a specific design management version identifier. The file list must be a single file or a single co-managed set.
`-cdslib` file	Specifies the library definition file to be used for mapping library names to library directories.
`-xtra` str	Allows additional arguments, specific to the design management command, to be passed through `gdmsetdefver` to that command.
`-name` tag	Corresponds to a tag specification in RCS wraps, or a release name in TDM.
`-help`	Displays information about this command and its arguments.
`-lib` lib.cell:view/file
	Library elements for which to set the default version. Names listed without `-lib` or `-file` are treated as `-file` arguments.
`-file` file	Files and directories (nonlibrary elements) for which to set the default version. Names listed without `-lib` or `-file` are treated as `-file` arguments.

gdmsetname

gdmsetname -name tag [-cdslib file] [-xtra str] [-recurse] [-version version]
[-help] [-lib lib.cell:view/file] [-file file] ...

Description

Associates the given name to the specified set of files currently in the workarea.

Arguments

`-name` tag	Corresponds to a tag specification in RCS wraps. DM-specific symbolic name string.
`-cdslib` file	Specifies the library definition file to be used for mapping library names to library directories.
`-xtra` str	Allows additional arguments, specific to the design management command, to be passed through `gdmsetname` to that command.
`-recurse`	If a nonlibrary specification is a directory name, by default it refers only to the files immediately below that directory. If the argument -recurse is present anywhere on the command line, it refers to the entire tree of files under that directory.
`-version` version	Value is a specific design management version identifier. For some design management systems, a missing file list is legal if `-name` is used. The file list must be a single file or a single co-managed set.
`-help`	Displays information about this command and its arguments.
`-lib` lib.cell:view/file
	Library elements for which to set name. Names listed without `-lib` or `-file` are treated as `-file` arguments.
`-file` file	Files and directories (nonlibrary elements) for which to set `name`. Names listed without `-lib` or `-file` are treated as `-file` arguments.

gdmstatus

gdmstatus [-cdslib file] [-lib lib.cell:view/file] [-file file] [-xtra str]
[-workarea] [-repository] [-civersion] [-coversion] [-updateversion] [-needupdate] [-cachedok] [-status] [-header] [-absolute] [-modified] [-where] [-recurse] [-help]

Description

Returns the design management status of files. If no file is present, the command operates on the current directory with -recurse.

Arguments

`-cdslib` file	Specifies the library definition file to be used for mapping library names to library directories.
`-lib` lib.cell:view/file
	Specifies the library elements. Names listed without `-lib` or `-file` are treated as `-file` arguments.
`-file` file	Specifies the files and directories (non-library elements) that need have their check out canceled. Names listed without `-lib` or `-file` are treated as `-file` arguments.
`-xtra` str	Allows additional arguments, specific to the design management status command, to be passed through `gdmstatus` to that command.
`-workarea`	Shows the specifications of the files present in the specified location.
`-repository`	Shows information, such as the files to be managed, where they are stored, and which views are accessible.
`-civersion`	Shows the `checkin` version.
`-coversion`	Shows the `checkout` version.
`-updateversion`	Shows the update version.
`-needupdate`	Indicates if the file needs to be updated. Returns one of the following: `outOfDate`: The file is out-of-date and an update is required in the cellview. `upToDate`: The file is up-to-date and no update is required in the cellview. <blank space>: DM does not support this feature.
`-cachedok`	Indicates to the DM to accept the cached status value information when querying the files. This option is recommended only when the speed for querying the files has the highest priority.
`-status`	Shows the status.
`-header`	Shows the header.
`-absolute`	Shows the absolute name from the slash ( / ). Otherwise, the output is relative to the current directory or as a library specification.
`-modified`	Displays the filename followed by an asterisk ( * ) if it is modified, or the filename followed by a question mark ( ? ) if its modification status is unknown.
`-where`	Asks GDM for both the `COLOC` and `COWHO` status. If `COLOC` is returned, it is displayed; otherwise, the `COWHO` string is displayed.
`-recurse`	Refers only to the files immediately below the directory, if the non-library specification is a directory name. If the argument -recurse is present anywhere on the command line, it refers to the entire tree of files under that directory.
`-help`	Displays information about this command and its arguments.

Example

Returns outOfDate. The master.tag file needs to be updated in the <rodTrLib | Design | layout> cellview.

gdmstatus -lib rodTrLib.Design:layout/master.tag –needupdate

=> outOfDate

gdmsubmit

gdmsubmit [-cdslib file] [-recurse] [-xtra str] [-description des_str]
[-dfile file] [-name name] [-includeco] [-initial] [-help]
[-lib lib.cell:view/file] [-file file] ...

Description

Submits files for a release; DM specific.

Arguments

`-cdslib` file	Specifies the library definition file to be used for mapping library names to library directories.
`-recurse`	If a nonlibrary specification is a directory name, by default it refers only to the files immediately below that directory. If the argument -recurse is present anywhere on the command line, it refers to the entire tree of files under that directory.
`-xtra` str	Allows additional arguments, specific to the design management submit command, to be passed through `gdmsubmit` to that command.
`-description` des_str
	Cannot be used with `-dfile`. The string `"str"` is used as the description for the `submit` operation.
`-dfile` file	Cannot be used with `-description`. Use `-dfile` to enter a multiline description. The contents of the file named are used as the description for the `submit` operation. Co-managed files in a view are always submitted as a group. Co-managed set behavior applies only to views when the view is specified as a library entry, such as `-lib lib.cell:view.`
`-name` name	Integration request name for TDM.
`-includeco`	Includes checked out files in the submission.
`-help`	Displays information about the command and its arguments.
`-lib`	Library elements for which to submit. Names listed without `-lib` or `-file` are treated as `-file` arguments.
`-file`	Files and directories (nonlibrary elements) for which to submit. Names listed without `-lib` or `-file` are treated as `-file` arguments.

gdmupdate

gdmupdate [-cdslib file] [-recurse] [-xtra str] -name relName [-byname]
[-version fileversion] [-force] [-help] [-lib lib.cell:view/file]
[-file file] ...

Description

Makes files in the workarea available for reading. Updates co-managed files in the same grouping they were checked in with. Cancels the checked-out status of files in the workarea only if -force is used.

Arguments

`-cdslib` file	Specifies the library definition file to be used for mapping library names to library directories.
`-recurse`	If no file list is present, the command operates on the current directory with `-recurse` unless `-byname` is used.
`-xtra` str	Allows additional arguments, specific to the design management update command, to be passed through `gdmupdate` to that command.
`-name` relName	Corresponds to a tag specification in RCS wraps or a release name in TDM. This is a required field. Do not use `-name` if the name request is non-NULL but an empty string.
`-byname`	Can only be used with `-name`, and only with some design management systems. It specifies use of the complete set of files indicated by `-name`.
`-version` fileversion
	Value is a specific design management version identifier. For some design management identifier systems, a missing file list is legal if `-name` is used. File list must only be a single file or view. A single file can be specified with a path, or as an explicit file in a library, cell, or view.
`-force`	Performs the update even if it overwrites modified files. GDM deletes modified files and makes sure that none are checked out. Receives the `-force` argument because TDM uses it to affect version selection for the update. Most design management wraps ignore it. Tells GDM to update files even if modifications are overwritten by doing so. If `-force` is not present and any modified files are present, the command gives an error.
`-help`	Displays information about this command and its arguments.
`-lib` lib.cell:view/file
	Library elements for which to update. Names listed without `-lib` or `-file` are treated as `-file` arguments.
`-file` file	Files and directories (nonlibrary elements) for which to update. Names listed without `-lib` or `-file` are treated as `-file` arguments.

`LD_LIBRARY_PATH`	on Sun
`LIBPATH`	on IBM RS
`LD_LIBRARY_PATH`	on Linux

Cadence Application Infrastructure User GuideProduct Version IC23.1, November 2023

8

Generic Design Management (GDM) Commands

GDM Concepts

Using Third-Party GDM Integrations

GDM Environment Variables

Related Topics

Common Arguments for GDM Commands

The -lib and -file Arguments

Important Points to Note

The -recurse Argument

The -cdslib Argument

The -xtra Argument

The -help Argument

Related Topics

Common Arguments for DM Commands

Related Topics

GDM Commands

Case Sensitivity

Related Topics

gdmcancel

Description

Arguments

Related Topics

gdmci

Description

Arguments

Related Topics

gdmco

Description

Arguments

Related Topics

gdmdelete

Description

Arguments

Related Topics

gdmexport

Description

Arguments

Examples

Related Topics

gdmhistory

Description

Arguments

Examples

Related Topics

gdmimport

Description

Arguments

Related Topics

gdmregprint

Description

Arguments

Related Topics

gdmsetdefver

Description

Arguments

Related Topics

gdmsetname

Description

Arguments

Related Topics

gdmstatus

Description

Arguments

Example

Related Topics

gdmsubmit

Description

Arguments

Related Topics

gdmupdate

Description

Arguments

Related Topics

Cadence Application Infrastructure User Guide
Product Version IC23.1, November 2023