How to know ADE runICRP files come from which library and cell view when the run status is pending?

I don't think you can. You can look in the ADE windows open and hover over the little terminal icon in the Run Summary assistant and one will state that it's Job 32, but I don't think there's any public way to link the two.

If you're trying to identify problems during starting of the jobs, then one thing that might help is to try setting the showJobStderr and showJobStdout cdsenv vars (use Options->Cdsenv editor in the CIW and search for "showJob"). However, that relies on your job submission command printing something as the job is submitted (you didn't say why you need this, although I'm guessing it might possibly be related to case 46607263 - was that you?)

Andrew

I don't think you can. You can look in the ADE windows open and hover over the little terminal icon in the Run Summary assistant and one will state that it's Job 32, but I don't think there's any public way to link the two.

If you're trying to identify problems during starting of the jobs, then one thing that might help is to try setting the showJobStderr and showJobStdout cdsenv vars (use Options->Cdsenv editor in the CIW and search for "showJob"). However, that relies on your job submission command printing something as the job is submitted (you didn't say why you need this, although I'm guessing it might possibly be related to case 46607263 - was that you?)

Andrew

case 46607263 is not mine, we want to add some process before the ICRP job starts to run, so need to know the ICRP comes from where.

OK, it was just a guess as it was very recent and sounded related and some of the characters in your user name suggested to me that you might be from the same company (again, just a guess). I think it's best you contact customer support, as maybe what you want to do can be achieved a different way - we'll probably need some info on what it is you're trying to do before the ICRP job starts.

Andrew

We want to automatic and dynamic add some LSF options according to the cell view name

Dear JMTKRex,

I am not sure if your need to dynamically add LSF options according to your cell name are related to the LSF resource requirements for the job. However, if they are, have you seen the following Cadence On-line support article detailing how the LSF command resources can be varied based on specte's estimate of its memory and recommended number of CPU for that job?

https://support.cadence.com/apex/ArticleAttachmentPortal?id=a1O0V000009Mom9UAC&pageName=ArticleContent

This may not be what you were hoping for, but thought I should at least pass it on JMTKRex!

Shawn

On similar lines to what Shawn was suggesting, I was thinking that a better approach might be to have a trigger (registered with axlSessionConnect, or maybe triggered by axlSessionRegisterCreationCallback). It might be the postCreateSessionDB or postLoadMainSetupDB signal (axlGetSignalList is the thing to look at) which then creates a per maestro cellView job-policy. Some people do this with a preRun trigger, but the downside is that if you end up changing the job policy at pre-run time it can restart the jobs and hence lose the benefit of any linger time.

This would be a better approach than having your submission command trying to infer stuff about the cellVIew based on the script it's being asked to submit, especially as there's no way of doing that.

Andrew