pbs_runjob(3B)

💖 NAME 💖

okay bestie, you're reading pbs_runjob(3B) from PBS Professional. This page is all about pbs_runjob — run a PBS batch job. iconic 💅

✨ SYNOPSIS ✨

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

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

🦋 DESCRIPTION 🦋

So like, pbs_runjob() issues a batch request to run a batch job. fr fr.

It generates a Run Job (15) request and sends it to the server over the connection specified by connect.

If no file stagein is required, the server replies when the job has started execution. If file stagein is required, the server replies when staging is started. the way that works 💫

👑 REQUIRED PRIVILEGE 👑

Bestie, you must have Manager or Operator privilege to use this command. no cap.

🎀 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 a job array:

<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. periodt 💅

-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. this part matters, bestie 🚨

extend

Character string for extensions to command. Not currently used.

🌈 RETURN VALUE 🌈

The routine returns 0 (zero) on success. slay.

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 🫶

Go check out qrun(1B), pbs_asyrunjob(3B), and pbs_connect(3B) — iykyk 💜

---

okay that's the whole vibe! Source/version: Local; date: 15 November 2019. Bye bestie, go run that job 💖🎀🦋