pbs_asyrunjob(3B)

💖 NAME 💖

pbs_asyrunjob — run an asynchronous PBS batch job

okay so bestie, this is the tea on pbs_asyrunjob(3B) from the PBS Professional manual. It's the call that asks the server to run an async batch job, and it's genuinely giving “I know my way around a scheduler” energy.

---

✨ SYNOPSIS ✨

#include <pbs_error.h>
#include <pbs_ifl.h>

int pbs_asyrunjob(int connect, char *jobID, char *location,
                  char *extend)

🌸 DESCRIPTION 🌸

Issues a batch request to run a batch job.

It generates an Asynchronous Run Job request and sends it to the server over the connection specified by connect.

The server validates the request and replies before initiating the execution of the job.

You can use this version of the call to reduce latency in scheduling, especially when the scheduler must start a large number of jobs. slay for batch scheduling, honestly.

🔐 REQUIRED PRIVILEGE 🔐

You must have Manager or Operator privilege to use this command.

no random user energy here — you need the privileges, periodt.

🎀 ARGUMENTS 🎀

• connect — Return value of pbs_connect(). Specifies connection over which to send batch request to server.
• jobID — ID of job to be run.

Format for a job:

<sequence number>.<server name>

Format for an array job, copied exactly as written:

<sequence number>[].<server name

• location — Location where job should run, and optionally resources to use. Same as qrun -H:

-H <vnode specification without resources> — The vnode specification without resources has this format:

(<vchunk>)[+(<vchunk>) ...]

where vchunk has the format

<vnode name>[+<vnode name> ...]

Example: -H (VnodeA+VnodeB)+(VnodeC)

PBS applies one requested chunk from the job's selection directive in round-robin fashion to each vchunk in the list. Each vchunk must be sufficient to run the job's corresponding chunk, otherwise the job may not execute correctly.

-H <vnode specification with resources> — The vnode specification with resources has this format:

(<vchunk>)[+(<vchunk>) ...]

where vchunk has the format

<vnode name>:<vnode resources>[+<vnode name>:<vnode
resources> ...]

and where vnode resources has the format

<resource name>=<value>[:<resource name>=<value> ...]

Example:

-H (VnodeA:mem=100kb:ncpus=1)+
     (VnodeB:mem=100kb:ncpus=2+ VnodeC:mem=100kb)

PBS creates a new selection directive from the vnode specification with resources, using it instead of the original specification from the user. Any single resource specification results in the job's original selection directive being ignored. Each vchunk must be sufficient to run the job's corresponding chunk, otherwise the job may not execute correctly.

⚠️ if the job being run requests -l place=exclhost, take extra care to satisfy the exclhost request. Make sure that if any vnodes are from a multi-vnoded host, all vnodes from that host are allocated. Otherwise those vnodes can be allocated to other jobs. literally do not skip this part, bestie.

• extend — Character string for extensions to command. Not currently used.

🦋 RETURN VALUE 🦋

The routine returns 0 (zero) on success.

If an error occurred, the routine returns a non-zero exit value, and the error number is available in the global integer pbs_errno.

🌈 SEE ALSO 🌈

• qrun(1B)
• pbs_connect(3B)
• pbs_runjob(3B)

---

mwah 💋 this page is from the Local source, PBS Professional, dated 11 December 2019 — and that's the whole vibe, no cap.