Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 14196
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Re: Writing Ocean script to call other ocean scripts?

slim5

  Could someone comment on how the syntax for OCEAN script be if I want to use one ocean script to submit a number of other ocean scripts to our local LSF with the bsub function? I read on this post www.cadence.com/.../883351.aspx believe it is possible but had not find anything in Cadence's documentation. We hae IC614 installed. Would variable sdeclared in the original OCEAN script be passed on to the otherocean scripts that it calls with the bsub function?

Regards,

S Lim

 

  • That other post is referring to submitting jobs with ADE XL, not submitting OCEAN scripts to LSF. You'd need to use something like:

    system("bsub ocean -restore yourScript.ocn")

    Variables defined in the parent OCEAN script would not be passed to the child OCEAN script. You could solve that by (say) using setShellEnvVar() to define a UNIX environment variable and then having getShellEnvVar() in the child OCEAN script to get the value.

    Andrew.

  •  Hi Andrew,

       Thank you for the reply, I figured it out awhile back. My solution is very identical to what you had just suggested. I used sh("bsub -replay yourScript.oc") and passed variables via setShellEnvVar() and getShellEnvVar().

     Out of curiosity, what does the flag -restore for ocean do?

    Regards,

    Su Lim

  • Su,

    The -restore argument can be used with ocean and virtuoso (and icfb in older versions). It's effectively the same as starting up the tool and then doing load("fileName"). The -replay argument is intended for replaying log files, but does actually work if the file doesn't have the /a, /i etc tags that you get in a CDS.log file. I just like -restore because it feels a bit cleaner...

    Regards,

    Andrew.

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.