<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML3.2 EN"> <HTML> <HEAD> <META NAME="GENERATOR" CONTENT="DOCTEXT"> <TITLE>MPI_Comm_set_errhandler</TITLE> </HEAD> <BODY BGCOLOR="FFFFFF"> <A NAME="MPI_Comm_set_errhandler"><H1>MPI_Comm_set_errhandler</H1></A> Set the error handler for a communicator <H2>Synopsis</H2> <PRE> int MPI_Comm_set_errhandler(MPI_Comm comm, MPI_Errhandler errhandler) </PRE> <H2>Input Parameters</H2> <DL> <DT><B>comm </B><DD>communicator (handle) <DT><B>errhandler </B><DD>new error handler for communicator (handle) </DL> <P> <P> <H2>Thread and Interrupt Safety</H2> <P> This routine is thread and interrupt safe only if no MPI routine that updates or frees the same MPI object may be called concurrently with this routine. <P> The MPI standard defined a thread-safe interface but this does not mean that all routines may be called without any thread locks. For example, two threads must not attempt to change the contents of the same <TT>MPI_Info</TT> object concurrently. The user is responsible in this case for using some mechanism, such as thread locks, to ensure that only one thread at a time makes use of this routine. <P> <P> <H2>Notes for Fortran</H2> All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have an additional argument <TT>ierr</TT> at the end of the argument list. <TT>ierr </TT>is an integer and has the same meaning as the return value of the routine in C. In Fortran, MPI routines are subroutines, and are invoked with the <TT>call</TT> statement. <P> All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER </TT>in Fortran. <P> <H2>Errors</H2> <P> All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) return an error value; C routines as the value of the function and Fortran routines in the last argument. Before the value is returned, the current MPI error handler is called. By default, this error handler aborts the MPI job. The error handler may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators), <TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for RMA windows). The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but its use is deprecated. The predefined error handler <TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned. Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past an error; however, MPI implementations will attempt to continue whenever possible. <P> <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully. </DL> <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator. A common error is to use a null communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>). </DL> <DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information about this error code. </DL> <P> <H2>See Also</H2> MPI_Comm_get_errhandler, MPI_Comm_call_errhandler <BR><P><B>Location:</B>comm_set_errhandler.c<P> </BODY></HTML>