JetJob Suite of ScriptsThe purpose of the JetJob suite is to facilitate a method of job submission and monitoring. SJOB communicates with the PBS server to execute common everyday commands that we all use. SJOB takes care of creating a suitable submission script and submits the job for you. By allowing SJOB to handle submission, you can utilize MJOB for monitoring when your job is complete. All scripts described herein can be found in /home/usrb/b1/jturney/bin. SJOB communicates with the queueing system to suggest to the user a different queue if their queue they want is full and the other has free nodes. To disable this capability (useful if used in scripts) set the environmental variable SJOB_SUGGEST to 'n'. How to use SJOBUsing SJOB can be a simple task. As with any new program you just have to learn what it likes and does not. A call to SJOB has the following form: (SJOB has been modified to display the following table when not required arguments are not given or --help is passed.) % sjob queue[=nodes] progname inputfile jobname outputfile
Example usage of SJOBTo submit an ACESII job to the bigmem2's any of the following is valid: % sjob reg=bigmem2 aces SJOB - Job submitted ID : 1000.clortho.ccqc.uga.edu Path : /home/usrb/b1/jturney/chem/acestest Program : ACESII % sjob reg=p3200 aces2 SJOB - Job submitted ID : 1001.clortho.ccqc.uga.edu Path : /home/usrb/b1/jturney/chem/acestest Program : ACESII To submit a MOLPRO job to any machine on the reg queue: % sjob reg molpro SJOB - Job submitted ID : 1002.clortho.ccqc.uga.edu Path : /home/usrb/b1/jturney/chem/molprotest Program : MOLPROor with a different input file: % sjob reg molpro h2.input SJOB - Job submitted ID : 1003.clortho.ccqc.uga.edu Path : /home/usrb/b1/jturney/chem/molprotest Program : MOLPRO To submit a NWChem job to the Opteron queue to run in parallel on 4 nodes: % sjob opt=4:ppn=2 nwchem SJOB - Job submitted ID : 1004.clortho.ccqc.uga.edu Path : /home/usrb/b1/jturney/chem/nwchemtest Program : NWCHEM Monitoring your jobsYou can use MJOB to monitor your jobs. It runs in a continuous loop refreshing every minute. I recommend just leaving MJOB running in its own window this way you are constantly up to date on the status of your jobs. MJOB has been updated to display walltime and executing node for all jobs running.
% mjob
MJOB - Monitor jobs compatible with SJOB
Report for jturney
Jobs currently waiting in the queue:
No jobs in queue.
Jobs currently running in the queue:
24977 29:22:40 opt19/0+opt19/1
~jturney/molpro/lion_triplet/lion_ts/cas
Jobs possibly completed/aborted:
23945 SUCCESS ~jturney/molpro/hnc/a_linear/ccsd
24981 SUCCESS ~jturney/molpro/lion_triplet/lino_ts/cas
Deleting your jobsIf you need to delete your job from the queue and/or from the MJOB list use DJOB. DJOB deletes jobs not only completed/aborted but also running or waiting. It is advised that before submitting another job in a directory that holds a previously completed job that you run djob anyways. If this is not done MJOB can become confused. % djob 12979 Attempting to qdel: 12979 done. If you are in the same directory of the job you want to delete use DJOB with no command line argument: % djob Attempting to qdel: 12979 done. If you are in the habit of running several jobs in the same directory and MJOB becomes confused to fix this run: % djob all Attempting to qdel: 12979 12980 12981 done.This deletes all jobs in the directory even ones that are still running. If you're still in the habit of running several jobs in the same directory, you have a job currently running a job in the directory, and MJOB becomes confused try: % djob done Attempting to qdel: 12979 12980 12981 done.This will only removes jobs that are completed in the current directory. |
