MPI\_UNPUBLISH\_NAME(3) Open MPI MPI\_UNPUBLISH\_NAME(3)

```
MPI_Unpublish_name - Unpublishes a service name
```

# [SYNTAX](#SYNTAX)

## [C Syntax](#C_Syntax)

```
#include <mpi.h>
int MPI_Unpublish_name(const char *service_name, MPI_Info info,


     const char *port_name)
```

## [Fortran Syntax](#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](#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](#INPUT_PARAMETERS)

- **service\_name**: A service name (string).
- **info**: Options to the name service functions (handle).
- **port\_name**: A port name (string).

# [OUTPUT PARAMETER](#OUTPUT_PARAMETER)

•

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

# [DESCRIPTION](#DESCRIPTION)

This routine removes the pair (*service\_name, port\_name*) so that applications may no longer retrieve *port\_name* by calling MPI\_Lookup\_name &lt;#mpi-lookup-name&gt;. It is an error to unpublish a *service\_name* that was not published via MPI\_Publish\_name &lt;#mpi-publish-name&gt;. Both the *service\_name* and *port\_name* arguments to MPI\_Unpublish\_name must be identical to the arguments to the previous call to MPI\_Publish\_name &lt;#mpi-publish-name&gt;.

# [INFO ARGUMENTS](#INFO_ARGUMENTS)

The following keys for *info* are recognized:

```
Key                   Type      Description
---                   ----      -----------
ompi_global_scope     bool      If set to true, unpublish the name from


                                the global scope.  Unpublish from the local


                                scope otherwise.  See the NAME SCOPE


                                section for more details.
```

*bool* info keys are actually strings but are evaluated as follows: if the string value is a number, it is 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.

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.

# [NAME SCOPE](#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 &lt;#mpi-publish-name&gt; man page.

# [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.

**See also:**

- MPI\_Publish\_name &lt;#mpi-publish-name&gt;
- MPI\_Lookup\_name &lt;#mpi-lookup-name&gt;
- MPI\_Open\_port &lt;#mpi-open-port&gt;

# [Copyright](#Copyright)

2003-2026, The Open MPI Community

July 6, 2026

---

Document: MPI_Unpublish_name(3) from openmpi-cuda-12.4 5.0.10-r2 (Chainguard OS)
Source: https://github.com/open-mpi/ompi
