QMOVE(1P)

💅 qmove — move batch jobs 💅

okay bestie, welcome to the POSIX Programmer's Manual entry for qmove(1P), straight out of the IEEE/The Open Group archives. pull up a chair, grab a strawberry 🍓, and let's get into it.

---

🦋 PROLOG

so like, this manual page is part of the POSIX Programmer's Manual. and here's the tea: the Linux implementation of this interface may differ (so pls consult the corresponding Linux manual page for the deets on Linux behavior), or honestly the interface may not be implemented on Linux at all. 🙈

---

✨ NAME

qmove — move batch jobs. that's it, that's the whole vibe. 👑

---

🎀 SYNOPSIS

qmove destination job_identifier...

---

💖 DESCRIPTION

okay so, to move a batch job is to remove the batch job from the batch queue it's currently living in and instantiate it in another batch queue. glow-up via relocation, basically. ✨

a batch job gets moved by a request sent to the batch server that manages the batch job. and qmove is a user-accessible batch client that requests the movement of one or more batch jobs.

the qmove utility shall move those batch jobs, and only those batch jobs, for which a batch job_identifier is presented to the utility. no surprise moves, no cap.

it shall move batch jobs in the order in which the corresponding batch job_identifiers are presented to the utility. first come, first relocated. 💅

if qmove fails to process a batch job_identifier successfully, the utility shall proceed to process the remaining batch job_identifiers, if any. it does not ghost the rest of the list, periodt.

and it moves batch jobs by sending a Move Job Request to the batch server that manages each batch job. the qmove utility shall not exit before the batch jobs corresponding to all successfully processed batch job_identifiers have been moved. it stays until the job is done. main character energy fr fr. 👑

---

🌸 OPTIONS

None. literally none, bestie. zero. the minimalism is iconic. 💀

---

🌈 OPERANDS

the qmove utility shall accept one operand that conforms to the syntax for a destination (see Section 3.3.2, Destination).

and it 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: one destination, then as many job ids as your heart desires. 🫶

---

💜 STDIN

Not used. nothing goes in here. 🙈

---

🧚 INPUT FILES

None.

---

⭐ ENVIRONMENT VARIABLES

these lil guys affect how qmove runs:

• 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, it overrides the values of all the other internationalization variables. it's giving "I'm in charge here." 💅
• 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. standard behavior, no drama.

---

💖 STDOUT

None. nothing gets printed here. silence, but make it slay. 😌

---

🎀 STDERR

the standard error shall be used only for diagnostic messages. that's its whole job.

---

🌸 OUTPUT FILES

None.

---

🌈 EXTENDED DESCRIPTION

None. this section is empty and honestly it's thriving. ✨

---

💅 EXIT STATUS

these exit values shall be returned:

• 0 — Successful completion. 🎉
• >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. so like, sometimes it just... won't tell you. 🙈

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

⚠️ the following sections are informative. they're the vibes, not the rules.

---

🍓 APPLICATION USAGE

None.

---

🧚 EXAMPLES

None.

---

💜 RATIONALE

the qmove utility allows users to move jobs between queues. simple as that, bestie.

the alternative to using qmove—deleting the batch job and requeuing it—entails considerably more typing. like, why would you do that to yourself. 😭

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. but 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. she left the group chat. 💀

---

⭐ FUTURE DIRECTIONS

the qmove utility may be removed in a future version. so like, enjoy her while she's here. 🥲

---

🌈 SEE ALSO

• Chapter 3, Batch Environment Services, qalter, qselect
• 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 was brought to you by the fine folks at IEEE/The Open Group, dated 2017, under the title QMOVE(1P). go forth and move those jobs. slay. 💅✨