Maybe - the standard does not say anything specific about the meaning of MPI_Abort with a value of zero. The "best effort" part and the fact that the value passed to MPI_Abort is not required as a job RC both make MPI_Abort unsatisfactory as currently described. The name "Abort" also sounds like an undesired outcome. You do not abort something when you have gotten what you wanted. If the Forum chose to be explicit about the meaning of MPI_Abort with zero, it would answer the need but it would still feel sort of ugly to me. In part, I bring this up because now that it has been pointed out to me, I am a bit surprised that I have never come across the issue before. That made me wonder if wanting to end a parallel application this way is rare or if people have just been calling ABORT and being content it seemed to work OK. Dick Treumann - MPI Team IBM Systems & Technology Group Dept X2ZA / MS P963 -- 2455 South Road -- Poughkeepsie, NY 12601 Tele (845) 433-7846 Fax (845) 433-8363 From: Fab Tillier <[email protected]> To: Main MPI Forum mailing list <[email protected]> Date: 04/05/2010 03:48 PM Subject: Re: [Mpi-forum] MPI_Abort - meaning Sent by: [email protected] Richard Treumann wrote on Mon, 5 Apr 2010 at 10:45:00

A call to MPI_Quit would let the application give a return code of 0 so a script or wrapper that checks the mpiexec return code would regard the application as a success.

How is this different than calling MPI_Abort with an error code of 0? Is it just that MPI_Quit would do more than 'best effort'? -Fab _______________________________________________ mpi-forum mailing list [email protected] http://lists.mpi-forum.org/mailman/listinfo.cgi/mpi-forum