SLURM Reference Manual for HP XC System Software

Available parameters with which to construct fstring (and thereby to split the I/O
among separate files) include:
%J (uppercase) creates one file for each job ID/step ID combination for
this running job, and imbeds jobid.stepid in each file's name (for
example, out%J might yield files out4812.0, out4812.1, etc.).
%j (lowercase) creates one file for each job ID and imbeds jobid in its
name (for example, job%j might yield file job4812).
%s (lowercase) creates one file for each step ID and imbeds stepid in
its name (for example, step%s.out would yield files step0.out,
step1.out, etc.). SRUN does not support job steps on BlueGene/L.
%N (uppercase) creates one file for each node on which this job runs
and imbeds that node's short hostname in the file name (for example,
node.%N might yield files node.mcr347, node.mcr348, etc.).
%n (lowercase) creates one file for each node on which this job runs
and imbeds that node's numerical identifier relative to the job (where
the each job's first node is 0, then 1, etc.) in the file name (for
example, node%n would yield files node0, node1, etc.).
%t (lowercase) creates one file for each separate task in this running
job and imbeds that task's numerical identifier relative to the job
(the first task is 0) in the file name (for example, job%j-%t.out might
yield files job4812-0.out, job4812-1.out, etc.).
For all fstring parameters except the nonnumeric case of %N, you
can insert an integer between the percent character and the letter
(such as %3t) to "zero-pad" the resulting file names, that is, to always
use the integer number of character positions and to fill any empty
positions with zeros from the left. Thus job%j-%3t.out might yield
files job4812-000.out, job4812-001.out, etc.
SLURM Reference Manual - 35