MPI_UNPUBLISH_NAME(3)

📦
version 5.0.10 · 7 versions
, in ubuntu stonking

💖 MPI_UNPUBLISH_NAME(3) 💖

okay bestie, welcome to Open MPI's manual page for MPI_Unpublish_name — the moment you finally clean up after yourself and take your service name off the board. it's giving ✨spring cleaning✨ but for the name service. let's get into it 🫶

🌸 SYNTAX 🌸

✨ C Syntax ✨

#include <mpi.h>

int MPI_Unpublish_name(const char *service_name, MPI_Info info,
     const char *port_name)

✨ Fortran Syntax ✨

USE MPI
! or the older form: INCLUDE 'mpif.h'
MPI_UNPUBLISH_NAME(SERVICE_NAME, INFO, PORT_NAME, IERROR)
     CHARACTER*(*)   SERVICE_NAME, PORT_NAME
     INTEGER         INFO, IERROR

✨ Fortran 2008 Syntax ✨

USE mpi_f08
MPI_Unpublish_name(service_name, info, port_name, ierror)
     CHARACTER(LEN=*), INTENT(IN) :: service_name, port_name
     TYPE(MPI_Info), INTENT(IN) :: info
     INTEGER, OPTIONAL, INTENT(OUT) :: ierror

📥 INPUT PARAMETERS 📥

  • service_name: a service name, as a string. 💅
  • info: the options that get handed to the name service functions — it's a handle.
  • port_name: a port name, also a string.

📤 OUTPUT PARAMETER 📤

  • ierror: Fortran only, bestie — the error status, as an integer. 😌

🎀 DESCRIPTION 🎀

so like, this routine literally removes the pair (service_name, port_name) so that applications can no longer retrieve port_name by calling MPI_Lookup_name. gone. deleted. no longer serving 💀

not me about to say something important: it is an error to unpublish a service_name that was not published via MPI_Publish_name. so don't be out here unpublishing random names you didn't publish, that's not the vibe.

and also, both the service_name and port_name arguments to MPI_Unpublish_name must be identical to the arguments from the previous call to MPI_Publish_name. like, copy-paste identical. no cap.

🔑 INFO ARGUMENTS 🔑

here's the key that info recognizes, icon:

  • ompi_global_scope — type bool. if it's set to true, unpublish the name from the global scope. unpublish from the local scope otherwise. (see the NAME SCOPE section for the whole tea ☕)

bool info keys are actually strings but they get evaluated like this: if the string value is a number, it gets converted to an integer and cast to a boolean — meaning that zero integers are false and non-zero values are true. if the string value is (case-insensitive) “yes” or “true”, the boolean is true. if the string value is (case-insensitive) “no” or “false”, the boolean is false. all other string values are unrecognized, and therefore false. periodt.

if no info key is provided, the function will first check to see if a global server has been specified and is available. if so, then the unpublish function will default to global scope first, followed by local. otherwise, the data will default to unpublish with local scope. slay, it picks for you 🌈

🦋 NAME SCOPE 🦋

Open MPI supports two name scopes: global and local. local scope values are placed in a data store located on the mpirun of the calling process' job, while global scope values reside on a central server. 🗄️

calls to MPI_Unpublish_name must correctly specify the scope to be used in finding the value to be removed. the function will return an error if the specified service name is not found on the indicated location. 😭

for a more detailed description of scoping rules, please see the MPI_Publish_name man page.

💀 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. classic.

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. 😵
  • 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
note that MPI does not guarantee that an MPI program can continue past an error. so like… don't hold your breath, bestie.

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_Publish_name
  • MPI_Lookup_name
  • MPI_Open_port

2003-2026, The Open MPI Community

and that's the whole thing, fr fr 💖 this page is from Open MPI, man page MPI_UNPUBLISH_NAME(3), dated Sep 10, 2026 — go forth and unpublish responsibly, bestie, ily 🌸🦋✨

📦 where this page comes from