PMAPUTLOG(3)

💖 pmaPutLog — the PMAPUTLOG(3) page, but make it cute 💖

okay bestie, so this is pmaPutLog(3) from the Library Functions Manual, and it's one of those internal PCP things. Let's get into it 🫶

---

✨ NAME ✨

pmaPutLog — direct write of the next record from an archive file. yes that's the whole name, it does what it says on the tin 💅

---

🌸 C SYNOPSIS 🌸

#include <pcp/pmapi.h>
#include <pcp/libpcp.h>
#include <pcp/archive.h>

void pmaPutLog(FILE *f, __int32_t *rbuf);

cc ... -lpcp_archive -lpcp

so you're pulling in three headers, calling it with a FILE *f and a __int32_t *rbuf, and you link against -lpcp_archive and -lpcp. that's the whole vibe ✨

---

⚠️ CAVEAT ⚠️

okay so listen, this is important:

• This documentation is intended for internal Performance Co-Pilot (PCP) developer use.
• These interfaces are not part of the PCP APIs that are guaranteed to remain fixed across releases, and they may not work, or may provide different semantics at some point in the future.

so like… it's giving "for the girlies on the inside only" 💀 do not build your whole personality on this API staying the same, fr fr.

---

🦋 DESCRIPTION 🦋

This is a cut-down version of the archive record reading routines from libpcp, that writes the next physical record on the stream identified by f.

The record is already formatted in rbuf, including the setup of the record header length and trailer length, and rbuf must be in network byte-order. no cap, if it's not in network byte-order you're on your own 🙈

There is no checking, so the record format must be correct and match the semantics of whichever physical file (metadata or data volume) that is associated with f.

bestie. there is NO checking. it is not going to catch you. it is not going to warn you. the record format has to be correct AND it has to match the semantics of whatever physical file — metadata or data volume — is hanging out with f. so like, know what you're doing 💅

---

🔥 DIAGNOSTICS AND RETURN VALUES 🔥

The return value is 0 if all is well, else some error code less than zero. slay when it's 0, and when it's not… it's negative, that's the whole diagnostic. no extra lore 😭

---

👑 SEE ALSO 👑

• pmaGetLog(3) — the other one, go look at it
• PMAPI(3) — the big one

---

okay that's the whole page, you ate that 🎀 Performance Co-Pilot, PCP, and this little PMAPUTLOG(3) moment — mwah, bye bestie 💖✨🌸🦋💅🫶