QRERUN(1P)

💖 QRERUN — bestie edition 💖

okay so real talk: this page comes from the POSIX Programmer's Manual, and it's qrerun(1P). before we get into it, the manual says — and I'm quoting the vibe here — that this manual page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ (consult the corresponding Linux manual page for details of Linux behavior), or the interface may not be implemented on Linux. 🫶 so like, don't come for me if your Linux box is doing its own thing.

---

✨ PROLOG ✨

This manual page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ (consult the corresponding Linux manual page for details of Linux behavior), or the interface may not be implemented on Linux.

ngl that's the whole prolog, she's short and she knows it 💅

---

🌸 NAME 🌸

qrerun — rerun batch jobs

like... it reruns ur batch jobs. that's the whole personality. 😌

---

🦋 SYNOPSIS 🦋

qrerun job_identifier...

yes bestie, that's it. one or more job_identifiers. no flags. no options. she's uncomplicated. ✨

---

💜 DESCRIPTION 💜

okay so to rerun a batch job means three things, and I need you to hold all three:

1. terminate the session leader of the batch job
2. delete any associated checkpoint files
3. return the batch job to the batch queued state

a batch job gets rerun because a request goes to the batch server that manages that batch job. and qrerun is the user-accessible batch client that asks for one or more batch jobs to get rerun. 🎀

so here's the rundown:

• qrerun shall rerun those batch jobs for which a batch job_identifier is presented to the utility.
• qrerun shall rerun batch jobs in the order in which their batch job_identifiers are presented to the utility. (order matters, she's a good listener 💅)
• If qrerun fails to process any batch job_identifier successfully, the utility shall proceed to process the remaining batch job_identifiers, if any. (no rage-quitting mid-list, we love a resilient queen 👑)
• qrerun shall rerun batch jobs by sending a Rerun Job Request to the batch server that manages each batch job.
• For each successfully processed batch job_identifier, qrerun shall have rerun the corresponding batch job at the time the utility exits.

periodt. that's the contract. 🦋

---

✨ OPTIONS ✨

None.

literally none. zero. the void. not a single flag. she said "I don't do options" and I respect it. 😭

---

🎀 OPERANDS 🎀

The qrerun utility shall accept one or more operands that conform to the syntax for a batch job_identifier (see Section 3.3.1, Batch Job Identifier).

so like, at least one operand, and each one has to be a real batch job_identifier. no random nonsense. 💖

---

🍓 STDIN 🍓

Not used.

she does not read from stdin. she's not listening to your pipe. 🙈

---

🧚 INPUT FILES 🧚

None.

---

🌈 ENVIRONMENT VARIABLES 🌈

these shall affect the execution of qrerun, so pay attention bestie:

• LANG — Provide a default value for the internationalization variables that are unset or null. (See the Base Definitions volume of POSIX.1‐2017, Section 8.2, Internationalization Variables the precedence of internationalization variables used to determine the values of locale categories.)
• LC_ALL — If set to a non-empty string value, override the values of all the other internationalization variables.
• LC_CTYPE — Determine the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multi-byte characters in arguments).
• LC_MESSAGES — Determine the locale that should be used to affect the format and contents of diagnostic messages written to standard error.
• LOGNAME — Determine the login name of the user.

five env vars, all iconic, all doing their little jobs 🫶

---

💅 ASYNCHRONOUS EVENTS 💅

Default.

---

⭐ STDOUT ⭐

None.

nope. nothing. silence. she's mysterious. ✨

---

💀 STDERR 💀

The standard error shall be used only for diagnostic messages.

so if something goes sideways, that's where you'll hear about it. 😭

---

🌸 OUTPUT FILES 🌸

None.

---

🦋 EXTENDED DESCRIPTION 🦋

None.

she said "no extended description, I'm built different" 💅

---

👑 EXIT STATUS 👑

The following exit values shall be returned:

• 0 — Successful completion. 🎉
• >0 — An error occurred. 😭

---

🙈 CONSEQUENCES OF ERRORS 🙈

In addition to the default behavior, qrerun shall not be required to write a diagnostic message to standard error when the error reply received from a batch server indicates that the batch job_identifier does not exist on the server. Whether or not qrerun waits to output the diagnostic message while attempting to locate the job on other servers is implementation-defined.

so like, sometimes silence is on purpose, okay? don't @ her about it. 🫶

The following sections are informative.

---

🎀 APPLICATION USAGE 🎀

None.

---

💖 EXAMPLES 💖

None.

no examples bestie, we're rawdogging the spec on vibes alone 😌

---

✨ RATIONALE ✨

The qrerun utility allows users to cause jobs in the running state to exit and rerun.

The qrerun utility is a new utility, vis-a-vis existing practice, that has been defined in this volume of POSIX.1‐2017 to correct user-perceived deficiencies in the existing practice.

she's new here and she's already fixing things. main character energy fr fr. 👑

---

🌟 FUTURE DIRECTIONS 🌟

The qrerun utility may be removed in a future version.

not to be dramatic but 💀 keep an eye on this one.

---

🔥 SEE ALSO 🔥

• Chapter 3, Batch Environment Services
• The Base Definitions volume of POSIX.1‐2017, Chapter 8, Environment Variables

---

🧚 COPYRIGHT 🧚

Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1-2017, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 7, 2018 Edition, Copyright (C) 2018 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html .

Any typographical or formatting errors that appear in this page are most likely to have been introduced during the conversion of the source files to man page format. To report such errors, see https://www.kernel.org/doc/man-pages/reporting_bugs.html .

---

and that's the whole thing bestie 🫶 this page was served up by IEEE/The Open Group, 2017 — QRERUN(1P), that's the one. stay queued, stay iconic, and remember: no options, no stdin, no output files, just vibes and a Rerun Job Request. 💖✨🎀