Pawsey supercomputers use Slurm as a job scheduling system. If your workflow is designed for PBS Pro, this page helps you to migrate from PBS Pro to Slurm.

There are two main aspects involved in the migration:

1. Learning how to interact with Slurm.
2. Making some minor changes to the directives and referenced environment variables in your batch scripts to use the Slurm equivalents.

The following sections detail commonly used PBS Pro commands, options and environment variables and their Slurm equivalents.

Command comparison 

Table 1 lists the most commonly used commands in PBS Pro and their equivalents in SLURM.

The SLURM commands behave in a similar way to their PBS Pro equivalents, though some (such as squeue) produce somewhat different output.

Submitting a batch job: the sbatch command

The sbatch command replaces qsub, submitting the job and printing the submitted job ID in the following format.

$ sbatch slurm.script.sh
Submitted batch job 16778

For batch jobs that capture the job ID to create job dependencies, the format is different from what qsub prints.

$ qsub pbs.script.sh
417462.ps1

Displaying job status: the squeue command

The output generated by squeue is similar to that of qstat, however the default fields and order are quite different in most cases.

$ squeue
JOBID PARTITION NAME USER ST TIME NODES NODELIST(REASON)
16793 work slurm.sc pryan R 0:01 4 nid000[32-35]
16794 work slurm.sc pryan PD 0:00 2 (Dependency)

For comparison purposes, the output of qstat is shown in terminal 4.

$ qstat
ps1:
Req'd Req'd Elap
Job ID Username Queue Jobname SessID NDS TSK Memory Time S Time
--------------- -------- -------- ---------- ------ --- --- ------ ----- - -----
417465.ps1 pryan debug pbs.script 30430 8 128 -- 00:45 R 00:00
417466.ps1 pryan debug pbs.script -- 8 128 -- 00:45 Q --

Submitting requests from an interactive session: the salloc command

For interactive jobs, Slurm uses a separate command, salloc, in place of the qsub -I of PBS Pro.

Option comparison 

Table 2 lists the most commonly used directives in PBS Pro and their equivalents in Slurm. These can be used with the sbatch or salloc commands or as directives inside a batch script.

To convert the PBS Pro select statement, use the --nodes and --ntasks-per-node options. For example, listing 2 shows the Slurm equivalent of the PBS Pro directive shown in listing 1.

#PBS -l select=10:ncpus=16:mpiprocs=16

#SBATCH --nodes=10
#SBATCH --ntasks-per-node=16

Alternatively, the --ntasks option can be used to specify the total number of tasks, rather than using --nodes.

#SBATCH --ntasks=160
#SBATCH --ntasks-per-node=16

Slurm batch script

The general concepts behind batch scripting are not different with Slurm. There is still a preamble portion of the script in which directives are given to the batch system, followed by the job commands. The main difference is that the script directive, the sequence of characters with which a directive must begin, is #SBATCH instead of #PBS, and the arguments differ slightly as well. We will begin by examining a simple script shown in listing 4.

#!/bin/bash -l
# 10 nodes, 32 MPI processes/node, 320 MPI processes total
#SBATCH --job-name="myjob"
#SBATCH --time=02:00:00
#SBATCH --ntasks=320
#SBATCH --ntasks-per-node=32
#SBACTH --cpus-per-task=1
#SBATCH --mem=58G
#SBATCH --output=myjob.%j.o
#SBATCH --error=myjob.%j.e
#SBATCH --account=projectcode
#SBATCH --export=NONE
#======START=====
echo "The current job ID is $SLURM_JOB_ID"
echo "Running on $SLURM_JOB_NUM_NODES nodes"
echo "Using $SLURM_NTASKS_PER_NODE tasks per node"
echo "A total of $SLURM_NTASKS tasks is used"
echo "Node list:"
sacct --format=JobID,NodeList%100 -j $SLURM_JOB_ID
srun -u -N $SLURM_JOB_NUM_NODES -n $SLURM_NTASKS -c $SLURM_CPUS_PER_TASK ./a.out
#=====END====

Line 1 invokes the shell (bash), and line 2 is a comment.

Lines 3 to 10 contain the script directives. Line 3 gives the job a name. Line 4 requests 2 hours of walltime. Line 5 requests 240 MPI processes, and line 6 requests 24 processes per node. Line 7 specifies the name of the output file (%j is the job number), and line 8 specifies the file to which errors should be written out. Line 9 gives the account to which this walltime should be charged.

Line 11 is an optional separator between the script directive preamble and the actions in the script.

Lines 12-17 are useful (but optional) diagnostic information that will be printed out.

Line 18 invokes srun  to run the code (./a.out).

Line 19 is an optional separator marking the end of the script.

From this script, you can see that the same concepts you already know from PBS Pro apply to Slurm as well. You must tell the scheduler how long the job will run for, and how many processors are required. You provide it with project accounting information. And there are other optional arguments that help the script to run. Within the body of the script, we can invoke the usual scripting utilities such as echo, and launch our application with the usual commands.

Environment variable comparison 

Table 3 lists some commonly used environment variables that are set by Slurm for each job, along with their PBS Pro equivalents. These variables can be used in the body of the script as well, as shown in listing 4.

Related pages

• Job Scheduling