Allow the -cwd path to be accessible to the job

Enable jobs to access the path specified by the bsub -cwd option. Currently if the job pre-exec or the job command create the -cwd path the job cannot change to the -cwd path. PMR 65697,227,000

Apparently by default the bsub -cwd option cannot access a path that is created by the job or the pre-exec command.

Post comment

Guest

Reply
| Mar 25, 2018

The behavior you are observing is correct.

When a job is dispatched, the pre-exec/job/post-exec will all run in the specified cwd. The check for whether the cwd actually exists is done the first time something tries to access it.

In your case, the pre-exec tries to run in "c:\temp\abaqus\username\projname" which does not exist at that point, so execution defaults to tmp. The pre-exec succeeds and the job is executed in tmp.

If you use a dynamic pattern for the cwd, then the directory will be automatically created before the pre-exec runs.

For example, bsub -cwd "C:\temp\abaqus\%U\projname" -P "projname" -E pre_exec.bat abaqus file.inp

%U is replaced by the current username, and the directory will be created prior to the pre-exec running.

0 reply Hide replies

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.

Please enter your email address

RELATED IDEAS

Allow the -cwd path to be accessible to the job