MPI_FILE_READ_ORDERED_END(3)

💖 MPI_File_read_ordered_end 💖

Open MPI manual page, bestie: MPI_FILE_READ_ORDERED_END(3). MPI_File_read_ordered_end — reads a file at a location specified by a shared file pointer; ending part of a split collective routine (blocking).

🌸 SYNTAX 🌸

C Syntax

          #include <mpi.h>

          int MPI_File_read_ordered_end(MPI_File fh, void *buf,
               MPI_Status *status)

Fortran Syntax

          USE MPI
          ! or the older form: INCLUDE 'mpif.h'
          MPI_FILE_READ_ORDERED_END(FH, BUF, STATUS, IERROR)
               <type>  BUF(*)
               INTEGER FH, STATUS(MPI_STATUS_SIZE), IERROR

Fortran 2008 Syntax

          USE mpi_f08
          MPI_File_read_ordered_end(fh, buf, status, ierror)
               TYPE(MPI_File), INTENT(IN) :: fh
               TYPE(*), DIMENSION(..), ASYNCHRONOUS :: buf
               TYPE(MPI_Status) :: status
               INTEGER, OPTIONAL, INTENT(OUT) :: ierror

🫶 INPUT/OUTPUT PARAMETER 🫶

• fh — file handle (handle).

✨ OUTPUT PARAMETERS ✨

• buf — initial address of buffer (choice).
• status — status object (status).
• ierror — Fortran only: error status (integer).

💅 DESCRIPTION 💅

Okay so MPI_File_read_ordered_end is the ending part of a split collective routine that must be called by all processes in the communicator group associated with the file handle fh. The manual says MPI_File_rad_ordered_end blocks until the operation initiated by MPI_File_read_ordered_begin completes — not me noticing the rad typo, bestie 😭. It attempts to read the file associated with fh into the user's buffer buf. The shared file pointer is updated by the amounts of data requested by all processes of the group. For each process, the location in the file at which data is read is the position at which the shared file pointer would be after all processes whose ranks within the group are less than that of this process had read their data.

🎀 NOTES 🎀

All the nonblocking collective routines for data access are "split" into two routines, each with _begin or _end as a suffix. These split collective routines are subject to the semantic rules described in Section 9.4.5 of the MPI-2 standard.

🚨 ERRORS 🚨

Almost all MPI routines return an error value; C routines as the return result of the function and Fortran routines in the last argument.

Before the error value is returned, the current MPI error handler associated with the communication object (e.g., communicator, window, file) is called. If no communication object is associated with the MPI call, then the call is considered attached to MPI_COMM_SELF and will call the associated MPI error handler. When MPI_COMM_SELF is not initialized (i.e., before MPI_Init/MPI_Init_thread, after MPI_Finalize, or when using the Sessions Model exclusively) the error raises the initial error handler. The initial error handler can be changed by calling MPI_Comm_set_errhandler on MPI_COMM_SELF when using the World model, or the mpi_initial_errhandler CLI argument to mpiexec or info key to MPI_Comm_spawn/MPI_Comm_spawn_multiple. If no other appropriate error handler has been set, then the MPI_ERRORS_RETURN error handler is called for MPI I/O functions and the MPI_ERRORS_ABORT error handler is called for all other MPI functions.

Open MPI includes three predefined error handlers that can be used:

• MPI_ERRORS_ARE_FATAL — causes the program to abort all connected MPI processes.
• MPI_ERRORS_ABORT — an error handler that can be invoked on a communicator, window, file, or session. When called on a communicator, it acts as if MPI_Abort was called on that communicator. If called on a window or file, acts as if MPI_Abort was called on a communicator containing the group of processes in the corresponding window or file. If called on a session, aborts only the local process.
• MPI_ERRORS_RETURN — returns an error code to the application.

MPI applications can also implement their own error handlers by calling:

• MPI_Comm_create_errhandler then MPI_Comm_set_errhandler
• MPI_File_create_errhandler then MPI_File_set_errhandler
• MPI_Session_create_errhandler then MPI_Session_set_errhandler or at MPI_Session_init
• MPI_Win_create_errhandler then MPI_Win_set_errhandler

Note that MPI does not guarantee that an MPI program can continue past an error.

See the MPI man page for a full list of MPI error codes.

See the Error Handling section of the MPI-3.1 standard for more information.

©️ COPYRIGHT ©️

2003-2026, The Open MPI Community

---

Okay bye bestie! This page is from Open MPI, dated Sep 11, 2026, and it’s the MPI_FILE_READ_ORDERED_END(3) page — mwah 💋✨