Synopsis

int MPI_Parrived(MPI_Request request, int partition, int *flag)

Input Parameters

request

partitioned communication request (handle)

partition

partition to be tested (non-negative integer)

Output Parameters

flag

true if operation completed on the specified partition, false if not (boolean)

Description

MPI_Parrived tests partial completion of partitioned receive operations.

A call on an active partitioned communication request returns flag = true if the operation for the specified partition is complete. The request is not marked as complete or inactive by this procedure; a subsequent call to a completing procedure such as MPI_TEST or MPI_WAIT is required. MPI_Parrived may be called multiple times for a partition and returns flag = true when called with a null or inactive request. Multiple threads may independently call MPI_Parrived to test different partitions. Calling MPI_Parrived on a request that does not correspond to a partitioned receive operation is erroneous.

Thread and Interrupt Safety

This routine is thread-safe. This means that this routine may be safely used by multiple threads without the need for any user-provided thread locks. However, the routine is not interrupt safe. Typically, this is due to the use of memory allocation routines such as 'malloc' or other non-MPICH runtime routines that are themselves not interrupt-safe.

Notes for Fortran

All MPI routines in Fortran (except for 'MPI_WTIME' and 'MPI_WTICK') have an additional argument 'ierr' at the end of the argument list. 'ierr' is an integer and has the same meaning as the return value of the routine in C. In Fortran, MPI routines are subroutines, and are invoked with the 'call' statement.

All MPI objects (e.g., 'MPI_Datatype', 'MPI_Comm') are of type 'INTEGER' in Fortran.

Errors

All MPI routines (except 'MPI_Wtime' and 'MPI_Wtick') return an error value; C routines as the value of the function and Fortran routines in the last argument. Before the value is returned, the current MPI error handler is called. By default, this error handler aborts the MPI job. The error handler may be changed with 'MPI_Comm_set_errhandler' (for communicators), 'MPI_File_set_errhandler' (for files), and 'MPI_Win_set_errhandler' (for RMA windows). The MPI-1 routine 'MPI_Errhandler_set' may be used but its use is deprecated. The predefined error handler 'MPI_ERRORS_RETURN' may be used to cause error values to be returned. Note that MPI does not guarantee that an MPI program can continue past an error; however, MPI implementations will attempt to continue whenever possible.

  • MPI_SUCCESS - No error; MPI routine completed successfully.

  • MPI_ERR_ARG - Invalid argument. Some argument is invalid and is not identified by a specific error class (e.g., 'MPI_ERR_RANK').

  • MPI_ERR_REQUEST - Invalid 'MPI_Request'. Either null or, in the case of a 'MPI_Start' or 'MPI_Startall', not a persistent request.

  • MPI_ERR_OTHER - Other error; use 'MPI_Error_string' to get more information about this error code.