qrls(1B)

πŸ“¦ version 23.06.06-unstable-2026-04, in nixos 26.05, nixpkgs unstable

πŸ’… qrls β€” release hold on PBS jobs πŸŽ€

okay bestie, welcome to the qrls(1B) page from PBS Professional β€” this is the one where we let your jobs out of hold jail ✨


🌸 NAME 🌸

  • qrls β€” release hold on PBS jobs

πŸ¦‹ SYNOPSIS πŸ¦‹

qrls [-h <hold list>] <job ID> [<job ID> ...]
qrls --version

✨ DESCRIPTION ✨

The qrls command removes or releases holds on batch jobs or job arrays β€” but not on subjobs or ranges of subjobs. no cap, that part matters πŸ’…

A job may have one or more types of holds which make the job ineligible for execution. like, it's literally sitting there waiting for you to free it πŸ₯Ί

If you qrls a job whose Execution_Time attribute is not set to a time in the future, the job changes to the queued state. If Execution_Time is in the future, the job changes to the waiting state. the way that timing just changes everything 😭

Holds can be set by the owner, an Operator, or Manager, when a job has a dependency, or when a job has its Execution_Time attribute set to a time in the future. see the qhold man page 🫢

πŸ‘‘ Effect of Privilege on Behavior πŸ‘‘

The following table shows the holds and the privilege required to release each:

  • u β€” User β€” job owner, Operator, Manager, administrator, root
  • o β€” Other β€” Operator, Manager, administrator, root
  • s β€” System β€” Manager, administrator, root, PBS (dependency)
  • n β€” None β€” job owner, Operator, Manager, administrator, root
  • p β€” Bad password β€” administrator, root

πŸŽ€ OPTIONS πŸŽ€

  • (no options) β€” defaults to -h u, removing user hold. so if you just run it with no flag, it's giving "free my user hold" energy ✨
  • -h <hold list> β€” types of holds to be released for the job(s).

The hold list argument is a string consisting of one or more of the letters "u", "o", or "s" in any combination, or one of the letters "n" or "p". lowkey just pick the letters you need and slay πŸ’…

  • --version β€” the qrls command returns its PBS version information and exits. this option can only be used alone. don't try to pair it with anything else, bestie β€” it's a solo main character πŸ™ˆ

πŸ¦‹ OPERANDS πŸ¦‹

The qrls command can be used on jobs and job arrays, but not on subjobs or ranges of subjobs. the qrls command accepts one or more job IDs in the form:

<sequence number>[.<server name>][@<server name>]
<sequence number>[][.<server name>][@<server name>]
not me warning you: some shells require that you enclose a job array identifier in double quotes. don't get caught lacking πŸ™ˆ

πŸ’€ STANDARD ERROR πŸ’€

The qrls command writes a diagnostic message to standard error for each error occurrence. so if something goes wrong, it will tell you β€” no silent treatment here πŸ’–


🌈 EXIT STATUS 🌈

  • Zero β€” upon successful processing of all operands. we love a clean exit ✨
  • Greater than zero β€” if the qrls command fails to process any operand. not the vibe, but at least you know 😭

πŸ’œ SEE ALSO πŸ’œ

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

that's the whole page, bestie 🫢 this lil icon was brought to you by Local, dated 6 May 2020 β€” mwah πŸ’‹

πŸ“¦ where this page comes from