1GLOBUS-JOB-RUN(1) Grid Community Toolkit Manual GLOBUS-JOB-RUN(1)
2
6 globus-job-run - Execute a job using GRAM
7
9 globus-job-run [-dumprsl|-dryrun|-verify] [-file ARGUMENT_FILE]
10 SERVICE-CONTACT [OPTIONS] EXECUTABLE ARGUMENT...
11 globus-job-run [-help | -usage | -version | -versions]
13
15 The globus-job-run 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-run provides similar functionality to globusrun in that
24 it allows interactive start-up of GRAM jobs. However, unlike globusrun,
25 it uses command-line parameters to define the job instead of RSL
26 expressions.
27
29 The full set of options to globus-job-run are:
30 -help, -usage
32 Display a help message to standard error and exit.
33 -version
35 Display the software version of the globus-job-run program to
36 standard output.
37 -version
39 Display the software version of the globus-job-run program
40 including DiRT information to standard output.
41 -dumprsl
43 Translate the command-line options to globus-job-run into an RSL
44 expression that can be used with tools such as globusrun.
45 -dryrun
47 Submit the job request to the GRAM service with the dryrun option
48 enabled. When this option is used, the GRAM service prepares to
49 execute the job but stops before submitting the job to the LRM.
50 This can be used to diagnose some problems such as missing files.
51 -verify
53 Submit the job request to the GRAM service with the dryrun option
54 enabled and then without it enabled if the dryrun is successful.
55 -file ARGUMENT_FILE
57 Read additional command-line options from ARGUMENT_FILE.
58 -np PROCESSES, -count PROCESSES
60 Start PROCESSES instances of the executable as a single job.
61 -m MAX_TIME, -maxtime MAX_TIME
63 Schedule the job to run for a maximum of MAX_TIME minutes.
64 -p PROJECT, -project PROJECT
66 Request that the job use the allocation PROJECT when submitting the
67 job to the LRM.
68 -q QUEUE, -queue QUEUE
70 Request that the job be submitted to the LRM using the named QUEUE.
71 -d DIRECTORY, -directory DIRECTORY
73 Run the job in the directory named by DIRECTORY. Input and output
74 files will be interpreted relative to this directory. This
75 directory must exist on the file system on the LRM-managed
76 resource. If not specified, the job will run in the home directory
77 of the user the job is running as.
78 -env NAME=VALUE
80 Define an environment variable named by NAME with the value VALUE
81 in the job environment. This option may be specified multiple times
82 to define multiple environment variables.
83 -stdin [-l | -s] STDIN_FILE
85 Use the file named by STDIN_FILE as the standard input of the job.
86 If the -l option is specified, then this file is interpreted to be
87 on a file system local to the LRM. If the -s option is specified,
88 then this file is interpreted to be on the file system where
89 globus-job-run is being executed, and the file will be staged via
90 GASS. If neither is specified, the local behavior is assumed.
91 -stdout [-l | -s] STDOUT_FILE
93 Use the file named by STDOUT_FILE as the destination for the
94 standard output of the job. If the -l option is specified, then
95 this file is interpreted to be on a file system local to the LRM.
96 If the -s option is specified, then this file is interpreted to be
97 on the file system where globus-job-run is being executed, and the
98 file will be staged via GASS. If neither is specified, the local
99 behavior is assumed.
100 -stderr [-l | -s] STDERR_FILE
102 Use the file named by STDERR_FILE as the destination for the
103 standard error of the job. If the -l option is specified, then this
104 file is interpreted to be on a file system local to the LRM. If the
105 -s option is specified, then this file is interpreted to be on the
106 file system where globus-job-run is being executed, and the file
107 will be staged via GASS. If neither is specified, the local
108 behavior is assumed.
109 -x RSL_CLAUSE
111 Add a set of custom RSL attributes described by RSL_CLAUSE to the
112 job description. The clause must be an RSL conjunction and may
113 contain one or more attributes. This can be used to include
114 attributes which can not be defined by other command-line options
115 of globus-job-run.
116 -l, -s
118 When included outside the context of -stdin, -stdout, or -stderr
119 command-line options, -l option alters the interpretation of the
120 executable path. If the -l option is specified, then the executable
121 is interpreted to be on a file system local to the LRM.
122
124 The following variables affect the execution of globus-job-run:
125 X509_USER_PROXY
127 Path to proxy credential.
128 X509_CERT_DIR
130 Path to trusted certificate directory.
131
133 globusrun(1), globus-job-submit(1), globus-job-clean(1),
134 globus-job-get-output(1), globus-job-cancel(1)
135
137 Copyright © 1999-2014 University of Chicago
138Grid Community Toolkit 6 03/31/2018 GLOBUS-JOB-RUN(1)