I think what we have doesn't require it to complete successfully. It says MPI_INIT should try to raise an error and not abort by default. Then the advice to implementors says a critical error can make it abort. However, I think maybe we should say that MPI_Init is not required to raise an error simply because it detected a process failure. It should raise an error (and give an error on the next non-errhandler function blah blah...) if it is unable to initialize the library due to a process failure. Or is this what you were suggesting? -d On Nov 7, 2011, at 12:58 PM, Josh Hursey wrote:

* We need to review 17.5.6: What if MPI_INIT does not internally complete successfully due to process failure? The text seems to assume that MPI_INIT will always be able to complete successfully in the presence of failure. Maybe we should state that 'if it is able to complete successfully, then it should even in the presence of failure'?