1GLOBUS-JOB-SUBMIT(1) Grid Community Toolkit Manual GLOBUS-JOB-SUBMIT(1)
2
6 globus-job-submit - Submit a batch job using GRAM
7
9 globus-job-submit [-dumprsl|-dryrun|-verify] [-file ARGUMENT_FILE]
10 SERVICE-CONTACT [OPTIONS] EXECUTABLE ARGUMENT...
11 globus-job-submit [-help | -usage | -version | -versions]
13
15 The globus-job-submit program constructs a job description from its
16 command-line options and then submits the job to the GRAM service
17 running at SERVICE_CONTACT. The executable and arguments to the
18 executable are provided on the command-line after all other options.
19 Note that the -dumprsl, -dryrun, -verify, and -file command-line
20 options must occur before the first non-option argument, the
21 SERVICE_CONTACT.
22 The globus-job-submit provides similar functionality to globusrun in
24 that it allows batch submission of GRAM jobs. However, unlike
25 globusrun, it uses command-line parameters to define the job instead of
26 RSL expressions.
27 To retrieve the output and error streams of the job, use the program
29 globus-job-get-output. To reclaim resources used by the job by deleting
30 cached files and job state, use the program globus-job-clean. To cancel
31 a batch job submitted by globus-job-submit, use the program
32 globus-job-cancel.
33
35 The full set of options to globus-job-submit are:
36 -help, -usage
38 Display a help message to standard error and exit.
39 -version
41 Display the software version of the globus-job-submit program to
42 standard output.
43 -versions
45 Display the software version of the globus-job-submit program
46 including DiRT information to standard output.
47 -dumprsl
49 Translate the command-line options to globus-job-submit into an RSL
50 expression that can be used with tools such as globusrun.
51 -dryrun
53 Submit the job request to the GRAM service with the dryrun option
54 enabled. When this option is used, the GRAM service prepares to
55 execute the job but stops before submitting the job to the LRM.
56 This can be used to diagnose some problems such as missing files.
57 -verify
59 Submit the job request to the GRAM service with the dryrun option
60 enabled and then without it enabled if the dryrun is successful.
61 -file ARGUMENT_FILE
63 Read additional command-line options from ARGUMENT_FILE.
64 -np PROCESSES, -count PROCESSES
66 Start PROCESSES instances of the executable as a single job.
67 -m MAX_TIME, -maxtime MAX_TIME
69 Schedule the job to run for a maximum of MAX_TIME minutes.
70 -p PROJECT, -project PROJECT
72 Request that the job use the allocation PROJECT when submitting the
73 job to the LRM.
74 -q QUEUE, -queue QUEUE
76 Request that the job be submitted to the LRM using the named QUEUE.
77 -d DIRECTORY, -directory DIRECTORY
79 Run the job in the directory named by DIRECTORY. Input and output
80 files will be interpreted relative to this directory. This
81 directory must exist on the file system on the LRM-managed
82 resource. If not specified, the job will run in the home directory
83 of the user the job is running as.
84 -env NAME=VALUE
86 Define an environment variable named by NAME with the value VALUE
87 in the job environment. This option may be specified multiple times
88 to define multiple environment variables.
89 -stdin [-l | -s] STDIN_FILE
91 Use the file named by STDIN_FILE as the standard input of the job.
92 If the -l option is specified, then this file is interpreted to be
93 on a file system local to the LRM. If the -s option is specified,
94 then this file is interpreted to be on the file system where
95 globus-job-submit is being executed, and the file will be staged
96 via GASS. If neither is specified, the local behavior is assumed.
97 -stdout [-l | -s] STDOUT_FILE
99 Use the file named by STDOUT_FILE as the destination for the
100 standard output of the job. If the -l option is specified, then
101 this file is interpreted to be on a file system local to the LRM.
102 If the -s option is specified, then this file is interpreted to be
103 on the file system where globus-job-submit is being executed, and
104 the file will be staged via GASS. If neither is specified, the
105 local behavior is assumed.
106 -stderr [-l | -s] STDERR_FILE
108 Use the file named by STDERR_FILE as the destination for the
109 standard error of the job. If the -l option is specified, then this
110 file is interpreted to be on a file system local to the LRM. If the
111 -s option is specified, then this file is interpreted to be on the
112 file system where globus-job-submit is being executed, and the file
113 will be staged via GASS. If neither is specified, the local
114 behavior is assumed.
115 -x RSL_CLAUSE
117 Add a set of custom RSL attributes described by RSL_CLAUSE to the
118 job description. The clause must be an RSL conjunction and may
119 contain one or more attributes. This can be used to include
120 attributes which can not be defined by other command-line options
121 of globus-job-submit.
122 -l
124 When included outside the context of -stdin, -stdout, or -stderr
125 command-line options, -l option alters the interpretation of the
126 executable path. If the -l option is specified, then the executable
127 is interpreted to be on a file system local to the LRM.
128 -s
130 When included outside the context of -stdin, -stdout, or -stderr
131 command-line options, -l option alters the interpretation of the
132 executable path. If the -s option is specified, then the executable
133 is interpreted to be on the file system where globus-job-run is
134 being executed, and the file will be staged via GASS. If neither is
135 specified, the local behavior is assumed.
136
138 If the following variables affect the execution of globus-job-submit.
139 X509_USER_PROXY
141 Path to proxy credential.
142 X509_CERT_DIR
144 Path to trusted certificate directory.
145
147 globusrun(1), globus-job-run(1), globus-job-clean(1),
148 globus-job-get-output(1), globus-job-cancel(1)
149
151 Copyright © 1999-2014 University of Chicago
152Grid Community Toolkit 6 03/31/2018 GLOBUS-JOB-SUBMIT(1)