Open MPI logo

MPI_File_iwrite_shared(3) man page (version 1.8.1)

  |   Home   |   Support   |   FAQ   |  

« Return to documentation listing

Table of Contents

Name

MPI_File_iwrite_shared - Writes a file using the shared file pointer (nonblocking, noncollective).

Syntax


C Syntax
    #include <mpi.h>
    int MPI_File_(MPI_File fh, const void *buf, int count, MPI_Datatype
              datatype, MPI_Request *request)

Fortran Syntax


    INCLUDE ’mpif.h’
    MPI_File_(FH, BUF, COUNT, DATATYPE, REQUEST, IERROR)
        <type>        BUF(*)
            INTEGER        FH, COUNT, DATATYPE, REQUEST, IERROR

C++ Syntax


#include <mpi.h>
MPI::Request MPI::File::Iwrite_shared(const void* buf, int count,
    const MPI::Datatype& datatype)

Input/Output Parameter

fh
File handle (handle).

Input Parameters

count
Number of elements in buffer (integer).
datatype
Data type of each buffer element (handle).

Output Parameters

buf
Initial address of buffer (choice).
request
Request object (handle).
IERROR
Fortran only: Error status (integer).

Description

MPI_File_iwrite_shared is a nonblocking routine that uses the shared file pointer to write files. The order of serialization is not deterministic for this noncollective routine, so you need to use other methods of synchronization to impose a particular order.

Errors

Almost all MPI routines return an error value; C routines as the value of the function and Fortran routines in the last argument. C++ functions do not return errors. If the default error handler is set to MPI::ERRORS_THROW_EXCEPTIONS, then on error the C++ exception mechanism will be used to throw an MPI::Exception object.

Before the error value is returned, the current MPI error handler is called. For MPI I/O function errors, the default error handler is set to MPI_ERRORS_RETURN. The error handler may be changed with MPI_File_set_errhandler; the predefined error handler MPI_ERRORS_ARE_FATAL may be used to make I/O errors fatal. Note that MPI does not guarantee that an MPI program can continue past an error.


Table of Contents

« Return to documentation listing