QMOVE(1POSIX)

📦 version 2017a, in debian bookworm, debian trixie, ubuntu jammy, ubuntu noble, ubuntu resolute, ubuntu stonking

💖 QMOVE(1POSIX) — the POSIX Programmer's Manual glow-up 💖

okay bestie, listen. This one's from the POSIX Programmer's Manual (the IEEE/The Open Group girlies), and it's all about qmove. Buckle up 🎀

🌸 PROLOG 🌸

Real talk: this manual page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ — so go check the corresponding Linux manual page for the actual Linux behavior — or honestly, the interface might not even be implemented on Linux at all. 💀 Not every platform shows up to the party.

✨ NAME ✨

qmove — move batch jobs. that's it. that's the whole job. 💅

🦋 SYNOPSIS 🦋

qmove destination job_identifier...

💜 DESCRIPTION 💜

So, to move a batch job means: you yank the batch job out of the batch queue it's currently sitting in, and you instantiate that batch job in another batch queue. A batch job gets moved when a request goes out to the batch server that manages that batch job. And qmove? It's a user-accessible batch client that requests the movement of one or more batch jobs. she's the messenger 🫶

The qmove utility shall move those batch jobs — and only those batch jobs — for which a batch job_identifier is presented to the utility.

The qmove utility shall move batch jobs in the order in which the corresponding batch *job_identifier*s are presented to the utility. first come, first moved, no cutting the line 🚫

If the qmove utility fails to process a batch job_identifier successfully, the utility shall proceed to process the remaining batch *job_identifier*s, if any. no quitting over one flop, she keeps it moving 💪

The qmove utility shall move batch jobs by sending a Move Job Request to the batch server that manages each batch job. And the qmove utility shall not exit before the batch jobs corresponding to all successfully processed batch *job_identifier*s have been moved. she waits until it's done, periodt ✋

🎀 OPTIONS 🎀

None.

bestie there are literally no options. zero. the void. the audacity. iconic behavior honestly 💅

🌈 OPERANDS 🌈

  • The qmove utility shall accept one operand that conforms to the syntax for a destination (see Section 3.3.2, Destination).
  • The qmove 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).

🌸 STDIN 🌸

Not used. she's not listening to stdin today 🙈

🦋 INPUT FILES 🦋

None.

💖 ENVIRONMENT VARIABLES 💖

The following environment variables shall affect the execution of qmove:

  • LANG — Provides 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 for the precedence of internationalization variables used to determine the values of locale categories.)
  • LC_ALL — If set to a non-empty string value, overrides the values of all the other internationalization variables. she overrules everybody 👑
  • LC_CTYPE — Determines 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 — Determines the locale that should be used to affect the format and contents of diagnostic messages written to standard error.
  • LOGNAME — Determines the login name of the user.

⭐ ASYNCHRONOUS EVENTS ⭐

Default. no drama, just vibes 🧚

🎀 STDOUT 🎀

None.

🍓 STDERR 🍓

The standard error shall be used only for diagnostic messages. that's its whole personality 😭

🌸 OUTPUT FILES 🌸

None.

✨ EXTENDED DESCRIPTION ✨

None.

💀 EXIT STATUS 💀

The following exit values shall be returned:

  • 0 — Successful completion. ate and left no crumbs 💅
  • >0 — An error occurred.

🔥 CONSEQUENCES OF ERRORS 🔥

In addition to the default behavior, the qmove 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 qmove utility waits to output the diagnostic message while attempting to locate the job on other servers is implementation-defined. (iykyk — it's giving "we'll see" 🙃)

The following sections are informative. (translation: not requirements, just lore 📖)

💜 APPLICATION USAGE 💜

None.

🦋 EXAMPLES 🦋

None.

👑 RATIONALE 👑

The qmove utility allows users to move jobs between queues.

The alternative to using the qmove utility — deleting the batch job and requeuing it — entails considerably more typing. and nobody has the energy for that fr fr 😩

Since the means of selecting jobs based on attributes has been encapsulated in the qselect utility, the only option of the qmove utility concerns authorization. The -u option provides the user with the convenience of changing the user identifier under which the batch job will execute. Minimalism and consistency have taken precedence over convenience; the -u option has been deleted because the equivalent capability exists with the -u option of the qalter utility. so the -u is gone, bestie, go use qalter for that 🫶

🌈 FUTURE DIRECTIONS 🌈

The qmove utility may be removed in a future version. not me saying this might get cancelled 😭

💖 SEE ALSO 💖

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

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 .

okay that's the whole page, bestie 🥰 this diva was brought to you by IEEE/The Open Group, 2017, and she is out. mwah 💅✨💖

📦 where this page comes from