Bug 1745 - The problem of globus-job-submit
: The problem of globus-job-submit
Status: RESOLVED FIXED
: GRAM
gt2 Gram client
: 3.2.0
: Sun Solaris
: P2 normal
: ---
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2004-05-20 01:36 by
Modified: 2004-07-28 11:10 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2004-05-20 01:36:42
When globus-job-submit is run, a prompt does not return until a job is
completed.
It behaves like globus-job-run.

Is this a bug?
------- Comment #1 From 2004-06-22 14:21:07 -------
It depends on the type of job you are running. If the job is short and you are 
using any staging in of executable or stdin file, then the script have 
globusrun wait until it gets an past the STAGE_IN_STATE (to ACTIVE, PENDING, 
DONE, or FAILED). 
 
For certain some jobs, this may make it look like globus-job-submit is waiting 
for the job to terminate. 
 
joe 
------- Comment #2 From 2004-06-22 19:34:59 -------
For example, suppose that the following simple jobs were run.

globusrun -b -r vppch29 '&(executable="/bin/sleep")(arguments="1000")'
globus_gram_client_callback_allow successful
GRAM Job submission successful
https://vppch29.aoi.pst.fujitsu.com:62125/6526/1087950375/
GLOBUS_GRAM_PROTOCOL_JOB_STATE_ACTIVE

This state continues for 1000 seconds.
Is this behavior exact as a batch job?
------- Comment #3 From 2004-07-28 11:10:39 -------
an update package is available at
http://www-unix.globus.org/ftppub/gt3/3.2/3.2.1/updates/src/globus_gram_client_tools-4.3.tar.gz