pbsdsh(1B)

✨ pbsdsh(1B) ✨

okay so bestie, welcome to pbsdsh — the PBS manual page that's gonna let you scatter a task across nodes like confetti 🎀 (this is the PBS manual, section 1B, just so we're clear, iykyk)

---

🌸 NAME 🌸

pbsdsh — distribute task to nodes under pbs

like literally, it hands your program out to the nodes 💅

---

🦋 SYNOPSIS 🦋

pbsdsh [-c copies] [-o] [-s] [-u] [-v] program [args]
pbsdsh [-n node] [-o] [-s] [-u] [-v] program [args]
pbsdsh [-h nodename] [-o] [-v] program [args]

three whole flavors, pick your fighter ✨

---

💖 DESCRIPTION 💖

Executes (spawns) a normal Unix program on one or more nodes under control of the Portable Batch System, PBS. periodt. 🫶

pbsdsh uses the Task Manager API, see tm_spawn(3), to distribute the program on the allocated nodes. the way it just... delegates. main character energy honestly 👑

When run without the -c or the -n option, pbsdsh will spawn the program on all nodes allocated to the PBS job. and the spawns take place concurrently — all execute at (about) the same time. no cap, they're all going at once 🔥

Users will find the PBS_TASKNUM, PBS_NODENUM, and the PBS_VNODENUM environmental variables useful. They contain the TM task id, the node identifier, and the cpu (virtual node) identifier. like little name tags for each spawn, obsessed 🏷️✨

---

💅 OPTIONS 💅

• -c copies — The program is spawned on the first Copies nodes allocated. This option is mutual exclusive with -n. (yes bestie, you can't have both, pick one 🙈)
• -n node — The program is spawned on one node which is the node-th node allocted. This option is mutual exclusive with -c.
• -h hostname — The program is spawned on the node specified.
• -o — Capture stdout of the spawned program. Normally stdout goes to the job's output. (lowkey useful when you're nosy about what the spawn is saying 👀)
• -s — If this option is given, the program is run in turn on each node, one after the other. no concurrency, we're taking turns like civilized people 🧚
• -u — The program is run once on each node (unique). This ignores the number of allocated processers on a given node. one and done 💀
• -v — Verbose output about error conditions and task exit status is produced. she's chatty and we love her 🗣️💜

ngl, note that -c and -n are mutually exclusive — the manpage says "mutual exclusive" and honestly same vibe, they cannot coexist 🚫

---

🍓 OPERANDS 🍓

The first operand, program, is the program to execute. like, the whole point bestie 🎯

Additional operands, args, are passed as arguments to the program. everything else just tags along for the ride 🚗✨

---

😭 STANDARD ERROR 😭

The pbsdsh command will write a diagnostic message to standard error for each error occurrence. so if something goes wrong, she will tell you about it, loudly, in stderr 💀📢

---

⭐ EXIT STATUS ⭐

Upon successful processing of all the operands presented to the command, the exit status will be a value of zero. slay 🎉

If the pbsdsh command fails to process any operand, or fails to contact the MOM daemon on the localhost, the command exits with a value greater than zero. not slay. red flag 🚩 (fr fr, if you see that, go check on your MOM daemon)

---

🌈 SEE ALSO 🌈

• qsub(1B)
• tm_spawn(3B)

go read those next, i believe in you 🫶📚

---

and that's the whole page bestie!! she's pbsdsh(1B), from the PBS corner of the world, marked Local at the bottom — this little pbsdsh(1B) icon is signing off 💜✨ 🎀 go distribute some tasks, you've got this 👑