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

NAME

6       MPI_Type_commit -  Commits the datatype
7

SYNOPSIS

9       #include <mpi.h>
10       int MPI_Type_commit(MPI_Datatype *dtype)
11

INPUT PARAMETER

13       dtype  - datatype (handle)
14
15

NOTES FOR FORTRAN

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

ERRORS

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

MORE INFORMATION

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

ACKNOWLEDGEMENTS

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

LOCATION

77       tcommit.c
78
79
80
81LAM/MPI 7.1.2                      2/23/2006                MPI_Type_commit(3)
Impressum