QRSTAT(1)

💖 QRSTAT(1) — the Grid Engine user command that spills ALL the tea on your Advance Reservations 💖

okay bestie, gather round, because qrstat is about to become your new obsession. it lives in the Grid Engine user commands corner of the manual (yes, the QRSTAT(1) one, that's the girl), and she's here to tell you everything about your ARs. no cap.

---

✨ NAME ✨

qrstat — show the status of Grid Engine Advance Reservations (AR)

---

🌸 SYNTAX 🌸

qrstat [-ar ar_id,...]  [-help] [-u user,...]  [-explain]

she's giving short and iconic, honestly.

---

🦋 DESCRIPTION 🦋

so like, qrstat shows the current status of the available Grid Engine ARs. that's the whole vibe. and if you wanna zoom in on one specific AR instead of the whole group chat? the selection option -ar has you covered, bestie.

now listen, the administrator and the user can both define files that hold any of the options described down below. the cluster-wide one is a sge_qrstat file, and it goes right here:

$SGE_ROOT/$SGE_CELL/common/sge_qrstat

your own private little file gets searched at $HOME/.sge_qrstat. and the way the hierarchy works? the home directory request file has the highest precedence over the cluster global file. she's the main character, periodt. and you can always use the command line to override the flags contained in those files — command line said "i'm the moment" and it's right.

---

💅 OPTIONS 💅

• -ar ar_id,... — prints various information about the ARs identified by the given ar_id list. like, name names and she'll spill.
• -explain — displays the reason for the error state of an AR. possible reasons are the unknown state of a host or queue instance. lowkey so helpful when something's acting up 😭

the output format for the alarm reasons is one line per reason. clean, organized, we love to see it.

• -help — prints a listing of all options. when in doubt, ask the girl herself.
• -u user,... — display information only for those ARs created by the users from the given user list.

the string $user is a placeholder for the current username. an asterisk "*" can be used as a username wildcard to request that all users' ARs be displayed. the default value for this switch is "-u $user". so if you don't say anything, she assumes you mean you. self-care fr fr.

• -xml — this option can be used with all other options and changes the output to XML. the schemas used are referenced in the XML output. the output is printed to stdout. she's bilingual, we stan a flexible queen 👑

---

🌈 OUTPUT FORMATS 🌈

depending on the presence or absence of the -ar option, there are two output formats that need to be differentiated. two whole aesthetics. choose your fighter.

🎀 Advance Reservation Summary (without -ar) 🎀

following the header line, a section for each AR is provided. the columns contain information for:

• the AR id;
• the name of the AR;
• the current state of the AR. one of the following letters with the given meaning:

w - waiting without error
W - warning (effective - waiting with error)
r - running
E - error (effective - running with error)
d - deleted

• the start time of the AR;
• the end time of the AR;
• the duration of the AR.

🧚 Detailed Format (with -ar) 🧚

the output contains two columns. the first one contains all AR attributes. the second one the corresponding value. it's giving "receipts, itemized" and honestly? iconic.

---

💜 ENVIRONMENT VARIABLES 💜

• SGE_ROOT — specifies the location of the Grid Engine standard configuration files.
• SGE_CELL — if set, specifies the default Grid Engine cell. to address a Grid Engine cell qrstat uses (in the order of precedence):
  1. the name of the cell specified in the environment variable SGE_CELL, if it is set.
  2. the name of the default cell, i.e. default.
• SGE_DEBUG_LEVEL — if set, specifies that debug information should be written to stderr. in addition the level of detail in which debug information is generated is defined. she's telling you exactly what's going on, no secrets between us 🫶
• SGE_QMASTER_PORT — if set, specifies the tcp port on which sge_qmaster(8) is expected to listen for communication requests. most installations will use a services map entry for the service "sge_qmaster" instead to define that port.

---

🍓 FILES 🍓

• <sge_root>/<cell>/common/act_qmaster — Grid Engine master host file
• <sge_root>/<cell>/common/sge_qrstat — cluster qrstat default options
• $HOME/.sge_qrstat — user qrstat default options

---

⭐ SEE ALSO ⭐

sge_intro(1), qrsub(1), qrdel(1), qsub(1),

go read the whole friend group, they're all linked 💖

---

👑 COPYRIGHT 👑

see sge_intro(1) for a full statement of rights and permissions.

---

ok and one last thing bestie — this page is from SGE 8.1.3pre, dated 2011-05-20, and she answers to QRSTAT(1). mwah 💋 go check your ARs, you deserve to know what's going on in your own cluster. slay, stay hydrated, and remember: -explain when things go weird. bye babes! 🌸✨💖