This is an old revision of the document!
The following CHPC HPC systems (Sun Microsytems, Blue Gene and GPU) use schedulers and resources managers to schedule and run jobs in the systems. Below is the detail information:
Sun Microsystems - Moab (Scheduler) and Torque (Resource manager). Blue Gene/P - Loadleveler (Resource manager). GPU - Torque (Resources manager)
SUBMITTING A JOB USING MOAB
Create a test job.
vi test the file named: job name. include the following in your script, for more info check http://www.clusterresources.com. To get the defination and more flags of MSUB do a command "man msub".
###These lines are for Moab #MSUB -l nodes=4:ppn=8 #MSUB -l walltime=2:00:00 #MSUB -m be #MSUB -o /export/home/nmonama/scratch/test/dlpoly.3.07.out #MSUB -e /export/home/nmonama/scratch/test/dlpoly.3.07.err #MSUB -d /export/home/nmonama/scratch/test #MSUB -mb #MSUB -M nmonama@csir.co.za
##### Running commands NP=`cat $PBS_NODEFILE | wc –l` mpirun –np $NP –machinefile $PBS_NODEFILE DLPOLY_3.07.SPARC.Y
SCRIPT Description/Ntes #MSUB -a Declares the time after which the job is eligible for execution. Syntax: (brackets delimit optional items with the default being current date/time): #MSUB -A account Defines the account associated with the job. #MSUB -e Defines the file name to be used for stderr. #MSUB -d path Specifies the directory in which the job should begin executing. #MSUB -h Put a user hold on the job at submission time. #MSUB -j oe Combine stdout and stderr into the same output file #MSUB -l string Defines the resources that are required by the job #MSUB -m options Defines the set of conditions (a=abort,b=begin,e=end) when the server will send a mail message about the job to the user #MSUB -N name Gives a user specified name to the job #MSUB -o filename Defines the file name to be used for stdout. #MSUB -p priority Assigns a user priority value to a job #MSUB -q queue Run the job in the specified queue (short.q,long.q,graphics.q,serial.q and interactive.q) #MSUB -r y Automatically rerun the job is there is a system failure #MSUB -S path Specifies the shell which interprets the job script. The default is your login shell. #MSUB -v list Specifically adds a list (comma separated) of environment variables that are exported to the job #MSUB -V Declares that all environment variables in the msub environment are exported to the batch job. #MSUB -W This option has been deprecated and should be ignored.
++++
submit test:
msub test -q x (where x=nehalem,harpertown or sparc)
*POST AND PRE PROCESSING*
Please use the following node for post and pre processing: chpcsp01 chpcsp02
Below is an example of Loadleveler script in Blue Gene/P:
#@ job_type = bluegene #@ bg_size = 64 #@ class = BGP #@ input = /dev/null #@ output = dlpoly.$(jobid).out #@ error = dlpoly.$(jobid).err #@ wall_clock_limit = 12:00:00 #@ resources = ConsumableCpus(1) #@ node_usage = shared #@ cluster_list = BGP #@ notification = complete #@ queue /bgsys/drivers/ppcfloor/bin/mpirun -np 32 -mode VN -cwd /CHPC/work/username/test -exe EXECUTABLENAME
There are various controls of Moab and Loadleveler that can help you to manage your job:
Some of Moab controls are as follows:
| Command | Description |
| msub | Scheduler job submission |
|---|---|
| showq | Show queued jobs |
| canceljob | Cancel job |
| showres | Show existing reservations |
| showstart | Show estimate of when job can or will start |
| Checkjob | Provide report for specified job |