ARCHCODE(3PVM)

✨ ARCHCODE(3PVM) — aka pvm_archcode ✨

okay bestie, this is page ARCHCODE(3PVM) from PVM Version 3.4, and it's a little one but it's honestly so useful 💖 sit with me for a sec.

---

🌸 NAME 🌸

pvm_archcode — Returns the data representation code for a PVM architecture name.

like… you hand it an arch name, it hands you back a number. that's the whole vibe.

---

🎀 SYNOPSIS 🎀

C    int cod = pvm_archcode( char *arch )

Fortran   call pvmfarchcode( arch, cod )

two flavors, pick your fighter 💅

---

🦋 PARAMETERS 🦋

• arch — a character string holding the architecture name. that's the input, the little name tag 🏷️
• cod — an integer that returns the architecture code. that's the output, the little number that comes back 🫶

---

💜 DESCRIPTION 💜

so pvm_archcode takes an architecture name and gives you back an integer, no cap. and here's the tea: the code it returns tells you which machines have compatible binary data formats ✨

for example, SUN4 and RS6K share the same code, while ALPHA gets a different one (because a few datatypes have different sizes on it, smh). this is literally so you can figure out when you can get away with using PvmDataRaw instead of PvmDataDefault encoding to pass messages between tasks running on two machines. it's giving "do we even need to translate or are we chill" 🌈

okay and this next part is important, bestie — do not assume the values pvm_archcode returns are etched in stone 👑 the numbers have no intrinsic meaning except for one thing: if two different arch names map to the same value, then they're compatible. that's it. that's the whole meaning of the number.

and now the part where I have to be honest with you 😭 this routine is actually obsolete, in the sense that the architecture codes it returns are already sitting there in the hi_dsig field of the pvmhostinfo structure that pvm_config() returns — there's an example of exactly that down below ⬇️ it's maintained for backwards compatibility only. iconic of it to still show up to the party though 💅

---

🌟 EXAMPLES 🌟

C:

struct pvmhostinfo *hip;
int i;

pvm_config((int *)0, (int *)0, &hip);
i = pvm_archcode(hip[0].hi_arch);

/* or you could just do:  i = hip[0].hi_dsig;  */

Fortran:

CALL PVMFARCHCODE( 'RS6K', k )

see? that comment in the C one is literally the whole "this is obsolete" plot twist, iykyk 🍓

---

🔥 ERRORS 🔥

on success, pvm_archcode returns a positive integer data signature ✨ all good, all slay.

but these error conditions can come back too, so heads up:

• PvmBadParam — you gave it an invalid architecture name. 🚫
• PvmNotFound — there is no host with the given architecture name in the current virtual machine configuration. it's not here, bestie, it's just not here 😭
• PvmSysErr — pvmd not responding. 💀

---

🌈 SEE ALSO 🌈

pvm_config(3PVM), pvm_initsend(3PVM), pvm_notify(3PVM), pvm_tasks(3PVM), pvm_tidtohost(3PVM)

go read pvm_config(3PVM) first fr fr, that's where the non-obsolete route lives 🫶

---

that's the whole page, babe 💖 this was ARCHCODE(3PVM) from PVM Version 3.4, dated 15 March, 1994 — yeah she's vintage, she's a classic, she ate and left no crumbs 👑✨ mwah, go write some distributed code 🌸