FAQ
General Frequently Asked Questions
Table of Contents
Running Jobs
- My job was killed sending mail with the subject PBS JOB jobid.lens-mgt.ccs.ornl.gov
- Why does my job’s execution time vary greatly from run to run?
- Why can I not use the module command in batch scripts?
Running Jobs
My job was killed sending mail with the subject PBS JOB jobid.lens-mgt.ccs.ornl.gov
Mail contents:
PBS Job Id:.lens-mgt.ccs.ornl.gov Job Name: comptst job deleted Job deleted at request of root@lens-mgt.ccs.ornl.gov job preempted ( )
On lens, jobs submitted to the computation queue may be preempted by jobs submitted to the analysis queue. When a job is preempted the above mail is sent to the preempted job’s owner. See the queues page for more information.
Why does my job’s execution time vary greatly from run to run?
Lens allows multiple jobs to run on a single node. Memory and cores are shared by all jobs allocated on the node within the node. The only way to ensure that your job does not share resources with another job(s) on the node, is to request the entire node.
Why can I not use the module command in batch scripts?
In order to use the module command from a batch script, you need to first source the module init file for your shell. For instance, if bash is your shell, then you need to source the bash init script.
. ${MODULESHOME}/init/bash
#PBS -A XXXYYY
#PBS -N test
#PBS -j oe
#PBS -l walltime=1:00:00,nodes=2:ppn=4
cd $PBS_O_WORKDIR
date
. ${MODULESHOME}/init/bash
module avail
