1MPI_Publish_name(3) LAM/MPI MPI_Publish_name(3)
2
6 MPI_Publish_name - Publish a service name for dynamic process control
7
9 #include <mpi.h>
10 int
11 MPI_Publish_name(char *service_name, MPI_Info info, char *port_name)
12
14 service_name
15 - a service name to associate with the port
16 info - implementation-specific information
17 port_name
18 - a port name from MPI_Open_port
19
23 Currently, LAM/MPI ignores any info keys that are passed to this func‐
24 tion. As such, info keys specific to a different implementation can
25 safely be passed to this function. Additionally, the MPI constant
26 MPI_INFO_NULL can also be used.
27 The scope of the published name is the LAM universe -- MPI processes
29 running on any node included from the initial lamboot are capable of
30 retrieving a name published by MPI_Publish_name . Service names stay
31 in existence until they are either manually removed with MPI_Unpub‐
32 lish_name or cleaned with the lamclean command. It is a common mistake
33 to forget to MPI_Unpublish_name at the end of a run, and therefore
34 leave published names in the LAM runtime environment.
35
38 All MPI routines in Fortran (except for MPI_WTIME and MPI_WTICK ) have
39 an additional argument ierr at the end of the argument list. ierr is
40 an integer and has the same meaning as the return value of the routine
41 in C. In Fortran, MPI routines are subroutines, and are invoked with
42 the call statement.
43 All MPI objects (e.g., MPI_Datatype , MPI_Comm ) are of type INTEGER in
45 Fortran.
46
49 If an error occurs in an MPI function, the current MPI error handler is
50 called to handle it. By default, this error handler aborts the MPI
51 job. The error handler may be changed with MPI_Errhandler_set ; the
52 predefined error handler MPI_ERRORS_RETURN may be used to cause error
53 values to be returned (in C and Fortran; this error handler is less
54 useful in with the C++ MPI bindings. The predefined error handler
55 MPI::ERRORS_THROW_EXCEPTIONS should be used in C++ if the error value
56 needs to be recovered). Note that MPI does not guarantee that an MPI
57 program can continue past an error.
58 All MPI routines (except MPI_Wtime and MPI_Wtick ) return an error
60 value; C routines as the value of the function and Fortran routines in
61 the last argument. The C++ bindings for MPI do not return error val‐
62 ues; instead, error values are communicated by throwing exceptions of
63 type MPI::Exception (but not by default). Exceptions are only thrown
64 if the error value is not MPI::SUCCESS .
65 Note that if the MPI::ERRORS_RETURN handler is set in C++, while MPI
68 functions will return upon an error, there will be no way to recover
69 what the actual error value was.
70 MPI_SUCCESS
71 - No error; MPI routine completed successfully.
72 MPI_ERR_ARG
73 - Invalid argument. Some argument is invalid and is not identi‐
74 fied by a specific error class. This is typically a NULL
75 pointer or other such error.
76 MPI_ERR_SERVICE
77 - This error class is associated with an error code that indi‐
78 cates that there was a problem with the service name that was
79 used. Depending on the context, this can indicate that the ser‐
80 vice name was already published or that the service name was not
81 yet published.
82
85 MPI_Lookup_name, MPI_Unpublish_name
86
89 For more information, please see the official MPI Forum web site, which
90 contains the text of both the MPI-1 and MPI-2 standards. These docu‐
91 ments contain detailed information about each MPI function (most of
92 which is not duplicated in these man pages).
93 http://www.mpi-forum.org/
95
97 namepub.c
98LAM/MPI 7.1.2 2/23/2006 MPI_Publish_name(3)