Login or Register to Ask a Question and Join Our Community


UNIX for Dummies Questions & Answers

Help in job submission!

 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers Help in job submission!
# 1  
Old 05-27-2009
Help in job submission!
I am attempting to submit alot of jobs to this CONDOR program, in which it utilizes alot of computers and puts a single job onto each. Anyways, im trying to use the same program (autodock) to analyze different input files (dpf files), where each input file has a different name but same file extension. The submit files uses an executable file however i cannot figure out to get this executable to recognize the different input dpf files and send those to the computers for the job to be ran. Does this make sense? The executable reads,

autodock4 -p name.dpf -l name.dlg

Ive tried a few different things but i cannot get this to work. Your help is appreciated. Thanks
 
Login or Register to Ask a Question

Previous Thread | Next Thread

4 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Multiple variables using awk and for loop for web form submission

Hi My goal is to fill an HTML form and submit. What I have managed to do: 1. curl command to fill up the form and submit 2. a file which has the input curl command: curl -v -b cookie.txt -d __CSRFToken__=dc23d5da47953b3b390ec68d972af10380908b14 -d do=create -d a=open -d... (10 Replies)
Discussion started by: zorrox
10 Replies

2. Shell Programming and Scripting

Request for help with SGE submission script manipulation

Hi, I have the following SGE submission (HPC calculation) script, which is just a Bash script: #!/bin/bash -l #$ -S /bin/bash #$ -l h_rt=1:00:0 #$ -l mem=4G #$ -N XXX #$ -pe qlc 24 #$ -P XXX #$ -wd /home/uccaxxx/Scratch/222PdT/3vac/c0001/ mpirun -m $TMPDIR/machines -np $NSLOTS... (2 Replies)
Discussion started by: crunchgargoyle
2 Replies

3. Shell Programming and Scripting

Script to Start a Job after finding the Old job completed

Hi Experts, I need a script advice to schedule 12 jobs ( SAS Codes execute back ground ). Algorithem: 1. Script checks first job. 2. Finds first job is done; invoke second job. 3. finds second job is done; invoke third job. .. Request you to please assist. (3 Replies)
Discussion started by: Jerald Nathan
3 Replies

4. Solaris

killing a unix job after the job process gets completed

Hi, Thanks in advance. i need to kill a unix background running job after that job process completes. i can kill a job by giving the following unix command kill -9 processid how to kill the job after the current process run gets completed ? Appreciate your valuable help. Thanks... (7 Replies)
Discussion started by: dtazv
7 Replies
Login or Register to Ask a Question

LEARN ABOUT X11R4

qstat

QSTAT(1)						User Contributed Perl Documentation						  QSTAT(1)

NAME

       qstat - display job/partition information in a familiar pbs format

SYNOPSIS

       qstat [-f] [-a|-i|-r] [-n [-1]] [-G|-M] [-u user_list] [-? | --help] [--man] [job_id...]

       qstat -Q [-f]

       qstat -q

DESCRIPTION

       The qstat command displays information about jobs.

OPTIONS

       -a  Displays all jobs in a single-line format. See the STANDARD OUTPUT section for format details.

       -i  Displays information about idle jobs. This includes jobs which are queued or held.

       -f  Displays the full information for each selected job in a multi-line format. See the STANDARD OUTPUT section for format details.

       -G  Display size information in gigabytes.

       -M  Show size information, disk or memory in mega-words.  A word is considered to be 8 bytes.

       -n  Displays nodes allocated to a job in addition to the basic information.

       -1  In combination with -n, the -1 option puts all of the nodes on the same line as the job id.

       -r  Displays information about running jobs. This includes jobs which are running or suspended.

       -u user_list
	   Display job information for all jobs owned by the specified user(s). The format of user_list is: user_name[,user_name...].

       -? | --help
	   brief help message

       --man
	   full documentation

STANDARD OUTPUT

       Displaying Job Status

       If the -a, -i, -f, -r, -u, -n, -G, and -M options are not specified, the brief single-line display format is used. The following items are
       displayed on a single line, in the specified order, separated by white space:

       the job id
       the job name
       the job owner
       the cpu time used
       the job state
	   C -	Job is completed after having run E -  Job is exiting after having run.  H -  Job is held.  Q -  job is queued, eligible to run or
	   routed.  R -  job is running.  T -  job is being moved to new location.  W -  job is waiting for its execution time (-a option) to be
	   reached.  S -  job is suspended.

       the queue that the job is in

       If the -f option is specified, the multi-line display format is used. The output for each job consists of the header line: Job Id:  job
       identifier followed by one line per job attribute of the form: attribute_name = value

       If any of the options -a, -i, -r, -u, -n, -G or -M are specified, the normal single-line display format is used. The following items are
       displayed on a single line, in the specified order, separated by white space:

       the job id
       the job owner
       the queue the job is in
       the job name
       the session id (if the job is running)
       the number of nodes requested by the job
       the number of cpus or tasks requested by the job
       the amount of memory requested by the job
       either the cpu time, if specified, or wall time requested  by the job, (in hh:mm)
       the job state
       The amount of cpu time or wall time used by the job (in hh:mm)

EXIT STATUS

       On success, qstat will exit with a value of zero. On failure, qstat will exit with a value greater than zero.

perl v5.14.2							    2012-04-10								  QSTAT(1)