MPI\_COMM\_DUP\_WITH\_INFO(3) Open MPI MPI\_COMM\_DUP\_WITH\_INFO(3) MPI\_Comm\_dup\_with\_info — Duplicates an existing communicator using provided info. # [SYNTAX](#SYNTAX) ## [C Syntax](#C_Syntax) ``` #include int MPI_Comm_dup_with_info(MPI_Comm comm, MPI_Info info, MPI_Comm *newcomm) ``` ## [Fortran Syntax](#Fortran_Syntax) ``` USE MPI ! or the older form: INCLUDE 'mpif.h' MPI_COMM_DUP_WITH_INFO(COMM, INFO, NEWCOMM, IERROR) INTEGER COMM, INFO, NEWCOMM, IERROR ``` ## [Fortran 2008 Syntax](#Fortran_2008_Syntax) ``` USE mpi_f08 MPI_Comm_dup_with_info(comm, info, newcomm, ierror) TYPE(MPI_Comm), INTENT(IN) :: comm TYPE(MPI_Info), INTENT(IN) :: info TYPE(MPI_Comm), INTENT(OUT) :: newcomm INTEGER, OPTIONAL, INTENT(OUT) :: ierror ``` # [INPUT PARAMETER](#INPUT_PARAMETER) - **comm** : Communicator (handle). - **info** : Info argument (handle). # [OUTPUT PARAMETERS](#OUTPUT_PARAMETERS) - **newcomm** : Copy of comm (handle). - **ierror** : Fortran only: Error status (integer). # [DESCRIPTION](#DESCRIPTION) MPI\_Comm\_dup\_with\_info acts exactly like MPI\_Comm\_dup <#mpi-comm-dup> except that the info hints associated with the communicator comm are not duplicated in newcomm. The hints provided by the argument info are associated with the output communicator newcomm instead. See MPI\_Comm\_set\_info <#mpi-comm-set-info> for the list of recognized info keys. # [NOTES](#NOTES) This operation is used to provide a parallel library call with a duplicate communication space that has the same properties as the original communicator. This includes any attributes (see below) and topologies (see the “Process Topologies” chapter in the MPI Standard <https://www.mpi-forum.org/docs/>. This call is valid even if there are pending point-to-point communications involving the communicator comm. A typical call might involve an MPI\_Comm\_dup\_with\_info at the beginning of the parallel call, and an MPI\_Comm\_free <#mpi-comm-free> of that duplicated communicator at the end of the call. Other models of communicator management are also possible. This call applies to both intra- and intercommunicators. Note that it is not defined by the MPI standard what happens if the attribute copy callback invokes other MPI functions. In Open MPI, it is not valid for attribute copy callbacks (or any of their children) to add or delete attributes on the same object on which the attribute copy callback is being invoked. # [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 <#mpi-init>/MPI\_Init\_thread <#mpi-init-thread>, after MPI\_Finalize <#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 <#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>/MPI\_Comm\_spawn\_multiple <#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 <#mpi-abort> was called on that communicator. If called on a window or file, acts as if MPI\_Abort <#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 <#mpi-comm-create-errhandler> then MPI\_Comm\_set\_errhandler <#mpi-comm-set-errhandler> - MPI\_File\_create\_errhandler <#mpi-file-create-errhandler> then MPI\_File\_set\_errhandler <#mpi-file-set-errhandler> - MPI\_Session\_create\_errhandler <#mpi-session-create-errhandler> then MPI\_Session\_set\_errhandler <#mpi-session-set-errhandler> or at MPI\_Session\_init <#mpi-session-init> - MPI\_Win\_create\_errhandler <#mpi-win-create-errhandler> then MPI\_Win\_set\_errhandler <#mpi-win-set-errhandler> Note that MPI does not guarantee that an MPI program can continue past an error. See the MPI man page <#open-mpi> for a full list of MPI error codes <#open-mpi-errors>. See the Error Handling section of the MPI-3.1 standard for more information. **See also:** MPI\_Comm\_dup <#mpi-comm-dup> # [Copyright](#Copyright) 2003-2026, The Open MPI Community September 16, 2026 --- Document: MPI_Comm_dup_with_info(3) from openmpi 5.0.11-r1 (Chainguard OS) Source: https://github.com/open-mpi/ompi