UNPACK(3PVM)

💖 UNPACK(3PVM) — pvm_unpack 💖

okay bestie, sit down, we're doing UNPACK(3PVM) from PVM Version 3.4 and it's literally the moment your receive buffer finally gives you your stuff back 🎀

---

✨ NAME ✨

pvm_unpack — Unpack the active message buffer into arrays of prescribed data type.

---

🌸 SYNOPSIS 🌸

C

int info = pvm_unpackf( const char *fmt, ... )
int info = pvm_upkbyte( char *xp, int nitem, int stride)
int info = pvm_upkcplx( float *cp, int nitem, int stride)
int info = pvm_upkdcplx( double *zp, int nitem, int stride)
int info = pvm_upkdouble( double *dp, int nitem, int stride)
int info = pvm_upkfloat( float *fp, int nitem, int stride)
int info = pvm_upkint( int *ip, int nitem, int stride)
int info = pvm_upkuint( unsigned int *ip, int nitem, int stride )
int info = pvm_upkushort( unsigned short *ip, int nitem, int stride )
int info = pvm_upkulong( unsigned long *ip, int nitem, int stride )
int info = pvm_upklong( long *ip, int nitem, int stride)
int info = pvm_upkshort( short *jp, int nitem, int stride)
int info = pvm_upkstr( char *sp )

Fortran

call pvmfunpack( what, xp, nitem, stride, info )

---

🦋 PARAMETERS 🦋

• fmt — the printf-like format expression that says what to pack. (there's a whole discussion below, iykyk)
• nitem — the total number of items to be unpacked. NOT the number of bytes, bestie, this trips people up every single time 💀
• stride — the stride to use when packing the items. like, if stride = 2 in pvm_upkcplx, then every other complex number gets unpacked. skipping through the array like 💅
• xp — pointer to the beginning of a block of bytes. can be any data type, but it must match the corresponding pack data type.
• cp — complex array at least nitem*stride items long.
• zp — double precision complex array at least nitem*stride items long.
• dp — double precision real array at least nitem*stride items long.
• fp — real array at least nitem*stride items long.
• ip — integer array at least nitem*stride items long.
• jp — Integer*2 array at least nitem*stride items long.
• sp — pointer to a null terminated character string.
• what — integer specifying the type of data being unpacked.
• info — integer status code returned by the routine. values less than zero indicate an error. 👀

🌈 the what options 🌈

• STRING — 0
• BYTE1 — 1
• INTEGER2 — 2
• INTEGER4 — 3
• REAL4 — 4
• COMPLEX8 — 5
• REAL8 — 6
• COMPLEX16 — 7

---

💅 DESCRIPTION 💅

Each of the pvm_upk* routines unpacks an array of the given data type from the active receive buffer. The arguments for each of the routines are a pointer to the array to be unpacked into, nitem which is the total number of items to unpack, and stride which is the stride to use when unpacking. that's it, that's the whole vibe ✨

An exception is pvm_upkstr() which by definition unpacks a NULL terminated character string and thus does not need nitem or stride arguments. the Fortran routine pvmfunpack( STRING, ... ) expects nitem to be the number of characters in the string and stride to be 1. she's special, she's got her own rules 🎀

If the unpacking is successful, info will be 0. If some error occurs then info will be < 0. 😭

A single variable (not an array) can be unpacked by setting nitem = 1 and stride = 1. iconic, one-item behavior, no notes 🫶

The routine pvm_unpackf() uses a printf-like format expression to specify what and how to unpack data from the receive buffer. All variables are passed as addresses. A BNF-like description of the format syntax is:

format : null | init | format fmt
init : null | '%' '+'
fmt : '%' count stride modifiers fchar
fchar : 'c' | 'd' | 'f' | 'x' | 's'
count : null | [0-9]+ | '*'
stride : null | '.' ( [0-9]+ | '*' )
modifiers : null | modifiers mchar
mchar : 'h' | 'l' | 'u'

Formats:

• + — means initsend - must match an int (how) in the param list.
• c — pack/unpack bytes
• d — integer
• f — float
• x — complex float
• s — string

Modifiers:

• h — short (int)
• l — long (int, float, complex float)
• u — unsigned (int)

'*' count or stride must match an int in the param list. ⭐

Future extensions to the what argument in pvmfunpack will include 64 bit types when XDR encoding of these types is available. Meanwhile users should be aware that precision can be lost when passing data from a 64 bit machine like a Cray to a 32 bit machine like a SPARCstation. As a mnemonic the what argument name includes the number of bytes of precision to expect. By setting encoding to PVMRAW (see pvmfinitsend) data can be transferred between two 64 bit machines with full precision even if the PVM configuration is heterogeneous. 👑

Messages should be unpacked exactly like they were packed to insure data integrity. Packing integers and unpacking them as floats will often fail because a type encoding will have occurred transferring the data between heterogeneous hosts. Packing 10 integers and 100 floats then trying to unpack only 3 integers and the 100 floats will also fail.

bestie, do NOT freestyle the symmetry here. pack it one way, unpack it the exact same way, or it's giving chaos 💀

---

🍓 EXAMPLES 🍓

C:

info = pvm_recv( tid, msgtag );
info = pvm_upkstr( string );
info = pvm_upkint( &size, 1, 1 );
info = pvm_upkint( array, size, 1 );
info = pvm_upkdouble( matrix, size*size, 1 );

int count, *iarry;
double darry[4];
   pvm_unpackf("%d", &count);
   pvm_unpackf("%*d %4lf", count, iarry, darry);

Fortran:

CALL PVMFRECV( TID, MSGTAG, INFO );
CALL PVMFUNPACK( INTEGER4, NSIZE, 1, 1, INFO )
CALL PVMFUNPACK( STRING, STEPNAME, 8, 1, INFO )
CALL PVMFUNPACK( REAL4, A(5,1), NSIZE, NSIZE , INFO )

---

😭 ERRORS 😭

• PvmNoData — Reading beyond the end of the receive buffer. Most likely cause is trying to unpack more items than were originally packed into the buffer.
• PvmBadMsg — The received message can not be decoded. Most likely because the hosts are heterogeneous and the user specified an incompatible encoding. Try setting the encoding to PvmDataDefault (see pvm_mkbuf).
• PvmNoBuf — There is no active receive buffer to unpack.

fr fr, check your info every time. she is telling you something. 🙈

---

👑 SEE ALSO 👑

pvm_pack(3PVM) pvm_send(3PVM), pvm_recv(3PVM), pvm_pkmesg(3PVM)

---

that's the whole page, bestie 💖 this one came from PVM Version 3.4 and it was dated 30 August, 1993 — so go forth, unpack responsibly, and remember: unpack it exactly like you packed it. periodt. 🎀✨🦋