MPI_WIN_SET_NAME(3)

🦋 MPI_Win_set_name 🦋

Okay bestie, this is the Open MPI manual page for MPI_Win_set_name — filed under MPI_WIN_SET_NAME(3) — and it does exactly what it says: Sets the name of a window. Periodt. ✨

---

✨ SYNTAX ✨

💻 C Syntax

#include <mpi.h>

int MPI_Win_set_name(MPI_Win win, const char *win_name)

🧚 Fortran Syntax

USE MPI
! or the older form: INCLUDE 'mpif.h'
MPI_WIN_SET_NAME(WIN, WIN_NAME, IERROR)
     INTEGER WIN, IERROR
     CHARACTER*(*) WIN_NAME

🌸 Fortran 2008 Syntax

USE mpi_f08
MPI_Win_set_name(win, win_name, ierror)
     TYPE(MPI_Win), INTENT(IN) :: win
     CHARACTER(LEN=*), INTENT(IN) :: win_name
     INTEGER, OPTIONAL, INTENT(OUT) :: ierror

---

🫶 INPUT/OUTPUT PARAMETER 🫶

• win — the window whose identifier is to be set (handle). 👑

💖 INPUT PARAMETER 💖

• win_name — the character string used as the name (string). 🎀

🦋 OUTPUT PARAMETER 🦋

• ierror — Fortran only: error status (integer). 💅

---

🌈 DESCRIPTION 🌈

Okay so the source page literally has no prose here — the DESCRIPTION section is empty, bestie. No cap, there are no extra description deets on this one. 🫥

---

🔥 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. 💅

Before that 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. 💀
• 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, 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, 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

🚨 Bestie, important: note that MPI does not guarantee that an MPI program can continue past an error. Like, do not assume it's gonna just walk it off. 😭

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.

---

👑 COPYRIGHT 👑

2003-2026, The Open MPI Community 💜

---

🎀 mwah, that's the whole page! Source/version: Open MPI; date: Sep 11, 2026; manual: MPI_WIN_SET_NAME(3). 💖