SLURM Reference Manual for HP XC System Software

Other SLURM-Relevant Variables.
Other environment variables important for SRUN-managed jobs include:
MAX_TASKS_PER_NODE
provides an upper bound on the number of tasks that SRUN assigns to each job node,
even if you allow more than one process per CPU by invoking SRUN's -O (uppercase
oh) option. (page 29)
SLURM_HOSTFILE
names the file that specifies how to assign tasks to nodes, rather than using the block
or cyclic approaches toggled by SRUN's -m (--distribution) option (page 24).
On AIX (IBM) machines only, this extra environment variable is automatically set by LCRM when
SLURM is used instead of LoadLeveler (alternatively, set with SRUN's --network=type option even though
POE launches tasks instead of SRUN under AIX):
SLURM_NETWORK
specifies four network features for each SLURM job step (which under AIX means
for each POE invocation), using an argument with this sequential format:
network.[protocol],[device],[adapteruse],[mode]
where:
protocol specifies the network protocol (such as MPI).
device specifies the kind of switch used for communication (ethernet, FDDI,
etc.), where the choices are the same abbreviation strings as the
possible values of environment variable MP_EUIDEVICE (see the
POE User Guide, "Task Communication" section (URL:
http://www.llnl.gov/LCdocs/poe/index.jsp?show=s6.3.3)).
adapteruse specifies whether (SHARED) or not (DEDICATED) your job is
willing to share a node's switch adapter with other jobs (see the POE
User Guide, "Other POE Environment Variables" section (URL:
http://www.llnl.gov/LCdocs/poe/index.jsp?show=s6.4) on
corresponding environment variable MP_ADAPTER_USE).
mode specifies which of two protocols or modes should be used for task
communications, where the choices are the same as the possible
values of environment variable MP_EUILIB (see the POE User
Guide, "Task Communication" section (URL:
http://www.llnl.gov/LCdocs/poe/index.jsp?show=s6.3.3)).
SLURM Reference Manual - 43