MPI_FILE_READ_ORDERED_BEGIN(3)

💖 MPI_FILE_READ_ORDERED_BEGIN 💖

okay bestie, buckle up — this is the Open MPI page for MPI_File_read_ordered_begin, and yes it's a whole mouthful but we're gonna get through it together 🫶

✨ NAME ✨

MPI_File_read_ordered_begin — reads a file at a location specified by a shared file pointer; it's the beginning part of a split collective routine, and it's nonblocking. no cap 💅

---

✨ SYNTAX ✨

🌸 C Syntax

#include <mpi.h>

int MPI_File_read_ordered_begin(MPI_File fh, void *buf,
     int count, MPI_Datatype datatype)

🌸 Fortran Syntax

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

🌸 Fortran 2008 Syntax

USE mpi_f08
MPI_File_read_ordered_begin(fh, buf, count, datatype, ierror)
     TYPE(MPI_File), INTENT(IN) :: fh
     TYPE(*), DIMENSION(..), ASYNCHRONOUS :: buf
     INTEGER, INTENT(IN) :: count
     TYPE(MPI_Datatype), INTENT(IN) :: datatype
     INTEGER, OPTIONAL, INTENT(OUT) :: ierror

---

✨ INPUT/OUTPUT PARAMETER ✨

• fh — the file handle (handle). it's giving "your ticket to the file" 🎀

✨ INPUT PARAMETERS ✨

• count — how many elements are chillin' in the buffer (integer).
• datatype — the data type of each buffer element (handle). so like, what kind of stuff is in there ✨

✨ OUTPUT PARAMETERS ✨

• buf — initial address of the buffer (choice). this is where the data lands 💖
• ierror — Fortran only: error status (integer).

---

✨ DESCRIPTION ✨

MPI_File_read_ordered_begin is the beginning part of a split collective, nonblocking routine, and listen — it must be called by all processes in the communicator group associated with the file handle fh. group project energy, everybody shows up 💅

Every process is allowed to pass different argument values for the datatype and count arguments. (yes, you can each bring your own snack, it's fine.)

Each process attempts to read, from the file associated with fh, a total number of count data items having datatype type into the user's buffer buf.

and here's the ordered part, the main character moment 👑 — 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.

so. line up by rank. everyone waits their turn. it's a queue, bestie, and you are in it. 🌈

---

✨ 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. 📚 (iykyk — go read it, fr fr)

---

✨ 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. so like… don't count on it, bestie 😭

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

---

and that's the whole page, you ate that 🎀✨ this has been the Open MPI MPI_FILE_READ_ORDERED_BEGIN(3) era, dated Sep 10, 2026 — go forth and read files in order, queen 👑💖 bye bestie!! 🦋