-snip- > Yes, some of the srun options apply to a job allocation, some to a job > step, and some to both. I'll agree this needs more documentation and > will put that on our to-do list.
Thanks. -snip- > The sbatch options controlling job layout (task count, node count, cpus > per task, etc.) are used to construct environment variables for the > batch script (same for salloc commands), so the srun command gets those > options by default. It is a typical use case for all resource > specification options to appear on the sbatch submit line (or in the > script), then have the srun commands within the script only identify > the application to be run. I think that connects a couple of concepts for me. I has read the documentation of environment variables that are equivalent to command line options and seen the variables set within a job but not thought of them as being the mechanism for influencing the nested srun. While command line options will be over-riding, they will not necessarily be compatible - or at least the situation is not as simple as just the command line options. > There is another mode of operation in which a single job executes a > multitude of srun commands within an allocation, using different size > and layout options. These various job steps (each srun invocation), can > run serially or in parallel using overlapping or separate resources > (see srun's --exclusive option). Thanks for mentioning that for completeness. I'm sure it will come up for us sooner or later. Gareth > -- > Morris "Moe" Jette > CTO, SchedMD LLC > Commercial Slurm Development and Support
