MPI_ATTR_PUT(3)

💅 MPI_ATTR_PUT(3) — Open MPI

okay bestie, before we even start: this page lives in the Open MPI manual, section 3. Buckle up 🎀

✨ NAME ✨

MPI_Attr_put — stores an attribute value that's associated with a key — and bestie, I have to be honest with you: this routine is deprecated in favor of MPI_Comm_set_attr. 😭 It's giving "legacy code energy," iykyk.

🌸 SYNTAX 🌸

💖 C Syntax

#include <mpi.h>

int MPI_Attr_put(MPI_Comm comm, int keyval, void *attribute_val)

🦋 Fortran Syntax

USE MPI
! or the older form: INCLUDE 'mpif.h'

MPI_ATTR_PUT(COMM, KEYVAL, ATTRIBUTE_VAL, IERROR)
     INTEGER COMM, KEYVAL, ATTRIBUTE_VAL, IERROR

🍓 INPUT PARAMETERS 🍓

• comm — the communicator you're attaching the attribute to, bestie (it's a handle).
• keyval — the key value, exactly as it came back from MPI_KEYVAL_CREATE (an integer, no cap).
• attribute_val — the attribute value itself. 🫶

🎀 OUTPUT PARAMETER 🎀

• ierror — Fortran only, babes: the error status (integer).

👑 DESCRIPTION 👑

So here's the tea ☕ — note that use of this routine is deprecated as of MPI-2, and it was deleted in MPI-3. Please use MPI_Comm_set_attr instead, fr fr. Also, this function does not have an mpi_f08 binding. That's it, that's the whole vibe. 💀

🔥 ERRORS 🔥

Okay so almost all MPI routines return an error value — C routines give it back as the return result of the function, and Fortran routines put it in the last argument. Keep that in mind, bestie.

Before the error value is returned, the current MPI error handler associated with the communication object (e.g., communicator, window, file) is called. If no communication object is associated with the MPI call, then the call is considered attached to MPI_COMM_SELF and will call the associated MPI error handler. When MPI_COMM_SELF is not initialized (i.e., before MPI_Init/MPI_Init_thread, after MPI_Finalize, or when using the Sessions Model exclusively) the error raises the initial error handler. The initial error handler can be changed by calling MPI_Comm_set_errhandler on MPI_COMM_SELF when using the World model, or the mpi_initial_errhandler CLI argument to mpiexec or info key to MPI_Comm_spawn/MPI_Comm_spawn_multiple. If no other appropriate error handler has been set, then the MPI_ERRORS_RETURN error handler is called for MPI I/O functions and the MPI_ERRORS_ABORT error handler is called for all other MPI functions. 😤

Open MPI includes three predefined error handlers that can be used:

• MPI_ERRORS_ARE_FATAL — causes the program to abort all connected MPI processes. dramatic, but valid 💅
• MPI_ERRORS_ABORT — an error handler that can be invoked on a communicator, window, file, or session. When called on a communicator, it acts as if MPI_Abort was called on that communicator. If called on a window or file, it acts as if MPI_Abort was called on a communicator containing the group of processes in the corresponding window or file. If called on a session, it aborts only the local process.
• MPI_ERRORS_RETURN — returns an error code to the application. 🫶

MPI applications can also implement their own error handlers by calling:

• MPI_Comm_create_errhandler then MPI_Comm_set_errhandler
• MPI_File_create_errhandler then MPI_File_set_errhandler
• MPI_Session_create_errhandler then MPI_Session_set_errhandler or at MPI_Session_init
• MPI_Win_create_errhandler then MPI_Win_set_errhandler

⚠️ Note that MPI does not guarantee that an MPI program can continue past an error. Like, at all. Do not test this. 🙈

See the MPI man page for a full list of MPI error codes. 🔍

See the Error Handling section of the MPI-3.1 standard for more information. 📚

👀 SEE ALSO

• MPI_Comm_set_attr

🌈 COPYRIGHT 🌈

2003-2026, The Open MPI Community

---

and that's the whole page, bestie — MPI_ATTR_PUT(3) from the Open MPI manual, dated Sep 11, 2026. go forth and use MPI_Comm_set_attr instead, ilysm 💜✨