<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Okay, I'll update the text on the ticket. I like this wording better.<div><br></div><div>Kathryn</div><div><br><div><div>On Aug 27, 2013, at 1:18 PM, Jeff Squyres (jsquyres) <<a href="mailto:jsquyres@cisco.com">jsquyres@cisco.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">I have a better suggestion (sorry... this is what happens at the last second...):<br><br>Current from Kathryn's PDF:<br><br>If the constant MPI_T_PVAR_ALL_HANDLES is passed in handle, the MPI implementation attempts to start all variables within the session identified by the parameter session for which handles have been allocated. In this case, the routine returns MPI_SUCCESS if all variables are started successfully, otherwise MPI_T_ERR_PVAR_NO_STARTSTOP is returned. MPI_SUCCESS is also returned if MPI_T_PVAR_ALL_HANDLES is passed in handles and if no handles are valid for session or all valid handles represent continuous variables. Continuous variables and variables that are already started are ignored when MPI_T_PVAR_ALL_HANDLES is specified.<br><br>Jeff's suggestion (delete the new sentence and add the text in ***):<br><br>If the constant MPI_T_PVAR_ALL_HANDLES is passed in handle, the MPI implementation attempts to start all variables within the session identified by the parameter session for which handles have been allocated. In this case, the routine returns MPI_SUCCESS if all variables are started successfully (even if there are no non-continuous variables to be started), otherwise MPI_T_ERR_PVAR_NO_STARTSTOP is returned. Continuous variables and variables that are already started are ignored when MPI_T_PVAR_ALL_HANDLES is specified.<br><br><br><br><br>On Aug 27, 2013, at 12:09 PM, Kathryn Mohror <<a href="mailto:kathryn@llnl.gov">kathryn@llnl.gov</a>> wrote:<br><br><blockquote type="cite">I made a ticket for this (#391) and uploaded a pdf with the proposed changes (also attached). <br><br>Is anyone opposed to putting this up for a reading as errata?<br><br>Kathryn<br><br><br>On Aug 27, 2013, at 5:14 AM, Jeff Squyres (jsquyres) <<a href="mailto:jsquyres@cisco.com">jsquyres@cisco.com</a>> wrote:<br><br><blockquote type="cite">On Aug 26, 2013, at 7:23 PM, "Schulz, Martin" <<a href="mailto:schulz6@llnl.gov">schulz6@llnl.gov</a>> wrote:<br><br><blockquote type="cite"><blockquote type="cite">I am now on the SUCCESS side of the fence. Does it need to be clarified as an errata? I would suggest (from 3.0 clean doc):<br></blockquote></blockquote><br>Just to be totally clear: I don't really care which way it goes. I just saw this issue as an ambiguity that should be resolved.<br><br><blockquote type="cite"><blockquote type="cite">page 580, line 41: <br>In this case, the routine returns MPI_SUCCESS if all variables are started successfully, otherwise MPI_T_ERR_PVAR_NO_STARTSTOP is returned. MPI_SUCCESS is also returned if no handles are valid for session and MPI_T_PVAR_ALL_HANDLES is passed in handle. <br></blockquote><br>Hmm - I fear we would have to be even more explicit: MPI_SUCCESS is also returned if MPI_T_PVAR_ALL_HANDLES is passed in handles and if no handles are valid for session or all valid handles represent continuous (read only for reset) variables.<br></blockquote><br>+1.<br><br>-- <br>Jeff Squyres<br><a href="mailto:jsquyres@cisco.com">jsquyres@cisco.com</a><br>For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/<br><br>_______________________________________________<br>mpiwg-tools mailing list<br>mpiwg-tools@lists.mpi-forum.org<br>http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools<br></blockquote><br>______________________________________________________________<br>Kathryn Mohror, <a href="mailto:kathryn@llnl.gov">kathryn@llnl.gov</a>, <a href="http://people.llnl.gov/mohror1">http://people.llnl.gov/mohror1</a><br>CASC @ Lawrence Livermore National Laboratory, Livermore, CA, USA<br><br><br><br><br><tools-3.pdf><br></blockquote><br><br>-- <br>Jeff Squyres<br><a href="mailto:jsquyres@cisco.com">jsquyres@cisco.com</a><br>For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/<br><br>_______________________________________________<br>mpiwg-tools mailing list<br>mpiwg-tools@lists.mpi-forum.org<br>http://lists.mpi-forum.org/mailman/listinfo.cgi/mpiwg-tools<br></blockquote></div><br><div>
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>______________________________________________________________<br>Kathryn Mohror, <a href="mailto:kathryn@llnl.gov">kathryn@llnl.gov</a>, <a href="http://people.llnl.gov/mohror1">http://people.llnl.gov/mohror1</a><br>CASC @ Lawrence Livermore National Laboratory, Livermore, CA, USA</div><div><br></div></div><br class="Apple-interchange-newline"><br class="Apple-interchange-newline">
</div>
<br></div></body></html>