How to call my own procedure which defined in custom .il ,in command line without GUI

Well if you want this procedure to be called as part of the virtuoso start process why don't you just put the call of MyTodo() at the end of MyTodo.il?
Other than that you can just manually type it at the command prompt which you get. Or maybe I'am just misunderstanding what you want to do???

I want parallel run multiple simulations on LSF, so need recall MyTodo() procedure many times

pseudocode maybe like this:

ParallelSim.sh:

loop(VIEWLIST

    bsub "cmd_sim.sh $VIEW $CELL $LIB "

)

cmd_sim.sh :

virtuoso -nograph -restore MyTodo($1 $2 $3) 

The -restore takes a filename, not a function call.

So, in your "cmd_sim.sh" I would do:

export CMDLIB=$3
export CMDCELL=$2
export CMDVIEW=$1

and then have the call to MyTodo in the bottom of MyTodo.il as:

MyTodo(getShellEnvVar("CMDVIEW") getShellEnvVar("CMDCELL") getShellEnvVar("CMDLIB"))

I kept your back to front order of the arguments (normal convention would be to supply lib/cell/view rather than view/cell/lib), but hopefully you get the idea.

Andrew

Thank you Andrew, this will do my job.

The original purpose of this cmd_sim.sh is that we find VERIFIER get stuck when submit >100 implementation simulations, even under batch mode.

BTW ,is there any better/smarter way to accelerate VERIFIER  submit  multiple simulations ?

Are you using Verifier in IC617? There was a major architectural change made in IC618 to address performance limitations of Verifier, so I would strongly recommend you move to IC618 (or ICADVM181) to use Verifier with a lot of simulations. Then you may not need to bother with this workaround.

Regards,

Andrew.

Hi Andrew

We have already used IC618.Especilly the new feature BATCH MODE(dedicated to submit multiple simulation).

Unfortunately even under BATCH MODE ONLY start up a single no-graph virtuoso thread at backgound,

when 100+ maestros submitted by 1 single virtuoso,stuck still happens,while post-simulation generates nestlist, even worse.