pbs_sigjob(3B)

💖 NAME 💖

okay so bestie, this page is pbs_sigjob(3B) from PBS, and it is literally about one thing: pbs_sigjob - send a signal to a pbs batch job ✨. That's the name, that's the vibe, that's the whole main character energy.

✨ SYNOPSIS ✨

like, here's the exact call shape, no cap:

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

int pbs_sigjob(int connect, char *job_id, char *signal, char *extend)

int pbs_sigjobasync(int connect, char *job_id, char *signal,
char *extend)

🦋 DESCRIPTION 🦋

So what it does is issue a batch request to send a signal to a batch job. A Signal Job batch request gets generated and sent to the server over the connection specified by connect, which is the return value of pbs_connect(). If the batch job is in the running state, the batch server will send the job the signal number corresponding to the signal named in signal. And when you use the asynchronous pbs_sigjobasync() call, the server will reply before passing the signal request to the pbs_mom. Like, it's giving async, but the reply comes first 💅.

The argument job_id identifies which job is to be signaled, and it's specified in the form:

sequence_number.server

If the name of the signal is not a recognized signal name on the execution host, no signal is sent and an error is returned. Same vibe if the job is not in the running state: no signal is sent, and an error is returned. Not me warning you twice, it's just in the page 😭.

The parameter extend is reserved for implementation defined extensions. That's it, don't touch, it's reserved 🎀.

🌈 SEE ALSO 🌈

• qsig(1B)
• pbs_connect(3B)

🔥 DIAGNOSTICS 🔥

When the batch request generated by the pbs_sigjob() or pbs_sigjobasync() function has been completed successfully by a batch server, the routine will return 0 (zero). Otherwise, a non zero error is returned. The error number is also set in pbs_errno. Periodt 💀✨.

💖 xoxo, your Unix bestie — footer says Local and pbs_sigjob(3B); there's no date on this one, so that's the whole sign-off vibe 🫶🌸