Hi Cal, I believe what you are referring to is a message that appears in the operating point information that HSPICE outputs to the *.lis file. It's a warning that HSPICE truncated the node names so that the formatting of the operating point information is readable. HSPICE did not truncate the names during the simulation. The warning has been around for a few years but, the reason it exists is because it's a way (not a really good one) of dealing with a legacy thing left over from the days when node and element names were restricted to 16 characters. In the 2003.09 release, the default for the LENNAM option is increased to 16 characters and it can be set to 1024 characters which is also the maximum node and element name length. So, in this case if .option LENNAM=40 is set, the operating point information will be printed with complete node names and the formatting of the *.lis file will change in order to keep the output readable and accommodate the complete node name. Tracy Barclay CAE Synopsys, Inc. -----Original Message----- From: si-list-bounce@xxxxxxxxxxxxx [mailto:si-list-bounce@xxxxxxxxxxxxx]On Behalf Of Calin Brabandt Sent: Wednesday, November 12, 2003 17:33 To: si-list@xxxxxxxxxxxxx Subject: [SI-LIST] HSPICE Problem: **warning** element name <oldname> is truncated as <newname> I have an HSPICE I/O buffer model library. If I run it in a simple testbench (driver into a testload or a simple dirver/receiver pair), it runs correctly. If I run it in a large deck with a full chipset, it truncates and renames hundreds or even thousands of nodes in my library model and many node names lose their uniqueness. The result is the netlist is converted into a large and non-functional, shorted wad. The node names are about 30-40 chars in length. Im running Synopsys 2002.2.2 and I've tried 2003.3. Am I hitting some kind of environment limit on node name buffer space? Thanks, Cal Brabandt __________________________________ Do you Yahoo!? Protect your identity with Yahoo! Mail AddressGuard http://antispam.yahoo.com/whatsnewfree ------------------------------------------------------------------ To unsubscribe from si-list: si-list-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field or to administer your membership from a web page, go to: //www.freelists.org/webpage/si-list For help: si-list-request@xxxxxxxxxxxxx with 'help' in the Subject field List technical documents are available at: http:/www.si-list.org List archives are viewable at: //www.freelists.org/archives/si-list or at our remote archives: http://groups.yahoo.com/group/si-list/messages Old (prior to June 6, 2001) list archives are viewable at: http://www.qsl.net/wb6tpu ------------------------------------------------------------------ To unsubscribe from si-list: si-list-request@xxxxxxxxxxxxx with 'unsubscribe' in the Subject field or to administer your membership from a web page, go to: //www.freelists.org/webpage/si-list For help: si-list-request@xxxxxxxxxxxxx with 'help' in the Subject field List technical documents are available at: http:/www.si-list.org List archives are viewable at: //www.freelists.org/archives/si-list or at our remote archives: http://groups.yahoo.com/group/si-list/messages Old (prior to June 6, 2001) list archives are viewable at: http://www.qsl.net/wb6tpu