F

Design Data Translators Environment Variables

This appendix covers the design data translators-specific environment variable names, descriptions, types, and values.

You can set the environment variables in the following three ways:

Within the .cdsenv File
Within the .cdsinit File
In the CIW

.cdsenv File

Add environment variables to the.cdsenv file when the settings are applied while launching Layout XL.

Use the following syntax:

xstream environmentVariableName dataType value

For example:

xstream XST_AUTO_LOAD_TEMPLATE_NAME 'string /home/user1/strmIn.tl

.cdsinit File

Like the .cdsenv file, the environment variable settings saved in the .cdsinit file get applied when you launch Layout XL.

Use the envSetVal() command, which has the following syntax, to add environment variables to the .cdsinit file:

envSetVal("xstream" "XST_AUTO_LOAD_TEMPLATE_NAME" 'string "/home/user1/strmIn.tl")

The datatType should be preceeded with a single quote, else the command will not work. Also, if datatType is string, enclose its value within double qoutes.

CIW

Use the envSetVal() command in the CIW to set an environment variable for the duration of the current session. The syntax is the same as described above for the .cdsinit file.

Alternatively, to set environment variables for a single session, you can include the envSetVal() command in any Cadence SKILL file that you load.

If you use the CIW to set an environment variable that controls a widget on the currently open form, the implemented settings get reflected only after you close the form and then re-open it.

Displaying the Current Value of an Environment Variable

To determine the current value of any Layout XL environment variable, use the following syntax in the CIW.

envGetVal("xstream" "environmentVariableName")

For example:

("xstream" "XST_AUTO_LOAD_TEMPLATE_NAME")

Setting Shell Environment Variables

To set Shell environment variables, use the following syntax before starting the Virtuoso session:

setenv environmentVariableName

For example:

setenv XST_AUTO_LOAD_TEMPLATE_NAME ""

List of Design Data Translators Environment Variables

This section covers the following design data environment variables:

XStream SKILL Environment Variables

XStream Fast Export SKILL Environment Variables

XStream Shell Environment Variables

XOasis SKILL Environment Variables

XOasis Fast Export SKILL Environment Variables

XOasis Shell Environment Variables

XST_AUTO_LOAD_TEMPLATE_NAME

xstream XST_AUTO_LOAD_TEMPLATE_NAME string "template_file_name"

Description

Loads the specified template file.

The default is "", which loads the default template file.

Setting the Default Information in XStream

You can set the default values of XStream In and XOasis Out options by using the XST_IN and XST_OUT environment variables along with XST_AUTO_LOAD_TEMPLATE_NAME. The following table summarizes the various possibilities and the behavior.

Template File Specified in the XST_IN/XST_OUT Environment Variables	Default values specified in the XST_AUTO_LOAD_ TEMPLATE_NAME Environment Variable	Command Line
Yes	default	In the first invocation, loads the template file pointed by the XST_IN/XST_OUT environment variable. In subsequent invocations, loads the values from its previous session.
No	default	In the first invocation, loads the GUI with empty fields because no template file is specified in the XST_IN/XST_OUT environment variable. In subsequent invocations, it loads the values from its previous session.
Yes	`""`	Always loads the template file pointed by the XST_IN/XST_OUT environment variables.
No	""	Always loads the GUI with empty fields because no template file is specified in the XST_IN/XST_OUT environment variable and it does not retain the values of the previous session.

GUI Equivalent

None

Examples

envGetVal("xstream" "XST_AUTO_LOAD_TEMPLATE_NAME")

envSetVal("xstream" "XST_AUTO_LOAD_TEMPLATE_NAME" 'string "")

XST_IN

xstream XST_IN string "template_file_path"

Description

Specifies the path for the template file to be used during XStream In translation.

The default is "".

You can set the default values of the XStream In option by using the XST_IN environment variable. This variable contains the path to the XStream In template file. The template file consists of the values for different XStream In options. Therefore, each time you run XStream In, the values of these options are taken from the template files and the path of the template file is taken from the XST_IN environment variables.

You can use the XST_IN environment variables while running XStream from GUI. For example, set XST_IN and invoke XStream In by using the following command:

setenv XST_IN /home/user1/templateIn.txt

XStream In is invoked in the interactive mode and the values of XStream In options are taken from the templateIn.txt template file specified in the XST_IN environment variable.

You can set XST_IN in your .cdsenv file by using the following command:

xstream XST_IN string "/home/user1/strmIn.tl"

For more information, about setting default values in XStream In using environment variables, see Setting the Default Information in XStream.

GUI Equivalent

None

Examples

envGetVal("xstream" "XST_IN")

envSetVal("xstream" "XST_IN" 'string "/home/user1/templateIn.txt")

XST_OUT

xstream XST_OUT string "template_file_path"

Description

Specifies the path for the template file to be used during XOasis Out translation. The environment variable also helps in retaining the last successful translation option settings for next Virtuoso session.

The default is "".

You can set the default values of the XOasis Out option by using the XST_OUT environment variable. This variable contains the path to the XOasis Out template file. The template file consists of the values for different XOasis Out options. Therefore, each time you run XOasis Out, the values of these options are taken from the template files and the path of the template file is taken from the XST_OUT environment variables.

You can use the XST_OUT environment variables while running XStream from GUI. For example, set XST_OUT and invoke XOasis Out by using the following command:

setenv XST_OUT /home/user1/templateOut.txt

XOasis Out is invoked in the interactive mode and the values of XOasis Out options are taken from the templateOut.txt template file specified in the XST_OUT environment variable.

You can set XST_OUT in your .cdsenv file by using the following command:

xstream XST_OUT string "/home/user1/strmOut.tl"

For more information, about setting default values in XOasis Out using environment variables, see Setting the Default Information in XStream.

GUI Equivalent

None

Examples

envGetVal("xstream" "XST_OUT")

envSetVal("xstream" "XST_OUT" 'string "/home/user1/strmIn.tl")

xstAlwaysLookupMapFilesInTech

xstream xstAlwaysLookupMapFilesInTech boolean { t | nil }

Description

Specifies whether the XStream automatically opens the technology library including ITDB hierarchy to search for map files in the technology libraries. If the technology library is already open, then setting this variable has no effect.

Fields for map files, if empty, are always automatically populated when technology library is already open in the current Virtuoso session. However, if the technology library is not open in the current Virtuoso session then XStream, by default, will open the technology library including the ITDB hierarchy to search for the map files ('<techlibname>.layermap' for layer map file, '<techlibname>.objectmap' for object map file, and '<techlibname>.labelmap' for label map file). Opening the technology library can take some time. Default behavior of opening the technology library including ITDB can be disabled by setting the value of this environment variable to nil.

This setting only prevents auto population of layer map files in GUI. Translation will still traverse through all the technology libraries to search for layer map files.

The default is t.

GUI Equivalent

None

Examples

envGetVal("xstream" "xstAlwaysLookupMapFilesInTech")

envSetVal("xstream" "xstAlwaysLookupMapFilesInTech" 'boolean t)

envSetVal("xstream" "xstAlwaysLookupMapFilesInTech" 'boolean nil)

xstEnableGUIHistory

xstream xstEnableGUIHistory boolean { t | nil }

Description

Saves the GUI history that lets you use the last preserved GUI history at command line. This environment variable also helps in retaining the option settings used during the last successful translation in the next Virtuoso session.

The default is nil, which means that the GUI history is not saved.

GUI Equivalent

None

Examples

("xstream" "xstEnableGUIHistory")

envSetVal("xstream" "xstEnableGUIHistory" 'boolean t)

envSetVal("xstream" "xstEnableGUIHistory" 'boolean nil)

xstHideMapAllColorToLocked

xstream xstHideMapAllColorToLocked boolean { t | nil }

Description

Hides the Map All Colors to Locked option.

The default is t, which means that the Map All Colors to Locked option is hidden.

GUI Equivalent

None

Examples

envGetVal("xstream" "xstHideMapAllColorToLocked")

envSetVal("xstream" "xstHideMapAllColorToLocked" 'boolean t)

envSetVal("xstream" "xstHideMapAllColorToLocked" 'boolean nil)

xstIgnoreCoveredViaShapes

xstream xstIgnoreCoveredViaShapes boolean { t | nil }

Description

Specifies whether standard via shapes covered by another shape on the same LPP should be exported during XOasis Out translation. The default is nil, which means that all standard via shapes are exported during XOasis Out translation.

When set to t, XOasis Out does not export standard via shapes if there is another shape on the same LPP inside the same standard via master that covers the first shape completely. This may happen in local-interconnect vias (with cut layer equal to either layer1 or layer2).

This option does not work with the -flattenVias option.

GUI Equivalent

None

Examples

envGetVal("xstream" "xstIgnoreCoveredViaShapes")

envSetVal("xstream" "xstIgnoreCoveredViaShapes" 'boolean t)

envSetVal("xstream" "xstIgnoreCoveredViaShapes" 'boolean nil)

xstInOverwriteLibPopup

xstream xstInOverwriteLibPopup boolean { t | nil }

Description

Enables a warning message that is displayed during the XStream In translation to an existing library to warn you that cells in the target library will be overwritten or appended to in this process.

This message is displayed when Write Mode is set to overwrite or append.

The default is nil.

GUI Equivalent

None

Examples

envGetVal("xstream" "xstInOverwriteLibPopup")

envSetVal("xstream" "xstInOverwriteLibPopup" 'boolean t)

envSetVal("xstream" "xstInOverwriteLibPopup" 'boolean nil)

xstOutAutoPopulateIfEmptyLCV

xstream xstOutAutoPopulateIfEmptyLCV boolean { t | nil }

Description

Specifies whether the Stream File, Library, TopCell(s), and View(s) fields on the XOasis Out main form should be filled automatically only when they are empty. If these fields already have some information and if the environment variable is set to t, then this information is not replaced even if a cellview is open.

The default is nil.

GUI Equivalent

None

Examples

envGetVal("xstream" "xstOutAutoPopulateIfEmptyLCV")

envSetVal("xstream" "xstOutAutoPopulateIfEmptyLCV" 'boolean t)

envSetVal("xstream" "xstOutAutoPopulateIfEmptyLCV" 'boolean nil)

xstShowCompletionMsgBox

xstream xstShowCompletionMsgBox boolean { t | nil }

Description

Specifies whether the Stream in translation complete message box should display the number of errors and warnings after the translation is complete.

The default is t.

GUI Equivalent

Command	Virtuoso XOasis Out – More Options – General –
Field	Show Completion Message Box

Examples

envGetVal("xstream" "xstShowCompletionMsgBox")

envSetVal("xstream" "xstShowCompletionMsgBox" 'boolean t)

envSetVal("xstream" "xstShowCompletionMsgBox" 'boolean nil)

strmFileExtension

xstream strmFileExtension string "Extension_Added_to_GDS_Files"

Description

Specifies the file extension to be added to the output top cell file name when the XStream Out translation is done using the Layout XL — File — Export Stream from VM option.

The default is gds.

This environment variable replaces xstOutExt. Support for the xstOutExt environment variable will be removed in a future release. Instead use strmFileExtension.

GUI Equivalent

None

Examples

envGetVal("xstream.fastExport" "strmFileExtension")

envSetVal("xstream.fastExport" "strmFileExtension" 'string "sf")

convertPin

xstream.fastExport convertPin string { "geometry" | "text" | "geometryAndText" | "ignore" }

Description

Specifies whether pins should be translated as geometries or text when Stream files are exported using the Layout XL – File – Export Stream from VM command.

The default is geometry.

GUI Equivalent

None

Examples

envGetVal("xstream.fastExport" "convertPin")

envSetVal("xstream.fastExport" "convertPin" 'string "text")

envSetVal("xstream.fastExport" "convertPin" 'string "geometry")

envSetVal("xstream.fastExport" "convertPin" 'string "geometryAndText")

envSetVal("xstream.fastExport" "convertPin" 'string "ignore")

layerMap

xstream.fastExport layerMap string { "name_of_layer_map_file" }

Description

Specifies the name of the layer map file to be used when Stream files are exported using the Layout XL – File – Export Stream from VM command.

The default is "".

GUI Equivalent

None

Examples

envGetVal("xstream.fastExport" "layerMap")

envSetVal("xstream.fastExport" "layerMap" 'string "strmLayerMap")

logFile

xstream.fastExport logFile string { name_of_log_file }

Description

Specifies the name of the log file to be used when Stream files are exported using the Layout XL – File – Export Stream from VM command.

The default is "".

GUI Equivalent

None

Examples

envGetVal("xstream.fastExport" "logFile")

envSetVal("xstream.fastExport" "logFile" 'string "strmLogFile")

maxVertices

xstream.fastExport maxVertices int integer

Description

Specifies the maximum number of coordinates for polygons and paths in Stream. Export – Stream divides polygons and paths in DFII that have vertices more than or equal to maxVertices into smaller objects.

Polygons and paths are stored differently in Design Framework II and Stream formats. The DFII database does not store both the start and end points of a polygon because they are the same point. The Stream format requires that both points be stored individually. The maximum limit imposed by the GDSII format is 200 and that by the Stream format is 8191. Therefore, the Stream/GDSII reader writer of each EDA vendor is responsible for handling restrictions imposed by their databases with this option.

The largest DFII polygon or path Export – Stream can process a maximum of 8191 vertices, which translates into 8191 Stream vertices.

Valid Values: 5 to 8191

The default is 200.

Command-line option: maxVertices

GUI Equivalent

None

Examples

envGetVal("xstream.fastExport" "maxVertices")

envSetVal("xstream.fastExport" "maxVertices" 'int 500)

objectMap

xstream.fastExport objectMap string { "name_of_object_map_file" }

Description

Specifies the name of the object map file to be used when Stream files are exported using the Layout XL – File – Export Stream from VM command.

The default is "".

GUI Equivalent

None

Examples

envGetVal("xstream.fastExport" "objectMap")

envSetVal("xstream.fastExport" "objectMap" 'string "strmObjMapFile")

summaryFile

xstream.fastExport summaryFile string { "name_of_summary_file" }

Description

Specifies the name of the summary map file to be used when Stream files are exported using the Layout XL – File – Export Stream from VM command.

The default is "".

GUI Equivalent

None

Examples

envGetVal("xstream.fastExport" "summaryFile")

envSetVal("xstream.fastExport" "summaryFile" 'string "strmObjMapFile")

enableColoring

xstream.fastExport enableColoring boolean { t | nil }

Description

Specifies the value for the enableColoring option when Stream files are exported from Layout XL – File – Export Stream from VM.

The default is nil.

GUI Equivalent

None

Examples

envGetVal("xstream.fastExport" "enableColoring")

envSetVal("xstream.fastExport" "enableColoring" 'boolean t)

envSetVal("xstream.fastExport" "enableColoring" 'boolean nil)

strmFilenameSuffix

xstream.fastExport strmFilenameSuffix string "Suffix_Added_to_Exported_VM_Files"

Description

Specifies the suffix to be added to the names of the Stream files exported using the Layout XL — File — Export Stream from VM command.

The default is "".

This environment variable replaces the xstream environment variable xstExportFromVmFilenameSuffix. Support for the xstExportFromVmFilenameSuffix environment variable will be removed in a future release. Instead use the xstream.fastExport environment variable strmFilenameSuffix.

GUI Equivalent

None

Examples

envGetVal("xstream.fastExport" "strmFilenameSuffix")

envSetVal("xstream.fastExport" "strmFilenameSuffix" 'string "_VM")

strmFilenamePrefix

xstream.fastExport strmFilenamePrefix string "Prefix_Added_to_Exported_VM_Files"

Description

Specifies the prefix to be added to the names of the Stream files exported using the Layout XL – File – Export Stream from VM command.

The default is "".

This environment variable replaces the xstream environment variable xstExportFromVmFilenamePrefix. Support for the xstExportFromVmFilenamePrefix environment variable will be removed in a future release. Instead use the xstream.fastExport environment variable strmFilenamePrefix.

GUI Equivalent

None

Examples

envGetVal("xstream.fastExport" "strmFilenamePrefix")

envSetVal("xstream.fastExport" "strmFilenamePrefix" 'string "VM_")

XStream Shell Environment Variables

XST_ALL_VIEWS

Description

Shows all the views currently listed for the selected cell in the library, cell, and view browser.

Example

setenv XST_ALL_VIEWS ""

XST_AUTO_LOAD_TEMPLATE_NAME

See XST_AUTO_LOAD_TEMPLATE_NAME.

Example

setenv XST_AUTO_LOAD_TEMPLATE_NAME ""

XST_IN

See XST_IN.

Example

setenv XST_IN /home/user1/strmIn.t1

XST_IN_VM_NT

Description

Specifies the number of threads to be used in Virtual Memory mode.

Example

For single thread use:

setenv XST_IN_VM_NT 1

XST_OUT

See XST_OUT.

Example

setenv XST_OUT /home/user1/strmIn.t1

XST_OUT_CC_CHOP

Description

Enables the alternate any-angle fracturing algorithm for any-angle non-CurvyCore polygons. This algorithm, fractures shapes by creating new edges between existing vertices and breaking the shape along the new edge.

By default, the classical fracturing algorithm is used for any-angle non-CurvyCore polygons. In the classic fracturing algorithm, a shape is chopped in half along its x or y axis until all the chopped shapes have fewer than the maximum number of vertices.

The maximum number of vertices is 200 by default and can be specified by user using the -maxVertices option.

The XStream Out translator uses:

The classic fracturing algorithm:
- For polygons with 45 or 90 degree angle edge.
- For all any-angle non-CurvyCore polygons.
The alternate any-angle fracturing algorithm:
- For any-angle CurvyCore polygons. This is enabled by default.
- For all any-angle non-CurvyCore polygons when the SHELL environment variable XST_OUT_CC_CHOP is set.

No special Photonics license is needed to set this variable.

Example

setenv XST_OUT_CC_CHOP

xoasEnableGUIHistory

xoasis xoasEnableGUIHistory boolean { t | nil }

Description

The default is nil, which means that the GUI history is not saved.

GUI Equivalent

None

Examples

envGetVal("xoasis" "xoasEnableGUIHistory")

envSetVal("xoasis" "xoasEnableGUIHistory" 'boolean t)

envSetVal("xoasis" "xoasEnableGUIHistory" 'boolean nil)

XOASIS_AUTO_LOAD_TEMPLATE_NAME

xoasis XOASIS_AUTO_LOAD_TEMPLATE_NAME string "template_file_name"

Description

Loads the specified template file.

The default is "" that loads the default template file.

Setting Default Values in XOasis

You can set the default values of XOasis In and XOasis Out options by using the XOASIS_IN and XOASIS_OUT environment variables along with XOASIS_AUTO_LOAD_TEMPLATE_NAME. The following table summarizes the various possibilities and the behavior.

Template File Specified in the XOASIS_IN/XOASIS_OUT Environment Variables	Default values specified in the XOASIS_AUTO_LOAD_ TEMPLATE_NAME Environment Variable	Command Line
Yes	default	In the first invocation, loads the template file pointed by the XOASIS_IN/XOASIS_OUT environment variable. In subsequent invocations, loads the values from its previous session.
No	default	In the first invocation, loads the GUI with empty fields because no template file is specified in the XOASIS_IN/XOASIS_OUT environment variable. In subsequent invocations, it loads the values from its previous session.
Yes	`""`	Loads the template file pointed by the XOASIS_IN/XOASIS_OUT environment variables.
No	`""`	Loads the GUI with empty fields because no template file is specified in the XOASIS_IN/XOASIS_OUT environment variable and it does not retain the values of the previous session.

GUI Equivalent

None

Examples

envGetVal("xoasis" "XOASIS_AUTO_LOAD_TEMPLATE_NAME")
envSetVal("xoasis" "XOASIS_AUTO_LOAD_TEMPLATE_NAME" 'string "/home/user1/oasIn.tl")

XOASIS_IN

xoasis XOASIS_IN string "template_file_path"

Description

Specifies the path for the template file to be used during XOasis In translation.

The default is "".

The XOASIS_IN environment variable sets the default values of the corresponding options as well as the template files. A template file consists of the values of the XOasis In option. Therefore, each time you run XOasis In, the values for the options are taken from the template files and the path of the template file is taken from the XOASIS_IN environment variables.

You can use the XOASIS_IN environment variable while running XOasis from GUI. For example, set XOASIS_IN and invoke XOasis In by using the following commands:

setenv XOASIS_IN /home/user1/templateIn.txt

XOasis In is invoked in interactive mode and the values of XOasis In options are taken from the templateIn.txt template file specified in the XOASIS_IN environment variable.

You can set XOASIS_IN in your .cdsenv file by using the following command:

xoasis XOASIS_IN string "/home/user1/xoasisIn.tl"

By default, XOasis retains the values of various XOasis In options from its previous session. Let us consider a scenario where the GUI is invoked. If you modify the value in the General tab of the XOasis In Options form to 6 and click the OK button, in the next session value, 6 will be displayed. However, in the session after that, if you modify the value to 3 and click the Cancel button, then the General tab of the XOasis In Options form will retain the previous value, 6.

If you run XOasis in the GUI mode, then the GUI form is populated with the values in the template file specified using these variables at startup. You can override these values by specifying different values explicitly.

Additionally, in case of XOasis in the GUI mode, CDS environment variables take precedence over the UNIX environment variables.

For more information, see Setting Default Values in XOasis.

GUI Equivalent

None

Examples

envGetVal("xoasis" "XOASIS_IN")

envSetVal("xoasis" "XOASIS_IN" 'string "/home/user1/templateIn.txt")

XOASIS_OUT

xoasis XOASIS_OUT string "template_file_path"

Description

Specifies the path for the template file to be used during XOasis Out translation.

The default is "".

The XOASIS_OUT environment variable sets the default values of the corresponding options as well as the template files. A template file consists of the values of the XOasis Out option. Therefore, each time you run XOasis Out, the values for the options are taken from the template files and the path of the template file is taken from the XOASIS_OUT environment variables.

You can use the XOASIS_OUT environment variable while running XOasis from GUI. For example, set XOASIS_OUT and invoke XOasis Out by using the following commands:

setenv XOASIS_OUT /home/user1/templateOut.txt

XOasis Out is invoked in interactive mode and the values of XOasis Out options are taken from the templateOut.txt template file specified in the XOASIS_OUT environment variable.

You can set XOASIS_OUT in your .cdsenv file by using the following command:

xoasis XOASIS_OUT string "/home/user1/xoasisOut.tl"

By default, XOasis retains the values of various XOasis Out options from its previous session. Let us consider a scenario where the GUI is invoked. If you modify the value in the General tab of the XOasis Out Options form to 6 and click the OK button, in the next session value, 6 will be displayed. However, in the session after that, if you modify the value to 3 and click the Cancel button, then the General tab of the XOasis Out Options form will retain the previous value, 6.

Additionally, in case of XOasis in the GUI mode, CDS environment variables take precedence over the UNIX environment variables.

For more information, see Setting Default Values in XOasis.

GUI Equivalent

None

Examples

envGetVal("xoasis" "XOASIS_OUT")

envSetVal("xoasis" "XOASIS_OUT" 'string "/home/user1/strmIn.tl")

xoasAlwaysLookupMapFilesInTech

xoasis xoasAlwaysLookupMapFilesInTech boolean { t | nil }

Description

Specifies whether the XOasis automatically opens the technology library including ITDB hierarchy to search for map files in the technology libraries. If the technology library is already open, setting this variable has no effect.

Fields for map files, if empty, are always automatically populated when technology library is already open in the current Virtuoso session. However, if the technology library is not open in the current Virtuoso session then XOasis, by default, will open the technology library including the ITDB hierarchy to search for the map files ('<techlibname>.layermap' for layer map file, '<techlibname>.objectmap' for object map file, and '<techlibname>.labelmap' for label map file). Opening the technology library can take some time. Default behavior of opening the technology library including ITDB can be disabled by setting the value of this environment variable to nil.

This setting only prevents auto population of layer map files in GUI. Translation will still traverse through all the technology libraries to search for layer map files.

The default is t.

GUI Equivalent

None

Examples

envGetVal("xoasis" "xoasAlwaysLookupMapFilesInTech")

envSetVal("xoasis" "xoasAlwaysLookupMapFilesInTech" 'boolean t)

envSetVal("xoasis" "xoasAlwaysLookupMapFilesInTech" 'boolean nil)

xoasOutAutoPopulateIfEmptyLCV

xoasis xoasOutAutoPopulateIfEmptyLCV boolean { t | nil }

Description

Specifies whether the OASIS File, Library, TopCell(s), and View(s) fields on the XOasis Out main form should be filled automatically only when they are empty. If these fields already have some information and if the environment variable is set to t, this information is not replaced even if a cellview is open.

The default is nil.

GUI Equivalent

None

Examples

envGetVal("xoasis" "xoasOutAutoPopulateIfEmptyLCV")

envSetVal("xoasis" "xoasOutAutoPopulateIfEmptyLCV" 'boolean t)

envSetVal("xoasis" "xoasOutAutoPopulateIfEmptyLCV" 'boolean nil)

xoasInOverwriteLibPopup

xoasis xoasInOverwriteLibPopup boolean { t | nil }

Description

Enables a warning message that is displayed during the XOasis In translation to an existing library to warn you that cells in the target library will be overwritten or appended to in this process.

This message is displayed when Write Mode is set to overwrite or append.

The default is nil.

GUI Equivalent

None

Examples

envGetVal("xoasis" "xoasInOverwriteLibPopup")

envSetVal("xoasis" "xoasInOverwriteLibPopup" 'boolean t)

envSetVal("xoasis" "xoasInOverwriteLibPopup" 'boolean nil)

xoasShowCompletionMsgBox

xoasis xoasShowCompletionMsgBox boolean { t | nil }

Description

Specifies whether the Oasis in translation complete message box should display the number of errors and warnings after the translation is complete.

The default is t.

GUI Equivalent

Command	Virtuoso XOasis Out
Field	Show Completion Message Box

Examples

envGetVal("xoasis" "xoasShowCompletionMsgBox")

envSetVal("xoasis" "xoasShowCompletionMsgBox" 'boolean t)

envSetVal("xoasis" "xoasShowCompletionMsgBox" 'boolean nil)

oasisFileExtension

xoasis oasisFileExtension string "Extension_Added_to_OASIS_Files"

Description

Specifies the file extension to be added to the output top cell file name when the XOasis Out translation is done using the Layout XL — File — Export Oasis from VM option.

The default is oasis.

This environment variable replaces xoasOutExt. Support for the xoasOutExt environment variable will be removed in a future release. Instead use oasisFileExtension.

GUI Equivalent

None

Examples

envGetVal("xoasis.fastExport" "oasisFileExtension")

envSetVal("xoasis.fastExport" "oasisFileExtension" 'string "of")

enableColoring

xoasis.fastExport enableColoring boolean { t | nil }

Description

Specifies the value for the enableColoring option when OASIS files are exported from Layout XL – File – Export Oasis from VM.

The default is nil.

GUI Equivalent

None

Examples

envGetVal("xoasis.fastExport" "enableColoring")

envSetVal("xoasis.fastExport" "enableColoring" 'boolean t)

envSetVal("xoasis.fastExport" "enableColoring" 'boolean nil)

oasisFilenamePrefix

xoasis.fastExport oasisFilenamePrefix string "Prefix_Added_to_Exported_VM_Files"

Description

Specifies the prefix to be added to the names of OASIS files exported from Layout XL — File — Export Oasis from VM.

The default is "".

GUI Equivalent

None

Examples

envGetVal("xoasis.fastExport" "oasisFilenamePrefix")

envSetVal("xoasis.fastExport" "oasisFilenamePrefix" 'string "VM_")

oasisFilenameSuffix

xoasis.fastExport oasisFilenameSuffix string "Suffix_Added_to_Exported_VM_Files"

Description

Specifies the suffix to be added to the names of the OASIS files exported from Layout XL — File — Export Oasis from VM.

The default is "".

GUI Equivalent

None

Examples

envGetVal("xoasis.fastExport" "oasisFilenameSuffix")

envSetVal("xoasis.fastExport" "oasisFilenameSuffix" 'string "_VM")

XOasis Shell Environment Variables

XOASIS_ALL_VIEWS

Description

Shows all views currently listed in a cellview of the selected cell in the library, cell, and view browser.

Example

setenv XOASIS_ALL_VIEWS ""

XOASIS_AUTO_LOAD_TEMPLATE_NAME

See XST_AUTO_LOAD_TEMPLATE_NAME.

Example

setenv XOASIS_AUTO_LOAD_TEMPLATE_NAME ""

XOASIS_IN

See XOASIS_IN.

Example

setenv XOASIS_IN /home/user1/oasIn.t1

XOASIS_IN_VM_NT

Description

Specifies the number of threads to be used in Virtual Memory mode.

Example

For single thread use:

setenv XOASIS_IN_VM_NT

XOASIS_OUT

See XOASIS_OUT.

Example

setenv XOASIS_OUT /home/user1/oasmIn.t1

Return to top

Design Data Translators ReferenceProduct Version IC23.1, November 2023

F

Design Data Translators Environment Variables

.cdsenv File

.cdsinit File

CIW

Displaying the Current Value of an Environment Variable

Setting Shell Environment Variables

List of Design Data Translators Environment Variables

XStream SKILL Environment Variables

XStream Fast Export SKILL Environment Variables

XStream Shell Environment Variables

XOasis SKILL Environment Variables

XOasis Fast Export SKILL Environment Variables

XOasis Shell Environment Variables

XST_AUTO_LOAD_TEMPLATE_NAME

Description

Setting the Default Information in XStream

GUI Equivalent

Examples

Related Topics

XST_IN

Description

GUI Equivalent

Examples

Related Topics

XST_OUT

Description

GUI Equivalent

Examples

Related Topics

xstAlwaysLookupMapFilesInTech

Description

GUI Equivalent

Examples

Related Topics

xstEnableGUIHistory

Description

GUI Equivalent

Examples

Related Topics

xstHideMapAllColorToLocked

Description

GUI Equivalent

Examples

Related Topics

xstIgnoreCoveredViaShapes

Description

GUI Equivalent

Examples

Related Topics

xstInOverwriteLibPopup

Description

GUI Equivalent

Examples

Related Topics

xstOutAutoPopulateIfEmptyLCV

GUI Equivalent

Examples

Related Topics

xstShowCompletionMsgBox

GUI Equivalent

GUI Equivalent

Examples

Related Topics

strmFileExtension

Description

GUI Equivalent

Examples

Related Topics

convertPin

Description

GUI Equivalent

Examples

Related Topics

layerMap

Description

GUI Equivalent

Examples

Related Topics

Design Data Translators Reference
Product Version IC23.1, November 2023