\fBMPI_File_sync\fP\- Makes semantics consistent for data-access operations (collective).
.SHSYNTAX
.ftR
.nf
C Syntax
#include <mpi.h>
int MPI_File_sync(MPI_File \fIfh\fP)
Fortran Syntax
INCLUDE 'mpif.h'
MPI_FILE_SYNC(\fIFH\fP, \fIIERROR\fP)
INTEGER FH, IERROR
.SHC++Syntax
.nf
#include <mpi.h>
void MPI::File::Sync()
.SHINPUTPARAMETER
.ftR
.TP1i
fh
File handle (handle).
.SHOUTPUTPARAMETER
.ftR
.TP1i
IERROR
Fortran only: Error status (integer).
.SHDESCRIPTION
.ftR
Calling MPI_File_sync with
.Ifh
causes all previous writes to
.Ifh
by the calling process to be written to permanent storage. If other processes have made updates to permanent storage, then all such updates become visible to subsequent reads of
.Ifh
by the calling process.
.sp
MPI_File_sync is a collective operation. The user is responsible for ensuring that all nonblocking requests on
.Ifh
have been completed before calling MPI_File_sync. Otherwise, the call to MPI_File_sync is erroneous.
.SHERRORS
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.
.sp
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.