MPI_TYPE_GET_NAME(3)

💅 MPI_TYPE_GET_NAME 💅

okay bestie, welcome to the Open MPI manual page for MPI_Type_get_name — she's a little function with main character energy and honestly? iconic. ✨

---

🌸 NAME 🌸

MPI_Type_get_name — gets the name of a data type. that's it, that's the whole vibe. 🎀

---

🦋 SYNTAX 🦋

💖 C Syntax 💖

#include <mpi.h>

int MPI_Type_get_name(MPI_Datatype type, char *type_name,
     int *resultlen)

💖 Fortran Syntax 💖

USE MPI
! or the older form: INCLUDE 'mpif.h'
MPI_TYPE_GET_NAME(TYPE, TYPE_NAME, RESULTLEN, IERROR)
     INTEGER TYPE, RESULTLEN, IERROR
     CHARACTER*(*) TYPE_NAME

💖 Fortran 2008 Syntax 💖

USE mpi_f08
MPI_Type_get_name(datatype, type_name, resultlen, ierror)
     TYPE(MPI_Datatype), INTENT(IN) :: datatype
     CHARACTER(LEN=MPI_MAX_OBJECT_NAME), INTENT(OUT) :: type_name
     INTEGER, INTENT(OUT) :: resultlen
     INTEGER, OPTIONAL, INTENT(OUT) :: ierror

like, yes, there are three of them. Fortran said "we contain multitudes" and honestly we respect it. 🫶

---

⭐ INPUT PARAMETER ⭐

• type — the data type whose name is to be returned (handle). she's the one we're asking about, the subject of the investigation, the main character 💅

---

🌈 OUTPUT PARAMETERS 🌈

• type_name — the name previously stored on the data type, or an empty string if not such name exists (string). so if nobody ever named her, you get nothing. an empty string. a blank nametag. 😭
• resultlen — length of returned name (integer). the character count, the "how many letters are we working with" of it all 🔥
• ierror — Fortran only: error status (integer). C girlies, this one's not for you 🙈

---

🧚 DESCRIPTION 🧚

MPI_Type_get_name returns the printable identifier associated with an MPI data type. lowkey that's the whole thing — you hand her a data type, she hands you back the cute little printable name attached to it. no cap. ✨

---

💀 ERRORS 💀

okay so this is the long part, but it's important, stay with me bestie 🫶

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/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? yes. effective? also yes. 💀
• 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. very "it depends on the context" of her, we love a versatile queen 👑
• MPI_ERRORS_RETURN — returns an error code to the application. the chill one. the "here's your receipt, handle it yourself" option 🧾

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, she might just not recover. fr fr. 😭

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_Type_set_name — the other half of this duo, the setter to this getter, the ship we all support 🫶

---

🍓 COPYRIGHT 🍓

2003-2026, The Open MPI Community

---

and that's the page bestie!! 💖 written up all cute for Open MPI, dated Sep 11, 2026 — go name some data types, you absolute icon. 🌈✨🎀