Weird warning messages from SKILL

Hi all,

Does anyone know what these warning messages mean? My code doesn't
touch these functions or variables, yet I get these warnings. (My code
is generating layout using PCells etc.).

*WARNING* envSetVal: Can't set the value of variable
'remasterInstSearchViewText', in tool[.partition] 'layout' - it has
not been registered.

*WARNING* envSetVal: Can't set the value of variable
'remasterInstSearchLibText', in tool[.partition] 'layout' - it has not
been registered.

*WARNING* envSetVal: Can't set the value of variable
'remasterInstCheckTerms', in tool[.partition] 'layout' - it has not
been registered.

*WARNING* envSetVal: Can't set the value of variable
'remasterInstUpdateCellText', in tool[.partition] 'layout' - it has
not been registered.

*WARNING* envSetVal: Can't set the value of variable
'measurementTextHeight', in tool[.partition] 'layout' - it has not
been registered.

*WARNING* envSetVal: Can't set the value of variable
'drdEditDisplayMarkers', in tool[.partition] 'layout' - it has not
been registered.

*WARNING* envSetVal: Can't set the value of variable
'openToStopLevel', in tool[.partition] 'layout' - it has not been
registered.

*WARNING* envSetVal: Can't set the value of variable
'measurementDisplayOn', in tool[.partition] 'layout' - it has not been
registered.

*WARNING* envCyclicStringToIndex: Can't set the value of variable
'drdEditMode', in tool[.partition] 'layout'

(** rest of message obscured **)

Thanks in advance...

--
Regards,

Peter Ballard
Adelaide, AUSTRALIA

 

Peter,

My guess is that you've used IC5033, saved your environment (Utilities->Save
Defaults), and then gone back to an earlier version. These environment variables
were added in IC5033, and so wouldn't be recognised in an earlier release.

Regards,

Andrew.

 

andrew:
Is there any way to track down these cases. I would like to filter this
type out.
(i.e. some funtion to tell me what startup file is using what
configuration stuff so I can remove it ... )


I have (for years) got this type of error. I think it stems from the
envroment setup files saving stuff
that is not in a different environment. (i.e. the source IC tech setup
has all the cadence tools, some poor
user has less and is constantly getting many of these!)

I is a constant source of annnoyance. (mostly because users learn to
ignore pages of warnings and then
miss some fatal error ... )

-- Gerry

 

Thanks Andrew, I'll follow this up.

(Yeah I know this message is a bit of a waste of bandwidth, but I do
appreciate Andrew's contributions).

 

Gerry,

I'm not entirely sure what you're asking, but I'll have a stab at what I
think you might mean...

If it is specifically about .cdsenv files, then the default is to load
the .cdsenv in the <instdir>/tools/dfII/local dir, and then the one
in your home dir. An environment variable CDS_LOAD_ENV controls
further loading options (search documentation to find how this works).

For any release, the cdsenv master files are in:

<instdir>/tools/dfII/etc/tools/*/.cdsenv

If you have an entry in the tools/dfII/local or a user file, which
doesn't exist in one of these master files, it will lead to the errors
and warnings mentioned below.

Andrew.