GLOBUS-JOB-RUN(1)
π globus-job-run β the Grid Community Toolkit manual, but make it a group chat π
okay so bestie, this is the page for globus-job-run, from the Grid Community Toolkit manual, section 1. yes it's a whole manpage. no it's not boring. sit down, hydrate, let's go π«Ά
β¨ NAME β¨
globus-job-run β execute a job using GRAM π
π SYNOPSIS π
globus-job-run [-dumprsl|-dryrun|-verify] [-file ARGUMENT_FILE]
SERVICE-CONTACT [OPTIONS] EXECUTABLE ARGUMENT...
globus-job-run [-help | -usage | -version | -versions]
π¦ DESCRIPTION π¦
So here's the tea β: globus-job-run builds a whole job description out of its command-line options, and then it hands that job over to the GRAM service running at SERVICE_CONTACT. The executable and the arguments you wanna feed that executable go on the command line after all the other options. That's the order. It matters. Don't fight it.
π¨ important bestie π¨ the-dumprsl,-dryrun,-verify, and-filecommand-line options must come before the first non-option argument, which is theSERVICE_CONTACT. That's not a vibe, that's a rule.
It does basically the same thing as globusrun in that it lets you start up GRAM jobs interactively β¨. BUT β and this is the plot twist β unlike globusrun, it defines the job with command-line parameters instead of RSL expressions. iykyk π
π OPTIONS π
the full set of options to globus-job-run is, and I quote the entire list because we do not skip, we do not summarise, we respect the material:
-help,-usageβ pops a help message over to standard error and then dips out. that's it. that's the whole thing. π-versionβ prints the software version of theglobus-job-runprogram to standard output β-versionβ prints the software version of theglobus-job-runprogram, this time including DiRT information, to standard output π yes bestie,-versionshows up twice in this list and I am simply passing along the lore, I don't make the rules. one is the plain version, one is the version with the DiRT info. both are real, both are listed, periodt.-dumprslβ translates the command-line options you gave toglobus-job-runinto an RSL expression, so you can go use it with tools likeglobusrun. it's giving translator energy π-dryrunβ submits the job request to the GRAM service with thedryrunoption enabled. when you use this, the GRAM service gets all ready to execute the job and then stops right before submitting it to the LRM. very "I'm not gonna do it, I'm just gonna think about it." it's useful for diagnosing problems like missing files π-verifyβ submits the job request to the GRAM service with thedryrunoption enabled, and then submits it again withoutdryrunenabled if that dryrun went fine. like a dress rehearsal and then the real show π-fileARGUMENT_FILE β reads additional command-line options from ARGUMENT_FILE π-npPROCESSES,-countPROCESSES β starts PROCESSES instances of the executable, all as a single job π―-mMAX_TIME,-maxtimeMAX_TIME β schedules the job to run for a max of MAX_TIME minutes β³-pPROJECT,-projectPROJECT β asks that the job use the allocation PROJECT when it gets submitted to the LRM π·οΈ-qQUEUE,-queueQUEUE β asks that the job be submitted to the LRM using the named QUEUE πΆββοΈ-dDIRECTORY,-directoryDIRECTORY β runs the job in the directory named by DIRECTORY. input and output files get interpreted relative to this directory. and listen β this directory must exist on the file system on the LRM-managed resource. if you don't specify one, the job runs in the home directory of the user the job is running as π-envNAME=VALUE β defines an environment variable named NAME with the value VALUE in the job environment π±. you can specify this option multiple times to define multiple environment variables. stack 'em π-stdin[-l|-s] STDIN_FILE β uses the file named by STDIN_FILE as the standard input of the job π₯. if-lis specified, the file is interpreted to be on a file system local to the LRM. if-sis specified, the file is interpreted to be on the file system whereglobus-job-runis being executed, and the file gets staged via GASS. if neither one is specified, the local behavior is assumed πΈ-stdout[-l|-s] STDOUT_FILE β uses the file named by STDOUT_FILE as the destination for the standard output of the job π€. if-lis specified, the file is interpreted to be on a file system local to the LRM. if-sis specified, the file is interpreted to be on the file system whereglobus-job-runis being executed, and the file gets staged via GASS. if neither one is specified, the local behavior is assumed πΊ-stderr[-l|-s] STDERR_FILE β uses the file named by STDERR_FILE as the destination for the standard error of the job π. if-lis specified, the file is interpreted to be on a file system local to the LRM. if-sis specified, the file is interpreted to be on the file system whereglobus-job-runis being executed, and the file gets staged via GASS. if neither one is specified, the local behavior is assumed π-xRSL_CLAUSE β adds a set of custom RSL attributes, described by RSL_CLAUSE, to the job description π§©. the clause must be an RSL conjunction and it may contain one or more attributes. use this for the attributes that just can't be defined by any of the other command-line options ofglobus-job-run. it's the wildcard slot π-l,-sβ when included outside the context of the-stdin,-stdout, or-stderrcommand-line options, the-loption alters the interpretation of the executable path π. if-lis specified, then the executable is interpreted to be on a file system local to the LRM.
π ENVIRONMENT π
these variables affect how globus-job-run runs, bestie:
X509_USER_PROXYβ path to proxy credential πX509_CERT_DIRβ path to trusted certificate directory π
π«Ά SEE ALSO π«Ά
go read these next, they're all iconic:
globusrun(1), globus-job-submit(1), globus-job-clean(1), globus-job-get-output(1), globus-job-cancel(1)
π AUTHOR π
Copyright Β© 1999-2014 University of Chicago
and that's the whole page, no notes β¨ this was the Grid Community Toolkit 6 manual, dated 03/31/2018, for GLOBUS-JOB-RUN(1) β tysm for reading, go run a job, slay, mwah ππ¦π
π¦ where this page comes from
- debian bookworm: globus-gram-client-tools 12.2-2 Β· Apache-2.0
- debian trixie: globus-gram-client-tools 12.2-3 Β· Apache-2.0
- epel 10: globus-gram-client-tools 12.2-4.el10_0 Β· Apache-2.0
- epel 9: globus-gram-client-tools 12.2-1.el9 Β· ASL 2.0
- fedora 43: globus-gram-client-tools 12.2-9.fc43 Β· Apache-2.0
- fedora 44: globus-gram-client-tools 12.2-10.fc44 Β· Apache-2.0
- ubuntu jammy: globus-gram-client-tools 12.1-1 Β· Apache-2.0
- ubuntu noble: globus-gram-client-tools 12.2-2build2 Β· Apache-2.0
- ubuntu questing: globus-gram-client-tools 12.2-3
- ubuntu resolute: globus-gram-client-tools 12.2-3build1 Β· Apache-2.0
- ubuntu stonking: globus-gram-client-tools 12.2-3build1 Β· Apache-2.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms