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

NAME

6       MPI_Type_get_attr -  Get datatype attribute value
7

SYNOPSIS

9       #include <mpi.h>
10       int
11       MPI_Type_get_attr(MPI_Datatype type, int key, void *value, int *found)
12

INPUT PARAMETERS

14       type   - Datatype to which the attribute is attached (handle)
15       key    - Key value (integer)
16
17

OUTPUT PARAMETERS

19       value  - Attribute value, unless flag = false
20       found  - False if no attribute is associated with the key (logical)
21
22

NOTES FOR FORTRAN

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

ERRORS

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

SEE ALSO

71       MPI_Type_create_keyval(3),                     MPI_Type_free_keyval(3),
72       MPI_Type_set_attr(3), MPI_Type_delete_attr(3)
73
74

MORE INFORMATION

76       For more information, please see the official MPI Forum web site, which
77       contains  the  text of both the MPI-1 and MPI-2 standards.  These docu‐
78       ments contain detailed information about each  MPI  function  (most  of
79       which is not duplicated in these man pages).
80
81       http://www.mpi-forum.org/
82

LOCATION

84       tgetattr.c
85
86
87
88LAM/MPI 7.1.2                      2/23/2006              MPI_Type_get_attr(3)
Impressum