QDEL(1P)

💅 QDEL(1P) — the POSIX Programmer's Manual, but make it cute

okay bestie, so this page lives in the POSIX Programmer's Manual, and before we even get into it there's a lil heads-up section, so let's go 🫶

✨ 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.

🚨 not me warning you upfront: if you're on Linux, go check the Linux page too, because things can be different over here, or the thing might not even exist on Linux at all. no cap.

---

🌸 NAME 🌸

qdel — delete batch jobs 💀✨

like. that's it. that's the whole vibe. it deletes jobs.

---

🎀 SYNOPSIS 🎀

qdel job_identifier...

one or more job identifiers, bestie. plural. she's flexible like that.

---

🦋 DESCRIPTION 🦋

So here's the tea ☕ — a batch job gets deleted by sending a request to the batch server that manages the batch job. And once a batch job has been deleted? It is no longer subject to management by batch services. gone. unbothered. free. 💅

The qdel utility is a user-accessible client of batch services that requests the deletion of one or more batch jobs.

The qdel utility shall request a batch server to delete those batch jobs for which a batch job_identifier is presented to the utility.

And the order matters, okay? The qdel utility shall delete batch jobs in the order in which their batch *job_identifier*s are presented to the utility. first come, first deleted, periodt.

Now, if the qdel utility fails to process any batch job_identifier successfully, she does NOT give up. The utility shall proceed to process the remaining batch *job_identifier*s, if any. resilience queen 👑

The qdel utility shall delete each batch job by sending a Delete Job Request to the batch server that manages the batch job.

And the qdel utility shall not exit until the batch job corresponding to each successfully processed batch job_identifier has been deleted. she waits. she's committed. no leaving early. 🫶

---

✨ OPTIONS ✨

None.

literally zero. nothing. the girl has no flags. we love a minimalist. 🙈

---

💖 OPERANDS 💖

The qdel 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 yeah, you gotta feed her proper job identifiers. she's not doing guesswork.

---

🌈 STDIN 🌈

Not used.

she does not read from you. do not pipe into her. she's not listening bestie 😭

---

💜 INPUT FILES 💜

None.

---

🧚 ENVIRONMENT VARIABLES 🧚

The following environment variables shall affect the execution of qdel:

• 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.

like, the whole locale squad + your login name. she checks the vibes of your environment before she moves 💅

---

⭐ ASYNCHRONOUS EVENTS ⭐

Default.

nothing fancy here, moving on.

---

🍓 STDOUT 🍓

An implementation of the qdel utility may write informative messages to standard output.

"may" — so like, she might chat a lil. might not. depends on the implementation's mood. ✨

---

🌸 STDERR 🌸

The standard error shall be used only for diagnostic messages.

only diagnostics. that's the rule. keep the drama in stderr where it belongs 💀

---

🎀 OUTPUT FILES 🎀

None.

---

🦋 EXTENDED DESCRIPTION 🦋

None.

she keeps it simple, iconic, and short. 👑

---

🔥 EXIT STATUS 🔥

The following exit values shall be returned:

1. 0 — Successful completion. ✨
2. >0 — An error occurred. 😭

---

💀 CONSEQUENCES OF ERRORS 💀

In addition to the default behavior, the qdel utility 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 the qdel utility waits to output the diagnostic message while attempting to locate the job on other servers is implementation-defined.

so basically: if the server's like "never heard of her", qdel isn't required to tell you. and whether she waits around to spill the tea while checking other servers? that's up to whoever implemented her. iykyk.

The following sections are informative.

---

💜 APPLICATION USAGE 💜

None.

---

🧚 EXAMPLES 🧚

None.

sorry bestie, no examples in the original. we work with what we got 😭

---

👑 RATIONALE 👑

The qdel utility allows users and administrators to delete jobs.

The qdel utility provides functionality that is not otherwise available. For example, the kill utility of the operating system does not suffice. First, to use the kill utility, the user might have to log in on a remote node, because the kill utility does not operate across the network. Second, unlike qdel, kill cannot remove jobs from queues. Lastly, the arguments of the qdel utility are job identifiers rather than process identifiers, and so this utility can be passed the output of the qselect utility, thus providing users with a means of deleting a list of jobs.

not me comparing her to kill 💅 kill can't do it across the network, can't yank jobs out of queues, and takes process identifiers instead of job identifiers. qdel is the upgrade, and she plays nice with qselect output, so you can nuke a whole list at once. ate.

Because a set of jobs can be selected using the qselect utility, the qdel utility has not been complicated with options that provide for selection of jobs. Instead, the batch jobs to be deleted are identified individually by their job identifiers.

that's the whole reason she has no options — qselect handles the picking, qdel handles the deleting. division of labor, we love to see it. 🤝

Historically, the qdel utility has been a component of NQS, the existing practice on which it is based. However, the qdel utility defined in this volume of POSIX.1‐2017 does not provide an option for specifying a signal number to send to the batch job prior to the killing of the process; that capability has been subsumed by the qsig utility.

so if you're looking for the "send a signal before killing" thing? that's not here anymore. that's qsig's job now. don't come for qdel about it. 🙈

A discussion was held about the delays of networking and the possibility that the batch server may never respond, due to a down router, down batch server, or other network mishap. The DESCRIPTION records this under the words ``fails to process any job identifier''. In the broad sense, the network problem is also an error, which causes the failure to process the batch job identifier.

they literally had a whole discussion about routers being down and servers ghosting you. in the broad sense, a network problem is also an error, and it causes the failure to process the batch job identifier. documented, iconic. ✨

---

🌈 FUTURE DIRECTIONS 🌈

The qdel utility may be removed in a future version.

😭 not the possible cancellation arc. enjoy her while she's here bestie.

---

💖 SEE ALSO 💖

• Chapter 3, Batch Environment Services
• kill
• qselect
• qsig

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 page, bestie!! this one came from IEEE/The Open Group, dated 2017, and the page is QDEL(1P). go forth and delete those jobs responsibly. slay 💅✨