It's because globus-job-submit does some extra work to make sure the
stdout/stderr are identifiable for retrieval by globus-job-get-output.
Specifically, the line that does the heavy lifting in globus-job-get-
output is:
${bindir}/globusrun -o -r "$resource" 2> $tmpfile \
"&(executable=\$(GLOBUS_LOCATION)/bin/globus-sh-exec)(arguments=-
exec \"file
=\`\${bindir}/globus-gass-cache -query -t anExtraTag x-gass-cache://$
{jobid}${st
ream}\`; if test -r \"\"\$file\"\" ; then ${command} \$file ; else
echo Invalid
job id. 1>&2; fi\")"
That globus-bass-cache -query -t anExtraTag -x-gass-cache://$jobid
$stream works because globus-job-submit explicitly sets the stdout/
stderr of the job to:
job_gass_cache_tag="x-gass-cache://\$
(GLOBUS_GRAM_JOB_CONTACT)"
job_stdout="${job_gass_cache_tag}stdout anExtraTag"
job_stderr="${job_gass_cache_tag}stderr anExtraTag"
and puts "(stdout=$job_stdout)(stderr=$job_stderr)" into the RSL for
you. So you can emulate this behavior by submitting:
'&(executable="/usr/bin/ical")(stdout="x-gass-cache://\$
(GLOBUS_GRAM_JOB_CONTACT)stdout anExtraTag")(stderr="x-gass-cache://\$
(GLOBUS_GRAM_JOB_CONTACT)stderr anExtraTag")'
But, of course, that's what using globus-job-submit does for you in
the first place. What's the problem you're trying to solve? Are you
avoiding globus-job-submit for some reason? You can set your stdout/
stderr to other things and still use a tool like globus-url-copy to
retrieve them later even if you didn't set things up for globus-job-
get-output specifically.
Charles
On Jul 14, 2008, at 10:46 AM, Omer Jilani wrote:
Hi all,
I'm having some problem with globus-job-get-output.
With
globus-job-submit node1.cluster.com:2119/jobmanager-pbs /usr/bin/cal
and getting the output using globus-job-get-output works fine
without any problem
But when I use a jdl as simple as
globus-job-submit node1.cluster.com:2119/jobmanager-pbs
'&(executable="/usr/bin/cal")'
I get the job ID but using get-output returns nothing.
For an empty job-output there is a log at the gatekeeper user home
which seems okay except the lines
NFS sync for '&(executable="/usr/bin/cal")' failed (may be
harmless). No such file or directory
and
NFS sync for /dev/null failed (may be harmless): Operation not
permitted
(I'm using Scientific Linux 4.6 and Globus 4.2)
Any idea about what's going on. Appreciate your help.
- omer
_________________________________________________________________
Connect to the next generation of MSN Messenger
http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-us&source=wlmailtagline
