# Job composer and star-ccm+

**URL:** <https://discourse.openondemand.org/t/job-composer-and-star-ccm/2238>\
**Category:** Get Help\
**Tags:** ondemand2, question\
**Created:** [August 17, 2022, 7:22pm UTC](https://discourse.openondemand.org/t/job-composer-and-star-ccm/2238 "2022-08-17T19:22:20Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![travert](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/travert/32/3074_2.png) [@travert](https://discourse.openondemand.org/u/travert)\
**Post date:** [August 18, 2022, 4:23pm UTC](https://discourse.openondemand.org/t/job-composer-and-star-ccm/2238/2 "2022-08-18T16:23:52Z")

</div>

Sorry for the issue. Reading what you have here I wonder if the fix is similar from a previous user’s issue:

> [@Slurm job fails in OOD but works at CLI](https://discourse.openondemand.org/t/slurm-job-fails-in-ood-but-works-at-cli/935/2):
>
> strace maybe? When you say you can run it from the cli, I’d ask if it’s the same host? The cli from the same server as OOD or some other login host? This could be your discrepancy, there could actually be some networking issue there. It could also be the environment. OOD defaults to SBATCH\_EXPORT=NONE so you can load a brand new environment. I would say add an env statement to see if there’s something you’re missing (some LD\_LIBRARY\_PATH missing?).

The solution seemed to be:

> [@Slurm job fails in OOD but works at CLI](https://discourse.openondemand.org/t/slurm-job-fails-in-ood-but-works-at-cli/935/3):
>
> I’ll bet it’s due to OOD defaulting to `SBATCH_EXPORT=NONE`, I believe that has issues with parallelism. I wonder if adding `#SBATCH --export=ALL` directive to the script overrides this?

Which might be why the environment is not what is expected? What happens when you add that to the line and submit in the job composer?

---

_[View the full topic](https://discourse.openondemand.org/t/job-composer-and-star-ccm/2238)._