qrls(1B)

πŸ“¦ version 6.1.3, in epel 9

πŸŽ€ qrls(1B) β€” the PBS manual page πŸŽ€

okay bestie, welcome to the PBS manual page for qrls β€” the command that releases hold energy so your batch jobs can move again. ✨


✨ NAME ✨

qrls β€” release hold on pbs batch jobs. periodt. πŸ’…


πŸ“œ SYNOPSIS πŸ“œ

qrls [-h hold_list] [-t array_range] job_identifier ...

One line, iconic, no cap. You pass a job or several, and optionally which holds and which array range. πŸŽ€


πŸ’– DESCRIPTION πŸ’–

The qrls command removes or releases holds which exist on batch jobs.

A job may have one or more types of holds which make the job ineligible for execution. The types of holds are USER, OTHER, and SYSTEM. The different types of holds may require that the user issuing the qrls command have special privilege. Typically, the owner of the job will be able to remove a USER hold, but not an OTHER or SYSTEM hold. An attempt to release a hold for which the user does not have the correct privilege is an error and no holds will be released for that job. 🚨 like, zero, none, don’t even try it.

If no -h option is specified, the USER hold will be released. default behavior, cute and simple. 🫢

If the job has no execution_time pending, the job will change to the queued state. If an execution_time is still pending, the job will change to the waiting state. the state machine is state-machining, bestie. πŸ¦‹


πŸ’… OPTIONS πŸ’…

  • -h hold_list β€” defines the types of hold to be released from the jobs. The hold_list option argument is a string consisting of one or more of the letters "u", "o", an "s" in any combination. The hold type associated with each letter is:
    • u β€” USER
    • o β€” OTHER
    • s β€” SYSTEM
  • -t array_range β€” the array_range argument is an integer id or a range of integers. Multiple ids or id ranges can be combined in a comma delimted list. Examples: -t 1-100 or -t 1,10,50-100 ✨

If an array range isn't specified, the command tries to operate on the entire array. The command acts on the array (or specified range of the array) just as it would on an individual job. so yes, the whole array can catch these hands. πŸ’…πŸ”₯


🧚 OPERANDS 🧚

The qrls command accepts one or more job_identifier operands of the form:

sequence_number[.server_name][@server]

keep the brackets exactly as shown, bestie. that’s the shape. πŸŽ€


😭 STANDARD ERROR 😭

The qrls command will write a diagnostic message to standard error for each error occurrence. so if something goes wrong, stderr is not gonna ghost you about it. πŸ˜­πŸ’€


🚦 EXIT STATUS 🚦

Upon successful processing of all the operands presented to the qrls command, the exit status will be a value of zero. slay, zero, clean exit, we love to see it. βœ…πŸ‘‘

If the qrls command fails to process any operand, the command exits with a value greater than zero. that’s the red flag: greater than zero. πŸš©πŸ™ˆ


🫢 SEE ALSO 🫢

other icons in the PBS cinematic universe:

  • qsub(1B)
  • qalter(1B)
  • qhold(1B)
  • pbs_alterjob(3B)
  • pbs_holdjob(3B)
  • pbs_rlsjob(3B)

okay that’s the whole page, bestie. this came from the Local source/version stamp for qrls(1B), and the footer didn’t give a date, so I’m not inventing one. πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from
  • epel 9: torque-client 6.1.3-8.el9 Β· OpenPBS and TORQUEv1.1
  • πŸ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms