MPI\_COMM\_SET\_ATTR(3) Open MPI MPI\_COMM\_SET\_ATTR(3)

MPI\_Comm\_set\_attr — Stores attribute value associated with a key.

# [SYNTAX](#SYNTAX)

## [C Syntax](#C_Syntax)

```
#include <mpi.h>
int MPI_Comm_set_attr(MPI_Comm comm, int comm_keyval, void *attribute_val)
```

## [Fortran Syntax](#Fortran_Syntax)

```
USE MPI
! or the older form: INCLUDE 'mpif.h'
MPI_COMM_SET_ATTR(COMM, COMM_KEYVAL, ATTRIBUTE_VAL, IERROR)


     INTEGER COMM, COMM_KEYVAL, IERROR


     INTEGER(KIND=MPI_ADDRESS_KIND) ATTRIBUTE_VAL
```

## [Fortran 2008 Syntax](#Fortran_2008_Syntax)

```
USE mpi_f08
MPI_Comm_set_attr(comm, comm_keyval, attribute_val, ierror)


     TYPE(MPI_Comm), INTENT(IN) :: comm


     INTEGER, INTENT(IN) :: comm_keyval


     INTEGER(KIND=MPI_ADDRESS_KIND), INTENT(IN) :: attribute_val


     INTEGER, OPTIONAL, INTENT(OUT) :: ierror
```

# [INPUT/OUTPUT PARAMETER](#INPUT/OUTPUT_PARAMETER)

•

**comm**: Communicator from which attribute will be attached (handle).

# [INPUT PARAMETERS](#INPUT_PARAMETERS)

- **comm\_keyval**: Key value (integer).
- **attribute\_val**: Attribute value.

# [OUTPUT PARAMETER](#OUTPUT_PARAMETER)

•

**ierror**: Fortran only: Error status (integer).

# [DESCRIPTION](#DESCRIPTION)

MPI\_Comm\_set\_attr stores the stipulated attribute value *attribute\_val* for subsequent retrieval by MPI\_Comm\_get\_attr &lt;#mpi-comm-get-attr&gt;. If the value is already present, then the outcome is as if MPI\_Comm\_delete\_attr &lt;#mpi-comm-delete-attr&gt; was first called to delete the previous value (and the callback function **delete\_fn** was executed), and a new value was next stored. The call is erroneous if there is no key with value *comm\_keyval*; in particular **MPI\_KEYVAL\_INVALID** is an erroneous key value. The call will fail if the delete\_fn function returned an error code other than **MPI\_SUCCESS**.

This function replaces MPI\_Attr\_put &lt;#mpi-attr-put&gt;, the use of which is deprecated. The C binding is identical. The Fortran binding differs in that *attribute\_val* is an address-sized integer.

# [NOTES](#NOTES)

Values of the permanent attributes **MPI\_TAG\_UB**, **MPI\_HOST**, **MPI\_IO**, and **MPI\_WTIME\_IS\_GLOBAL** may not be changed.

The type of the attribute value depends on whether C or Fortran is being used. In C, an attribute value is a pointer (**void \***); in Fortran, it is a single, address-size integer system for which a pointer does not fit in an integer.

If an attribute is already present, the delete function (specified when the corresponding keyval was created) will be called.

# [ERRORS](#ERRORS)

Almost all MPI routines return an error value; C routines as the return result of the function and Fortran routines in the last argument.

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 &lt;#mpi-init&gt;/MPI\_Init\_thread &lt;#mpi-init-thread&gt;, after MPI\_Finalize &lt;#mpi-finalize&gt;, 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 &lt;#mpi-comm-set-errhandler&gt; 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 &lt;#mpi-comm-spawn&gt;/MPI\_Comm\_spawn\_multiple &lt;#mpi-comm-spawn-multiple&gt;. 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.
- **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 &lt;#mpi-abort&gt; was called on that communicator. If called on a window or file, acts as if MPI\_Abort &lt;#mpi-abort&gt; was called on a communicator containing the group of processes in the corresponding window or file. If called on a session, 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 &lt;#mpi-comm-create-errhandler&gt; then MPI\_Comm\_set\_errhandler &lt;#mpi-comm-set-errhandler&gt;
- MPI\_File\_create\_errhandler &lt;#mpi-file-create-errhandler&gt; then MPI\_File\_set\_errhandler &lt;#mpi-file-set-errhandler&gt;
- MPI\_Session\_create\_errhandler &lt;#mpi-session-create-errhandler&gt; then MPI\_Session\_set\_errhandler &lt;#mpi-session-set-errhandler&gt; or at MPI\_Session\_init &lt;#mpi-session-init&gt;
- MPI\_Win\_create\_errhandler &lt;#mpi-win-create-errhandler&gt; then MPI\_Win\_set\_errhandler &lt;#mpi-win-set-errhandler&gt;

Note that MPI does not guarantee that an MPI program can continue past an error.

See the MPI man page &lt;#open-mpi&gt; for a full list of MPI error codes &lt;#open-mpi-errors&gt;.

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

# [Copyright](#Copyright)

2003-2026, The Open MPI Community

October 9, 2026

---

Document: MPI_Comm_set_attr(3) from openmpi-cuda-13.2 5.0.11-r1 (Chainguard OS)
Source: https://github.com/open-mpi/ompi
