Suppress: *WARNING* COMBINE attribute library not defined

Hi Aldo

Currently it is not possible to suppress warnings about non-existent libraries. It is actually better to have the warnings so that user can take note of any issues in cds.lib file (e.g. wrong path, lib name, etc).


Best regards
Quek

Hi Quek, 

Thank you for your answer. 

I would like to hide them when I run ocean scripts. Is it possible to address them to NULL standard output?

Thank you 

Best regards 

• Aldo

Aldo,

Why don't you just fix the COMBINE statement so that it doesn't reference non-existent libraries? That's the simplest solution.

Whilst it would be possible to temporarily redirect the woport elsewhere so that warnings don't get displayed, this would affect all warnings, and it won't help in this case because the warnings get output before you have a chance to redirect the warning port.

Regards,

Andrew.

Hi Andrew, 

I don't know how to fix the COMBINE statement. I followed the instructions given in the link reported in my post. How should I modify my cds.lib to fix it? 

Thank you 

Best regards 

Aldo

Hi Aldo

There is no special keyword, etc in the COMBINE statement to ignore non-existent libraries. Hence we have to fix the warning by removing the bad libraries.

Suppose you have the following lines in cds.lib file:

DEFINE lib1 /good-path1/lib1
DEFINE lib2 /good-path2/lib2
DEFINE lib3 /bad-path/lib3

ASSIGN my_category COMBINE lib1 lib2 lib3

The following warning can be found in CIW:

library: 'lib3' file: '.../cds.lib', line: 118


You can resolve the problem as follows:
a. Check the path for lib3 and correct it if necessary
b. If lib3 no longer exists, remove it completely from cds.lib file. E.g.

DEFINE lib1 /good-path1/lib1
DEFINE lib2 /good-path2/lib2

ASSIGN my_category COMBINE lib1 lib2


Best regards
Quek

Hi Quek,

All the libraries define in my cds.lib exist.

The error: "*WARNING* COMBINE attribute library not defined" refers to existing and correctly defined libraries.

I think that the problem is due to the dummy directory with the name of the combined library I'm defining.

In https://community.cadence.com/cadence_blogs_8/b/cic/posts/things-you-didn-t-know-about-virtuoso-library-manager is stated that:

"...To do this (i.e. create combined libraries), first you'll need to create a dummy directory with the name you want to give your combined library..."

Thank you

Happy new year

Aldo

Hi Aldo

It is good to know that you have found the cause of the warning. Have a great 2019. : )

Best regards
Quek

...and I return to the initial point: how can I suppress or remove all the warnings due to the COMBINE attribute when I run ocean scripts??

Best regards

Aldo

Aldo2 said:

...and I return to the initial point: how can I suppress or remove all the warnings due to the COMBINE attribute when I run ocean scripts??

As has been stated before, you can't. You need to fix the problem with the COMBINE attribute. The warning only occurs when one of the libraries in the COMBINE attribute does not exist. I've never seen this occur when the libraries are fully defined correctly. In your OCEAN session, can you do:

ddGetLibList()~>name

and compare the libraries listed with the libraries on the COMBINE statement (both the library being assigned to, plus all the library names after the COMBINE). Note that the warning doesn't seem to occur if the library being ASSIGNed to doesn't exist - it's only if the libraries after the COMBINE statement that cause the problem. Also the point about the dummy directory is only valid if you don't already have a library you can use to ASSIGN to.

Also, which IC subversion are you using (i.e. what does getVersion(t) return)? Just in case this was a bug in some version earlier than the one I'm trying...

Regards,

Andrew.

IC subversion is: IC6.1.7-64b.500.14

Regards,

Aldo