Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This document describes the use of PBS Pro 2022.1.1 version.


Job running

User applications (hereinafter jobs) that are started using the PBS system must be described by a start shell script (sh, bash, zsh...). Within the startup script above the normal commands, the PBS parameters are listed. These parameters can also be specified when submitting a job.

...

Code Block
qcat jobID
qcat -e jobID
qtail jobID
qtail -e jobID

Job submitting

There are s

everal several ways jobs can be submitted:

...

Tip
titleJob Array

This method is preferred over multiple submissions (e.g. with a for loop) because:

  • reduces job queue load - each job will compete for resources simultaneously with everyone else in the queue, instead of one after the other
  • easier management - modification of all jobs is possible by calling the main (e.g. 14575[]) or individual (e.g. 14575[3]) job identifier 

The environment variables defined by PBS during their execution are:

  • PBS_ARRAY_INDEX - ordinal number of sub-jobs in the job field (e.g. one to nine in the example above)
  • PBS_ARRAY_ID - identifier of the main job field
  • PBS_JOBID - subjob identifier in the job field


Job Description

The PBS system language is used to describe jobs, while the job description file is a standard shell script. In the header of each script, PBS parameters are listed that describe the job in detail, followed by commands to execute the desired application.

Structure of the startup script:

Code Block
languagebash
titlemy_job.pbs
#!/bin/bash
 
#PBS -P test_example
#PBS -q cpu
#PBS -e /home/my_directiry
#PBS -l select=2:ncpus=10
 
module load gcc/12.1.0
 
gcc --version


Example of a startup script:

Code Block
languagebash
titlemy_job.pbs
#!/bin/bash
 
#PBS -<parametar1> <value>
#PBS -<parametar2> <value>
 
<command>