1. Mail discussion
    MPI_COMM_PARENT instead of MPI_COMM_GET_PARENT

    Page 179, lines 4-5 change

    Thus, the names of MPI_COMM_WORLD, MPI_COMM_SELF, and MPI_COMM_PARENT will have the default of MPI_COMM_WORLD, MPI_COMM_SELF, and MPI_COMM_PARENT.

    to

    Thus, the names of MPI_COMM_WORLD, MPI_COMM_SELF, and the communicator returned by MPI_COMM_GET_PARENT (if not MPI_COMM_NULL) will have the default of MPI_COMM_WORLD, MPI_COMM_SELF, and MPI_COMM_PARENT.

    Page 94, line 3-5, change 

    * The manager is represented as the process with rank 0 in (the remote
* group of) MPI_COMM_PARENT. If the workers need to communicate among
* themselves, they can use MPI_COMM_WORLD.

    to 

    * The manager is represented as the process with rank 0 in (the remote
* group of) the parent communicator. If the workers need to communicate 
* among themselves, they can use MPI_COMM_WORLD.

  2. Mail discussion
    MPI_UNPACK_EXTERNAL

    Page 79, Line 11 is 

    MPI_UNPACK_EXTERNAL (datarep, inbuf, incount, datatype, outbuf, outsize,
position)
    but should be 
    MPI_UNPACK_EXTERNAL (datarep, inbuf, insize, position, outbuf, outcount,
datatype)

  3. Mail discussion
    Additional C++ binding errors

    Page 337, line 31-32 reads 

    bool MPI::Win::Get_attr(const MPI::Win&win, int win_keyval, 
              void* attribute_val) const
    but should read 
    bool MPI::Win::Get_attr(int win_keyval, void* attribute_val) const

  4. Mail discussion
    MPI_REQUEST_CANCEL used where MPI_CANCEL intended

    On page 172 in section 8.2, change MPI_REQUEST_CANCEL to MPI_CANCEL.

  5. Mail discussion
    Intercommunicator collective and datatypes

    Page 163, line 22 reads

    Within each group, all processes provide the same recvcounts argument, and the sum of the recvcounts entries should be the same for the two groups.
    but should read
    Within each group, all processes provide the same recvcounts argument, and the sum of the recvcounts entries and datatype should specify the same type signature for the two groups.

  6. Mail discussion
    const in C++ specification of predefined MPI objects

    Page 345, line 37: Remove the const from const MPI::Op.

    Page 346, line 20: Remove the const from const MPI::Group.

    Page 346, add after line 34:
    Advice to implementors: If an implementation does not change the value of predefined handles while execution of MPI_Init, the implementation is free to define the predefined operation handles as const MPI::Op and the predefined group handle MPI::GROUP_EMPTY as const MPI::Group. Other predefined handles must not be "const" because they are allowed as INOUT argument in the MPI_COMM_SET_NAME/ATTR and MPI_TYPE_SET_NAME/ATTR routines. End of advice to implementors