PMNAMEINDOM(3)

🌸 PMNAMEINDOM(3) — bestie edition 🌸

ok so this is the manual page for pmNameInDom from the Performance Co-Pilot library, and honestly? it's a glow-up translator. let's get into it 💅

---

✨ NAME ✨

pmNameInDom — the way that it translates an instance identifier into an instance name 🦋 (yes literally that's its whole job and it ate)

---

✨ C SYNOPSIS ✨

#include <pcp/pmapi.h>

int pmNameInDom(pmInDom indom, int inst, char **name);

cc ... -lpcp

that's it. that's the whole vibe. three args, one int returned, and a linker flag that you cannot forget or nothing will work and you'll be sad 😭

---

✨ DESCRIPTION ✨

okay so picture this: you're in the current Performance Metrics Application Programming Interface (PMAPI) context — that's your home base, your main character era — and you've got an instance domain indom. inside that domain there's an instance, and that instance has an internal instance identifier chilling in the variable inst. 🎀

what pmNameInDom does is locate that instance and hand you back its full external instance identification through name. so like… internal code name in, pretty human-readable name out. it's giving translator, it's giving interpreter, it's giving glow-up. ✨

now, where does indom come from, bestie? usually you pull the value for the instance domain indom out of a pmDesc structure, right after you call pmLookupDesc(3) for whatever performance metric you're obsessed with. that's the pipeline. 🔥

⚠️ IMPORTANT, no cap: the space for the value of name gets allocated inside pmNameInDom with malloc(3). which means it is YOUR job — the caller's job — to free(3) that space when you don't need it anymore. do not leave it hanging. that's a memory leak and memory leaks are not cute. 🙈

and the return value? pmNameInDom returns zero on success. zero = slay. zero = we ball. 🫶

---

✨ DIAGNOSTICS ✨

when things go wrong (and sometimes they do 😭), you get one of these:

• PM_ERR_INDOM — indom is not a valid instance domain identifier. so like, that's not a real domain bestie, try again 💀
• PM_ERR_INST — the instance identifier inst is not known for the instance domain indom in the current PMAPI context. you're looking for an instance that simply does not exist in this context. ghosted fr fr 👻

---

✨ SEE ALSO ✨

go read these next, they're all iconic in their own way 👑

• PMAPI(3)
• pmGetConfig(3)
• pmGetInDom(3)
• pmLookupInDom(3)
• pmNameInDomArchive(3)
• pcp.conf(5)
• pcp.env(5)

---

and that's the whole page, bestie 🎀 this one comes to you straight from the Performance Co-Pilot crew, section PCP, and it's filed under PMNAMEINDOM(3) in case you ever need to find it again. now go free(3) your strings and hydrate. periodt. 💖✨🦋