SLURM Reference Manual for HP XC System Software
Table Of Contents
- Preface
- Introduction
- SLURM Goals and Roles
- SLURM Features
- SLURM Operation
- SLURM Utilities
- SRUN (Submit Jobs)
- SQUEUE (List Jobs)
- SINFO (List Nodes)
- SMAP (Show Job Geometry)
- SCONTROL (Manage Configurations)
- Disclaimer
- Keyword Index
- Alphabetical List of Keywords
- Date and Revisions
SCONTROL (Manage Configurations)
ROLE.
SCONTROL is the SLURM utility that manages SLURM's own configuration, including the properties
that it assigns to nodes, node partitions, and other SLURM-controlled system features. Most SCONTROL
options and commands are intended for, and can only be successfully executed by, a system administrator
(a privileged or root user). Some SCONTROL commands report useful configuration information or
manage job checkpoints, however, and any user can benefit from invoking them appropriately. The rest
of this section discusses only those few general-user SCONTROL commands.
EXECUTE LINE.
Run SCONTROL by typing
scontrol command argument
where the general-user commands and their specific arguments are summarized below (most commands
are for system administrators only). Without any command, SCONTROL prompts for input.
GENERAL-USER COMMANDS.
The subset of SCONTROL commands that any user can invoke includes these:
checkpoint action jobid[.stepid]
requests one of several allowed checkpoint activities on those LC AIX machines that
also use SLURM (instead of IBM's LoadLeveler). You must (previously) set
environment variable CHECKPOINT to YES and specify a location and name for
future checkpoint files. See the "Checkpointing with SLURM and POE" section (URL:
http://www.llnl.gov/LCdocs/dpcs/index.jsp?show=s7.5) of the LCRM Reference
Manual for details, especially for LCRM batch jobs. Here:
action specifies what to do after the requested checkpoint occurs, where
the three most useful alternatives are:
create requests a checkpoint and continues the job(step)
after it occurs.
vacate requests a checkpoint and terminates the job(step)
after it occurs.
restart resumes execution of a previously checkpointed
job(step).
jobid[.stepid] specifies the range for the checkpointing activity, which can be all
existing steps for a specified jobid alone (e.g., 4812), or the
individual job step indicated by a jobid.stepid combination (e.g.,
4812.4).
exit (or QUIT) terminates SCONTROL during interactive sessions.
SLURM Reference Manual - 65