Neoflash,

Although in general it's not that difficult. Spectre is able to read HSPICE syntax netlists, although you'd want to specify the analysis statements in spectre syntax. The simplest way of doing this would probably be to do something like:
Code:

//
include "design.ckt"
pss pss fund=10M ...
 

Spectre syntax is very simple, as it's pretty regular. Instances and analyses are of the form:

instanceName [(conn1 conn2 ...)] component param1=val1 param2=val2

where component is the name of the device, subckt, model or analysis that you're instantiating, instanceName is a unique name for the instance, you have an optional list of connections to the component or analysis (the square brackets are there to show it's optional, but you should include any connections in parentheses), and then followed by param=value pairs. For more details on any component or analysis, you can use "spectre -h" and "spectre -h component" (e.g. "spectre -h pss").

You should be able to find examples on this forum, and also (say) in the
http://www.designers-guide.org/Analysis/sc-filters.pdf paper on this site.

Sheldon was really just advising a bit of caution though, because you need to ensure model compatibility, and potentially case sensitivity can bite you. So still worth talking to your local Cadence support.

Regards,

Andrew.