pbs_connect(3B)

Bestie, this is pbs_connect(3B) from the PBS manual — yes, the batch-server PBS — and it’s literally the “open the connection first” moment of the whole API. 🫶✨

💖 NAME 💖

pbs_connect — connect to a pbs batch server. That’s the whole vibe: you’re linking up to the batch server so the rest of the pbs_ girlies can do their thing. 💅

🦋 SYNOPSIS 🦋

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

int pbs_connect(char *server)

extern char *pbs_server;

✨ DESCRIPTION ✨

Okay so here’s the tea: a virtual stream (TCP/IP) connection gets established with the server specified by server. That’s the whole point of pbs_connect() — connection era, no cap. 🌈

🚨 Bestie, listen: this function must be called before any of the other pbs_ functions. They will transmit their batch requests over the connection established by this function. So yes, pbs_connect() is the main character, and everyone else is riding the connection it opened.

Multiple requests may be issued over the connection before it is closed. So you can absolutely send a little group chat of batch requests, not just one message. 💬

The connection should be closed by a call to pbs_disconnect() when all requests have been sent to the server. That’s the “okay bye, love you” of this whole situation. 🫶

The parameter, server, is of the form host_name[:port], see section 2.7.9. If port is not specified, the standard PBS port number will be used. 🎀

If the parameter, server, is either the null string or a null pointer, a connection will be opened to the default server. The default server is defined by:

• (a) the setting of the environment variable PBS_DEFAULT, which contains a destination, or
• (b) the destination in the batch administrator established file {PBS_DIR}/default_destn.

So like, blank server doesn’t mean “nowhere” — it means “default server, please and thank you.” 💖

The variable pbs_server, declared in pbs_ifl.h, is set on return to point to the server name to which pbs_connect() connected or attempted to connect. Yes, even the attempted-to-connect case keeps that pointer pointed at the server name, bestie. 👑

🌸 SEE ALSO 🌸

Go read these next, because the PBS lore is deep and honestly kind of iconic:

• qsub(1B)
• pbs_alterjob(3B)
• pbs_deljob(3B)
• pbs_disconnect(3B)
• pbs_geterrmsg(3B)
• pbs_holdjob(3B)
• pbs_locate(3B)
• pbs_manager(3B)
• pbs_movejob(3B)
• pbs_msgjob(3B)
• pbs_rerunjob(3B)
• pbs_rlsjob(3B)
• pbs_runjob(3B)
• pbs_selectjob(3B)
• pbs_selstat(3B)
• pbs_sigjob(3B)
• pbs_statjob(3B)
• pbs_statque(3B)
• pbs_statserver(3B)
• pbs_submit(3B)
• pbs_terminate(3B)
• pbs_server(8B)
• and the PBS External Reference Specification

💀 DIAGNOSTICS 💀

When the connection to batch server has been successfully created, the routine will return a connection identifier which is positive. Slay. Positive number = connection created, bestie. ✅

Otherwise, a negative value is returned. Not slay. ❌

The error number is set in pbs_errno. So if it goes negative, check pbs_errno for the details — that’s where the drama is documented. 🔥

---

xoxo, from the Local edition of pbs_connect(3B) 💅 — the source footer’s date slot is blank, so I’m not inventing a date, bestie. 🎀✨