GLOBUS-JOB-GET-OU(1)

💖 GLOBUS-JOB-GET-OU(1) 💖

okay bestie, so this page lives in the Grid Community Toolkit Manual — it's the glow-up guide for globus-job-get-output, and no cap, it's about to make your GRAM job's output retrieval feel like main character energy ✨

🌸 NAME 🌸

globus-job-get-output — go grab the output and error streams from a GRAM job, like a little detective 🕵️♀️💅

🦋 SYNOPSIS 🦋

globus-job-get-output [ -r RESOURCE | -resource RESOURCE ] [OPTIONS]
JOBID

globus-job-get-output [-help | -usage | -version | -versions ]

✨ DESCRIPTION ✨

so basically, globus-job-get-output is the program that goes and fetches the output and error streams of whatever job is named by JOBID. iconic behavior honestly.

By default? It grabs all the output and error data from that job and shows it to you on its own output and error streams. cute. But you can switch things up with command-line options if you want a different vibe — other behavior can be controlled by using command-line options, periodt.

Now here's the behind-the-scenes tea 🍵: the data retrieval is implemented by submitting another job which simply displays the contents of the first job's output and error streams. Yeah, it's jobs all the way down, we love a recursive moment.

And where does that retrieval job go? By default it's submitted to the default GRAM resource running on the same host as the job. But bestie, you can control this — just specify a particular resource manager contact string as the RESOURCE parameter to the -r or -resource option. slay 🔥

🎀 OPTIONS 🎀

• -help, -usage — shows you a help message over on standard error and then dips out (exits). 💫
• -version — prints the software version of the globus-job-get-output program to standard output. flex it.
• -versions — prints the software version of the globus-job-get-output program, and it includes DiRT information too, straight to standard output. extra detail, we love to see it 👑
• -resource RESOURCE, -r RESOURCE — submits the retrieval job to the resource named by RESOURCE instead of the default GRAM service on the same host as the job contact. like, you're picking the location yourself, main character choice 💅
• -out — retrieve only the standard output stream of the job. the default is to retrieve both standard output and standard error, so this is the "just the good stuff" option.
• -err — retrieve only the standard error stream of the job. again, default is both standard output and standard error, so this is you choosing chaos specifically 😭
• -tail LINES, -t LINES — prints only the last LINES count lines of output from the data streams being retrieved. by default, the entire output and error file data is retrieved.

⚠️ heads up bestie: this option can not be used along with the -f or -follow options. pick a lane 💀

• -follow LINES, -f LINES — prints the last LINES count lines of output from the data streams being retrieved, and then waits until canceled, printing any subsequent job output that occurs. it's giving "I'll be here all night" energy. by default, the entire output and error file data is retrieved.

⚠️ and this one can not be used along with the -t or -tail options. no mixing, fr fr 🙈

🌈 ENVIRONMENT 🌈

The following variables affect the execution of globus-job-get-output — so like, they're the vibes in the background making stuff work:

• X509_USER_PROXY — path to proxy credential. 🔑
• X509_CERT_DIR — path to trusted certificate directory. 📁

👑 AUTHOR 👑

Copyright © 1999-2014 University of Chicago

that's the whole page, bestie 💖 this came to you from the Grid Community Toolkit 6, dated 03/31/2018 — stay iconic, go get that output 🫶✨🌸