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 -file command-line options must come before the first non-option argument, which is the SERVICE_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 the globus-job-run program to standard output ⭐
  • -version β€” prints the software version of the globus-job-run program, this time including DiRT information, to standard output πŸ’€ yes bestie, -version shows 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 to globus-job-run into an RSL expression, so you can go use it with tools like globusrun. it's giving translator energy 🌈
  • -dryrun β€” submits the job request to the GRAM service with the dryrun option 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 the dryrun option enabled, and then submits it again without dryrun enabled if that dryrun went fine. like a dress rehearsal and then the real show πŸ’ƒ
  • -file ARGUMENT_FILE β€” reads additional command-line options from ARGUMENT_FILE πŸ“„
  • -np PROCESSES, -count PROCESSES β€” starts PROCESSES instances of the executable, all as a single job πŸ‘―
  • -m MAX_TIME, -maxtime MAX_TIME β€” schedules the job to run for a max of MAX_TIME minutes ⏳
  • -p PROJECT, -project PROJECT β€” asks that the job use the allocation PROJECT when it gets submitted to the LRM 🏷️
  • -q QUEUE, -queue QUEUE β€” asks that the job be submitted to the LRM using the named QUEUE πŸšΆβ€β™€οΈ
  • -d DIRECTORY, -directory DIRECTORY β€” 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 🏠
  • -env NAME=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 -l is specified, the file is interpreted to be on a file system local to the LRM. if -s is specified, the file is interpreted to be on the file system where globus-job-run is 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 -l is specified, the file is interpreted to be on a file system local to the LRM. if -s is specified, the file is interpreted to be on the file system where globus-job-run is 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 -l is specified, the file is interpreted to be on a file system local to the LRM. if -s is specified, the file is interpreted to be on the file system where globus-job-run is being executed, and the file gets staged via GASS. if neither one is specified, the local behavior is assumed πŸ“
  • -x RSL_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 of globus-job-run. it's the wildcard slot 😎
  • -l, -s β€” when included outside the context of the -stdin, -stdout, or -stderr command-line options, the -l option alters the interpretation of the executable path πŸ‘€. if -l is 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 πŸ’–πŸ¦‹πŸ‘‘