1MPI_Comm_test_inter(3)              LAM/MPI             MPI_Comm_test_inter(3)
2
3
4

NAME

6       MPI_Comm_test_inter -  Tests to see if a comm is an inter-communicator
7

SYNOPSIS

9       #include <mpi.h>
10       int MPI_Comm_test_inter(MPI_Comm comm, int *flag)
11

INPUT PARAMETER

13       comm   - communicator (handle)
14
15

OUTPUT PARAMETER

17       flag   - (logical)
18
19

NOTES FOR FORTRAN

21       All  MPI routines in Fortran (except for MPI_WTIME and MPI_WTICK ) have
22       an additional argument ierr at the end of the argument list.   ierr  is
23       an  integer and has the same meaning as the return value of the routine
24       in C.  In Fortran, MPI routines are subroutines, and are  invoked  with
25       the call statement.
26
27       All MPI objects (e.g., MPI_Datatype , MPI_Comm ) are of type INTEGER in
28       Fortran.
29
30

ERRORS

32       If an error occurs in an MPI function, the current MPI error handler is
33       called  to  handle  it.   By default, this error handler aborts the MPI
34       job.  The error handler may be changed with  MPI_Errhandler_set  ;  the
35       predefined  error  handler MPI_ERRORS_RETURN may be used to cause error
36       values to be returned (in C and Fortran; this  error  handler  is  less
37       useful  in  with  the  C++  MPI bindings.  The predefined error handler
38       MPI::ERRORS_THROW_EXCEPTIONS should be used in C++ if the  error  value
39       needs  to  be recovered).  Note that MPI does not guarantee that an MPI
40       program can continue past an error.
41
42       All MPI routines (except MPI_Wtime and  MPI_Wtick  )  return  an  error
43       value;  C routines as the value of the function and Fortran routines in
44       the last argument.  The C++ bindings for MPI do not return  error  val‐
45       ues;  instead,  error values are communicated by throwing exceptions of
46       type MPI::Exception (but not by default).  Exceptions are  only  thrown
47       if the error value is not MPI::SUCCESS .
48
49
50       Note  that  if  the MPI::ERRORS_RETURN handler is set in C++, while MPI
51       functions will return upon an error, there will be no  way  to  recover
52       what the actual error value was.
53       MPI_SUCCESS
54              - No error; MPI routine completed successfully.
55       MPI_ERR_COMM
56              -  Invalid communicator.  A common error is to use a null commu‐
57              nicator in a call (not even allowed in MPI_Comm_rank ).
58       MPI_ERR_ARG
59              - Invalid argument.  Some argument is invalid and is not identi‐
60              fied  by  a  specific  error  class.   This  is typically a NULL
61              pointer or other such error.
62
63

MORE INFORMATION

65       For more information, please see the official MPI Forum web site, which
66       contains  the  text of both the MPI-1 and MPI-2 standards.  These docu‐
67       ments contain detailed information about each  MPI  function  (most  of
68       which is not duplicated in these man pages).
69
70       http://www.mpi-forum.org/
71
72
73

ACKNOWLEDGEMENTS

75       The  LAM Team would like the thank the MPICH Team for the handy program
76       to generate man pages  ("doctext"  from  ftp://ftp.mcs.anl.gov/pub/sow‐
77       ing/sowing.tar.gz  ), the initial formatting, and some initial text for
78       most of the MPI-1 man pages.
79

LOCATION

81       ctestinter.c
82
83
84
85LAM/MPI 7.1.2                      2/23/2006            MPI_Comm_test_inter(3)
Impressum