Using LAYOUT INPUT EXCEPTION SEVERITY to change an error to a warning (Non a-string for TEXTSTRING as an example)

Document created by chris_balcom on Jun 26, 2012
Version 1Show Document
  • View in full screen mode

The LAYOUT INPUT EXCEPTION SEVERITY statement can be used in a rule file to control the error or warning behavior in many situations. Certain situations that would cause an error to be reported can be downgraded to "warnings" or even ignored if you wish. One example is the following error that can be encountered while reading a file into Calibre:


ERROR: Non a-string for TEXTSTRING record in input file


The related layout input exception controlling the behavior for this particular situation is "TEXTSTRING_ASTRING". You might consider adding the following statement to the rulefile:




This changes the fatal error to a warning, allowing the job to continue while also providing specific information about the problem labels so that they can be modified in the layout database if desired. The default value for this statement is "2" which indicates a fatal error should be output. The value "1" is used if you prefer to see just a warning. There are many other LAYOUT INPUT EXCEPTION SEVERITY possibilities for many situations, all documented in the SVRF manual.


(Note on the particular error used in this example... this error may be reported for the OASIS file, but not a corresponding GDS file, because the checking can be more stringent for OASIS)



Content © Copyright 1995-2012 Mentor Graphics Corp, All rights reserved.

Product names are trademarks and/or ® registered trademarks of their respective owners.