PMUSECONTEXT(3)

PMUSECONTEXT(3) 💖

okay so this is a page from the Library Functions Manual bestie, and it's all about pmUseContext from the Performance Co-Pilot (PCP) world 🎀

---

✨ NAME ✨

pmUseContext — change current PMAPI context 💅

---

🌸 C SYNOPSIS 🌸

#include <pcp/pmapi.h>

int pmUseContext(int handle);

cc ... -lpcp

---

🦋 DESCRIPTION 🦋

So here's the tea: if you're an application using the Performance Metrics Application Programming Interface (PMAPI, yes queen 👑), you can juggle several concurrent contexts at once. Each one is tied to a source of performance metrics — like pmcd(1) running on some host, or an archive of performance metrics as created by pmlogger(1). Multiple vibes, multiple sources, all at the same time, no cap. ✨

Calling pmUseContext sets the current PMAPI context to the one identified by handle. And bestie, that handle value must be one returned from an earlier call to pmNewContext(3) or pmDupContext(3). Like, you can't just make one up, okay? 🙈

Now here's the part that's giving main character energy: below the PMAPI, every context your application uses gets saved in its most recently modified state. So pmUseContext restores the context to the state it was in the last time the context was used — not the state of the context back when it was first established. It's giving "we pick up right where we left off," and honestly? Obsessed. 💖

---

💀 DIAGNOSTICS 💀

• PM_ERR_NOCONTEXT — handle does not identify a valid PMAPI context 😭 (literally it doesn't know her)

---

👑 SEE ALSO 👑

PMAPI(3), pmDestroyContext(3), pmDupContext(3), pmNewContext(3) and pmWhichContext(3). Go read those too, they ate. 🔥

---

k bye ily, this was Performance Co-Pilot (PCP) content, PMUSECONTEXT(3), and yes it really is that iconic 🫶✨