diff --git a/linx64/mpi/mpich/bin/hydra_nameserver b/linx64/mpi/mpich/bin/hydra_nameserver
index 3452b025..e0998a95 100755
Binary files a/linx64/mpi/mpich/bin/hydra_nameserver and b/linx64/mpi/mpich/bin/hydra_nameserver differ
diff --git a/linx64/mpi/mpich/bin/hydra_persist b/linx64/mpi/mpich/bin/hydra_persist
index ab0d9163..553fdd05 100755
Binary files a/linx64/mpi/mpich/bin/hydra_persist and b/linx64/mpi/mpich/bin/hydra_persist differ
diff --git a/linx64/mpi/mpich/bin/hydra_pmi_proxy b/linx64/mpi/mpich/bin/hydra_pmi_proxy
index 31eade4e..603b8858 100755
Binary files a/linx64/mpi/mpich/bin/hydra_pmi_proxy and b/linx64/mpi/mpich/bin/hydra_pmi_proxy differ
diff --git a/linx64/mpi/mpich/bin/mpicc b/linx64/mpi/mpich/bin/mpicc
index d13d7ede..de943ad4 100755
--- a/linx64/mpi/mpich/bin/mpicc
+++ b/linx64/mpi/mpich/bin/mpicc
@@ -1,4 +1,4 @@
-#! /bin/bash
+#! /usr/bin/bash
 # 
 # (C) 2006 by Argonne National Laboratory.
 #     See COPYRIGHT in top-level directory.
@@ -27,17 +27,17 @@
 #
 # Directory locations: Fixed for any MPI implementation.
 # Set from the directory arguments to configure (e.g., --prefix=/usr/local)
-prefix=/home/brgirgis/Documents/code/thirdparty/mpi/mpich_/build/../release_install
-exec_prefix=/home/brgirgis/Documents/code/thirdparty/mpi/mpich_/build/../release_install
-sysconfdir=/home/brgirgis/Documents/code/thirdparty/mpi/mpich_/build/../release_install/etc
-includedir=/home/brgirgis/Documents/code/thirdparty/mpi/mpich_/build/../release_install/include
-libdir=/home/brgirgis/Documents/code/thirdparty/mpi/mpich_/build/../release_install/lib64
+prefix=/home/brgirgis/Documents/code/idiscovery/cpp-thirdparty-src/mpi/mpich/install/3.3.1
+exec_prefix=/home/brgirgis/Documents/code/idiscovery/cpp-thirdparty-src/mpi/mpich/install/3.3.1
+sysconfdir=/home/brgirgis/Documents/code/idiscovery/cpp-thirdparty-src/mpi/mpich/install/3.3.1/etc
+includedir=/home/brgirgis/Documents/code/idiscovery/cpp-thirdparty-src/mpi/mpich/install/3.3.1/include
+libdir=/home/brgirgis/Documents/code/idiscovery/cpp-thirdparty-src/mpi/mpich/install/3.3.1/lib64
 
 # Default settings for compiler, flags, and libraries.
 # Determined by a combination of environment variables and tests within
 # configure (e.g., determining whehter -lsocket is needee)
 CC="gcc"
-MPICH_VERSION="3.2.1"
+MPICH_VERSION="3.3.1"
 
 enable_wrapper_rpath="yes"
 
@@ -117,6 +117,7 @@ linking=yes
 allargs=("$@")
 argno=0
 interlib_deps=yes
+static_mpi=no
 for arg in "$@" ; do
     # Set addarg to no if this arg should be ignored by the C compiler
     addarg=yes
@@ -133,6 +134,11 @@ for arg in "$@" ; do
     -static)
     interlib_deps=no
     ;;
+    -static-mpi)
+    interlib_deps=no
+    static_mpi=yes
+    addarg=no
+    ;;
     -echo)
     addarg=no
     set -x
@@ -244,7 +250,7 @@ final_ldflags=" "
 final_libs=""
 if test "yes" = "no" -o "${interlib_deps}" = "no" ; then
     final_ldflags="${final_ldflags} "
-    final_libs="${final_libs} -lpthread    -lrt -lpthread "
+    final_libs="${final_libs}  -lm   -lpthread  -lrt "
 fi
 
 # -----------------------------------------------------------------------
@@ -275,7 +281,20 @@ if [ "$linking" = yes ] ; then
         $Show $CC ${final_cppflags} $PROFILE_INCPATHS ${final_cflags} ${final_ldflags} "${allargs[@]}" -I$includedir
         rc=$?
     else
-        $Show $CC ${final_cppflags} $PROFILE_INCPATHS ${final_cflags} ${final_ldflags} "${allargs[@]}" -I$includedir -L$libdir $PROFILE_PRELIB $PROFILE_FOO $rpath_flags -lmpi  $PROFILE_POSTLIB ${final_libs}
+        if [ "$static_mpi" = no ] ; then
+          $Show $CC ${final_cppflags} $PROFILE_INCPATHS ${final_cflags} ${final_ldflags} "${allargs[@]}" -I$includedir -L$libdir $PROFILE_PRELIB $PROFILE_FOO $rpath_flags -lmpi  $PROFILE_POSTLIB ${final_libs}
+        else
+          fabric_dep=""
+          if [ "" = yes ] ; then
+              fabric_dep=`pkg-config --static --libs $libdir/pkgconfig/libfabric.pc`
+              fabric_dep=`echo $fabric_dep | sed 's/-lfabric//'`
+          elif [ -f /lib/pkgconfig/libfabric.pc ] ; then
+              fabric_dep=`pkg-config --static --libs /lib/pkgconfig/libfabric.pc`
+          else
+              fabric_dep=`pkg-config --static --libs libfabric`
+          fi
+          $Show $CC ${final_cppflags} $PROFILE_INCPATHS ${final_cflags} ${final_ldflags} "${allargs[@]}" -I$includedir -L$libdir $PROFILE_PRELIB $PROFILE_FOO $rpath_flags $libdir/libmpi.a  $PROFILE_POSTLIB ${final_libs} ${fabric_dep}
+        fi
         rc=$?
     fi
 else
diff --git a/linx64/mpi/mpich/bin/mpichversion b/linx64/mpi/mpich/bin/mpichversion
index d82e5b12..d3ba662b 100755
Binary files a/linx64/mpi/mpich/bin/mpichversion and b/linx64/mpi/mpich/bin/mpichversion differ
diff --git a/linx64/mpi/mpich/bin/mpiexec.hydra b/linx64/mpi/mpich/bin/mpiexec.hydra
index e554a68b..ff8ea579 100755
Binary files a/linx64/mpi/mpich/bin/mpiexec.hydra and b/linx64/mpi/mpich/bin/mpiexec.hydra differ
diff --git a/linx64/mpi/mpich/bin/mpivars b/linx64/mpi/mpich/bin/mpivars
index fa4d414a..0aead2fe 100755
Binary files a/linx64/mpi/mpich/bin/mpivars and b/linx64/mpi/mpich/bin/mpivars differ
diff --git a/linx64/mpi/mpich/include/mpi.h b/linx64/mpi/mpich/include/mpi.h
index 4f43fa8b..a29e1046 100644
--- a/linx64/mpi/mpich/include/mpi.h
+++ b/linx64/mpi/mpich/include/mpi.h
@@ -9,6 +9,12 @@
 
 /* user include file for MPI programs */
 
+#if defined(HAVE_VISIBILITY)
+#define MPICH_API_PUBLIC __attribute__((visibility ("default")))
+#else
+#define MPICH_API_PUBLIC
+#endif
+
 /* Keep C++ compilers from getting confused */
 #if defined(__cplusplus)
 extern "C" {
@@ -381,8 +387,8 @@ typedef enum MPIR_Win_model {
 typedef enum MPIR_Topo_type { MPI_GRAPH=1, MPI_CART=2, MPI_DIST_GRAPH=3 } MPIR_Topo_type;
 
 #define MPI_BOTTOM      (void *)0
-extern int * const MPI_UNWEIGHTED;
-extern int * const MPI_WEIGHTS_EMPTY;
+extern int * const MPI_UNWEIGHTED MPICH_API_PUBLIC;
+extern int * const MPI_WEIGHTS_EMPTY MPICH_API_PUBLIC;
 
 #define MPI_PROC_NULL   (-1)
 #define MPI_ANY_SOURCE 	(-2)
@@ -484,8 +490,8 @@ typedef int (MPI_Delete_function) ( MPI_Comm, int, void *, void * );
  * digits for REV, 1 digit for EXT and 2 digits for EXT_NUMBER. So,
  * 1.0.7rc1 will have the numeric version 10007201.
  */
-#define MPICH_VERSION "3.2.1"
-#define MPICH_NUMVERSION 30201300
+#define MPICH_VERSION "3.3.1"
+#define MPICH_NUMVERSION 30301300
 
 #define MPICH_RELEASE_TYPE_ALPHA  0
 #define MPICH_RELEASE_TYPE_BETA   1
@@ -545,6 +551,9 @@ typedef int MPI_Info;
 /* predefined types for MPI_Comm_split_type */
 #define MPI_COMM_TYPE_SHARED    1
 
+/* MPICH-specific types */
+#define MPIX_COMM_TYPE_NEIGHBORHOOD 2
+
 /* Definitions that are determined by configure. */
 typedef long MPI_Aint;
 typedef int MPI_Fint;
@@ -593,7 +602,7 @@ typedef struct MPIR_T_pvar_handle_s * MPI_T_pvar_handle;
 typedef struct MPIR_T_pvar_session_s * MPI_T_pvar_session;
 
 /* extra const at front would be safer, but is incompatible with MPI_T_ prototypes */
-extern struct MPIR_T_pvar_handle_s * const MPI_T_PVAR_ALL_HANDLES;
+extern struct MPIR_T_pvar_handle_s * const MPI_T_PVAR_ALL_HANDLES MPICH_API_PUBLIC;
 
 #define MPI_T_ENUM_NULL         ((MPI_T_enum)NULL)
 #define MPI_T_CVAR_HANDLE_NULL  ((MPI_T_cvar_handle)NULL)
@@ -724,8 +733,8 @@ typedef enum MPIR_T_pvar_class_t {
 
 /* See 4.12.5 for MPI_F_STATUS(ES)_IGNORE */
 #define MPIU_DLL_SPEC
-extern MPIU_DLL_SPEC MPI_Fint * MPI_F_STATUS_IGNORE;
-extern MPIU_DLL_SPEC MPI_Fint * MPI_F_STATUSES_IGNORE;
+extern MPIU_DLL_SPEC MPI_Fint * MPI_F_STATUS_IGNORE MPICH_API_PUBLIC;
+extern MPIU_DLL_SPEC MPI_Fint * MPI_F_STATUSES_IGNORE MPICH_API_PUBLIC;
 /* The annotation MPIU_DLL_SPEC to the extern statements is used 
    as a hook for systems that require C extensions to correctly construct
    DLLs, and is defined as an empty string otherwise
@@ -745,16 +754,16 @@ typedef struct {
     MPI_Fint MPI_SOURCE;
     MPI_Fint MPI_TAG;
     MPI_Fint MPI_ERROR;
-} MPI_F08_Status;
+} MPI_F08_status;
 
-extern MPI_F08_Status MPIR_F08_MPI_STATUS_IGNORE_OBJ;
-extern MPI_F08_Status MPIR_F08_MPI_STATUSES_IGNORE_OBJ[1];
-extern int MPIR_F08_MPI_IN_PLACE;
-extern int MPIR_F08_MPI_BOTTOM;
+extern MPI_F08_status MPIR_F08_MPI_STATUS_IGNORE_OBJ MPICH_API_PUBLIC;
+extern MPI_F08_status MPIR_F08_MPI_STATUSES_IGNORE_OBJ[1] MPICH_API_PUBLIC;
+extern int MPIR_F08_MPI_IN_PLACE MPICH_API_PUBLIC;
+extern int MPIR_F08_MPI_BOTTOM MPICH_API_PUBLIC;
 
 /* Pointers to above objects */
-extern MPI_F08_Status *MPI_F08_STATUS_IGNORE;
-extern MPI_F08_Status *MPI_F08_STATUSES_IGNORE;
+extern MPI_F08_status *MPI_F08_STATUS_IGNORE MPICH_API_PUBLIC;
+extern MPI_F08_status *MPI_F08_STATUSES_IGNORE MPICH_API_PUBLIC;
 
 /* For supported thread levels */
 #define MPI_THREAD_SINGLE 0
@@ -873,7 +882,6 @@ typedef int (MPIX_Grequest_wait_function)(int, void **, double, MPI_Status *);
 
 #define MPI_ERR_LASTCODE    0x3fffffff  /* Last valid error code for a 
 					   predefined error class */
-/* WARNING: this is also defined in mpishared.h.  Update both locations */
 #define MPICH_ERR_LAST_CLASS 74     /* It is also helpful to know the
 				       last valid class */
 
@@ -886,8 +894,10 @@ typedef int (MPIX_Grequest_wait_function)(int, void **, double, MPI_Status *);
 #define MPIX_ERR_PROC_FAILED_PENDING  MPICH_ERR_FIRST_MPIX+2 /* A failure has caused this request
                                                               * to be pending */
 #define MPIX_ERR_REVOKED              MPICH_ERR_FIRST_MPIX+3 /* The communciation object has been revoked */
+#define MPIX_ERR_EAGAIN               MPICH_ERR_FIRST_MPIX+4 /* Operation could not be issued */
+#define MPIX_ERR_NOREQ                MPICH_ERR_FIRST_MPIX+5 /* Cannot allocate request */
 
-#define MPICH_ERR_LAST_MPIX           MPICH_ERR_FIRST_MPIX+3
+#define MPICH_ERR_LAST_MPIX           MPICH_ERR_FIRST_MPIX+5
 
 
 /* End of MPI's error classes */
@@ -914,642 +924,642 @@ typedef int (MPI_Datarep_extent_function)(MPI_Datatype datatype, MPI_Aint *,
 /* We require that the C compiler support prototypes */
 /* Begin Prototypes */
 int MPI_Send(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-             MPI_Comm comm) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+             MPI_Comm comm) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int MPI_Recv(void *buf, int count, MPI_Datatype datatype, int source, int tag,
-             MPI_Comm comm, MPI_Status *status) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
-int MPI_Get_count(const MPI_Status *status, MPI_Datatype datatype, int *count);
+             MPI_Comm comm, MPI_Status *status) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
+int MPI_Get_count(const MPI_Status *status, MPI_Datatype datatype, int *count) MPICH_API_PUBLIC;
 int MPI_Bsend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-              MPI_Comm comm) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+              MPI_Comm comm) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int MPI_Ssend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-              MPI_Comm comm) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+              MPI_Comm comm) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int MPI_Rsend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-              MPI_Comm comm) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
-int MPI_Buffer_attach(void *buffer, int size);
-int MPI_Buffer_detach(void *buffer_addr, int *size);
+              MPI_Comm comm) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
+int MPI_Buffer_attach(void *buffer, int size) MPICH_API_PUBLIC;
+int MPI_Buffer_detach(void *buffer_addr, int *size) MPICH_API_PUBLIC;
 int MPI_Isend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-              MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+              MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int MPI_Ibsend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-               MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+               MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int MPI_Issend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-               MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+               MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int MPI_Irsend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-               MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+               MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int MPI_Irecv(void *buf, int count, MPI_Datatype datatype, int source, int tag,
-              MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
-int MPI_Wait(MPI_Request *request, MPI_Status *status);
-int MPI_Test(MPI_Request *request, int *flag, MPI_Status *status);
-int MPI_Request_free(MPI_Request *request);
-int MPI_Waitany(int count, MPI_Request array_of_requests[], int *indx, MPI_Status *status);
+              MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
+int MPI_Wait(MPI_Request *request, MPI_Status *status) MPICH_API_PUBLIC;
+int MPI_Test(MPI_Request *request, int *flag, MPI_Status *status) MPICH_API_PUBLIC;
+int MPI_Request_free(MPI_Request *request) MPICH_API_PUBLIC;
+int MPI_Waitany(int count, MPI_Request array_of_requests[], int *indx, MPI_Status *status) MPICH_API_PUBLIC;
 int MPI_Testany(int count, MPI_Request array_of_requests[], int *indx, int *flag,
-                MPI_Status *status);
-int MPI_Waitall(int count, MPI_Request array_of_requests[], MPI_Status array_of_statuses[]);
+                MPI_Status *status) MPICH_API_PUBLIC;
+int MPI_Waitall(int count, MPI_Request array_of_requests[], MPI_Status array_of_statuses[]) MPICH_API_PUBLIC;
 int MPI_Testall(int count, MPI_Request array_of_requests[], int *flag,
-                MPI_Status array_of_statuses[]);
+                MPI_Status array_of_statuses[]) MPICH_API_PUBLIC;
 int MPI_Waitsome(int incount, MPI_Request array_of_requests[], int *outcount,
-                 int array_of_indices[], MPI_Status array_of_statuses[]);
+                 int array_of_indices[], MPI_Status array_of_statuses[]) MPICH_API_PUBLIC;
 int MPI_Testsome(int incount, MPI_Request array_of_requests[], int *outcount,
-                 int array_of_indices[], MPI_Status array_of_statuses[]);
-int MPI_Iprobe(int source, int tag, MPI_Comm comm, int *flag, MPI_Status *status);
-int MPI_Probe(int source, int tag, MPI_Comm comm, MPI_Status *status);
-int MPI_Cancel(MPI_Request *request);
-int MPI_Test_cancelled(const MPI_Status *status, int *flag);
+                 int array_of_indices[], MPI_Status array_of_statuses[]) MPICH_API_PUBLIC;
+int MPI_Iprobe(int source, int tag, MPI_Comm comm, int *flag, MPI_Status *status) MPICH_API_PUBLIC;
+int MPI_Probe(int source, int tag, MPI_Comm comm, MPI_Status *status) MPICH_API_PUBLIC;
+int MPI_Cancel(MPI_Request *request) MPICH_API_PUBLIC;
+int MPI_Test_cancelled(const MPI_Status *status, int *flag) MPICH_API_PUBLIC;
 int MPI_Send_init(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-                  MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+                  MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int MPI_Bsend_init(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-                   MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+                   MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int MPI_Ssend_init(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-                   MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+                   MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int MPI_Rsend_init(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-                   MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+                   MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int MPI_Recv_init(void *buf, int count, MPI_Datatype datatype, int source, int tag,
-                  MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
-int MPI_Start(MPI_Request *request);
-int MPI_Startall(int count, MPI_Request array_of_requests[]);
+                  MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
+int MPI_Start(MPI_Request *request) MPICH_API_PUBLIC;
+int MPI_Startall(int count, MPI_Request array_of_requests[]) MPICH_API_PUBLIC;
 int MPI_Sendrecv(const void *sendbuf, int sendcount, MPI_Datatype sendtype, int dest,
                  int sendtag, void *recvbuf, int recvcount, MPI_Datatype recvtype,
                  int source, int recvtag, MPI_Comm comm, MPI_Status *status)
-                 MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(6,8);
+                 MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(6,8) MPICH_API_PUBLIC;
 int MPI_Sendrecv_replace(void *buf, int count, MPI_Datatype datatype, int dest,
                          int sendtag, int source, int recvtag, MPI_Comm comm,
-                         MPI_Status *status) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
-int MPI_Type_contiguous(int count, MPI_Datatype oldtype, MPI_Datatype *newtype);
+                         MPI_Status *status) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
+int MPI_Type_contiguous(int count, MPI_Datatype oldtype, MPI_Datatype *newtype) MPICH_API_PUBLIC;
 int MPI_Type_vector(int count, int blocklength, int stride, MPI_Datatype oldtype,
-                    MPI_Datatype *newtype);
+                    MPI_Datatype *newtype) MPICH_API_PUBLIC;
 int MPI_Type_hvector(int count, int blocklength, MPI_Aint stride, MPI_Datatype oldtype,
-                     MPI_Datatype *newtype);
+                     MPI_Datatype *newtype) MPICH_API_PUBLIC;
 int MPI_Type_indexed(int count, const int *array_of_blocklengths,
                      const int *array_of_displacements, MPI_Datatype oldtype,
-                     MPI_Datatype *newtype);
+                     MPI_Datatype *newtype) MPICH_API_PUBLIC;
 int MPI_Type_hindexed(int count, int *array_of_blocklengths,
                       MPI_Aint *array_of_displacements, MPI_Datatype oldtype,
-                      MPI_Datatype *newtype);
+                      MPI_Datatype *newtype) MPICH_API_PUBLIC;
 int MPI_Type_struct(int count, int *array_of_blocklengths,
                     MPI_Aint *array_of_displacements,
-                    MPI_Datatype *array_of_types, MPI_Datatype *newtype);
-int MPI_Address(void *location, MPI_Aint *address);
-int MPI_Type_extent(MPI_Datatype datatype, MPI_Aint *extent);
-int MPI_Type_size(MPI_Datatype datatype, int *size);
-int MPI_Type_lb(MPI_Datatype datatype, MPI_Aint *displacement);
-int MPI_Type_ub(MPI_Datatype datatype, MPI_Aint *displacement);
-int MPI_Type_commit(MPI_Datatype *datatype);
-int MPI_Type_free(MPI_Datatype *datatype);
-int MPI_Get_elements(const MPI_Status *status, MPI_Datatype datatype, int *count);
+                    MPI_Datatype *array_of_types, MPI_Datatype *newtype) MPICH_API_PUBLIC;
+int MPI_Address(void *location, MPI_Aint *address) MPICH_API_PUBLIC;
+int MPI_Type_extent(MPI_Datatype datatype, MPI_Aint *extent) MPICH_API_PUBLIC;
+int MPI_Type_size(MPI_Datatype datatype, int *size) MPICH_API_PUBLIC;
+int MPI_Type_lb(MPI_Datatype datatype, MPI_Aint *displacement) MPICH_API_PUBLIC;
+int MPI_Type_ub(MPI_Datatype datatype, MPI_Aint *displacement) MPICH_API_PUBLIC;
+int MPI_Type_commit(MPI_Datatype *datatype) MPICH_API_PUBLIC;
+int MPI_Type_free(MPI_Datatype *datatype) MPICH_API_PUBLIC;
+int MPI_Get_elements(const MPI_Status *status, MPI_Datatype datatype, int *count) MPICH_API_PUBLIC;
 int MPI_Pack(const void *inbuf, int incount, MPI_Datatype datatype, void *outbuf,
-             int outsize, int *position, MPI_Comm comm) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+             int outsize, int *position, MPI_Comm comm) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int MPI_Unpack(const void *inbuf, int insize, int *position, void *outbuf, int outcount,
-               MPI_Datatype datatype, MPI_Comm comm) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6);
-int MPI_Pack_size(int incount, MPI_Datatype datatype, MPI_Comm comm, int *size);
-int MPI_Barrier(MPI_Comm comm);
+               MPI_Datatype datatype, MPI_Comm comm) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6) MPICH_API_PUBLIC;
+int MPI_Pack_size(int incount, MPI_Datatype datatype, MPI_Comm comm, int *size) MPICH_API_PUBLIC;
+int MPI_Barrier(MPI_Comm comm) MPICH_API_PUBLIC;
 int MPI_Bcast(void *buffer, int count, MPI_Datatype datatype, int root, MPI_Comm comm)
-              MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+              MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int MPI_Gather(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
                int recvcount, MPI_Datatype recvtype, int root, MPI_Comm comm)
-               MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6);
+               MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6) MPICH_API_PUBLIC;
 int MPI_Gatherv(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
                 const int *recvcounts, const int *displs, MPI_Datatype recvtype, int root,
                 MPI_Comm comm)
-                MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,7);
+                MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,7) MPICH_API_PUBLIC;
 int MPI_Scatter(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
                 int recvcount, MPI_Datatype recvtype, int root, MPI_Comm comm)
-                MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6);
+                MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6) MPICH_API_PUBLIC;
 int MPI_Scatterv(const void *sendbuf, const int *sendcounts, const int *displs,
                  MPI_Datatype sendtype, void *recvbuf, int recvcount, MPI_Datatype recvtype,
                  int root, MPI_Comm comm)
-                 MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(5,7);
+                 MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(5,7) MPICH_API_PUBLIC;
 int MPI_Allgather(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
                   int recvcount, MPI_Datatype recvtype, MPI_Comm comm)
-                  MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6);
+                  MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6) MPICH_API_PUBLIC;
 int MPI_Allgatherv(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
                    const int *recvcounts, const int *displs, MPI_Datatype recvtype, MPI_Comm comm)
-                   MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,7);
+                   MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,7) MPICH_API_PUBLIC;
 int MPI_Alltoall(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
                  int recvcount, MPI_Datatype recvtype, MPI_Comm comm)
-                 MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6);
+                 MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6) MPICH_API_PUBLIC;
 int MPI_Alltoallv(const void *sendbuf, const int *sendcounts, const int *sdispls,
                   MPI_Datatype sendtype, void *recvbuf, const int *recvcounts,
                   const int *rdispls, MPI_Datatype recvtype, MPI_Comm comm)
-                  MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(5,8);
+                  MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(5,8) MPICH_API_PUBLIC;
 int MPI_Alltoallw(const void *sendbuf, const int sendcounts[], const int sdispls[],
                   const MPI_Datatype sendtypes[], void *recvbuf, const int recvcounts[],
-                  const int rdispls[], const MPI_Datatype recvtypes[], MPI_Comm comm);
+                  const int rdispls[], const MPI_Datatype recvtypes[], MPI_Comm comm) MPICH_API_PUBLIC;
 int MPI_Exscan(const void *sendbuf, void *recvbuf, int count, MPI_Datatype datatype,
                MPI_Op op, MPI_Comm comm)
-               MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+               MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) MPICH_API_PUBLIC;
 int MPI_Reduce(const void *sendbuf, void *recvbuf, int count, MPI_Datatype datatype,
                MPI_Op op, int root, MPI_Comm comm)
-               MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
-int MPI_Op_create(MPI_User_function *user_fn, int commute, MPI_Op *op);
-int MPI_Op_free(MPI_Op *op);
+               MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) MPICH_API_PUBLIC;
+int MPI_Op_create(MPI_User_function *user_fn, int commute, MPI_Op *op) MPICH_API_PUBLIC;
+int MPI_Op_free(MPI_Op *op) MPICH_API_PUBLIC;
 int MPI_Allreduce(const void *sendbuf, void *recvbuf, int count, MPI_Datatype datatype,
                   MPI_Op op, MPI_Comm comm)
-                  MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                  MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) MPICH_API_PUBLIC;
 int MPI_Reduce_scatter(const void *sendbuf, void *recvbuf, const int recvcounts[],
                        MPI_Datatype datatype, MPI_Op op, MPI_Comm comm)
-                       MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                       MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) MPICH_API_PUBLIC;
 int MPI_Scan(const void *sendbuf, void *recvbuf, int count, MPI_Datatype datatype, MPI_Op op,
              MPI_Comm comm)
-             MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
-int MPI_Group_size(MPI_Group group, int *size);
-int MPI_Group_rank(MPI_Group group, int *rank);
+             MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) MPICH_API_PUBLIC;
+int MPI_Group_size(MPI_Group group, int *size) MPICH_API_PUBLIC;
+int MPI_Group_rank(MPI_Group group, int *rank) MPICH_API_PUBLIC;
 int MPI_Group_translate_ranks(MPI_Group group1, int n, const int ranks1[], MPI_Group group2,
-                              int ranks2[]);
-int MPI_Group_compare(MPI_Group group1, MPI_Group group2, int *result);
-int MPI_Comm_group(MPI_Comm comm, MPI_Group *group);
-int MPI_Group_union(MPI_Group group1, MPI_Group group2, MPI_Group *newgroup);
-int MPI_Group_intersection(MPI_Group group1, MPI_Group group2, MPI_Group *newgroup);
-int MPI_Group_difference(MPI_Group group1, MPI_Group group2, MPI_Group *newgroup);
-int MPI_Group_incl(MPI_Group group, int n, const int ranks[], MPI_Group *newgroup);
-int MPI_Group_excl(MPI_Group group, int n, const int ranks[], MPI_Group *newgroup);
-int MPI_Group_range_incl(MPI_Group group, int n, int ranges[][3], MPI_Group *newgroup);
-int MPI_Group_range_excl(MPI_Group group, int n, int ranges[][3], MPI_Group *newgroup);
-int MPI_Group_free(MPI_Group *group);
-int MPI_Comm_size(MPI_Comm comm, int *size);
-int MPI_Comm_rank(MPI_Comm comm, int *rank);
-int MPI_Comm_compare(MPI_Comm comm1, MPI_Comm comm2, int *result);
-int MPI_Comm_dup(MPI_Comm comm, MPI_Comm *newcomm);
-int MPI_Comm_dup_with_info(MPI_Comm comm, MPI_Info info, MPI_Comm *newcomm);
-int MPI_Comm_create(MPI_Comm comm, MPI_Group group, MPI_Comm *newcomm);
-int MPI_Comm_split(MPI_Comm comm, int color, int key, MPI_Comm *newcomm);
-int MPI_Comm_free(MPI_Comm *comm);
-int MPI_Comm_test_inter(MPI_Comm comm, int *flag);
-int MPI_Comm_remote_size(MPI_Comm comm, int *size);
-int MPI_Comm_remote_group(MPI_Comm comm, MPI_Group *group);
+                              int ranks2[]) MPICH_API_PUBLIC;
+int MPI_Group_compare(MPI_Group group1, MPI_Group group2, int *result) MPICH_API_PUBLIC;
+int MPI_Comm_group(MPI_Comm comm, MPI_Group *group) MPICH_API_PUBLIC;
+int MPI_Group_union(MPI_Group group1, MPI_Group group2, MPI_Group *newgroup) MPICH_API_PUBLIC;
+int MPI_Group_intersection(MPI_Group group1, MPI_Group group2, MPI_Group *newgroup) MPICH_API_PUBLIC;
+int MPI_Group_difference(MPI_Group group1, MPI_Group group2, MPI_Group *newgroup) MPICH_API_PUBLIC;
+int MPI_Group_incl(MPI_Group group, int n, const int ranks[], MPI_Group *newgroup) MPICH_API_PUBLIC;
+int MPI_Group_excl(MPI_Group group, int n, const int ranks[], MPI_Group *newgroup) MPICH_API_PUBLIC;
+int MPI_Group_range_incl(MPI_Group group, int n, int ranges[][3], MPI_Group *newgroup) MPICH_API_PUBLIC;
+int MPI_Group_range_excl(MPI_Group group, int n, int ranges[][3], MPI_Group *newgroup) MPICH_API_PUBLIC;
+int MPI_Group_free(MPI_Group *group) MPICH_API_PUBLIC;
+int MPI_Comm_size(MPI_Comm comm, int *size) MPICH_API_PUBLIC;
+int MPI_Comm_rank(MPI_Comm comm, int *rank) MPICH_API_PUBLIC;
+int MPI_Comm_compare(MPI_Comm comm1, MPI_Comm comm2, int *result) MPICH_API_PUBLIC;
+int MPI_Comm_dup(MPI_Comm comm, MPI_Comm *newcomm) MPICH_API_PUBLIC;
+int MPI_Comm_dup_with_info(MPI_Comm comm, MPI_Info info, MPI_Comm *newcomm) MPICH_API_PUBLIC;
+int MPI_Comm_create(MPI_Comm comm, MPI_Group group, MPI_Comm *newcomm) MPICH_API_PUBLIC;
+int MPI_Comm_split(MPI_Comm comm, int color, int key, MPI_Comm *newcomm) MPICH_API_PUBLIC;
+int MPI_Comm_free(MPI_Comm *comm) MPICH_API_PUBLIC;
+int MPI_Comm_test_inter(MPI_Comm comm, int *flag) MPICH_API_PUBLIC;
+int MPI_Comm_remote_size(MPI_Comm comm, int *size) MPICH_API_PUBLIC;
+int MPI_Comm_remote_group(MPI_Comm comm, MPI_Group *group) MPICH_API_PUBLIC;
 int MPI_Intercomm_create(MPI_Comm local_comm, int local_leader, MPI_Comm peer_comm,
-                         int remote_leader, int tag, MPI_Comm *newintercomm);
-int MPI_Intercomm_merge(MPI_Comm intercomm, int high, MPI_Comm *newintracomm);
+                         int remote_leader, int tag, MPI_Comm *newintercomm) MPICH_API_PUBLIC;
+int MPI_Intercomm_merge(MPI_Comm intercomm, int high, MPI_Comm *newintracomm) MPICH_API_PUBLIC;
 int MPI_Keyval_create(MPI_Copy_function *copy_fn, MPI_Delete_function *delete_fn,
-                      int *keyval, void *extra_state);
-int MPI_Keyval_free(int *keyval);
-int MPI_Attr_put(MPI_Comm comm, int keyval, void *attribute_val);
-int MPI_Attr_get(MPI_Comm comm, int keyval, void *attribute_val, int *flag);
-int MPI_Attr_delete(MPI_Comm comm, int keyval);
-int MPI_Topo_test(MPI_Comm comm, int *status);
+                      int *keyval, void *extra_state) MPICH_API_PUBLIC;
+int MPI_Keyval_free(int *keyval) MPICH_API_PUBLIC;
+int MPI_Attr_put(MPI_Comm comm, int keyval, void *attribute_val) MPICH_API_PUBLIC;
+int MPI_Attr_get(MPI_Comm comm, int keyval, void *attribute_val, int *flag) MPICH_API_PUBLIC;
+int MPI_Attr_delete(MPI_Comm comm, int keyval) MPICH_API_PUBLIC;
+int MPI_Topo_test(MPI_Comm comm, int *status) MPICH_API_PUBLIC;
 int MPI_Cart_create(MPI_Comm comm_old, int ndims, const int dims[], const int periods[],
-                    int reorder, MPI_Comm *comm_cart);
-int MPI_Dims_create(int nnodes, int ndims, int dims[]);
+                    int reorder, MPI_Comm *comm_cart) MPICH_API_PUBLIC;
+int MPI_Dims_create(int nnodes, int ndims, int dims[]) MPICH_API_PUBLIC;
 int MPI_Graph_create(MPI_Comm comm_old, int nnodes, const int indx[], const int edges[],
-                     int reorder, MPI_Comm *comm_graph);
-int MPI_Graphdims_get(MPI_Comm comm, int *nnodes, int *nedges);
-int MPI_Graph_get(MPI_Comm comm, int maxindex, int maxedges, int indx[], int edges[]);
-int MPI_Cartdim_get(MPI_Comm comm, int *ndims);
-int MPI_Cart_get(MPI_Comm comm, int maxdims, int dims[], int periods[], int coords[]);
-int MPI_Cart_rank(MPI_Comm comm, const int coords[], int *rank);
-int MPI_Cart_coords(MPI_Comm comm, int rank, int maxdims, int coords[]);
-int MPI_Graph_neighbors_count(MPI_Comm comm, int rank, int *nneighbors);
-int MPI_Graph_neighbors(MPI_Comm comm, int rank, int maxneighbors, int neighbors[]);
-int MPI_Cart_shift(MPI_Comm comm, int direction, int disp, int *rank_source, int *rank_dest);
-int MPI_Cart_sub(MPI_Comm comm, const int remain_dims[], MPI_Comm *newcomm);
-int MPI_Cart_map(MPI_Comm comm, int ndims, const int dims[], const int periods[], int *newrank);
-int MPI_Graph_map(MPI_Comm comm, int nnodes, const int indx[], const int edges[], int *newrank);
-int MPI_Get_processor_name(char *name, int *resultlen);
-int MPI_Get_version(int *version, int *subversion);
-int MPI_Get_library_version(char *version, int *resultlen);
-int MPI_Errhandler_create(MPI_Handler_function *function, MPI_Errhandler *errhandler);
-int MPI_Errhandler_set(MPI_Comm comm, MPI_Errhandler errhandler);
-int MPI_Errhandler_get(MPI_Comm comm, MPI_Errhandler *errhandler);
-int MPI_Errhandler_free(MPI_Errhandler *errhandler);
-int MPI_Error_string(int errorcode, char *string, int *resultlen);
-int MPI_Error_class(int errorcode, int *errorclass);
-double MPI_Wtime(void);
-double MPI_Wtick(void);
-int MPI_Init(int *argc, char ***argv);
-int MPI_Finalize(void);
-int MPI_Initialized(int *flag);
-int MPI_Abort(MPI_Comm comm, int errorcode);
+                     int reorder, MPI_Comm *comm_graph) MPICH_API_PUBLIC;
+int MPI_Graphdims_get(MPI_Comm comm, int *nnodes, int *nedges) MPICH_API_PUBLIC;
+int MPI_Graph_get(MPI_Comm comm, int maxindex, int maxedges, int indx[], int edges[]) MPICH_API_PUBLIC;
+int MPI_Cartdim_get(MPI_Comm comm, int *ndims) MPICH_API_PUBLIC;
+int MPI_Cart_get(MPI_Comm comm, int maxdims, int dims[], int periods[], int coords[]) MPICH_API_PUBLIC;
+int MPI_Cart_rank(MPI_Comm comm, const int coords[], int *rank) MPICH_API_PUBLIC;
+int MPI_Cart_coords(MPI_Comm comm, int rank, int maxdims, int coords[]) MPICH_API_PUBLIC;
+int MPI_Graph_neighbors_count(MPI_Comm comm, int rank, int *nneighbors) MPICH_API_PUBLIC;
+int MPI_Graph_neighbors(MPI_Comm comm, int rank, int maxneighbors, int neighbors[]) MPICH_API_PUBLIC;
+int MPI_Cart_shift(MPI_Comm comm, int direction, int disp, int *rank_source, int *rank_dest) MPICH_API_PUBLIC;
+int MPI_Cart_sub(MPI_Comm comm, const int remain_dims[], MPI_Comm *newcomm) MPICH_API_PUBLIC;
+int MPI_Cart_map(MPI_Comm comm, int ndims, const int dims[], const int periods[], int *newrank) MPICH_API_PUBLIC;
+int MPI_Graph_map(MPI_Comm comm, int nnodes, const int indx[], const int edges[], int *newrank) MPICH_API_PUBLIC;
+int MPI_Get_processor_name(char *name, int *resultlen) MPICH_API_PUBLIC;
+int MPI_Get_version(int *version, int *subversion) MPICH_API_PUBLIC;
+int MPI_Get_library_version(char *version, int *resultlen) MPICH_API_PUBLIC;
+int MPI_Errhandler_create(MPI_Handler_function *function, MPI_Errhandler *errhandler) MPICH_API_PUBLIC;
+int MPI_Errhandler_set(MPI_Comm comm, MPI_Errhandler errhandler) MPICH_API_PUBLIC;
+int MPI_Errhandler_get(MPI_Comm comm, MPI_Errhandler *errhandler) MPICH_API_PUBLIC;
+int MPI_Errhandler_free(MPI_Errhandler *errhandler) MPICH_API_PUBLIC;
+int MPI_Error_string(int errorcode, char *string, int *resultlen) MPICH_API_PUBLIC;
+int MPI_Error_class(int errorcode, int *errorclass) MPICH_API_PUBLIC;
+double MPI_Wtime(void) MPICH_API_PUBLIC;
+double MPI_Wtick(void) MPICH_API_PUBLIC;
+int MPI_Init(int *argc, char ***argv) MPICH_API_PUBLIC;
+int MPI_Finalize(void) MPICH_API_PUBLIC;
+int MPI_Initialized(int *flag) MPICH_API_PUBLIC;
+int MPI_Abort(MPI_Comm comm, int errorcode) MPICH_API_PUBLIC;
 
 /* Note that we may need to define a @PCONTROL_LIST@ depending on whether
    stdargs are supported */
-int MPI_Pcontrol(const int level, ...);
+int MPI_Pcontrol(const int level, ...) MPICH_API_PUBLIC;
 int MPI_DUP_FN(MPI_Comm oldcomm, int keyval, void *extra_state, void *attribute_val_in,
-               void *attribute_val_out, int *flag);
+               void *attribute_val_out, int *flag) MPICH_API_PUBLIC;
 
 /* Process Creation and Management */
-int MPI_Close_port(const char *port_name);
+int MPI_Close_port(const char *port_name) MPICH_API_PUBLIC;
 int MPI_Comm_accept(const char *port_name, MPI_Info info, int root, MPI_Comm comm,
-                    MPI_Comm *newcomm);
+                    MPI_Comm *newcomm) MPICH_API_PUBLIC;
 int MPI_Comm_connect(const char *port_name, MPI_Info info, int root, MPI_Comm comm,
-                     MPI_Comm *newcomm);
-int MPI_Comm_disconnect(MPI_Comm *comm);
-int MPI_Comm_get_parent(MPI_Comm *parent);
-int MPI_Comm_join(int fd, MPI_Comm *intercomm);
+                     MPI_Comm *newcomm) MPICH_API_PUBLIC;
+int MPI_Comm_disconnect(MPI_Comm *comm) MPICH_API_PUBLIC;
+int MPI_Comm_get_parent(MPI_Comm *parent) MPICH_API_PUBLIC;
+int MPI_Comm_join(int fd, MPI_Comm *intercomm) MPICH_API_PUBLIC;
 int MPI_Comm_spawn(const char *command, char *argv[], int maxprocs, MPI_Info info, int root,
-                   MPI_Comm comm, MPI_Comm *intercomm, int array_of_errcodes[]);
+                   MPI_Comm comm, MPI_Comm *intercomm, int array_of_errcodes[]) MPICH_API_PUBLIC;
 int MPI_Comm_spawn_multiple(int count, char *array_of_commands[], char **array_of_argv[],
                             const int array_of_maxprocs[], const MPI_Info array_of_info[],
-                            int root, MPI_Comm comm, MPI_Comm *intercomm, int array_of_errcodes[]);
-int MPI_Lookup_name(const char *service_name, MPI_Info info, char *port_name);
-int MPI_Open_port(MPI_Info info, char *port_name);
-int MPI_Publish_name(const char *service_name, MPI_Info info, const char *port_name);
-int MPI_Unpublish_name(const char *service_name, MPI_Info info, const char *port_name);
-int MPI_Comm_set_info(MPI_Comm comm, MPI_Info info);
-int MPI_Comm_get_info(MPI_Comm comm, MPI_Info *info);
+                            int root, MPI_Comm comm, MPI_Comm *intercomm, int array_of_errcodes[]) MPICH_API_PUBLIC;
+int MPI_Lookup_name(const char *service_name, MPI_Info info, char *port_name) MPICH_API_PUBLIC;
+int MPI_Open_port(MPI_Info info, char *port_name) MPICH_API_PUBLIC;
+int MPI_Publish_name(const char *service_name, MPI_Info info, const char *port_name) MPICH_API_PUBLIC;
+int MPI_Unpublish_name(const char *service_name, MPI_Info info, const char *port_name) MPICH_API_PUBLIC;
+int MPI_Comm_set_info(MPI_Comm comm, MPI_Info info) MPICH_API_PUBLIC;
+int MPI_Comm_get_info(MPI_Comm comm, MPI_Info *info) MPICH_API_PUBLIC;
 
 /* One-Sided Communications */
 int MPI_Accumulate(const void *origin_addr, int origin_count, MPI_Datatype origin_datatype,
                    int target_rank, MPI_Aint target_disp, int target_count,
                    MPI_Datatype target_datatype, MPI_Op op, MPI_Win win)
-                   MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+                   MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int MPI_Get(void *origin_addr, int origin_count, MPI_Datatype origin_datatype,
             int target_rank, MPI_Aint target_disp, int target_count,
-            MPI_Datatype target_datatype, MPI_Win win) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+            MPI_Datatype target_datatype, MPI_Win win) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int MPI_Put(const void *origin_addr, int origin_count, MPI_Datatype origin_datatype,
             int target_rank, MPI_Aint target_disp, int target_count,
-            MPI_Datatype target_datatype, MPI_Win win) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
-int MPI_Win_complete(MPI_Win win);
+            MPI_Datatype target_datatype, MPI_Win win) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
+int MPI_Win_complete(MPI_Win win) MPICH_API_PUBLIC;
 int MPI_Win_create(void *base, MPI_Aint size, int disp_unit, MPI_Info info, MPI_Comm comm,
-                   MPI_Win *win);
-int MPI_Win_fence(int assert, MPI_Win win);
-int MPI_Win_free(MPI_Win *win);
-int MPI_Win_get_group(MPI_Win win, MPI_Group *group);
-int MPI_Win_lock(int lock_type, int rank, int assert, MPI_Win win);
-int MPI_Win_post(MPI_Group group, int assert, MPI_Win win);
-int MPI_Win_start(MPI_Group group, int assert, MPI_Win win);
-int MPI_Win_test(MPI_Win win, int *flag);
-int MPI_Win_unlock(int rank, MPI_Win win);
-int MPI_Win_wait(MPI_Win win);
+                   MPI_Win *win) MPICH_API_PUBLIC;
+int MPI_Win_fence(int assert, MPI_Win win) MPICH_API_PUBLIC;
+int MPI_Win_free(MPI_Win *win) MPICH_API_PUBLIC;
+int MPI_Win_get_group(MPI_Win win, MPI_Group *group) MPICH_API_PUBLIC;
+int MPI_Win_lock(int lock_type, int rank, int assert, MPI_Win win) MPICH_API_PUBLIC;
+int MPI_Win_post(MPI_Group group, int assert, MPI_Win win) MPICH_API_PUBLIC;
+int MPI_Win_start(MPI_Group group, int assert, MPI_Win win) MPICH_API_PUBLIC;
+int MPI_Win_test(MPI_Win win, int *flag) MPICH_API_PUBLIC;
+int MPI_Win_unlock(int rank, MPI_Win win) MPICH_API_PUBLIC;
+int MPI_Win_wait(MPI_Win win) MPICH_API_PUBLIC;
 
 /* MPI-3 One-Sided Communication Routines */
 int MPI_Win_allocate(MPI_Aint size, int disp_unit, MPI_Info info, MPI_Comm comm, void *baseptr,
-                     MPI_Win *win);
+                     MPI_Win *win) MPICH_API_PUBLIC;
 int MPI_Win_allocate_shared(MPI_Aint size, int disp_unit, MPI_Info info, MPI_Comm comm,
-                            void *baseptr, MPI_Win *win);
-int MPI_Win_shared_query(MPI_Win win, int rank, MPI_Aint *size, int *disp_unit, void *baseptr);
-int MPI_Win_create_dynamic(MPI_Info info, MPI_Comm comm, MPI_Win *win);
-int MPI_Win_attach(MPI_Win win, void *base, MPI_Aint size);
-int MPI_Win_detach(MPI_Win win, const void *base);
-int MPI_Win_get_info(MPI_Win win, MPI_Info *info_used);
-int MPI_Win_set_info(MPI_Win win, MPI_Info info);
+                            void *baseptr, MPI_Win *win) MPICH_API_PUBLIC;
+int MPI_Win_shared_query(MPI_Win win, int rank, MPI_Aint *size, int *disp_unit, void *baseptr) MPICH_API_PUBLIC;
+int MPI_Win_create_dynamic(MPI_Info info, MPI_Comm comm, MPI_Win *win) MPICH_API_PUBLIC;
+int MPI_Win_attach(MPI_Win win, void *base, MPI_Aint size) MPICH_API_PUBLIC;
+int MPI_Win_detach(MPI_Win win, const void *base) MPICH_API_PUBLIC;
+int MPI_Win_get_info(MPI_Win win, MPI_Info *info_used) MPICH_API_PUBLIC;
+int MPI_Win_set_info(MPI_Win win, MPI_Info info) MPICH_API_PUBLIC;
 int MPI_Get_accumulate(const void *origin_addr, int origin_count,
                         MPI_Datatype origin_datatype, void *result_addr, int result_count,
                         MPI_Datatype result_datatype, int target_rank, MPI_Aint target_disp,
                         int target_count, MPI_Datatype target_datatype, MPI_Op op, MPI_Win win)
                         MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3)
-                        MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6);
+                        MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6) MPICH_API_PUBLIC;
 int MPI_Fetch_and_op(const void *origin_addr, void *result_addr,
                       MPI_Datatype datatype, int target_rank, MPI_Aint target_disp,
                       MPI_Op op, MPI_Win win)
-                      MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+                      MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int MPI_Compare_and_swap(const void *origin_addr, const void *compare_addr,
                           void *result_addr, MPI_Datatype datatype, int target_rank,
                           MPI_Aint target_disp, MPI_Win win)
                           MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4)
                           MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4)
-                          MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,4);
+                          MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,4) MPICH_API_PUBLIC;
 int MPI_Rput(const void *origin_addr, int origin_count,
               MPI_Datatype origin_datatype, int target_rank, MPI_Aint target_disp,
               int target_count, MPI_Datatype target_datatype, MPI_Win win,
               MPI_Request *request)
-              MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+              MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int MPI_Rget(void *origin_addr, int origin_count,
               MPI_Datatype origin_datatype, int target_rank, MPI_Aint target_disp,
               int target_count, MPI_Datatype target_datatype, MPI_Win win,
               MPI_Request *request)
-              MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+              MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int MPI_Raccumulate(const void *origin_addr, int origin_count,
                      MPI_Datatype origin_datatype, int target_rank, MPI_Aint target_disp,
                      int target_count, MPI_Datatype target_datatype, MPI_Op op, MPI_Win win,
                      MPI_Request *request)
-                     MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+                     MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int MPI_Rget_accumulate(const void *origin_addr, int origin_count,
                          MPI_Datatype origin_datatype, void *result_addr, int result_count,
                          MPI_Datatype result_datatype, int target_rank, MPI_Aint target_disp,
                          int target_count, MPI_Datatype target_datatype, MPI_Op op, MPI_Win win,
                          MPI_Request *request)
                          MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3)
-                         MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6);
-int MPI_Win_lock_all(int assert, MPI_Win win);
-int MPI_Win_unlock_all(MPI_Win win);
-int MPI_Win_flush(int rank, MPI_Win win);
-int MPI_Win_flush_all(MPI_Win win);
-int MPI_Win_flush_local(int rank, MPI_Win win);
-int MPI_Win_flush_local_all(MPI_Win win);
-int MPI_Win_sync(MPI_Win win);
+                         MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6) MPICH_API_PUBLIC;
+int MPI_Win_lock_all(int assert, MPI_Win win) MPICH_API_PUBLIC;
+int MPI_Win_unlock_all(MPI_Win win) MPICH_API_PUBLIC;
+int MPI_Win_flush(int rank, MPI_Win win) MPICH_API_PUBLIC;
+int MPI_Win_flush_all(MPI_Win win) MPICH_API_PUBLIC;
+int MPI_Win_flush_local(int rank, MPI_Win win) MPICH_API_PUBLIC;
+int MPI_Win_flush_local_all(MPI_Win win) MPICH_API_PUBLIC;
+int MPI_Win_sync(MPI_Win win) MPICH_API_PUBLIC;
  
 /* External Interfaces */
-int MPI_Add_error_class(int *errorclass);
-int MPI_Add_error_code(int errorclass, int *errorcode);
-int MPI_Add_error_string(int errorcode, const char *string);
-int MPI_Comm_call_errhandler(MPI_Comm comm, int errorcode);
+int MPI_Add_error_class(int *errorclass) MPICH_API_PUBLIC;
+int MPI_Add_error_code(int errorclass, int *errorcode) MPICH_API_PUBLIC;
+int MPI_Add_error_string(int errorcode, const char *string) MPICH_API_PUBLIC;
+int MPI_Comm_call_errhandler(MPI_Comm comm, int errorcode) MPICH_API_PUBLIC;
 int MPI_Comm_create_keyval(MPI_Comm_copy_attr_function *comm_copy_attr_fn,
                            MPI_Comm_delete_attr_function *comm_delete_attr_fn, int *comm_keyval,
-                           void *extra_state);
-int MPI_Comm_delete_attr(MPI_Comm comm, int comm_keyval);
-int MPI_Comm_free_keyval(int *comm_keyval);
-int MPI_Comm_get_attr(MPI_Comm comm, int comm_keyval, void *attribute_val, int *flag);
-int MPI_Comm_get_name(MPI_Comm comm, char *comm_name, int *resultlen);
-int MPI_Comm_set_attr(MPI_Comm comm, int comm_keyval, void *attribute_val);
-int MPI_Comm_set_name(MPI_Comm comm, const char *comm_name);
-int MPI_File_call_errhandler(MPI_File fh, int errorcode);
-int MPI_Grequest_complete(MPI_Request request);
+                           void *extra_state) MPICH_API_PUBLIC;
+int MPI_Comm_delete_attr(MPI_Comm comm, int comm_keyval) MPICH_API_PUBLIC;
+int MPI_Comm_free_keyval(int *comm_keyval) MPICH_API_PUBLIC;
+int MPI_Comm_get_attr(MPI_Comm comm, int comm_keyval, void *attribute_val, int *flag) MPICH_API_PUBLIC;
+int MPI_Comm_get_name(MPI_Comm comm, char *comm_name, int *resultlen) MPICH_API_PUBLIC;
+int MPI_Comm_set_attr(MPI_Comm comm, int comm_keyval, void *attribute_val) MPICH_API_PUBLIC;
+int MPI_Comm_set_name(MPI_Comm comm, const char *comm_name) MPICH_API_PUBLIC;
+int MPI_File_call_errhandler(MPI_File fh, int errorcode) MPICH_API_PUBLIC;
+int MPI_Grequest_complete(MPI_Request request) MPICH_API_PUBLIC;
 int MPI_Grequest_start(MPI_Grequest_query_function *query_fn, MPI_Grequest_free_function *free_fn,
                        MPI_Grequest_cancel_function *cancel_fn, void *extra_state,
-                       MPI_Request *request);
-int MPI_Init_thread(int *argc, char ***argv, int required, int *provided);
-int MPI_Is_thread_main(int *flag);
-int MPI_Query_thread(int *provided);
-int MPI_Status_set_cancelled(MPI_Status *status, int flag);
-int MPI_Status_set_elements(MPI_Status *status, MPI_Datatype datatype, int count);
+                       MPI_Request *request) MPICH_API_PUBLIC;
+int MPI_Init_thread(int *argc, char ***argv, int required, int *provided) MPICH_API_PUBLIC;
+int MPI_Is_thread_main(int *flag) MPICH_API_PUBLIC;
+int MPI_Query_thread(int *provided) MPICH_API_PUBLIC;
+int MPI_Status_set_cancelled(MPI_Status *status, int flag) MPICH_API_PUBLIC;
+int MPI_Status_set_elements(MPI_Status *status, MPI_Datatype datatype, int count) MPICH_API_PUBLIC;
 int MPI_Type_create_keyval(MPI_Type_copy_attr_function *type_copy_attr_fn,
                            MPI_Type_delete_attr_function *type_delete_attr_fn,
-                           int *type_keyval, void *extra_state);
-int MPI_Type_delete_attr(MPI_Datatype datatype, int type_keyval);
-int MPI_Type_dup(MPI_Datatype oldtype, MPI_Datatype *newtype);
-int MPI_Type_free_keyval(int *type_keyval);
-int MPI_Type_get_attr(MPI_Datatype datatype, int type_keyval, void *attribute_val, int *flag);
+                           int *type_keyval, void *extra_state) MPICH_API_PUBLIC;
+int MPI_Type_delete_attr(MPI_Datatype datatype, int type_keyval) MPICH_API_PUBLIC;
+int MPI_Type_dup(MPI_Datatype oldtype, MPI_Datatype *newtype) MPICH_API_PUBLIC;
+int MPI_Type_free_keyval(int *type_keyval) MPICH_API_PUBLIC;
+int MPI_Type_get_attr(MPI_Datatype datatype, int type_keyval, void *attribute_val, int *flag) MPICH_API_PUBLIC;
 int MPI_Type_get_contents(MPI_Datatype datatype, int max_integers, int max_addresses,
                           int max_datatypes, int array_of_integers[],
-                          MPI_Aint array_of_addresses[], MPI_Datatype array_of_datatypes[]);
+                          MPI_Aint array_of_addresses[], MPI_Datatype array_of_datatypes[]) MPICH_API_PUBLIC;
 int MPI_Type_get_envelope(MPI_Datatype datatype, int *num_integers, int *num_addresses,
-                          int *num_datatypes, int *combiner);
-int MPI_Type_get_name(MPI_Datatype datatype, char *type_name, int *resultlen);
-int MPI_Type_set_attr(MPI_Datatype datatype, int type_keyval, void *attribute_val);
-int MPI_Type_set_name(MPI_Datatype datatype, const char *type_name);
-int MPI_Type_match_size(int typeclass, int size, MPI_Datatype *datatype);
-int MPI_Win_call_errhandler(MPI_Win win, int errorcode);
+                          int *num_datatypes, int *combiner) MPICH_API_PUBLIC;
+int MPI_Type_get_name(MPI_Datatype datatype, char *type_name, int *resultlen) MPICH_API_PUBLIC;
+int MPI_Type_set_attr(MPI_Datatype datatype, int type_keyval, void *attribute_val) MPICH_API_PUBLIC;
+int MPI_Type_set_name(MPI_Datatype datatype, const char *type_name) MPICH_API_PUBLIC;
+int MPI_Type_match_size(int typeclass, int size, MPI_Datatype *datatype) MPICH_API_PUBLIC;
+int MPI_Win_call_errhandler(MPI_Win win, int errorcode) MPICH_API_PUBLIC;
 int MPI_Win_create_keyval(MPI_Win_copy_attr_function *win_copy_attr_fn,
                           MPI_Win_delete_attr_function *win_delete_attr_fn, int *win_keyval,
-                          void *extra_state);
-int MPI_Win_delete_attr(MPI_Win win, int win_keyval);
-int MPI_Win_free_keyval(int *win_keyval);
-int MPI_Win_get_attr(MPI_Win win, int win_keyval, void *attribute_val, int *flag);
-int MPI_Win_get_name(MPI_Win win, char *win_name, int *resultlen);
-int MPI_Win_set_attr(MPI_Win win, int win_keyval, void *attribute_val);
-int MPI_Win_set_name(MPI_Win win, const char *win_name);
+                          void *extra_state) MPICH_API_PUBLIC;
+int MPI_Win_delete_attr(MPI_Win win, int win_keyval) MPICH_API_PUBLIC;
+int MPI_Win_free_keyval(int *win_keyval) MPICH_API_PUBLIC;
+int MPI_Win_get_attr(MPI_Win win, int win_keyval, void *attribute_val, int *flag) MPICH_API_PUBLIC;
+int MPI_Win_get_name(MPI_Win win, char *win_name, int *resultlen) MPICH_API_PUBLIC;
+int MPI_Win_set_attr(MPI_Win win, int win_keyval, void *attribute_val) MPICH_API_PUBLIC;
+int MPI_Win_set_name(MPI_Win win, const char *win_name) MPICH_API_PUBLIC;
 
-int MPI_Alloc_mem(MPI_Aint size, MPI_Info info, void *baseptr);
+int MPI_Alloc_mem(MPI_Aint size, MPI_Info info, void *baseptr) MPICH_API_PUBLIC;
 int MPI_Comm_create_errhandler(MPI_Comm_errhandler_function *comm_errhandler_fn,
-                               MPI_Errhandler *errhandler);
-int MPI_Comm_get_errhandler(MPI_Comm comm, MPI_Errhandler *errhandler);
-int MPI_Comm_set_errhandler(MPI_Comm comm, MPI_Errhandler errhandler);
+                               MPI_Errhandler *errhandler) MPICH_API_PUBLIC;
+int MPI_Comm_get_errhandler(MPI_Comm comm, MPI_Errhandler *errhandler) MPICH_API_PUBLIC;
+int MPI_Comm_set_errhandler(MPI_Comm comm, MPI_Errhandler errhandler) MPICH_API_PUBLIC;
 int MPI_File_create_errhandler(MPI_File_errhandler_function *file_errhandler_fn,
-                               MPI_Errhandler *errhandler);
-int MPI_File_get_errhandler(MPI_File file, MPI_Errhandler *errhandler);
-int MPI_File_set_errhandler(MPI_File file, MPI_Errhandler errhandler);
-int MPI_Finalized(int *flag);
-int MPI_Free_mem(void *base);
-int MPI_Get_address(const void *location, MPI_Aint *address);
-int MPI_Info_create(MPI_Info *info);
-int MPI_Info_delete(MPI_Info info, const char *key);
-int MPI_Info_dup(MPI_Info info, MPI_Info *newinfo);
-int MPI_Info_free(MPI_Info *info);
-int MPI_Info_get(MPI_Info info, const char *key, int valuelen, char *value, int *flag);
-int MPI_Info_get_nkeys(MPI_Info info, int *nkeys);
-int MPI_Info_get_nthkey(MPI_Info info, int n, char *key);
-int MPI_Info_get_valuelen(MPI_Info info, const char *key, int *valuelen, int *flag);
-int MPI_Info_set(MPI_Info info, const char *key, const char *value);
+                               MPI_Errhandler *errhandler) MPICH_API_PUBLIC;
+int MPI_File_get_errhandler(MPI_File file, MPI_Errhandler *errhandler) MPICH_API_PUBLIC;
+int MPI_File_set_errhandler(MPI_File file, MPI_Errhandler errhandler) MPICH_API_PUBLIC;
+int MPI_Finalized(int *flag) MPICH_API_PUBLIC;
+int MPI_Free_mem(void *base) MPICH_API_PUBLIC;
+int MPI_Get_address(const void *location, MPI_Aint *address) MPICH_API_PUBLIC;
+int MPI_Info_create(MPI_Info *info) MPICH_API_PUBLIC;
+int MPI_Info_delete(MPI_Info info, const char *key) MPICH_API_PUBLIC;
+int MPI_Info_dup(MPI_Info info, MPI_Info *newinfo) MPICH_API_PUBLIC;
+int MPI_Info_free(MPI_Info *info) MPICH_API_PUBLIC;
+int MPI_Info_get(MPI_Info info, const char *key, int valuelen, char *value, int *flag) MPICH_API_PUBLIC;
+int MPI_Info_get_nkeys(MPI_Info info, int *nkeys) MPICH_API_PUBLIC;
+int MPI_Info_get_nthkey(MPI_Info info, int n, char *key) MPICH_API_PUBLIC;
+int MPI_Info_get_valuelen(MPI_Info info, const char *key, int *valuelen, int *flag) MPICH_API_PUBLIC;
+int MPI_Info_set(MPI_Info info, const char *key, const char *value) MPICH_API_PUBLIC;
 int MPI_Pack_external(const char datarep[], const void *inbuf, int incount,
                       MPI_Datatype datatype, void *outbuf, MPI_Aint outsize, MPI_Aint *position)
-                      MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                      MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) MPICH_API_PUBLIC;
 int MPI_Pack_external_size(const char datarep[], int incount, MPI_Datatype datatype,
-                           MPI_Aint *size);
-int MPI_Request_get_status(MPI_Request request, int *flag, MPI_Status *status);
-int MPI_Status_c2f(const MPI_Status *c_status, MPI_Fint *f_status);
-int MPI_Status_f2c(const MPI_Fint *f_status, MPI_Status *c_status);
+                           MPI_Aint *size) MPICH_API_PUBLIC;
+int MPI_Request_get_status(MPI_Request request, int *flag, MPI_Status *status) MPICH_API_PUBLIC;
+int MPI_Status_c2f(const MPI_Status *c_status, MPI_Fint *f_status) MPICH_API_PUBLIC;
+int MPI_Status_f2c(const MPI_Fint *f_status, MPI_Status *c_status) MPICH_API_PUBLIC;
 int MPI_Type_create_darray(int size, int rank, int ndims, const int array_of_gsizes[],
                            const int array_of_distribs[], const int array_of_dargs[],
                            const int array_of_psizes[], int order, MPI_Datatype oldtype,
-                           MPI_Datatype *newtype);
+                           MPI_Datatype *newtype) MPICH_API_PUBLIC;
 int MPI_Type_create_hindexed(int count, const int array_of_blocklengths[],
                              const MPI_Aint array_of_displacements[], MPI_Datatype oldtype,
-                             MPI_Datatype *newtype);
+                             MPI_Datatype *newtype) MPICH_API_PUBLIC;
 int MPI_Type_create_hvector(int count, int blocklength, MPI_Aint stride, MPI_Datatype oldtype,
-                            MPI_Datatype *newtype);
+                            MPI_Datatype *newtype) MPICH_API_PUBLIC;
 int MPI_Type_create_indexed_block(int count, int blocklength, const int array_of_displacements[],
-                                  MPI_Datatype oldtype, MPI_Datatype *newtype);
+                                  MPI_Datatype oldtype, MPI_Datatype *newtype) MPICH_API_PUBLIC;
 int MPI_Type_create_hindexed_block(int count, int blocklength,
                                    const MPI_Aint array_of_displacements[],
-                                   MPI_Datatype oldtype, MPI_Datatype *newtype);
+                                   MPI_Datatype oldtype, MPI_Datatype *newtype) MPICH_API_PUBLIC;
 int MPI_Type_create_resized(MPI_Datatype oldtype, MPI_Aint lb, MPI_Aint extent,
-                            MPI_Datatype *newtype);
+                            MPI_Datatype *newtype) MPICH_API_PUBLIC;
 int MPI_Type_create_struct(int count, const int array_of_blocklengths[],
                            const MPI_Aint array_of_displacements[],
-                           const MPI_Datatype array_of_types[], MPI_Datatype *newtype);
+                           const MPI_Datatype array_of_types[], MPI_Datatype *newtype) MPICH_API_PUBLIC;
 int MPI_Type_create_subarray(int ndims, const int array_of_sizes[],
                              const int array_of_subsizes[], const int array_of_starts[],
-                             int order, MPI_Datatype oldtype, MPI_Datatype *newtype);
-int MPI_Type_get_extent(MPI_Datatype datatype, MPI_Aint *lb, MPI_Aint *extent);
-int MPI_Type_get_true_extent(MPI_Datatype datatype, MPI_Aint *true_lb, MPI_Aint *true_extent);
+                             int order, MPI_Datatype oldtype, MPI_Datatype *newtype) MPICH_API_PUBLIC;
+int MPI_Type_get_extent(MPI_Datatype datatype, MPI_Aint *lb, MPI_Aint *extent) MPICH_API_PUBLIC;
+int MPI_Type_get_true_extent(MPI_Datatype datatype, MPI_Aint *true_lb, MPI_Aint *true_extent) MPICH_API_PUBLIC;
 int MPI_Unpack_external(const char datarep[], const void *inbuf, MPI_Aint insize,
                         MPI_Aint *position, void *outbuf, int outcount, MPI_Datatype datatype)
-                        MPICH_ATTR_POINTER_WITH_TYPE_TAG(5,7);
+                        MPICH_ATTR_POINTER_WITH_TYPE_TAG(5,7) MPICH_API_PUBLIC;
 int MPI_Win_create_errhandler(MPI_Win_errhandler_function *win_errhandler_fn,
-                              MPI_Errhandler *errhandler);
-int MPI_Win_get_errhandler(MPI_Win win, MPI_Errhandler *errhandler);
-int MPI_Win_set_errhandler(MPI_Win win, MPI_Errhandler errhandler);
+                              MPI_Errhandler *errhandler) MPICH_API_PUBLIC;
+int MPI_Win_get_errhandler(MPI_Win win, MPI_Errhandler *errhandler) MPICH_API_PUBLIC;
+int MPI_Win_set_errhandler(MPI_Win win, MPI_Errhandler errhandler) MPICH_API_PUBLIC;
 
 /* Fortran 90-related functions.  These routines are available only if
    Fortran 90 support is enabled 
 */
-int MPI_Type_create_f90_integer(int range, MPI_Datatype *newtype);
-int MPI_Type_create_f90_real(int precision, int range, MPI_Datatype *newtype);
-int MPI_Type_create_f90_complex(int precision, int range, MPI_Datatype *newtype);
+int MPI_Type_create_f90_integer(int range, MPI_Datatype *newtype) MPICH_API_PUBLIC;
+int MPI_Type_create_f90_real(int precision, int range, MPI_Datatype *newtype) MPICH_API_PUBLIC;
+int MPI_Type_create_f90_complex(int precision, int range, MPI_Datatype *newtype) MPICH_API_PUBLIC;
 
 int MPI_Reduce_local(const void *inbuf, void *inoutbuf, int count, MPI_Datatype datatype,
                      MPI_Op op)
-                     MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
-int MPI_Op_commutative(MPI_Op op, int *commute);
+                     MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) MPICH_API_PUBLIC;
+int MPI_Op_commutative(MPI_Op op, int *commute) MPICH_API_PUBLIC;
 int MPI_Reduce_scatter_block(const void *sendbuf, void *recvbuf, int recvcount,
                              MPI_Datatype datatype, MPI_Op op, MPI_Comm comm)
                              MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4)
-                             MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                             MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) MPICH_API_PUBLIC;
 int MPI_Dist_graph_create_adjacent(MPI_Comm comm_old, int indegree, const int sources[],
                                    const int sourceweights[], int outdegree,
                                    const int destinations[], const int destweights[],
-                                   MPI_Info info, int reorder, MPI_Comm *comm_dist_graph);
+                                   MPI_Info info, int reorder, MPI_Comm *comm_dist_graph) MPICH_API_PUBLIC;
 int MPI_Dist_graph_create(MPI_Comm comm_old, int n, const int sources[], const int degrees[],
                           const int destinations[], const int weights[], MPI_Info info,
-                          int reorder, MPI_Comm *comm_dist_graph);
-int MPI_Dist_graph_neighbors_count(MPI_Comm comm, int *indegree, int *outdegree, int *weighted);
+                          int reorder, MPI_Comm *comm_dist_graph) MPICH_API_PUBLIC;
+int MPI_Dist_graph_neighbors_count(MPI_Comm comm, int *indegree, int *outdegree, int *weighted) MPICH_API_PUBLIC;
 int MPI_Dist_graph_neighbors(MPI_Comm comm, int maxindegree, int sources[], int sourceweights[],
-                             int maxoutdegree, int destinations[], int destweights[]);
+                             int maxoutdegree, int destinations[], int destweights[]) MPICH_API_PUBLIC;
 
 /* Matched probe functionality */
 int MPI_Improbe(int source, int tag, MPI_Comm comm, int *flag, MPI_Message *message,
-                MPI_Status *status);
+                MPI_Status *status) MPICH_API_PUBLIC;
 int MPI_Imrecv(void *buf, int count, MPI_Datatype datatype, MPI_Message *message,
-               MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
-int MPI_Mprobe(int source, int tag, MPI_Comm comm, MPI_Message *message, MPI_Status *status);
+               MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
+int MPI_Mprobe(int source, int tag, MPI_Comm comm, MPI_Message *message, MPI_Status *status) MPICH_API_PUBLIC;
 int MPI_Mrecv(void *buf, int count, MPI_Datatype datatype, MPI_Message *message,
-              MPI_Status *status) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+              MPI_Status *status) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 
 /* Nonblocking collectives */
-int MPI_Comm_idup(MPI_Comm comm, MPI_Comm *newcomm, MPI_Request *request);
-int MPI_Ibarrier(MPI_Comm comm, MPI_Request *request);
+int MPI_Comm_idup(MPI_Comm comm, MPI_Comm *newcomm, MPI_Request *request) MPICH_API_PUBLIC;
+int MPI_Ibarrier(MPI_Comm comm, MPI_Request *request) MPICH_API_PUBLIC;
 int MPI_Ibcast(void *buffer, int count, MPI_Datatype datatype, int root, MPI_Comm comm,
-               MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+               MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int MPI_Igather(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
                 int recvcount, MPI_Datatype recvtype, int root, MPI_Comm comm,
                 MPI_Request *request)
-                MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6);
+                MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6) MPICH_API_PUBLIC;
 int MPI_Igatherv(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
                  const int recvcounts[], const int displs[], MPI_Datatype recvtype, int root,
                  MPI_Comm comm, MPI_Request *request)
-                 MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,7);
+                 MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,7) MPICH_API_PUBLIC;
 int MPI_Iscatter(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
                  int recvcount, MPI_Datatype recvtype, int root, MPI_Comm comm,
                  MPI_Request *request)
-                 MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6);
+                 MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6) MPICH_API_PUBLIC;
 int MPI_Iscatterv(const void *sendbuf, const int sendcounts[], const int displs[],
                   MPI_Datatype sendtype, void *recvbuf, int recvcount, MPI_Datatype recvtype,
                   int root, MPI_Comm comm, MPI_Request *request)
-                  MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(5,7);
+                  MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(5,7) MPICH_API_PUBLIC;
 int MPI_Iallgather(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
                    int recvcount, MPI_Datatype recvtype, MPI_Comm comm, MPI_Request *request)
-                   MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6);
+                   MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6) MPICH_API_PUBLIC;
 int MPI_Iallgatherv(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
                     const int recvcounts[], const int displs[], MPI_Datatype recvtype,
                     MPI_Comm comm, MPI_Request *request)
-                    MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,7);
+                    MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,7) MPICH_API_PUBLIC;
 int MPI_Ialltoall(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
                   int recvcount, MPI_Datatype recvtype, MPI_Comm comm, MPI_Request *request)
-                  MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6);
+                  MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6) MPICH_API_PUBLIC;
 int MPI_Ialltoallv(const void *sendbuf, const int sendcounts[], const int sdispls[],
                    MPI_Datatype sendtype, void *recvbuf, const int recvcounts[],
                    const int rdispls[], MPI_Datatype recvtype, MPI_Comm comm,
                    MPI_Request *request)
-                   MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(5,8);
+                   MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(5,8) MPICH_API_PUBLIC;
 int MPI_Ialltoallw(const void *sendbuf, const int sendcounts[], const int sdispls[],
                    const MPI_Datatype sendtypes[], void *recvbuf, const int recvcounts[],
                    const int rdispls[], const MPI_Datatype recvtypes[], MPI_Comm comm,
-                   MPI_Request *request);
+                   MPI_Request *request) MPICH_API_PUBLIC;
 int MPI_Ireduce(const void *sendbuf, void *recvbuf, int count, MPI_Datatype datatype,
                 MPI_Op op, int root, MPI_Comm comm, MPI_Request *request)
-                MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) MPICH_API_PUBLIC;
 int MPI_Iallreduce(const void *sendbuf, void *recvbuf, int count, MPI_Datatype datatype,
                    MPI_Op op, MPI_Comm comm, MPI_Request *request)
-                   MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                   MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) MPICH_API_PUBLIC;
 int MPI_Ireduce_scatter(const void *sendbuf, void *recvbuf, const int recvcounts[],
                         MPI_Datatype datatype, MPI_Op op, MPI_Comm comm, MPI_Request *request)
-                        MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                        MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) MPICH_API_PUBLIC;
 int MPI_Ireduce_scatter_block(const void *sendbuf, void *recvbuf, int recvcount,
                               MPI_Datatype datatype, MPI_Op op, MPI_Comm comm,
                               MPI_Request *request)
                               MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4)
-                              MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                              MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) MPICH_API_PUBLIC;
 int MPI_Iscan(const void *sendbuf, void *recvbuf, int count, MPI_Datatype datatype, MPI_Op op,
               MPI_Comm comm, MPI_Request *request)
-              MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+              MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) MPICH_API_PUBLIC;
 int MPI_Iexscan(const void *sendbuf, void *recvbuf, int count, MPI_Datatype datatype,
                 MPI_Op op, MPI_Comm comm, MPI_Request *request)
-                MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) MPICH_API_PUBLIC;
 
 /* Neighborhood collectives */
 int MPI_Ineighbor_allgather(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
                             void *recvbuf, int recvcount, MPI_Datatype recvtype,
                             MPI_Comm comm, MPI_Request *request)
                             MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3)
-                            MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6);
+                            MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6) MPICH_API_PUBLIC;
 int MPI_Ineighbor_allgatherv(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
                              void *recvbuf, const int recvcounts[], const int displs[],
                              MPI_Datatype recvtype, MPI_Comm comm, MPI_Request *request)
                              MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3)
-                             MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,7);
+                             MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,7) MPICH_API_PUBLIC;
 int MPI_Ineighbor_alltoall(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
                            void *recvbuf, int recvcount, MPI_Datatype recvtype, MPI_Comm comm,
                            MPI_Request *request)
                            MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3)
-                           MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6);
+                           MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6) MPICH_API_PUBLIC;
 int MPI_Ineighbor_alltoallv(const void *sendbuf, const int sendcounts[], const int sdispls[],
                             MPI_Datatype sendtype, void *recvbuf, const int recvcounts[],
                             const int rdispls[], MPI_Datatype recvtype, MPI_Comm comm,
                             MPI_Request *request)
                             MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4)
-                            MPICH_ATTR_POINTER_WITH_TYPE_TAG(5,8);
+                            MPICH_ATTR_POINTER_WITH_TYPE_TAG(5,8) MPICH_API_PUBLIC;
 int MPI_Ineighbor_alltoallw(const void *sendbuf, const int sendcounts[],
                             const MPI_Aint sdispls[], const MPI_Datatype sendtypes[],
                             void *recvbuf, const int recvcounts[], const MPI_Aint rdispls[],
-                            const MPI_Datatype recvtypes[], MPI_Comm comm, MPI_Request *request);
+                            const MPI_Datatype recvtypes[], MPI_Comm comm, MPI_Request *request) MPICH_API_PUBLIC;
 int MPI_Neighbor_allgather(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
                            void *recvbuf, int recvcount, MPI_Datatype recvtype, MPI_Comm comm)
                            MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3)
-                           MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6);
+                           MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6) MPICH_API_PUBLIC;
 int MPI_Neighbor_allgatherv(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
                             void *recvbuf, const int recvcounts[], const int displs[],
                             MPI_Datatype recvtype, MPI_Comm comm)
                             MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3)
-                            MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,7);
+                            MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,7) MPICH_API_PUBLIC;
 int MPI_Neighbor_alltoall(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
                           void *recvbuf, int recvcount, MPI_Datatype recvtype, MPI_Comm comm)
                           MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3)
-                          MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6);
+                          MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6) MPICH_API_PUBLIC;
 int MPI_Neighbor_alltoallv(const void *sendbuf, const int sendcounts[], const int sdispls[],
                            MPI_Datatype sendtype, void *recvbuf, const int recvcounts[],
                            const int rdispls[], MPI_Datatype recvtype, MPI_Comm comm)
                            MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4)
-                           MPICH_ATTR_POINTER_WITH_TYPE_TAG(5,8);
+                           MPICH_ATTR_POINTER_WITH_TYPE_TAG(5,8) MPICH_API_PUBLIC;
 int MPI_Neighbor_alltoallw(const void *sendbuf, const int sendcounts[], const MPI_Aint sdispls[],
                            const MPI_Datatype sendtypes[], void *recvbuf, const int recvcounts[],
-                           const MPI_Aint rdispls[], const MPI_Datatype recvtypes[], MPI_Comm comm);
+                           const MPI_Aint rdispls[], const MPI_Datatype recvtypes[], MPI_Comm comm) MPICH_API_PUBLIC;
 
 /* Shared memory */
-int MPI_Comm_split_type(MPI_Comm comm, int split_type, int key, MPI_Info info, MPI_Comm *newcomm);
+int MPI_Comm_split_type(MPI_Comm comm, int split_type, int key, MPI_Info info, MPI_Comm *newcomm) MPICH_API_PUBLIC;
 
 /* MPI-3 "large count" routines */
-int MPI_Get_elements_x(const MPI_Status *status, MPI_Datatype datatype, MPI_Count *count);
-int MPI_Status_set_elements_x(MPI_Status *status, MPI_Datatype datatype, MPI_Count count);
-int MPI_Type_get_extent_x(MPI_Datatype datatype, MPI_Count *lb, MPI_Count *extent);
-int MPI_Type_get_true_extent_x(MPI_Datatype datatype, MPI_Count *lb, MPI_Count *extent);
-int MPI_Type_size_x(MPI_Datatype datatype, MPI_Count *size);
+int MPI_Get_elements_x(const MPI_Status *status, MPI_Datatype datatype, MPI_Count *count) MPICH_API_PUBLIC;
+int MPI_Status_set_elements_x(MPI_Status *status, MPI_Datatype datatype, MPI_Count count) MPICH_API_PUBLIC;
+int MPI_Type_get_extent_x(MPI_Datatype datatype, MPI_Count *lb, MPI_Count *extent) MPICH_API_PUBLIC;
+int MPI_Type_get_true_extent_x(MPI_Datatype datatype, MPI_Count *lb, MPI_Count *extent) MPICH_API_PUBLIC;
+int MPI_Type_size_x(MPI_Datatype datatype, MPI_Count *size) MPICH_API_PUBLIC;
 
 /* Noncollective communicator creation */
-int MPI_Comm_create_group(MPI_Comm comm, MPI_Group group, int tag, MPI_Comm *newcomm);
+int MPI_Comm_create_group(MPI_Comm comm, MPI_Group group, int tag, MPI_Comm *newcomm) MPICH_API_PUBLIC;
 
 /* MPI_Aint addressing arithmetic */
-MPI_Aint MPI_Aint_add(MPI_Aint base, MPI_Aint disp);
-MPI_Aint MPI_Aint_diff(MPI_Aint addr1, MPI_Aint addr2);
+MPI_Aint MPI_Aint_add(MPI_Aint base, MPI_Aint disp) MPICH_API_PUBLIC;
+MPI_Aint MPI_Aint_diff(MPI_Aint addr1, MPI_Aint addr2) MPICH_API_PUBLIC;
 
 /* MPI_T interface */
 /* The MPI_T routines are available only in C bindings - tell tools that they
    can skip these prototypes */
 /* Begin Skip Prototypes */
-int MPI_T_init_thread(int required, int *provided);
-int MPI_T_finalize(void);
-int MPI_T_enum_get_info(MPI_T_enum enumtype, int *num, char *name, int *name_len);
-int MPI_T_enum_get_item(MPI_T_enum enumtype, int indx, int *value, char *name, int *name_len);
-int MPI_T_cvar_get_num(int *num_cvar);
+int MPI_T_init_thread(int required, int *provided) MPICH_API_PUBLIC;
+int MPI_T_finalize(void) MPICH_API_PUBLIC;
+int MPI_T_enum_get_info(MPI_T_enum enumtype, int *num, char *name, int *name_len) MPICH_API_PUBLIC;
+int MPI_T_enum_get_item(MPI_T_enum enumtype, int indx, int *value, char *name, int *name_len) MPICH_API_PUBLIC;
+int MPI_T_cvar_get_num(int *num_cvar) MPICH_API_PUBLIC;
 int MPI_T_cvar_get_info(int cvar_index, char *name, int *name_len, int *verbosity,
                         MPI_Datatype *datatype, MPI_T_enum *enumtype, char *desc, int *desc_len,
-                        int *binding, int *scope);
+                        int *binding, int *scope) MPICH_API_PUBLIC;
 int MPI_T_cvar_handle_alloc(int cvar_index, void *obj_handle, MPI_T_cvar_handle *handle,
-                            int *count);
-int MPI_T_cvar_handle_free(MPI_T_cvar_handle *handle);
-int MPI_T_cvar_read(MPI_T_cvar_handle handle, void *buf);
-int MPI_T_cvar_write(MPI_T_cvar_handle handle, const void *buf);
-int MPI_T_pvar_get_num(int *num_pvar);
+                            int *count) MPICH_API_PUBLIC;
+int MPI_T_cvar_handle_free(MPI_T_cvar_handle *handle) MPICH_API_PUBLIC;
+int MPI_T_cvar_read(MPI_T_cvar_handle handle, void *buf) MPICH_API_PUBLIC;
+int MPI_T_cvar_write(MPI_T_cvar_handle handle, const void *buf) MPICH_API_PUBLIC;
+int MPI_T_pvar_get_num(int *num_pvar) MPICH_API_PUBLIC;
 int MPI_T_pvar_get_info(int pvar_index, char *name, int *name_len, int *verbosity, int *var_class,
                         MPI_Datatype *datatype, MPI_T_enum *enumtype, char *desc, int *desc_len,
-                        int *binding, int *readonly, int *continuous, int *atomic);
-int MPI_T_pvar_session_create(MPI_T_pvar_session *session);
-int MPI_T_pvar_session_free(MPI_T_pvar_session *session);
+                        int *binding, int *readonly, int *continuous, int *atomic) MPICH_API_PUBLIC;
+int MPI_T_pvar_session_create(MPI_T_pvar_session *session) MPICH_API_PUBLIC;
+int MPI_T_pvar_session_free(MPI_T_pvar_session *session) MPICH_API_PUBLIC;
 int MPI_T_pvar_handle_alloc(MPI_T_pvar_session session, int pvar_index, void *obj_handle,
-                            MPI_T_pvar_handle *handle, int *count);
-int MPI_T_pvar_handle_free(MPI_T_pvar_session session, MPI_T_pvar_handle *handle);
-int MPI_T_pvar_start(MPI_T_pvar_session session, MPI_T_pvar_handle handle);
-int MPI_T_pvar_stop(MPI_T_pvar_session session, MPI_T_pvar_handle handle);
-int MPI_T_pvar_read(MPI_T_pvar_session session, MPI_T_pvar_handle handle, void *buf);
-int MPI_T_pvar_write(MPI_T_pvar_session session, MPI_T_pvar_handle handle, const void *buf);
-int MPI_T_pvar_reset(MPI_T_pvar_session session, MPI_T_pvar_handle handle);
-int MPI_T_pvar_readreset(MPI_T_pvar_session session, MPI_T_pvar_handle handle, void *buf);
-int MPI_T_category_get_num(int *num_cat);
+                            MPI_T_pvar_handle *handle, int *count) MPICH_API_PUBLIC;
+int MPI_T_pvar_handle_free(MPI_T_pvar_session session, MPI_T_pvar_handle *handle) MPICH_API_PUBLIC;
+int MPI_T_pvar_start(MPI_T_pvar_session session, MPI_T_pvar_handle handle) MPICH_API_PUBLIC;
+int MPI_T_pvar_stop(MPI_T_pvar_session session, MPI_T_pvar_handle handle) MPICH_API_PUBLIC;
+int MPI_T_pvar_read(MPI_T_pvar_session session, MPI_T_pvar_handle handle, void *buf) MPICH_API_PUBLIC;
+int MPI_T_pvar_write(MPI_T_pvar_session session, MPI_T_pvar_handle handle, const void *buf) MPICH_API_PUBLIC;
+int MPI_T_pvar_reset(MPI_T_pvar_session session, MPI_T_pvar_handle handle) MPICH_API_PUBLIC;
+int MPI_T_pvar_readreset(MPI_T_pvar_session session, MPI_T_pvar_handle handle, void *buf) MPICH_API_PUBLIC;
+int MPI_T_category_get_num(int *num_cat) MPICH_API_PUBLIC;
 int MPI_T_category_get_info(int cat_index, char *name, int *name_len, char *desc, int *desc_len,
-                            int *num_cvars, int *num_pvars, int *num_categories);
-int MPI_T_category_get_cvars(int cat_index, int len, int indices[]);
-int MPI_T_category_get_pvars(int cat_index, int len, int indices[]);
-int MPI_T_category_get_categories(int cat_index, int len, int indices[]);
-int MPI_T_category_changed(int *stamp);
-int MPI_T_cvar_get_index(const char *name, int *cvar_index);
-int MPI_T_pvar_get_index(const char *name, int var_class, int *pvar_index);
-int MPI_T_category_get_index(const char *name, int *cat_index);
+                            int *num_cvars, int *num_pvars, int *num_categories) MPICH_API_PUBLIC;
+int MPI_T_category_get_cvars(int cat_index, int len, int indices[]) MPICH_API_PUBLIC;
+int MPI_T_category_get_pvars(int cat_index, int len, int indices[]) MPICH_API_PUBLIC;
+int MPI_T_category_get_categories(int cat_index, int len, int indices[]) MPICH_API_PUBLIC;
+int MPI_T_category_changed(int *stamp) MPICH_API_PUBLIC;
+int MPI_T_cvar_get_index(const char *name, int *cvar_index) MPICH_API_PUBLIC;
+int MPI_T_pvar_get_index(const char *name, int var_class, int *pvar_index) MPICH_API_PUBLIC;
+int MPI_T_category_get_index(const char *name, int *cat_index) MPICH_API_PUBLIC;
 /* End Skip Prototypes */
 
 
 /* Non-standard but public extensions to MPI */
 /* Fault Tolerance Extensions */
-int MPIX_Comm_failure_ack(MPI_Comm comm);
-int MPIX_Comm_failure_get_acked(MPI_Comm comm, MPI_Group *failedgrp);
-int MPIX_Comm_revoke(MPI_Comm comm);
-int MPIX_Comm_shrink(MPI_Comm comm, MPI_Comm *newcomm);
-int MPIX_Comm_agree(MPI_Comm comm, int *flag);
+int MPIX_Comm_failure_ack(MPI_Comm comm) MPICH_API_PUBLIC;
+int MPIX_Comm_failure_get_acked(MPI_Comm comm, MPI_Group *failedgrp) MPICH_API_PUBLIC;
+int MPIX_Comm_revoke(MPI_Comm comm) MPICH_API_PUBLIC;
+int MPIX_Comm_shrink(MPI_Comm comm, MPI_Comm *newcomm) MPICH_API_PUBLIC;
+int MPIX_Comm_agree(MPI_Comm comm, int *flag) MPICH_API_PUBLIC;
 
 
 /* End Prototypes */
@@ -1559,643 +1569,643 @@ int MPIX_Comm_agree(MPI_Comm comm, int *flag);
 /* Here are the bindings of the profiling routines */
 #if !defined(MPI_BUILD_PROFILING)
 int PMPI_Send(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-              MPI_Comm comm) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+              MPI_Comm comm) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int PMPI_Recv(void *buf, int count, MPI_Datatype datatype, int source, int tag,
-              MPI_Comm comm, MPI_Status *status) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
-int PMPI_Get_count(const MPI_Status *status, MPI_Datatype datatype, int *count);
+              MPI_Comm comm, MPI_Status *status) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
+int PMPI_Get_count(const MPI_Status *status, MPI_Datatype datatype, int *count) MPICH_API_PUBLIC;
 int PMPI_Bsend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-               MPI_Comm comm) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+               MPI_Comm comm) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int PMPI_Ssend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-               MPI_Comm comm) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+               MPI_Comm comm) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int PMPI_Rsend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-               MPI_Comm comm) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
-int PMPI_Buffer_attach(void *buffer, int size);
-int PMPI_Buffer_detach(void *buffer_addr, int *size);
+               MPI_Comm comm) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
+int PMPI_Buffer_attach(void *buffer, int size) MPICH_API_PUBLIC;
+int PMPI_Buffer_detach(void *buffer_addr, int *size) MPICH_API_PUBLIC;
 int PMPI_Isend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-               MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+               MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int PMPI_Ibsend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-                MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+                MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int PMPI_Issend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-                MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+                MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int PMPI_Irsend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-                MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+                MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int PMPI_Irecv(void *buf, int count, MPI_Datatype datatype, int source, int tag,
-               MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
-int PMPI_Wait(MPI_Request *request, MPI_Status *status);
-int PMPI_Test(MPI_Request *request, int *flag, MPI_Status *status);
-int PMPI_Request_free(MPI_Request *request);
-int PMPI_Waitany(int count, MPI_Request array_of_requests[], int *indx, MPI_Status *status);
+               MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
+int PMPI_Wait(MPI_Request *request, MPI_Status *status) MPICH_API_PUBLIC;
+int PMPI_Test(MPI_Request *request, int *flag, MPI_Status *status) MPICH_API_PUBLIC;
+int PMPI_Request_free(MPI_Request *request) MPICH_API_PUBLIC;
+int PMPI_Waitany(int count, MPI_Request array_of_requests[], int *indx, MPI_Status *status) MPICH_API_PUBLIC;
 int PMPI_Testany(int count, MPI_Request array_of_requests[], int *indx, int *flag,
-                 MPI_Status *status);
-int PMPI_Waitall(int count, MPI_Request array_of_requests[], MPI_Status array_of_statuses[]);
+                 MPI_Status *status) MPICH_API_PUBLIC;
+int PMPI_Waitall(int count, MPI_Request array_of_requests[], MPI_Status array_of_statuses[]) MPICH_API_PUBLIC;
 int PMPI_Testall(int count, MPI_Request array_of_requests[], int *flag,
-                 MPI_Status array_of_statuses[]);
+                 MPI_Status array_of_statuses[]) MPICH_API_PUBLIC;
 int PMPI_Waitsome(int incount, MPI_Request array_of_requests[], int *outcount,
-                  int array_of_indices[], MPI_Status array_of_statuses[]);
+                  int array_of_indices[], MPI_Status array_of_statuses[]) MPICH_API_PUBLIC;
 int PMPI_Testsome(int incount, MPI_Request array_of_requests[], int *outcount,
-                  int array_of_indices[], MPI_Status array_of_statuses[]);
-int PMPI_Iprobe(int source, int tag, MPI_Comm comm, int *flag, MPI_Status *status);
-int PMPI_Probe(int source, int tag, MPI_Comm comm, MPI_Status *status);
-int PMPI_Cancel(MPI_Request *request);
-int PMPI_Test_cancelled(const MPI_Status *status, int *flag);
+                  int array_of_indices[], MPI_Status array_of_statuses[]) MPICH_API_PUBLIC;
+int PMPI_Iprobe(int source, int tag, MPI_Comm comm, int *flag, MPI_Status *status) MPICH_API_PUBLIC;
+int PMPI_Probe(int source, int tag, MPI_Comm comm, MPI_Status *status) MPICH_API_PUBLIC;
+int PMPI_Cancel(MPI_Request *request) MPICH_API_PUBLIC;
+int PMPI_Test_cancelled(const MPI_Status *status, int *flag) MPICH_API_PUBLIC;
 int PMPI_Send_init(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-                   MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+                   MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int PMPI_Bsend_init(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-                    MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+                    MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int PMPI_Ssend_init(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-                    MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+                    MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int PMPI_Rsend_init(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-                    MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+                    MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int PMPI_Recv_init(void *buf, int count, MPI_Datatype datatype, int source, int tag,
-                   MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
-int PMPI_Start(MPI_Request *request);
-int PMPI_Startall(int count, MPI_Request array_of_requests[]);
+                   MPI_Comm comm, MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
+int PMPI_Start(MPI_Request *request) MPICH_API_PUBLIC;
+int PMPI_Startall(int count, MPI_Request array_of_requests[]) MPICH_API_PUBLIC;
 int PMPI_Sendrecv(const void *sendbuf, int sendcount, MPI_Datatype sendtype, int dest,
                   int sendtag, void *recvbuf, int recvcount, MPI_Datatype recvtype,
                   int source, int recvtag, MPI_Comm comm, MPI_Status *status)
                   MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3)
-                  MPICH_ATTR_POINTER_WITH_TYPE_TAG(6,8);
+                  MPICH_ATTR_POINTER_WITH_TYPE_TAG(6,8) MPICH_API_PUBLIC;
 int PMPI_Sendrecv_replace(void *buf, int count, MPI_Datatype datatype, int dest,
                           int sendtag, int source, int recvtag, MPI_Comm comm,
-                          MPI_Status *status) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
-int PMPI_Type_contiguous(int count, MPI_Datatype oldtype, MPI_Datatype *newtype);
+                          MPI_Status *status) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
+int PMPI_Type_contiguous(int count, MPI_Datatype oldtype, MPI_Datatype *newtype) MPICH_API_PUBLIC;
 int PMPI_Type_vector(int count, int blocklength, int stride, MPI_Datatype oldtype,
-                     MPI_Datatype *newtype);
+                     MPI_Datatype *newtype) MPICH_API_PUBLIC;
 int PMPI_Type_hvector(int count, int blocklength, MPI_Aint stride, MPI_Datatype oldtype,
-                      MPI_Datatype *newtype);
+                      MPI_Datatype *newtype) MPICH_API_PUBLIC;
 int PMPI_Type_indexed(int count, const int *array_of_blocklengths,
                       const int *array_of_displacements, MPI_Datatype oldtype,
-                      MPI_Datatype *newtype);
+                      MPI_Datatype *newtype) MPICH_API_PUBLIC;
 int PMPI_Type_hindexed(int count, int *array_of_blocklengths,
                        MPI_Aint *array_of_displacements, MPI_Datatype oldtype,
-                       MPI_Datatype *newtype);
+                       MPI_Datatype *newtype) MPICH_API_PUBLIC;
 int PMPI_Type_struct(int count, int *array_of_blocklengths,
                      MPI_Aint *array_of_displacements,
-                     MPI_Datatype *array_of_types, MPI_Datatype *newtype);
-int PMPI_Address(void *location, MPI_Aint *address);
-int PMPI_Type_extent(MPI_Datatype datatype, MPI_Aint *extent);
-int PMPI_Type_size(MPI_Datatype datatype, int *size);
-int PMPI_Type_lb(MPI_Datatype datatype, MPI_Aint *displacement);
-int PMPI_Type_ub(MPI_Datatype datatype, MPI_Aint *displacement);
-int PMPI_Type_commit(MPI_Datatype *datatype);
-int PMPI_Type_free(MPI_Datatype *datatype);
-int PMPI_Get_elements(const MPI_Status *status, MPI_Datatype datatype, int *count);
+                     MPI_Datatype *array_of_types, MPI_Datatype *newtype) MPICH_API_PUBLIC;
+int PMPI_Address(void *location, MPI_Aint *address) MPICH_API_PUBLIC;
+int PMPI_Type_extent(MPI_Datatype datatype, MPI_Aint *extent) MPICH_API_PUBLIC;
+int PMPI_Type_size(MPI_Datatype datatype, int *size) MPICH_API_PUBLIC;
+int PMPI_Type_lb(MPI_Datatype datatype, MPI_Aint *displacement) MPICH_API_PUBLIC;
+int PMPI_Type_ub(MPI_Datatype datatype, MPI_Aint *displacement) MPICH_API_PUBLIC;
+int PMPI_Type_commit(MPI_Datatype *datatype) MPICH_API_PUBLIC;
+int PMPI_Type_free(MPI_Datatype *datatype) MPICH_API_PUBLIC;
+int PMPI_Get_elements(const MPI_Status *status, MPI_Datatype datatype, int *count) MPICH_API_PUBLIC;
 int PMPI_Pack(const void *inbuf, int incount, MPI_Datatype datatype, void *outbuf,
-              int outsize, int *position, MPI_Comm comm) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+              int outsize, int *position, MPI_Comm comm) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int PMPI_Unpack(const void *inbuf, int insize, int *position, void *outbuf, int outcount,
-                MPI_Datatype datatype, MPI_Comm comm) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6);
-int PMPI_Pack_size(int incount, MPI_Datatype datatype, MPI_Comm comm, int *size);
-int PMPI_Barrier(MPI_Comm comm);
+                MPI_Datatype datatype, MPI_Comm comm) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6) MPICH_API_PUBLIC;
+int PMPI_Pack_size(int incount, MPI_Datatype datatype, MPI_Comm comm, int *size) MPICH_API_PUBLIC;
+int PMPI_Barrier(MPI_Comm comm) MPICH_API_PUBLIC;
 int PMPI_Bcast(void *buffer, int count, MPI_Datatype datatype, int root, MPI_Comm comm)
-               MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+               MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int PMPI_Gather(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
                 int recvcount, MPI_Datatype recvtype, int root, MPI_Comm comm)
-                MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6);
+                MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6) MPICH_API_PUBLIC;
 int PMPI_Gatherv(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
                  const int *recvcounts, const int *displs, MPI_Datatype recvtype, int root,
                  MPI_Comm comm)
-                 MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,7);
+                 MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,7) MPICH_API_PUBLIC;
 int PMPI_Scatter(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
                  int recvcount, MPI_Datatype recvtype, int root, MPI_Comm comm)
-                 MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6);
+                 MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6) MPICH_API_PUBLIC;
 int PMPI_Scatterv(const void *sendbuf, const int *sendcounts, const int *displs,
                   MPI_Datatype sendtype, void *recvbuf, int recvcount, MPI_Datatype recvtype,
                   int root, MPI_Comm comm)
-                  MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(5,7);
+                  MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(5,7) MPICH_API_PUBLIC;
 int PMPI_Allgather(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
                    int recvcount, MPI_Datatype recvtype, MPI_Comm comm)
-                   MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6);
+                   MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6) MPICH_API_PUBLIC;
 int PMPI_Allgatherv(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
                     const int *recvcounts, const int *displs, MPI_Datatype recvtype, MPI_Comm comm)
-                    MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,7);
+                    MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,7) MPICH_API_PUBLIC;
 int PMPI_Alltoall(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
                   int recvcount, MPI_Datatype recvtype, MPI_Comm comm)
-                  MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6);
+                  MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6) MPICH_API_PUBLIC;
 int PMPI_Alltoallv(const void *sendbuf, const int *sendcounts, const int *sdispls,
                    MPI_Datatype sendtype, void *recvbuf, const int *recvcounts,
                    const int *rdispls, MPI_Datatype recvtype, MPI_Comm comm)
-                   MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(5,8);
+                   MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(5,8) MPICH_API_PUBLIC;
 int PMPI_Alltoallw(const void *sendbuf, const int sendcounts[], const int sdispls[],
                    const MPI_Datatype sendtypes[], void *recvbuf, const int recvcounts[],
-                   const int rdispls[], const MPI_Datatype recvtypes[], MPI_Comm comm);
+                   const int rdispls[], const MPI_Datatype recvtypes[], MPI_Comm comm) MPICH_API_PUBLIC;
 int PMPI_Exscan(const void *sendbuf, void *recvbuf, int count, MPI_Datatype datatype,
                 MPI_Op op, MPI_Comm comm)
-                MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) MPICH_API_PUBLIC;
 int PMPI_Reduce(const void *sendbuf, void *recvbuf, int count, MPI_Datatype datatype,
                 MPI_Op op, int root, MPI_Comm comm)
-                MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
-int PMPI_Op_create(MPI_User_function *user_fn, int commute, MPI_Op *op);
-int PMPI_Op_free(MPI_Op *op);
+                MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) MPICH_API_PUBLIC;
+int PMPI_Op_create(MPI_User_function *user_fn, int commute, MPI_Op *op) MPICH_API_PUBLIC;
+int PMPI_Op_free(MPI_Op *op) MPICH_API_PUBLIC;
 int PMPI_Allreduce(const void *sendbuf, void *recvbuf, int count, MPI_Datatype datatype,
                    MPI_Op op, MPI_Comm comm)
-                   MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                   MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) MPICH_API_PUBLIC;
 int PMPI_Reduce_scatter(const void *sendbuf, void *recvbuf, const int recvcounts[],
                         MPI_Datatype datatype, MPI_Op op, MPI_Comm comm)
-                        MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                        MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) MPICH_API_PUBLIC;
 int PMPI_Scan(const void *sendbuf, void *recvbuf, int count, MPI_Datatype datatype, MPI_Op op,
               MPI_Comm comm)
-              MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
-int PMPI_Group_size(MPI_Group group, int *size);
-int PMPI_Group_rank(MPI_Group group, int *rank);
+              MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) MPICH_API_PUBLIC;
+int PMPI_Group_size(MPI_Group group, int *size) MPICH_API_PUBLIC;
+int PMPI_Group_rank(MPI_Group group, int *rank) MPICH_API_PUBLIC;
 int PMPI_Group_translate_ranks(MPI_Group group1, int n, const int ranks1[], MPI_Group group2,
-                               int ranks2[]);
-int PMPI_Group_compare(MPI_Group group1, MPI_Group group2, int *result);
-int PMPI_Comm_group(MPI_Comm comm, MPI_Group *group);
-int PMPI_Group_union(MPI_Group group1, MPI_Group group2, MPI_Group *newgroup);
-int PMPI_Group_intersection(MPI_Group group1, MPI_Group group2, MPI_Group *newgroup);
-int PMPI_Group_difference(MPI_Group group1, MPI_Group group2, MPI_Group *newgroup);
-int PMPI_Group_incl(MPI_Group group, int n, const int ranks[], MPI_Group *newgroup);
-int PMPI_Group_excl(MPI_Group group, int n, const int ranks[], MPI_Group *newgroup);
-int PMPI_Group_range_incl(MPI_Group group, int n, int ranges[][3], MPI_Group *newgroup);
-int PMPI_Group_range_excl(MPI_Group group, int n, int ranges[][3], MPI_Group *newgroup);
-int PMPI_Group_free(MPI_Group *group);
-int PMPI_Comm_size(MPI_Comm comm, int *size);
-int PMPI_Comm_rank(MPI_Comm comm, int *rank);
-int PMPI_Comm_compare(MPI_Comm comm1, MPI_Comm comm2, int *result);
-int PMPI_Comm_dup(MPI_Comm comm, MPI_Comm *newcomm);
-int PMPI_Comm_dup_with_info(MPI_Comm comm, MPI_Info info, MPI_Comm *newcomm);
-int PMPI_Comm_create(MPI_Comm comm, MPI_Group group, MPI_Comm *newcomm);
-int PMPI_Comm_split(MPI_Comm comm, int color, int key, MPI_Comm *newcomm);
-int PMPI_Comm_free(MPI_Comm *comm);
-int PMPI_Comm_test_inter(MPI_Comm comm, int *flag);
-int PMPI_Comm_remote_size(MPI_Comm comm, int *size);
-int PMPI_Comm_remote_group(MPI_Comm comm, MPI_Group *group);
+                               int ranks2[]) MPICH_API_PUBLIC;
+int PMPI_Group_compare(MPI_Group group1, MPI_Group group2, int *result) MPICH_API_PUBLIC;
+int PMPI_Comm_group(MPI_Comm comm, MPI_Group *group) MPICH_API_PUBLIC;
+int PMPI_Group_union(MPI_Group group1, MPI_Group group2, MPI_Group *newgroup) MPICH_API_PUBLIC;
+int PMPI_Group_intersection(MPI_Group group1, MPI_Group group2, MPI_Group *newgroup) MPICH_API_PUBLIC;
+int PMPI_Group_difference(MPI_Group group1, MPI_Group group2, MPI_Group *newgroup) MPICH_API_PUBLIC;
+int PMPI_Group_incl(MPI_Group group, int n, const int ranks[], MPI_Group *newgroup) MPICH_API_PUBLIC;
+int PMPI_Group_excl(MPI_Group group, int n, const int ranks[], MPI_Group *newgroup) MPICH_API_PUBLIC;
+int PMPI_Group_range_incl(MPI_Group group, int n, int ranges[][3], MPI_Group *newgroup) MPICH_API_PUBLIC;
+int PMPI_Group_range_excl(MPI_Group group, int n, int ranges[][3], MPI_Group *newgroup) MPICH_API_PUBLIC;
+int PMPI_Group_free(MPI_Group *group) MPICH_API_PUBLIC;
+int PMPI_Comm_size(MPI_Comm comm, int *size) MPICH_API_PUBLIC;
+int PMPI_Comm_rank(MPI_Comm comm, int *rank) MPICH_API_PUBLIC;
+int PMPI_Comm_compare(MPI_Comm comm1, MPI_Comm comm2, int *result) MPICH_API_PUBLIC;
+int PMPI_Comm_dup(MPI_Comm comm, MPI_Comm *newcomm) MPICH_API_PUBLIC;
+int PMPI_Comm_dup_with_info(MPI_Comm comm, MPI_Info info, MPI_Comm *newcomm) MPICH_API_PUBLIC;
+int PMPI_Comm_create(MPI_Comm comm, MPI_Group group, MPI_Comm *newcomm) MPICH_API_PUBLIC;
+int PMPI_Comm_split(MPI_Comm comm, int color, int key, MPI_Comm *newcomm) MPICH_API_PUBLIC;
+int PMPI_Comm_free(MPI_Comm *comm) MPICH_API_PUBLIC;
+int PMPI_Comm_test_inter(MPI_Comm comm, int *flag) MPICH_API_PUBLIC;
+int PMPI_Comm_remote_size(MPI_Comm comm, int *size) MPICH_API_PUBLIC;
+int PMPI_Comm_remote_group(MPI_Comm comm, MPI_Group *group) MPICH_API_PUBLIC;
 int PMPI_Intercomm_create(MPI_Comm local_comm, int local_leader, MPI_Comm peer_comm,
-                          int remote_leader, int tag, MPI_Comm *newintercomm);
-int PMPI_Intercomm_merge(MPI_Comm intercomm, int high, MPI_Comm *newintracomm);
+                          int remote_leader, int tag, MPI_Comm *newintercomm) MPICH_API_PUBLIC;
+int PMPI_Intercomm_merge(MPI_Comm intercomm, int high, MPI_Comm *newintracomm) MPICH_API_PUBLIC;
 int PMPI_Keyval_create(MPI_Copy_function *copy_fn, MPI_Delete_function *delete_fn,
-                       int *keyval, void *extra_state);
-int PMPI_Keyval_free(int *keyval);
-int PMPI_Attr_put(MPI_Comm comm, int keyval, void *attribute_val);
-int PMPI_Attr_get(MPI_Comm comm, int keyval, void *attribute_val, int *flag);
-int PMPI_Attr_delete(MPI_Comm comm, int keyval);
-int PMPI_Topo_test(MPI_Comm comm, int *status);
+                       int *keyval, void *extra_state) MPICH_API_PUBLIC;
+int PMPI_Keyval_free(int *keyval) MPICH_API_PUBLIC;
+int PMPI_Attr_put(MPI_Comm comm, int keyval, void *attribute_val) MPICH_API_PUBLIC;
+int PMPI_Attr_get(MPI_Comm comm, int keyval, void *attribute_val, int *flag) MPICH_API_PUBLIC;
+int PMPI_Attr_delete(MPI_Comm comm, int keyval) MPICH_API_PUBLIC;
+int PMPI_Topo_test(MPI_Comm comm, int *status) MPICH_API_PUBLIC;
 int PMPI_Cart_create(MPI_Comm comm_old, int ndims, const int dims[], const int periods[],
-                     int reorder, MPI_Comm *comm_cart);
-int PMPI_Dims_create(int nnodes, int ndims, int dims[]);
+                     int reorder, MPI_Comm *comm_cart) MPICH_API_PUBLIC;
+int PMPI_Dims_create(int nnodes, int ndims, int dims[]) MPICH_API_PUBLIC;
 int PMPI_Graph_create(MPI_Comm comm_old, int nnodes, const int indx[], const int edges[],
-                      int reorder, MPI_Comm *comm_graph);
-int PMPI_Graphdims_get(MPI_Comm comm, int *nnodes, int *nedges);
-int PMPI_Graph_get(MPI_Comm comm, int maxindex, int maxedges, int indx[], int edges[]);
-int PMPI_Cartdim_get(MPI_Comm comm, int *ndims);
-int PMPI_Cart_get(MPI_Comm comm, int maxdims, int dims[], int periods[], int coords[]);
-int PMPI_Cart_rank(MPI_Comm comm, const int coords[], int *rank);
-int PMPI_Cart_coords(MPI_Comm comm, int rank, int maxdims, int coords[]);
-int PMPI_Graph_neighbors_count(MPI_Comm comm, int rank, int *nneighbors);
-int PMPI_Graph_neighbors(MPI_Comm comm, int rank, int maxneighbors, int neighbors[]);
-int PMPI_Cart_shift(MPI_Comm comm, int direction, int disp, int *rank_source, int *rank_dest);
-int PMPI_Cart_sub(MPI_Comm comm, const int remain_dims[], MPI_Comm *newcomm);
-int PMPI_Cart_map(MPI_Comm comm, int ndims, const int dims[], const int periods[], int *newrank);
-int PMPI_Graph_map(MPI_Comm comm, int nnodes, const int indx[], const int edges[], int *newrank);
-int PMPI_Get_processor_name(char *name, int *resultlen);
-int PMPI_Get_version(int *version, int *subversion);
-int PMPI_Get_library_version(char *version, int *resultlen);
-int PMPI_Errhandler_create(MPI_Handler_function *function, MPI_Errhandler *errhandler);
-int PMPI_Errhandler_set(MPI_Comm comm, MPI_Errhandler errhandler);
-int PMPI_Errhandler_get(MPI_Comm comm, MPI_Errhandler *errhandler);
-int PMPI_Errhandler_free(MPI_Errhandler *errhandler);
-int PMPI_Error_string(int errorcode, char *string, int *resultlen);
-int PMPI_Error_class(int errorcode, int *errorclass);
-double PMPI_Wtime(void);
-double PMPI_Wtick(void);
-int PMPI_Init(int *argc, char ***argv);
-int PMPI_Finalize(void);
-int PMPI_Initialized(int *flag);
-int PMPI_Abort(MPI_Comm comm, int errorcode);
+                      int reorder, MPI_Comm *comm_graph) MPICH_API_PUBLIC;
+int PMPI_Graphdims_get(MPI_Comm comm, int *nnodes, int *nedges) MPICH_API_PUBLIC;
+int PMPI_Graph_get(MPI_Comm comm, int maxindex, int maxedges, int indx[], int edges[]) MPICH_API_PUBLIC;
+int PMPI_Cartdim_get(MPI_Comm comm, int *ndims) MPICH_API_PUBLIC;
+int PMPI_Cart_get(MPI_Comm comm, int maxdims, int dims[], int periods[], int coords[]) MPICH_API_PUBLIC;
+int PMPI_Cart_rank(MPI_Comm comm, const int coords[], int *rank) MPICH_API_PUBLIC;
+int PMPI_Cart_coords(MPI_Comm comm, int rank, int maxdims, int coords[]) MPICH_API_PUBLIC;
+int PMPI_Graph_neighbors_count(MPI_Comm comm, int rank, int *nneighbors) MPICH_API_PUBLIC;
+int PMPI_Graph_neighbors(MPI_Comm comm, int rank, int maxneighbors, int neighbors[]) MPICH_API_PUBLIC;
+int PMPI_Cart_shift(MPI_Comm comm, int direction, int disp, int *rank_source, int *rank_dest) MPICH_API_PUBLIC;
+int PMPI_Cart_sub(MPI_Comm comm, const int remain_dims[], MPI_Comm *newcomm) MPICH_API_PUBLIC;
+int PMPI_Cart_map(MPI_Comm comm, int ndims, const int dims[], const int periods[], int *newrank) MPICH_API_PUBLIC;
+int PMPI_Graph_map(MPI_Comm comm, int nnodes, const int indx[], const int edges[], int *newrank) MPICH_API_PUBLIC;
+int PMPI_Get_processor_name(char *name, int *resultlen) MPICH_API_PUBLIC;
+int PMPI_Get_version(int *version, int *subversion) MPICH_API_PUBLIC;
+int PMPI_Get_library_version(char *version, int *resultlen) MPICH_API_PUBLIC;
+int PMPI_Errhandler_create(MPI_Handler_function *function, MPI_Errhandler *errhandler) MPICH_API_PUBLIC;
+int PMPI_Errhandler_set(MPI_Comm comm, MPI_Errhandler errhandler) MPICH_API_PUBLIC;
+int PMPI_Errhandler_get(MPI_Comm comm, MPI_Errhandler *errhandler) MPICH_API_PUBLIC;
+int PMPI_Errhandler_free(MPI_Errhandler *errhandler) MPICH_API_PUBLIC;
+int PMPI_Error_string(int errorcode, char *string, int *resultlen) MPICH_API_PUBLIC;
+int PMPI_Error_class(int errorcode, int *errorclass) MPICH_API_PUBLIC;
+double PMPI_Wtime(void) MPICH_API_PUBLIC;
+double PMPI_Wtick(void) MPICH_API_PUBLIC;
+int PMPI_Init(int *argc, char ***argv) MPICH_API_PUBLIC;
+int PMPI_Finalize(void) MPICH_API_PUBLIC;
+int PMPI_Initialized(int *flag) MPICH_API_PUBLIC;
+int PMPI_Abort(MPI_Comm comm, int errorcode) MPICH_API_PUBLIC;
 
 /* Note that we may need to define a @PCONTROL_LIST@ depending on whether
    stdargs are supported */
-int PMPI_Pcontrol(const int level, ...);
+int PMPI_Pcontrol(const int level, ...) MPICH_API_PUBLIC;
 
 /* Process Creation and Management */
-int PMPI_Close_port(const char *port_name);
+int PMPI_Close_port(const char *port_name) MPICH_API_PUBLIC;
 int PMPI_Comm_accept(const char *port_name, MPI_Info info, int root, MPI_Comm comm,
-                     MPI_Comm *newcomm);
+                     MPI_Comm *newcomm) MPICH_API_PUBLIC;
 int PMPI_Comm_connect(const char *port_name, MPI_Info info, int root, MPI_Comm comm,
-                      MPI_Comm *newcomm);
-int PMPI_Comm_disconnect(MPI_Comm *comm);
-int PMPI_Comm_get_parent(MPI_Comm *parent);
-int PMPI_Comm_join(int fd, MPI_Comm *intercomm);
+                      MPI_Comm *newcomm) MPICH_API_PUBLIC;
+int PMPI_Comm_disconnect(MPI_Comm *comm) MPICH_API_PUBLIC;
+int PMPI_Comm_get_parent(MPI_Comm *parent) MPICH_API_PUBLIC;
+int PMPI_Comm_join(int fd, MPI_Comm *intercomm) MPICH_API_PUBLIC;
 int PMPI_Comm_spawn(const char *command, char *argv[], int maxprocs, MPI_Info info, int root,
-                    MPI_Comm comm, MPI_Comm *intercomm, int array_of_errcodes[]);
+                    MPI_Comm comm, MPI_Comm *intercomm, int array_of_errcodes[]) MPICH_API_PUBLIC;
 int PMPI_Comm_spawn_multiple(int count, char *array_of_commands[], char **array_of_argv[],
                              const int array_of_maxprocs[], const MPI_Info array_of_info[],
-                             int root, MPI_Comm comm, MPI_Comm *intercomm, int array_of_errcodes[]);
-int PMPI_Lookup_name(const char *service_name, MPI_Info info, char *port_name);
-int PMPI_Open_port(MPI_Info info, char *port_name);
-int PMPI_Publish_name(const char *service_name, MPI_Info info, const char *port_name);
-int PMPI_Unpublish_name(const char *service_name, MPI_Info info, const char *port_name);
-int PMPI_Comm_set_info(MPI_Comm comm, MPI_Info info);
-int PMPI_Comm_get_info(MPI_Comm comm, MPI_Info *info);
+                             int root, MPI_Comm comm, MPI_Comm *intercomm, int array_of_errcodes[]) MPICH_API_PUBLIC;
+int PMPI_Lookup_name(const char *service_name, MPI_Info info, char *port_name) MPICH_API_PUBLIC;
+int PMPI_Open_port(MPI_Info info, char *port_name) MPICH_API_PUBLIC;
+int PMPI_Publish_name(const char *service_name, MPI_Info info, const char *port_name) MPICH_API_PUBLIC;
+int PMPI_Unpublish_name(const char *service_name, MPI_Info info, const char *port_name) MPICH_API_PUBLIC;
+int PMPI_Comm_set_info(MPI_Comm comm, MPI_Info info) MPICH_API_PUBLIC;
+int PMPI_Comm_get_info(MPI_Comm comm, MPI_Info *info) MPICH_API_PUBLIC;
 
 /* One-Sided Communications */
 int PMPI_Accumulate(const void *origin_addr, int origin_count, MPI_Datatype origin_datatype,
                     int target_rank, MPI_Aint target_disp, int target_count,
                     MPI_Datatype target_datatype, MPI_Op op, MPI_Win win)
-                    MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+                    MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int PMPI_Get(void *origin_addr, int origin_count, MPI_Datatype origin_datatype,
              int target_rank, MPI_Aint target_disp, int target_count,
-             MPI_Datatype target_datatype, MPI_Win win) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+             MPI_Datatype target_datatype, MPI_Win win) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int PMPI_Put(const void *origin_addr, int origin_count, MPI_Datatype origin_datatype,
              int target_rank, MPI_Aint target_disp, int target_count,
-             MPI_Datatype target_datatype, MPI_Win win) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
-int PMPI_Win_complete(MPI_Win win);
+             MPI_Datatype target_datatype, MPI_Win win) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
+int PMPI_Win_complete(MPI_Win win) MPICH_API_PUBLIC;
 int PMPI_Win_create(void *base, MPI_Aint size, int disp_unit, MPI_Info info, MPI_Comm comm,
-                    MPI_Win *win);
-int PMPI_Win_fence(int assert, MPI_Win win);
-int PMPI_Win_free(MPI_Win *win);
-int PMPI_Win_get_group(MPI_Win win, MPI_Group *group);
-int PMPI_Win_lock(int lock_type, int rank, int assert, MPI_Win win);
-int PMPI_Win_post(MPI_Group group, int assert, MPI_Win win);
-int PMPI_Win_start(MPI_Group group, int assert, MPI_Win win);
-int PMPI_Win_test(MPI_Win win, int *flag);
-int PMPI_Win_unlock(int rank, MPI_Win win);
-int PMPI_Win_wait(MPI_Win win);
+                    MPI_Win *win) MPICH_API_PUBLIC;
+int PMPI_Win_fence(int assert, MPI_Win win) MPICH_API_PUBLIC;
+int PMPI_Win_free(MPI_Win *win) MPICH_API_PUBLIC;
+int PMPI_Win_get_group(MPI_Win win, MPI_Group *group) MPICH_API_PUBLIC;
+int PMPI_Win_lock(int lock_type, int rank, int assert, MPI_Win win) MPICH_API_PUBLIC;
+int PMPI_Win_post(MPI_Group group, int assert, MPI_Win win) MPICH_API_PUBLIC;
+int PMPI_Win_start(MPI_Group group, int assert, MPI_Win win) MPICH_API_PUBLIC;
+int PMPI_Win_test(MPI_Win win, int *flag) MPICH_API_PUBLIC;
+int PMPI_Win_unlock(int rank, MPI_Win win) MPICH_API_PUBLIC;
+int PMPI_Win_wait(MPI_Win win) MPICH_API_PUBLIC;
 
 /* MPI-3 One-Sided Communication Routines */
 int PMPI_Win_allocate(MPI_Aint size, int disp_unit, MPI_Info info, MPI_Comm comm, void *baseptr,
-                      MPI_Win *win);
+                      MPI_Win *win) MPICH_API_PUBLIC;
 int PMPI_Win_allocate_shared(MPI_Aint size, int disp_unit, MPI_Info info, MPI_Comm comm,
-                             void *baseptr, MPI_Win *win);
-int PMPI_Win_shared_query(MPI_Win win, int rank, MPI_Aint *size, int *disp_unit, void *baseptr);
-int PMPI_Win_create_dynamic(MPI_Info info, MPI_Comm comm, MPI_Win *win);
-int PMPI_Win_attach(MPI_Win win, void *base, MPI_Aint size);
-int PMPI_Win_detach(MPI_Win win, const void *base);
-int PMPI_Win_get_info(MPI_Win win, MPI_Info *info_used);
-int PMPI_Win_set_info(MPI_Win win, MPI_Info info);
+                             void *baseptr, MPI_Win *win) MPICH_API_PUBLIC;
+int PMPI_Win_shared_query(MPI_Win win, int rank, MPI_Aint *size, int *disp_unit, void *baseptr) MPICH_API_PUBLIC;
+int PMPI_Win_create_dynamic(MPI_Info info, MPI_Comm comm, MPI_Win *win) MPICH_API_PUBLIC;
+int PMPI_Win_attach(MPI_Win win, void *base, MPI_Aint size) MPICH_API_PUBLIC;
+int PMPI_Win_detach(MPI_Win win, const void *base) MPICH_API_PUBLIC;
+int PMPI_Win_get_info(MPI_Win win, MPI_Info *info_used) MPICH_API_PUBLIC;
+int PMPI_Win_set_info(MPI_Win win, MPI_Info info) MPICH_API_PUBLIC;
 int PMPI_Get_accumulate(const void *origin_addr, int origin_count,
                          MPI_Datatype origin_datatype, void *result_addr, int result_count,
                          MPI_Datatype result_datatype, int target_rank, MPI_Aint target_disp,
                          int target_count, MPI_Datatype target_datatype, MPI_Op op, MPI_Win win)
                          MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3)
-                         MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6);
+                         MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6) MPICH_API_PUBLIC;
 int PMPI_Fetch_and_op(const void *origin_addr, void *result_addr,
                        MPI_Datatype datatype, int target_rank, MPI_Aint target_disp,
                        MPI_Op op, MPI_Win win)
-                       MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+                       MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int PMPI_Compare_and_swap(const void *origin_addr, const void *compare_addr,
                            void *result_addr, MPI_Datatype datatype, int target_rank,
                            MPI_Aint target_disp, MPI_Win win)
                            MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4)
                            MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4)
-                           MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,4);
+                           MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,4) MPICH_API_PUBLIC;
 int PMPI_Rput(const void *origin_addr, int origin_count,
                MPI_Datatype origin_datatype, int target_rank, MPI_Aint target_disp,
                int target_count, MPI_Datatype target_datatype, MPI_Win win,
                MPI_Request *request)
-               MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+               MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int PMPI_Rget(void *origin_addr, int origin_count,
                MPI_Datatype origin_datatype, int target_rank, MPI_Aint target_disp,
                int target_count, MPI_Datatype target_datatype, MPI_Win win,
                MPI_Request *request)
-               MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+               MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int PMPI_Raccumulate(const void *origin_addr, int origin_count,
                       MPI_Datatype origin_datatype, int target_rank, MPI_Aint target_disp,
                       int target_count, MPI_Datatype target_datatype, MPI_Op op, MPI_Win win,
                       MPI_Request *request)
-                      MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+                      MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int PMPI_Rget_accumulate(const void *origin_addr, int origin_count,
                           MPI_Datatype origin_datatype, void *result_addr, int result_count,
                           MPI_Datatype result_datatype, int target_rank, MPI_Aint target_disp,
                           int target_count, MPI_Datatype target_datatype, MPI_Op op, MPI_Win win,
                           MPI_Request *request)
                           MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3)
-                          MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6);
-int PMPI_Win_lock_all(int assert, MPI_Win win);
-int PMPI_Win_unlock_all(MPI_Win win);
-int PMPI_Win_flush(int rank, MPI_Win win);
-int PMPI_Win_flush_all(MPI_Win win);
-int PMPI_Win_flush_local(int rank, MPI_Win win);
-int PMPI_Win_flush_local_all(MPI_Win win);
-int PMPI_Win_sync(MPI_Win win);
+                          MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6) MPICH_API_PUBLIC;
+int PMPI_Win_lock_all(int assert, MPI_Win win) MPICH_API_PUBLIC;
+int PMPI_Win_unlock_all(MPI_Win win) MPICH_API_PUBLIC;
+int PMPI_Win_flush(int rank, MPI_Win win) MPICH_API_PUBLIC;
+int PMPI_Win_flush_all(MPI_Win win) MPICH_API_PUBLIC;
+int PMPI_Win_flush_local(int rank, MPI_Win win) MPICH_API_PUBLIC;
+int PMPI_Win_flush_local_all(MPI_Win win) MPICH_API_PUBLIC;
+int PMPI_Win_sync(MPI_Win win) MPICH_API_PUBLIC;
  
 /* External Interfaces */
-int PMPI_Add_error_class(int *errorclass);
-int PMPI_Add_error_code(int errorclass, int *errorcode);
-int PMPI_Add_error_string(int errorcode, const char *string);
-int PMPI_Comm_call_errhandler(MPI_Comm comm, int errorcode);
+int PMPI_Add_error_class(int *errorclass) MPICH_API_PUBLIC;
+int PMPI_Add_error_code(int errorclass, int *errorcode) MPICH_API_PUBLIC;
+int PMPI_Add_error_string(int errorcode, const char *string) MPICH_API_PUBLIC;
+int PMPI_Comm_call_errhandler(MPI_Comm comm, int errorcode) MPICH_API_PUBLIC;
 int PMPI_Comm_create_keyval(MPI_Comm_copy_attr_function *comm_copy_attr_fn,
                             MPI_Comm_delete_attr_function *comm_delete_attr_fn, int *comm_keyval,
-                            void *extra_state);
-int PMPI_Comm_delete_attr(MPI_Comm comm, int comm_keyval);
-int PMPI_Comm_free_keyval(int *comm_keyval);
-int PMPI_Comm_get_attr(MPI_Comm comm, int comm_keyval, void *attribute_val, int *flag);
-int PMPI_Comm_get_name(MPI_Comm comm, char *comm_name, int *resultlen);
-int PMPI_Comm_set_attr(MPI_Comm comm, int comm_keyval, void *attribute_val);
-int PMPI_Comm_set_name(MPI_Comm comm, const char *comm_name);
-int PMPI_File_call_errhandler(MPI_File fh, int errorcode);
-int PMPI_Grequest_complete(MPI_Request request);
+                            void *extra_state) MPICH_API_PUBLIC;
+int PMPI_Comm_delete_attr(MPI_Comm comm, int comm_keyval) MPICH_API_PUBLIC;
+int PMPI_Comm_free_keyval(int *comm_keyval) MPICH_API_PUBLIC;
+int PMPI_Comm_get_attr(MPI_Comm comm, int comm_keyval, void *attribute_val, int *flag) MPICH_API_PUBLIC;
+int PMPI_Comm_get_name(MPI_Comm comm, char *comm_name, int *resultlen) MPICH_API_PUBLIC;
+int PMPI_Comm_set_attr(MPI_Comm comm, int comm_keyval, void *attribute_val) MPICH_API_PUBLIC;
+int PMPI_Comm_set_name(MPI_Comm comm, const char *comm_name) MPICH_API_PUBLIC;
+int PMPI_File_call_errhandler(MPI_File fh, int errorcode) MPICH_API_PUBLIC;
+int PMPI_Grequest_complete(MPI_Request request) MPICH_API_PUBLIC;
 int PMPI_Grequest_start(MPI_Grequest_query_function *query_fn, MPI_Grequest_free_function *free_fn,
                         MPI_Grequest_cancel_function *cancel_fn, void *extra_state,
-                        MPI_Request *request);
-int PMPI_Init_thread(int *argc, char ***argv, int required, int *provided);
-int PMPI_Is_thread_main(int *flag);
-int PMPI_Query_thread(int *provided);
-int PMPI_Status_set_cancelled(MPI_Status *status, int flag);
-int PMPI_Status_set_elements(MPI_Status *status, MPI_Datatype datatype, int count);
+                        MPI_Request *request) MPICH_API_PUBLIC;
+int PMPI_Init_thread(int *argc, char ***argv, int required, int *provided) MPICH_API_PUBLIC;
+int PMPI_Is_thread_main(int *flag) MPICH_API_PUBLIC;
+int PMPI_Query_thread(int *provided) MPICH_API_PUBLIC;
+int PMPI_Status_set_cancelled(MPI_Status *status, int flag) MPICH_API_PUBLIC;
+int PMPI_Status_set_elements(MPI_Status *status, MPI_Datatype datatype, int count) MPICH_API_PUBLIC;
 int PMPI_Type_create_keyval(MPI_Type_copy_attr_function *type_copy_attr_fn,
                             MPI_Type_delete_attr_function *type_delete_attr_fn,
-                            int *type_keyval, void *extra_state);
-int PMPI_Type_delete_attr(MPI_Datatype datatype, int type_keyval);
-int PMPI_Type_dup(MPI_Datatype oldtype, MPI_Datatype *newtype);
-int PMPI_Type_free_keyval(int *type_keyval);
-int PMPI_Type_get_attr(MPI_Datatype datatype, int type_keyval, void *attribute_val, int *flag);
+                            int *type_keyval, void *extra_state) MPICH_API_PUBLIC;
+int PMPI_Type_delete_attr(MPI_Datatype datatype, int type_keyval) MPICH_API_PUBLIC;
+int PMPI_Type_dup(MPI_Datatype oldtype, MPI_Datatype *newtype) MPICH_API_PUBLIC;
+int PMPI_Type_free_keyval(int *type_keyval) MPICH_API_PUBLIC;
+int PMPI_Type_get_attr(MPI_Datatype datatype, int type_keyval, void *attribute_val, int *flag) MPICH_API_PUBLIC;
 int PMPI_Type_get_contents(MPI_Datatype datatype, int max_integers, int max_addresses,
                            int max_datatypes, int array_of_integers[],
-                           MPI_Aint array_of_addresses[], MPI_Datatype array_of_datatypes[]);
+                           MPI_Aint array_of_addresses[], MPI_Datatype array_of_datatypes[]) MPICH_API_PUBLIC;
 int PMPI_Type_get_envelope(MPI_Datatype datatype, int *num_integers, int *num_addresses,
-                           int *num_datatypes, int *combiner);
-int PMPI_Type_get_name(MPI_Datatype datatype, char *type_name, int *resultlen);
-int PMPI_Type_set_attr(MPI_Datatype datatype, int type_keyval, void *attribute_val);
-int PMPI_Type_set_name(MPI_Datatype datatype, const char *type_name);
-int PMPI_Type_match_size(int typeclass, int size, MPI_Datatype *datatype);
-int PMPI_Win_call_errhandler(MPI_Win win, int errorcode);
+                           int *num_datatypes, int *combiner) MPICH_API_PUBLIC;
+int PMPI_Type_get_name(MPI_Datatype datatype, char *type_name, int *resultlen) MPICH_API_PUBLIC;
+int PMPI_Type_set_attr(MPI_Datatype datatype, int type_keyval, void *attribute_val) MPICH_API_PUBLIC;
+int PMPI_Type_set_name(MPI_Datatype datatype, const char *type_name) MPICH_API_PUBLIC;
+int PMPI_Type_match_size(int typeclass, int size, MPI_Datatype *datatype) MPICH_API_PUBLIC;
+int PMPI_Win_call_errhandler(MPI_Win win, int errorcode) MPICH_API_PUBLIC;
 int PMPI_Win_create_keyval(MPI_Win_copy_attr_function *win_copy_attr_fn,
                            MPI_Win_delete_attr_function *win_delete_attr_fn, int *win_keyval,
-                           void *extra_state);
-int PMPI_Win_delete_attr(MPI_Win win, int win_keyval);
-int PMPI_Win_free_keyval(int *win_keyval);
-int PMPI_Win_get_attr(MPI_Win win, int win_keyval, void *attribute_val, int *flag);
-int PMPI_Win_get_name(MPI_Win win, char *win_name, int *resultlen);
-int PMPI_Win_set_attr(MPI_Win win, int win_keyval, void *attribute_val);
-int PMPI_Win_set_name(MPI_Win win, const char *win_name);
+                           void *extra_state) MPICH_API_PUBLIC;
+int PMPI_Win_delete_attr(MPI_Win win, int win_keyval) MPICH_API_PUBLIC;
+int PMPI_Win_free_keyval(int *win_keyval) MPICH_API_PUBLIC;
+int PMPI_Win_get_attr(MPI_Win win, int win_keyval, void *attribute_val, int *flag) MPICH_API_PUBLIC;
+int PMPI_Win_get_name(MPI_Win win, char *win_name, int *resultlen) MPICH_API_PUBLIC;
+int PMPI_Win_set_attr(MPI_Win win, int win_keyval, void *attribute_val) MPICH_API_PUBLIC;
+int PMPI_Win_set_name(MPI_Win win, const char *win_name) MPICH_API_PUBLIC;
 
-int PMPI_Alloc_mem(MPI_Aint size, MPI_Info info, void *baseptr);
+int PMPI_Alloc_mem(MPI_Aint size, MPI_Info info, void *baseptr) MPICH_API_PUBLIC;
 int PMPI_Comm_create_errhandler(MPI_Comm_errhandler_function *comm_errhandler_fn,
-                                MPI_Errhandler *errhandler);
-int PMPI_Comm_get_errhandler(MPI_Comm comm, MPI_Errhandler *errhandler);
-int PMPI_Comm_set_errhandler(MPI_Comm comm, MPI_Errhandler errhandler);
+                                MPI_Errhandler *errhandler) MPICH_API_PUBLIC;
+int PMPI_Comm_get_errhandler(MPI_Comm comm, MPI_Errhandler *errhandler) MPICH_API_PUBLIC;
+int PMPI_Comm_set_errhandler(MPI_Comm comm, MPI_Errhandler errhandler) MPICH_API_PUBLIC;
 int PMPI_File_create_errhandler(MPI_File_errhandler_function *file_errhandler_fn,
-                                MPI_Errhandler *errhandler);
-int PMPI_File_get_errhandler(MPI_File file, MPI_Errhandler *errhandler);
-int PMPI_File_set_errhandler(MPI_File file, MPI_Errhandler errhandler);
-int PMPI_Finalized(int *flag);
-int PMPI_Free_mem(void *base);
-int PMPI_Get_address(const void *location, MPI_Aint *address);
-int PMPI_Info_create(MPI_Info *info);
-int PMPI_Info_delete(MPI_Info info, const char *key);
-int PMPI_Info_dup(MPI_Info info, MPI_Info *newinfo);
-int PMPI_Info_free(MPI_Info *info);
-int PMPI_Info_get(MPI_Info info, const char *key, int valuelen, char *value, int *flag);
-int PMPI_Info_get_nkeys(MPI_Info info, int *nkeys);
-int PMPI_Info_get_nthkey(MPI_Info info, int n, char *key);
-int PMPI_Info_get_valuelen(MPI_Info info, const char *key, int *valuelen, int *flag);
-int PMPI_Info_set(MPI_Info info, const char *key, const char *value);
+                                MPI_Errhandler *errhandler) MPICH_API_PUBLIC;
+int PMPI_File_get_errhandler(MPI_File file, MPI_Errhandler *errhandler) MPICH_API_PUBLIC;
+int PMPI_File_set_errhandler(MPI_File file, MPI_Errhandler errhandler) MPICH_API_PUBLIC;
+int PMPI_Finalized(int *flag) MPICH_API_PUBLIC;
+int PMPI_Free_mem(void *base) MPICH_API_PUBLIC;
+int PMPI_Get_address(const void *location, MPI_Aint *address) MPICH_API_PUBLIC;
+int PMPI_Info_create(MPI_Info *info) MPICH_API_PUBLIC;
+int PMPI_Info_delete(MPI_Info info, const char *key) MPICH_API_PUBLIC;
+int PMPI_Info_dup(MPI_Info info, MPI_Info *newinfo) MPICH_API_PUBLIC;
+int PMPI_Info_free(MPI_Info *info) MPICH_API_PUBLIC;
+int PMPI_Info_get(MPI_Info info, const char *key, int valuelen, char *value, int *flag) MPICH_API_PUBLIC;
+int PMPI_Info_get_nkeys(MPI_Info info, int *nkeys) MPICH_API_PUBLIC;
+int PMPI_Info_get_nthkey(MPI_Info info, int n, char *key) MPICH_API_PUBLIC;
+int PMPI_Info_get_valuelen(MPI_Info info, const char *key, int *valuelen, int *flag) MPICH_API_PUBLIC;
+int PMPI_Info_set(MPI_Info info, const char *key, const char *value) MPICH_API_PUBLIC;
 int PMPI_Pack_external(const char datarep[], const void *inbuf, int incount,
                        MPI_Datatype datatype, void *outbuf, MPI_Aint outsize, MPI_Aint *position)
-                       MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                       MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) MPICH_API_PUBLIC;
 int PMPI_Pack_external_size(const char datarep[], int incount, MPI_Datatype datatype,
-                            MPI_Aint *size);
-int PMPI_Request_get_status(MPI_Request request, int *flag, MPI_Status *status);
-int PMPI_Status_c2f(const MPI_Status *c_status, MPI_Fint *f_status);
-int PMPI_Status_f2c(const MPI_Fint *f_status, MPI_Status *c_status);
+                            MPI_Aint *size) MPICH_API_PUBLIC;
+int PMPI_Request_get_status(MPI_Request request, int *flag, MPI_Status *status) MPICH_API_PUBLIC;
+int PMPI_Status_c2f(const MPI_Status *c_status, MPI_Fint *f_status) MPICH_API_PUBLIC;
+int PMPI_Status_f2c(const MPI_Fint *f_status, MPI_Status *c_status) MPICH_API_PUBLIC;
 int PMPI_Type_create_darray(int size, int rank, int ndims, const int array_of_gsizes[],
                             const int array_of_distribs[], const int array_of_dargs[],
                             const int array_of_psizes[], int order, MPI_Datatype oldtype,
-                            MPI_Datatype *newtype);
+                            MPI_Datatype *newtype) MPICH_API_PUBLIC;
 int PMPI_Type_create_hindexed(int count, const int array_of_blocklengths[],
                               const MPI_Aint array_of_displacements[], MPI_Datatype oldtype,
-                              MPI_Datatype *newtype);
+                              MPI_Datatype *newtype) MPICH_API_PUBLIC;
 int PMPI_Type_create_hvector(int count, int blocklength, MPI_Aint stride, MPI_Datatype oldtype,
-                             MPI_Datatype *newtype);
+                             MPI_Datatype *newtype) MPICH_API_PUBLIC;
 int PMPI_Type_create_indexed_block(int count, int blocklength, const int array_of_displacements[],
-                                   MPI_Datatype oldtype, MPI_Datatype *newtype);
+                                   MPI_Datatype oldtype, MPI_Datatype *newtype) MPICH_API_PUBLIC;
 int PMPI_Type_create_hindexed_block(int count, int blocklength,
                                     const MPI_Aint array_of_displacements[],
-                                    MPI_Datatype oldtype, MPI_Datatype *newtype);
+                                    MPI_Datatype oldtype, MPI_Datatype *newtype) MPICH_API_PUBLIC;
 int PMPI_Type_create_resized(MPI_Datatype oldtype, MPI_Aint lb, MPI_Aint extent,
-                             MPI_Datatype *newtype);
+                             MPI_Datatype *newtype) MPICH_API_PUBLIC;
 int PMPI_Type_create_struct(int count, const int array_of_blocklengths[],
                             const MPI_Aint array_of_displacements[],
-                            const MPI_Datatype array_of_types[], MPI_Datatype *newtype);
+                            const MPI_Datatype array_of_types[], MPI_Datatype *newtype) MPICH_API_PUBLIC;
 int PMPI_Type_create_subarray(int ndims, const int array_of_sizes[],
                               const int array_of_subsizes[], const int array_of_starts[],
-                              int order, MPI_Datatype oldtype, MPI_Datatype *newtype);
-int PMPI_Type_get_extent(MPI_Datatype datatype, MPI_Aint *lb, MPI_Aint *extent);
-int PMPI_Type_get_true_extent(MPI_Datatype datatype, MPI_Aint *true_lb, MPI_Aint *true_extent);
+                              int order, MPI_Datatype oldtype, MPI_Datatype *newtype) MPICH_API_PUBLIC;
+int PMPI_Type_get_extent(MPI_Datatype datatype, MPI_Aint *lb, MPI_Aint *extent) MPICH_API_PUBLIC;
+int PMPI_Type_get_true_extent(MPI_Datatype datatype, MPI_Aint *true_lb, MPI_Aint *true_extent) MPICH_API_PUBLIC;
 int PMPI_Unpack_external(const char datarep[], const void *inbuf, MPI_Aint insize,
                          MPI_Aint *position, void *outbuf, int outcount, MPI_Datatype datatype)
-                         MPICH_ATTR_POINTER_WITH_TYPE_TAG(5,7);
+                         MPICH_ATTR_POINTER_WITH_TYPE_TAG(5,7) MPICH_API_PUBLIC;
 int PMPI_Win_create_errhandler(MPI_Win_errhandler_function *win_errhandler_fn,
-                               MPI_Errhandler *errhandler);
-int PMPI_Win_get_errhandler(MPI_Win win, MPI_Errhandler *errhandler);
-int PMPI_Win_set_errhandler(MPI_Win win, MPI_Errhandler errhandler);
+                               MPI_Errhandler *errhandler) MPICH_API_PUBLIC;
+int PMPI_Win_get_errhandler(MPI_Win win, MPI_Errhandler *errhandler) MPICH_API_PUBLIC;
+int PMPI_Win_set_errhandler(MPI_Win win, MPI_Errhandler errhandler) MPICH_API_PUBLIC;
 
 /* Fortran 90-related functions.  These routines are available only if
    Fortran 90 support is enabled 
 */
-int PMPI_Type_create_f90_integer(int r, MPI_Datatype *newtype);
-int PMPI_Type_create_f90_real(int p, int r, MPI_Datatype *newtype);
-int PMPI_Type_create_f90_complex(int p, int r, MPI_Datatype *newtype);
+int PMPI_Type_create_f90_integer(int r, MPI_Datatype *newtype) MPICH_API_PUBLIC;
+int PMPI_Type_create_f90_real(int p, int r, MPI_Datatype *newtype) MPICH_API_PUBLIC;
+int PMPI_Type_create_f90_complex(int p, int r, MPI_Datatype *newtype) MPICH_API_PUBLIC;
 
 int PMPI_Reduce_local(const void *inbuf, void *inoutbuf, int count, MPI_Datatype datatype,
                       MPI_Op op)
-                      MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
-int PMPI_Op_commutative(MPI_Op op, int *commute);
+                      MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) MPICH_API_PUBLIC;
+int PMPI_Op_commutative(MPI_Op op, int *commute) MPICH_API_PUBLIC;
 int PMPI_Reduce_scatter_block(const void *sendbuf, void *recvbuf, int recvcount,
                               MPI_Datatype datatype, MPI_Op op, MPI_Comm comm)
                               MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4)
-                              MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                              MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) MPICH_API_PUBLIC;
 int PMPI_Dist_graph_create_adjacent(MPI_Comm comm_old, int indegree, const int sources[],
                                     const int sourceweights[], int outdegree,
                                     const int destinations[], const int destweights[],
-                                    MPI_Info info, int reorder, MPI_Comm *comm_dist_graph);
+                                    MPI_Info info, int reorder, MPI_Comm *comm_dist_graph) MPICH_API_PUBLIC;
 int PMPI_Dist_graph_create(MPI_Comm comm_old, int n, const int sources[], const int degrees[],
                            const int destinations[], const int weights[], MPI_Info info,
-                           int reorder, MPI_Comm *comm_dist_graph);
-int PMPI_Dist_graph_neighbors_count(MPI_Comm comm, int *indegree, int *outdegree, int *weighted);
+                           int reorder, MPI_Comm *comm_dist_graph) MPICH_API_PUBLIC;
+int PMPI_Dist_graph_neighbors_count(MPI_Comm comm, int *indegree, int *outdegree, int *weighted) MPICH_API_PUBLIC;
 int PMPI_Dist_graph_neighbors(MPI_Comm comm, int maxindegree, int sources[], int sourceweights[],
-                              int maxoutdegree, int destinations[], int destweights[]);
+                              int maxoutdegree, int destinations[], int destweights[]) MPICH_API_PUBLIC;
 
 /* Matched probe functionality */
 int PMPI_Improbe(int source, int tag, MPI_Comm comm, int *flag, MPI_Message *message,
-                 MPI_Status *status);
+                 MPI_Status *status) MPICH_API_PUBLIC;
 int PMPI_Imrecv(void *buf, int count, MPI_Datatype datatype, MPI_Message *message,
-                MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
-int PMPI_Mprobe(int source, int tag, MPI_Comm comm, MPI_Message *message, MPI_Status *status);
+                MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
+int PMPI_Mprobe(int source, int tag, MPI_Comm comm, MPI_Message *message, MPI_Status *status) MPICH_API_PUBLIC;
 int PMPI_Mrecv(void *buf, int count, MPI_Datatype datatype, MPI_Message *message,
-               MPI_Status *status) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+               MPI_Status *status) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 
 /* Nonblocking collectives */
-int PMPI_Comm_idup(MPI_Comm comm, MPI_Comm *newcomm, MPI_Request *request);
-int PMPI_Ibarrier(MPI_Comm comm, MPI_Request *request);
+int PMPI_Comm_idup(MPI_Comm comm, MPI_Comm *newcomm, MPI_Request *request) MPICH_API_PUBLIC;
+int PMPI_Ibarrier(MPI_Comm comm, MPI_Request *request) MPICH_API_PUBLIC;
 int PMPI_Ibcast(void *buffer, int count, MPI_Datatype datatype, int root, MPI_Comm comm,
-                MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3);
+                MPI_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_API_PUBLIC;
 int PMPI_Igather(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
                  int recvcount, MPI_Datatype recvtype, int root, MPI_Comm comm,
                  MPI_Request *request)
-                 MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6);
+                 MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6) MPICH_API_PUBLIC;
 int PMPI_Igatherv(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
                   const int recvcounts[], const int displs[], MPI_Datatype recvtype, int root,
                   MPI_Comm comm, MPI_Request *request)
-                  MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,7);
+                  MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,7) MPICH_API_PUBLIC;
 int PMPI_Iscatter(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
                   int recvcount, MPI_Datatype recvtype, int root, MPI_Comm comm,
                   MPI_Request *request)
-                  MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6);
+                  MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6) MPICH_API_PUBLIC;
 int PMPI_Iscatterv(const void *sendbuf, const int sendcounts[], const int displs[],
                    MPI_Datatype sendtype, void *recvbuf, int recvcount, MPI_Datatype recvtype,
                    int root, MPI_Comm comm, MPI_Request *request)
-                   MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(5,7);
+                   MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(5,7) MPICH_API_PUBLIC;
 int PMPI_Iallgather(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
                     int recvcount, MPI_Datatype recvtype, MPI_Comm comm, MPI_Request *request)
-                    MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6);
+                    MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6) MPICH_API_PUBLIC;
 int PMPI_Iallgatherv(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
                      const int recvcounts[], const int displs[], MPI_Datatype recvtype,
                      MPI_Comm comm, MPI_Request *request)
-                     MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,7);
+                     MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,7) MPICH_API_PUBLIC;
 int PMPI_Ialltoall(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
                    int recvcount, MPI_Datatype recvtype, MPI_Comm comm, MPI_Request *request)
-                   MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6);
+                   MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3) MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6) MPICH_API_PUBLIC;
 int PMPI_Ialltoallv(const void *sendbuf, const int sendcounts[], const int sdispls[],
                     MPI_Datatype sendtype, void *recvbuf, const int recvcounts[],
                     const int rdispls[], MPI_Datatype recvtype, MPI_Comm comm,
                     MPI_Request *request)
-                    MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(5,8);
+                    MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(5,8) MPICH_API_PUBLIC;
 int PMPI_Ialltoallw(const void *sendbuf, const int sendcounts[], const int sdispls[],
                     const MPI_Datatype sendtypes[], void *recvbuf, const int recvcounts[],
                     const int rdispls[], const MPI_Datatype recvtypes[], MPI_Comm comm,
-                    MPI_Request *request);
+                    MPI_Request *request) MPICH_API_PUBLIC;
 int PMPI_Ireduce(const void *sendbuf, void *recvbuf, int count, MPI_Datatype datatype,
                  MPI_Op op, int root, MPI_Comm comm, MPI_Request *request)
-                 MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                 MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) MPICH_API_PUBLIC;
 int PMPI_Iallreduce(const void *sendbuf, void *recvbuf, int count, MPI_Datatype datatype,
                     MPI_Op op, MPI_Comm comm, MPI_Request *request)
-                    MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                    MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) MPICH_API_PUBLIC;
 int PMPI_Ireduce_scatter(const void *sendbuf, void *recvbuf, const int recvcounts[],
                          MPI_Datatype datatype, MPI_Op op, MPI_Comm comm, MPI_Request *request)
                          MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4)
-                         MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                         MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) MPICH_API_PUBLIC;
 int PMPI_Ireduce_scatter_block(const void *sendbuf, void *recvbuf, int recvcount,
                                MPI_Datatype datatype, MPI_Op op, MPI_Comm comm,
                                MPI_Request *request)
                                MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4)
-                               MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                               MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) MPICH_API_PUBLIC;
 int PMPI_Iscan(const void *sendbuf, void *recvbuf, int count, MPI_Datatype datatype, MPI_Op op,
                MPI_Comm comm, MPI_Request *request)
-               MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+               MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) MPICH_API_PUBLIC;
 int PMPI_Iexscan(const void *sendbuf, void *recvbuf, int count, MPI_Datatype datatype,
                  MPI_Op op, MPI_Comm comm, MPI_Request *request)
-                 MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                 MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) MPICH_API_PUBLIC;
 
 /* Neighborhood collectives */
 int PMPI_Ineighbor_allgather(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
                              void *recvbuf, int recvcount, MPI_Datatype recvtype,
                              MPI_Comm comm, MPI_Request *request)
                              MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3)
-                             MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6);
+                             MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6) MPICH_API_PUBLIC;
 int PMPI_Ineighbor_allgatherv(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
                               void *recvbuf, const int recvcounts[], const int displs[],
                               MPI_Datatype recvtype, MPI_Comm comm, MPI_Request *request)
                               MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3)
-                              MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,7);
+                              MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,7) MPICH_API_PUBLIC;
 int PMPI_Ineighbor_alltoall(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
                             void *recvbuf, int recvcount, MPI_Datatype recvtype, MPI_Comm comm,
                             MPI_Request *request)
                             MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3)
-                            MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6);
+                            MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6) MPICH_API_PUBLIC;
 int PMPI_Ineighbor_alltoallv(const void *sendbuf, const int sendcounts[], const int sdispls[],
                              MPI_Datatype sendtype, void *recvbuf, const int recvcounts[],
                              const int rdispls[], MPI_Datatype recvtype, MPI_Comm comm,
                              MPI_Request *request)
                              MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4)
-                             MPICH_ATTR_POINTER_WITH_TYPE_TAG(5,8);
+                             MPICH_ATTR_POINTER_WITH_TYPE_TAG(5,8) MPICH_API_PUBLIC;
 int PMPI_Ineighbor_alltoallw(const void *sendbuf, const int sendcounts[],
                              const MPI_Aint sdispls[], const MPI_Datatype sendtypes[],
                              void *recvbuf, const int recvcounts[], const MPI_Aint rdispls[],
-                             const MPI_Datatype recvtypes[], MPI_Comm comm, MPI_Request *request);
+                             const MPI_Datatype recvtypes[], MPI_Comm comm, MPI_Request *request) MPICH_API_PUBLIC;
 int PMPI_Neighbor_allgather(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
                             void *recvbuf, int recvcount, MPI_Datatype recvtype, MPI_Comm comm)
                             MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3)
-                            MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6);
+                            MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6) MPICH_API_PUBLIC;
 int PMPI_Neighbor_allgatherv(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
                              void *recvbuf, const int recvcounts[], const int displs[],
                              MPI_Datatype recvtype, MPI_Comm comm)
                              MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3)
-                             MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,7);
+                             MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,7) MPICH_API_PUBLIC;
 int PMPI_Neighbor_alltoall(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
                            void *recvbuf, int recvcount, MPI_Datatype recvtype, MPI_Comm comm)
                            MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,3)
-                           MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6);
+                           MPICH_ATTR_POINTER_WITH_TYPE_TAG(4,6) MPICH_API_PUBLIC;
 int PMPI_Neighbor_alltoallv(const void *sendbuf, const int sendcounts[], const int sdispls[],
                             MPI_Datatype sendtype, void *recvbuf, const int recvcounts[],
                             const int rdispls[], MPI_Datatype recvtype, MPI_Comm comm)
                             MPICH_ATTR_POINTER_WITH_TYPE_TAG(1,4)
-                            MPICH_ATTR_POINTER_WITH_TYPE_TAG(5,8);
+                            MPICH_ATTR_POINTER_WITH_TYPE_TAG(5,8) MPICH_API_PUBLIC;
 int PMPI_Neighbor_alltoallw(const void *sendbuf, const int sendcounts[], const MPI_Aint sdispls[],
                             const MPI_Datatype sendtypes[], void *recvbuf, const int recvcounts[],
                             const MPI_Aint rdispls[], const MPI_Datatype recvtypes[],
-                            MPI_Comm comm);
+                            MPI_Comm comm) MPICH_API_PUBLIC;
 
 /* Shared memory */
-int PMPI_Comm_split_type(MPI_Comm comm, int split_type, int key, MPI_Info info, MPI_Comm *newcomm);
+int PMPI_Comm_split_type(MPI_Comm comm, int split_type, int key, MPI_Info info, MPI_Comm *newcomm) MPICH_API_PUBLIC;
 
 /* Noncollective communicator creation */
-int PMPI_Comm_create_group(MPI_Comm comm, MPI_Group group, int tag, MPI_Comm *newcomm);
+int PMPI_Comm_create_group(MPI_Comm comm, MPI_Group group, int tag, MPI_Comm *newcomm) MPICH_API_PUBLIC;
 
 /* MPI-3 "large count" routines */
-int PMPI_Get_elements_x(const MPI_Status *status, MPI_Datatype datatype, MPI_Count *count);
-int PMPI_Status_set_elements_x(MPI_Status *status, MPI_Datatype datatype, MPI_Count count);
-int PMPI_Type_get_extent_x(MPI_Datatype datatype, MPI_Count *lb, MPI_Count *extent);
-int PMPI_Type_get_true_extent_x(MPI_Datatype datatype, MPI_Count *lb, MPI_Count *extent);
-int PMPI_Type_size_x(MPI_Datatype datatype, MPI_Count *size);
+int PMPI_Get_elements_x(const MPI_Status *status, MPI_Datatype datatype, MPI_Count *count) MPICH_API_PUBLIC;
+int PMPI_Status_set_elements_x(MPI_Status *status, MPI_Datatype datatype, MPI_Count count) MPICH_API_PUBLIC;
+int PMPI_Type_get_extent_x(MPI_Datatype datatype, MPI_Count *lb, MPI_Count *extent) MPICH_API_PUBLIC;
+int PMPI_Type_get_true_extent_x(MPI_Datatype datatype, MPI_Count *lb, MPI_Count *extent) MPICH_API_PUBLIC;
+int PMPI_Type_size_x(MPI_Datatype datatype, MPI_Count *size) MPICH_API_PUBLIC;
 
 /* MPI_Aint addressing arithmetic */
-MPI_Aint PMPI_Aint_add(MPI_Aint base, MPI_Aint disp);
-MPI_Aint PMPI_Aint_diff(MPI_Aint addr1, MPI_Aint addr2);
+MPI_Aint PMPI_Aint_add(MPI_Aint base, MPI_Aint disp) MPICH_API_PUBLIC;
+MPI_Aint PMPI_Aint_diff(MPI_Aint addr1, MPI_Aint addr2) MPICH_API_PUBLIC;
 
 /* MPI_T interface */
 /* The MPI_T routines are available only in C bindings - tell tools that they
    can skip these prototypes */
 /* Begin Skip Prototypes */
-int PMPI_T_init_thread(int required, int *provided);
-int PMPI_T_finalize(void);
-int PMPI_T_enum_get_info(MPI_T_enum enumtype, int *num, char *name, int *name_len);
-int PMPI_T_enum_get_item(MPI_T_enum enumtype, int indx, int *value, char *name, int *name_len);
-int PMPI_T_cvar_get_num(int *num_cvar);
+int PMPI_T_init_thread(int required, int *provided) MPICH_API_PUBLIC;
+int PMPI_T_finalize(void) MPICH_API_PUBLIC;
+int PMPI_T_enum_get_info(MPI_T_enum enumtype, int *num, char *name, int *name_len) MPICH_API_PUBLIC;
+int PMPI_T_enum_get_item(MPI_T_enum enumtype, int indx, int *value, char *name, int *name_len) MPICH_API_PUBLIC;
+int PMPI_T_cvar_get_num(int *num_cvar) MPICH_API_PUBLIC;
 int PMPI_T_cvar_get_info(int cvar_index, char *name, int *name_len, int *verbosity,
                          MPI_Datatype *datatype, MPI_T_enum *enumtype, char *desc, int *desc_len,
-                         int *binding, int *scope);
+                         int *binding, int *scope) MPICH_API_PUBLIC;
 int PMPI_T_cvar_handle_alloc(int cvar_index, void *obj_handle, MPI_T_cvar_handle *handle,
-                             int *count);
-int PMPI_T_cvar_handle_free(MPI_T_cvar_handle *handle);
-int PMPI_T_cvar_read(MPI_T_cvar_handle handle, void *buf);
-int PMPI_T_cvar_write(MPI_T_cvar_handle handle, const void *buf);
-int PMPI_T_pvar_get_num(int *num_pvar);
+                             int *count) MPICH_API_PUBLIC;
+int PMPI_T_cvar_handle_free(MPI_T_cvar_handle *handle) MPICH_API_PUBLIC;
+int PMPI_T_cvar_read(MPI_T_cvar_handle handle, void *buf) MPICH_API_PUBLIC;
+int PMPI_T_cvar_write(MPI_T_cvar_handle handle, const void *buf) MPICH_API_PUBLIC;
+int PMPI_T_pvar_get_num(int *num_pvar) MPICH_API_PUBLIC;
 int PMPI_T_pvar_get_info(int pvar_index, char *name, int *name_len, int *verbosity, int *var_class,
                          MPI_Datatype *datatype, MPI_T_enum *enumtype, char *desc, int *desc_len,
-                         int *binding, int *readonly, int *continuous, int *atomic);
-int PMPI_T_pvar_session_create(MPI_T_pvar_session *session);
-int PMPI_T_pvar_session_free(MPI_T_pvar_session *session);
+                         int *binding, int *readonly, int *continuous, int *atomic) MPICH_API_PUBLIC;
+int PMPI_T_pvar_session_create(MPI_T_pvar_session *session) MPICH_API_PUBLIC;
+int PMPI_T_pvar_session_free(MPI_T_pvar_session *session) MPICH_API_PUBLIC;
 int PMPI_T_pvar_handle_alloc(MPI_T_pvar_session session, int pvar_index, void *obj_handle,
-                             MPI_T_pvar_handle *handle, int *count);
-int PMPI_T_pvar_handle_free(MPI_T_pvar_session session, MPI_T_pvar_handle *handle);
-int PMPI_T_pvar_start(MPI_T_pvar_session session, MPI_T_pvar_handle handle);
-int PMPI_T_pvar_stop(MPI_T_pvar_session session, MPI_T_pvar_handle handle);
-int PMPI_T_pvar_read(MPI_T_pvar_session session, MPI_T_pvar_handle handle, void *buf);
-int PMPI_T_pvar_write(MPI_T_pvar_session session, MPI_T_pvar_handle handle, const void *buf);
-int PMPI_T_pvar_reset(MPI_T_pvar_session session, MPI_T_pvar_handle handle);
-int PMPI_T_pvar_readreset(MPI_T_pvar_session session, MPI_T_pvar_handle handle, void *buf);
-int PMPI_T_category_get_num(int *num_cat);
+                             MPI_T_pvar_handle *handle, int *count) MPICH_API_PUBLIC;
+int PMPI_T_pvar_handle_free(MPI_T_pvar_session session, MPI_T_pvar_handle *handle) MPICH_API_PUBLIC;
+int PMPI_T_pvar_start(MPI_T_pvar_session session, MPI_T_pvar_handle handle) MPICH_API_PUBLIC;
+int PMPI_T_pvar_stop(MPI_T_pvar_session session, MPI_T_pvar_handle handle) MPICH_API_PUBLIC;
+int PMPI_T_pvar_read(MPI_T_pvar_session session, MPI_T_pvar_handle handle, void *buf) MPICH_API_PUBLIC;
+int PMPI_T_pvar_write(MPI_T_pvar_session session, MPI_T_pvar_handle handle, const void *buf) MPICH_API_PUBLIC;
+int PMPI_T_pvar_reset(MPI_T_pvar_session session, MPI_T_pvar_handle handle) MPICH_API_PUBLIC;
+int PMPI_T_pvar_readreset(MPI_T_pvar_session session, MPI_T_pvar_handle handle, void *buf) MPICH_API_PUBLIC;
+int PMPI_T_category_get_num(int *num_cat) MPICH_API_PUBLIC;
 int PMPI_T_category_get_info(int cat_index, char *name, int *name_len, char *desc, int *desc_len,
-                             int *num_cvars, int *num_pvars, int *num_categories);
-int PMPI_T_category_get_cvars(int cat_index, int len, int indices[]);
-int PMPI_T_category_get_pvars(int cat_index, int len, int indices[]);
-int PMPI_T_category_get_categories(int cat_index, int len, int indices[]);
-int PMPI_T_category_changed(int *stamp);
-int PMPI_T_cvar_get_index(const char *name, int *cvar_index);
-int PMPI_T_pvar_get_index(const char *name, int var_class, int *pvar_index);
-int PMPI_T_category_get_index(const char *name, int *cat_index);
+                             int *num_cvars, int *num_pvars, int *num_categories) MPICH_API_PUBLIC;
+int PMPI_T_category_get_cvars(int cat_index, int len, int indices[]) MPICH_API_PUBLIC;
+int PMPI_T_category_get_pvars(int cat_index, int len, int indices[]) MPICH_API_PUBLIC;
+int PMPI_T_category_get_categories(int cat_index, int len, int indices[]) MPICH_API_PUBLIC;
+int PMPI_T_category_changed(int *stamp) MPICH_API_PUBLIC;
+int PMPI_T_cvar_get_index(const char *name, int *cvar_index) MPICH_API_PUBLIC;
+int PMPI_T_pvar_get_index(const char *name, int var_class, int *pvar_index) MPICH_API_PUBLIC;
+int PMPI_T_category_get_index(const char *name, int *cat_index) MPICH_API_PUBLIC;
 /* End Skip Prototypes */
 
 
 /* Non-standard but public extensions to MPI */
 /* Fault Tolerance Extensions */
-int PMPIX_Comm_failure_ack(MPI_Comm comm);
-int PMPIX_Comm_failure_get_acked(MPI_Comm comm, MPI_Group *failedgrp);
-int PMPIX_Comm_revoke(MPI_Comm comm);
-int PMPIX_Comm_shrink(MPI_Comm comm, MPI_Comm *newcomm);
-int PMPIX_Comm_agree(MPI_Comm comm, int *flag);
+int PMPIX_Comm_failure_ack(MPI_Comm comm) MPICH_API_PUBLIC;
+int PMPIX_Comm_failure_get_acked(MPI_Comm comm, MPI_Group *failedgrp) MPICH_API_PUBLIC;
+int PMPIX_Comm_revoke(MPI_Comm comm) MPICH_API_PUBLIC;
+int PMPIX_Comm_shrink(MPI_Comm comm, MPI_Comm *newcomm) MPICH_API_PUBLIC;
+int PMPIX_Comm_agree(MPI_Comm comm, int *flag) MPICH_API_PUBLIC;
 
 #endif  /* MPI_BUILD_PROFILING */
 /* End of MPI bindings */
@@ -2240,23 +2250,23 @@ int MPIX_Grequest_class_create(MPI_Grequest_query_function *query_fn,
                                MPI_Grequest_cancel_function *cancel_fn,
                                MPIX_Grequest_poll_function *poll_fn,
                                MPIX_Grequest_wait_function *wait_fn,
-                               MPIX_Grequest_class *greq_class);
+                               MPIX_Grequest_class *greq_class) MPICH_API_PUBLIC;
 int MPIX_Grequest_class_allocate(MPIX_Grequest_class greq_class, void *extra_state,
-                                 MPI_Request *request);
+                                 MPI_Request *request) MPICH_API_PUBLIC;
 int MPIX_Grequest_start(MPI_Grequest_query_function *query_fn,
                         MPI_Grequest_free_function *free_fn,
                         MPI_Grequest_cancel_function *cancel_fn,
                         MPIX_Grequest_poll_function *poll_fn,
                         MPIX_Grequest_wait_function *wait_fn, void *extra_state,
-                        MPI_Request *request);
+                        MPI_Request *request) MPICH_API_PUBLIC;
 
 /* RMA Mutexes Extensions */
 struct mpixi_mutex_s;
 typedef struct mpixi_mutex_s * MPIX_Mutex;
-int MPIX_Mutex_create(int count, MPI_Comm comm, MPIX_Mutex *hdl);
-int MPIX_Mutex_free(MPIX_Mutex *hdl);
-int MPIX_Mutex_lock(MPIX_Mutex hdl, int mutex, int proc);
-int MPIX_Mutex_unlock(MPIX_Mutex hdl, int mutex, int proc);
+int MPIX_Mutex_create(int count, MPI_Comm comm, MPIX_Mutex *hdl) MPICH_API_PUBLIC;
+int MPIX_Mutex_free(MPIX_Mutex *hdl) MPICH_API_PUBLIC;
+int MPIX_Mutex_lock(MPIX_Mutex hdl, int mutex, int proc) MPICH_API_PUBLIC;
+int MPIX_Mutex_unlock(MPIX_Mutex hdl, int mutex, int proc) MPICH_API_PUBLIC;
 
 
 #if !defined(MPI_BUILD_PROFILING)
@@ -2266,21 +2276,21 @@ int PMPIX_Grequest_class_create(MPI_Grequest_query_function *query_fn,
                                 MPI_Grequest_cancel_function *cancel_fn,
                                 MPIX_Grequest_poll_function *poll_fn,
                                 MPIX_Grequest_wait_function *wait_fn,
-                                MPIX_Grequest_class *greq_class);
+                                MPIX_Grequest_class *greq_class) MPICH_API_PUBLIC;
 int PMPIX_Grequest_class_allocate(MPIX_Grequest_class greq_class, void *extra_state,
-                                  MPI_Request *request);
+                                  MPI_Request *request) MPICH_API_PUBLIC;
 int PMPIX_Grequest_start(MPI_Grequest_query_function *query_fn,
                          MPI_Grequest_free_function *free_fn,
                          MPI_Grequest_cancel_function *cancel_fn,
                          MPIX_Grequest_poll_function *poll_fn,
                          MPIX_Grequest_wait_function *wait_fn, void *extra_state,
-                         MPI_Request *request);
+                         MPI_Request *request) MPICH_API_PUBLIC;
 
 /* RMA Mutexes Extensions */
-int PMPIX_Mutex_create(int count, MPI_Comm comm, MPIX_Mutex *hdl);
-int PMPIX_Mutex_free(MPIX_Mutex *hdl);
-int PMPIX_Mutex_lock(MPIX_Mutex hdl, int mutex, int proc);
-int PMPIX_Mutex_unlock(MPIX_Mutex hdl, int mutex, int proc);
+int PMPIX_Mutex_create(int count, MPI_Comm comm, MPIX_Mutex *hdl) MPICH_API_PUBLIC;
+int PMPIX_Mutex_free(MPIX_Mutex *hdl) MPICH_API_PUBLIC;
+int PMPIX_Mutex_lock(MPIX_Mutex hdl, int mutex, int proc) MPICH_API_PUBLIC;
+int PMPIX_Mutex_unlock(MPIX_Mutex hdl, int mutex, int proc) MPICH_API_PUBLIC;
 #endif /* MPI_BUILD_PROFILING */
 
 #endif
diff --git a/linx64/mpi/mpich/include/mpio.h b/linx64/mpi/mpich/include/mpio.h
index 6b76a66d..e057dd93 100644
--- a/linx64/mpi/mpich/include/mpio.h
+++ b/linx64/mpi/mpich/include/mpio.h
@@ -12,6 +12,12 @@
 
 #include "mpi.h"
 
+#if defined(HAVE_VISIBILITY)
+#define ROMIO_API_PUBLIC __attribute__((visibility ("default")))
+#else
+#define ROMIO_API_PUBLIC
+#endif
+
 #if defined(__cplusplus)
 extern "C" {
 #endif
@@ -24,7 +30,9 @@ extern "C" {
 typedef struct ADIOI_FileD *MPI_File;
 #endif
 
+/* *INDENT-OFF* */
 #define HAVE_MPI_GREQUEST 1
+/* *INDENT-ON* */
 #ifndef HAVE_MPI_GREQUEST
 typedef struct ADIOI_RequestD *MPIO_Request;  
 #else
@@ -39,7 +47,9 @@ typedef struct ADIOI_RequestD *MPIO_Request;
 #define MPIO_REQUEST_DEFINED
 
 #ifndef HAVE_MPI_OFFSET
+/* *INDENT-OFF* */
 typedef long long MPI_Offset;
+/* *INDENT-ON* */
 /* If we needed to define MPI_Offset, then we also need to make
    this definition. */
 #ifndef HAVE_MPI_DATAREP_FUNCTIONS
@@ -52,14 +62,18 @@ typedef int (MPI_Datarep_extent_function)(MPI_Datatype datatype, MPI_Aint *,
 #endif
 
 #ifndef NEEDS_MPI_FINT
+/* *INDENT-OFF* */
 
+/* *INDENT-ON* */
 #endif
 #ifdef NEEDS_MPI_FINT
 typedef int MPI_Fint; 
 #endif
 
 #ifndef HAVE_MPI_INFO
+/* *INDENT-OFF* */
 #define HAVE_MPI_INFO
+/* *INDENT-ON* */
 #endif
 #ifndef HAVE_MPI_INFO
   typedef struct MPIR_Info *MPI_Info;
@@ -99,7 +113,9 @@ typedef int MPI_Fint;
 #endif
 
 #ifndef HAVE_MPI_DARRAY_SUBARRAY
+/* *INDENT-OFF* */
 #define HAVE_MPI_DARRAY_SUBARRAY
+/* *INDENT-ON* */
 #endif
 #ifndef HAVE_MPI_DARRAY_SUBARRAY
 #  define MPI_ORDER_C             56
@@ -120,150 +136,150 @@ typedef int MPI_Fint;
 
 /* Section 9.2 */
 /* Begin Prototypes */
-int MPI_File_open(MPI_Comm comm, const char *filename, int amode, MPI_Info info, MPI_File *fh);
-int MPI_File_close(MPI_File *fh);
-int MPI_File_delete(const char *filename, MPI_Info info);
-int MPI_File_set_size(MPI_File fh, MPI_Offset size);
-int MPI_File_preallocate(MPI_File fh, MPI_Offset size);
-int MPI_File_get_size(MPI_File fh, MPI_Offset *size);
-int MPI_File_get_group(MPI_File fh, MPI_Group *group);
-int MPI_File_get_amode(MPI_File fh, int *amode);
-int MPI_File_set_info(MPI_File fh, MPI_Info info);
-int MPI_File_get_info(MPI_File fh, MPI_Info *info_used);
+int MPI_File_open(MPI_Comm comm, const char *filename, int amode, MPI_Info info, MPI_File *fh) ROMIO_API_PUBLIC;
+int MPI_File_close(MPI_File *fh) ROMIO_API_PUBLIC;
+int MPI_File_delete(const char *filename, MPI_Info info) ROMIO_API_PUBLIC;
+int MPI_File_set_size(MPI_File fh, MPI_Offset size) ROMIO_API_PUBLIC;
+int MPI_File_preallocate(MPI_File fh, MPI_Offset size) ROMIO_API_PUBLIC;
+int MPI_File_get_size(MPI_File fh, MPI_Offset *size) ROMIO_API_PUBLIC;
+int MPI_File_get_group(MPI_File fh, MPI_Group *group) ROMIO_API_PUBLIC;
+int MPI_File_get_amode(MPI_File fh, int *amode) ROMIO_API_PUBLIC;
+int MPI_File_set_info(MPI_File fh, MPI_Info info) ROMIO_API_PUBLIC;
+int MPI_File_get_info(MPI_File fh, MPI_Info *info_used) ROMIO_API_PUBLIC;
 
 /* Section 9.3 */
 int MPI_File_set_view(MPI_File fh, MPI_Offset disp, MPI_Datatype etype, MPI_Datatype filetype,
-                      const char *datarep, MPI_Info info);
+                      const char *datarep, MPI_Info info) ROMIO_API_PUBLIC;
 int MPI_File_get_view(MPI_File fh, MPI_Offset *disp, MPI_Datatype *etype, MPI_Datatype *filetype,
-                      char *datarep);
+                      char *datarep) ROMIO_API_PUBLIC;
 
 /* Section 9.4.2 */
 int MPI_File_read_at(MPI_File fh, MPI_Offset offset, void *buf, int count, MPI_Datatype datatype,
-                     MPI_Status *status) MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5);
+                     MPI_Status *status) MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5) ROMIO_API_PUBLIC;
 int MPI_File_read_at_all(MPI_File fh, MPI_Offset offset, void * buf, int count,
                          MPI_Datatype datatype, MPI_Status *status)
-    MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5);
+    MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5) ROMIO_API_PUBLIC;
 int MPI_File_write_at(MPI_File fh, MPI_Offset offset, const void * buf, int count,
                       MPI_Datatype datatype, MPI_Status *status)
-    MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5);
+    MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5) ROMIO_API_PUBLIC;
 int MPI_File_write_at_all(MPI_File fh, MPI_Offset offset, const void *buf, int count,
                           MPI_Datatype datatype, MPI_Status *status)
-    MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5);
+    MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5) ROMIO_API_PUBLIC;
 
 /* nonblocking calls currently use MPIO_Request, because generalized
    requests not yet implemented. For the same reason, MPIO_Test and 
    MPIO_Wait are used to test and wait on nonblocking I/O requests */ 
 int MPI_File_iread_at(MPI_File fh, MPI_Offset offset, void *buf, int count, MPI_Datatype datatype,
-                      MPIO_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5);
+                      MPIO_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5) ROMIO_API_PUBLIC;
 int MPI_File_iwrite_at(MPI_File fh, MPI_Offset offset, const void *buf, int count,
                        MPI_Datatype datatype, MPIO_Request *request)
-    MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5);
+    MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5) ROMIO_API_PUBLIC;
 
 /* Section 9.4.3 */
 int MPI_File_read(MPI_File fh, void *buf, int count, MPI_Datatype datatype, MPI_Status *status)
-    MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+    MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
 int MPI_File_read_all(MPI_File fh, void *buf, int count, MPI_Datatype datatype, MPI_Status *status)
-    MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+    MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
 int MPI_File_write(MPI_File fh, const void *buf, int count, MPI_Datatype datatype,
-                   MPI_Status *status) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                   MPI_Status *status) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
 int MPI_File_write_all(MPI_File fh, const void *buf, int count, MPI_Datatype datatype,
-                       MPI_Status *status) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                       MPI_Status *status) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
 
 /* nonblocking calls currently use MPIO_Request, because generalized
    requests not yet implemented. For the same reason, MPIO_Test and 
    MPIO_Wait are used to test and wait on nonblocking I/O requests */ 
 
 int MPI_File_iread(MPI_File fh, void *buf, int count, MPI_Datatype datatype, MPIO_Request *request)
-    MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+    MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
 int MPI_File_iwrite(MPI_File fh, const void *buf, int count, MPI_Datatype datatype,
-                    MPIO_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                    MPIO_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
 
-int MPI_File_seek(MPI_File fh, MPI_Offset offset, int whence);
-int MPI_File_get_position(MPI_File fh, MPI_Offset *offset);
-int MPI_File_get_byte_offset(MPI_File fh, MPI_Offset offset, MPI_Offset *disp);
+int MPI_File_seek(MPI_File fh, MPI_Offset offset, int whence) ROMIO_API_PUBLIC;
+int MPI_File_get_position(MPI_File fh, MPI_Offset *offset) ROMIO_API_PUBLIC;
+int MPI_File_get_byte_offset(MPI_File fh, MPI_Offset offset, MPI_Offset *disp) ROMIO_API_PUBLIC;
 
 /* Section 9.4.4 */
 int MPI_File_read_shared(MPI_File fh, void *buf, int count, MPI_Datatype datatype,
-                         MPI_Status *status) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                         MPI_Status *status) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
 int MPI_File_write_shared(MPI_File fh, const void *buf, int count, MPI_Datatype datatype,
-                          MPI_Status *status) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                          MPI_Status *status) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
 int MPI_File_iread_shared(MPI_File fh, void *buf, int count, MPI_Datatype datatype,
-                          MPIO_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                          MPIO_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
 int MPI_File_iwrite_shared(MPI_File fh, const void *buf, int count, MPI_Datatype datatype,
-                           MPIO_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                           MPIO_Request *request) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
 int MPI_File_read_ordered(MPI_File fh, void *buf, int count, MPI_Datatype datatype,
-                          MPI_Status *status) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                          MPI_Status *status) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
 int MPI_File_write_ordered(MPI_File fh, const void *buf, int count, MPI_Datatype datatype,
-                           MPI_Status *status) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
-int MPI_File_seek_shared(MPI_File fh, MPI_Offset offset, int whence);
-int MPI_File_get_position_shared(MPI_File fh, MPI_Offset *offset);
+                           MPI_Status *status) MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
+int MPI_File_seek_shared(MPI_File fh, MPI_Offset offset, int whence) ROMIO_API_PUBLIC;
+int MPI_File_get_position_shared(MPI_File fh, MPI_Offset *offset) ROMIO_API_PUBLIC;
 
 /* Section 9.4.5 */
 int MPI_File_read_at_all_begin(MPI_File fh, MPI_Offset offset, void *buf, int count,
-                               MPI_Datatype datatype) MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5);
-int MPI_File_read_at_all_end(MPI_File fh, void *buf, MPI_Status *status);
+                               MPI_Datatype datatype) MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5) ROMIO_API_PUBLIC;
+int MPI_File_read_at_all_end(MPI_File fh, void *buf, MPI_Status *status) ROMIO_API_PUBLIC;
 int MPI_File_write_at_all_begin(MPI_File fh, MPI_Offset offset, const void *buf, int count,
-                                MPI_Datatype datatype) MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5);
-int MPI_File_write_at_all_end(MPI_File fh, const void *buf, MPI_Status *status);
+                                MPI_Datatype datatype) MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5) ROMIO_API_PUBLIC;
+int MPI_File_write_at_all_end(MPI_File fh, const void *buf, MPI_Status *status) ROMIO_API_PUBLIC;
 int MPI_File_read_all_begin(MPI_File fh, void *buf, int count, MPI_Datatype datatype)
-    MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
-int MPI_File_read_all_end(MPI_File fh, void *buf, MPI_Status *status);
+    MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
+int MPI_File_read_all_end(MPI_File fh, void *buf, MPI_Status *status) ROMIO_API_PUBLIC;
 int MPI_File_write_all_begin(MPI_File fh, const void *buf, int count, MPI_Datatype datatype)
-    MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
-int MPI_File_write_all_end(MPI_File fh, const void *buf, MPI_Status *status);
+    MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
+int MPI_File_write_all_end(MPI_File fh, const void *buf, MPI_Status *status) ROMIO_API_PUBLIC;
 int MPI_File_read_ordered_begin(MPI_File fh, void *buf, int count, MPI_Datatype datatype)
-    MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
-int MPI_File_read_ordered_end(MPI_File fh, void *buf, MPI_Status *status);
+    MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
+int MPI_File_read_ordered_end(MPI_File fh, void *buf, MPI_Status *status) ROMIO_API_PUBLIC;
 int MPI_File_write_ordered_begin(MPI_File fh, const void *buf, int count, MPI_Datatype datatype)
-    MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
-int MPI_File_write_ordered_end(MPI_File fh, const void *buf, MPI_Status *status);
+    MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
+int MPI_File_write_ordered_end(MPI_File fh, const void *buf, MPI_Status *status) ROMIO_API_PUBLIC;
 
 /* Section 9.5.1 */
-int MPI_File_get_type_extent(MPI_File fh, MPI_Datatype datatype, MPI_Aint *extent);
+int MPI_File_get_type_extent(MPI_File fh, MPI_Datatype datatype, MPI_Aint *extent) ROMIO_API_PUBLIC;
 
 /* Section 9.5.3 */
 int MPI_Register_datarep(const char *datarep, MPI_Datarep_conversion_function *read_conversion_fn,
 			 MPI_Datarep_conversion_function *write_conversion_fn,
-			 MPI_Datarep_extent_function *dtype_file_extent_fn, void *extra_state);
+			 MPI_Datarep_extent_function *dtype_file_extent_fn, void *extra_state) ROMIO_API_PUBLIC;
 
 /* Section 9.6.1 */
-int MPI_File_set_atomicity(MPI_File fh, int flag);
-int MPI_File_get_atomicity(MPI_File fh, int *flag);
-int MPI_File_sync(MPI_File fh);
+int MPI_File_set_atomicity(MPI_File fh, int flag) ROMIO_API_PUBLIC;
+int MPI_File_get_atomicity(MPI_File fh, int *flag) ROMIO_API_PUBLIC;
+int MPI_File_sync(MPI_File fh) ROMIO_API_PUBLIC;
 
 /* Section 4.13.3 */
 #ifndef MPICH
 /* MPICH provides these definitions */
-int MPI_File_set_errhandler(MPI_File file, MPI_Errhandler errhandler);
-int MPI_File_get_errhandler(MPI_File file, MPI_Errhandler *errhandler);
+int MPI_File_set_errhandler(MPI_File file, MPI_Errhandler errhandler) ROMIO_API_PUBLIC;
+int MPI_File_get_errhandler(MPI_File file, MPI_Errhandler *errhandler) ROMIO_API_PUBLIC;
 #endif
 
 /* For MPI 3.1 */
 int MPI_File_iread_at_all(MPI_File fh, MPI_Offset offset, void *buf, int count,
                            MPI_Datatype datatype, MPI_Request *request)
-    MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5);
+    MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5) ROMIO_API_PUBLIC;
 int MPI_File_iwrite_at_all(MPI_File fh, MPI_Offset offset, const void *buf, int count,
                             MPI_Datatype datatype, MPI_Request *request)
-    MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5);
+    MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5) ROMIO_API_PUBLIC;
 int MPI_File_iread_all(MPI_File fh, void *buf, int count, MPI_Datatype datatype,
                         MPI_Request *request)
-    MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+    MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
 int MPI_File_iwrite_all(MPI_File fh, const void *buf, int count, MPI_Datatype datatype,
                          MPI_Request *request)
-    MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+    MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
 /* End Prototypes */
 
 #ifndef HAVE_MPI_DARRAY_SUBARRAY
 /* Section 4.14.4 */
 int MPI_Type_create_subarray(int ndims, const int array_of_sizes[], const int array_of_subsizes[],
                              const int array_of_starts[], int order, MPI_Datatype oldtype,
-                             MPI_Datatype *newtype);
+                             MPI_Datatype *newtype) ROMIO_API_PUBLIC;
 
 /* Section 4.14.5 */
 int MPI_Type_create_darray(int size, int rank, int ndims, const int array_of_gsizes[],
                            const int array_of_distribs[], const int array_of_dargs[],
                            const int array_of_psizes, int order, MPI_Datatype oldtype,
-                           MPI_Datatype *newtype);
+                           MPI_Datatype *newtype) ROMIO_API_PUBLIC;
 #endif
 
 /* The globus2 device has to rename MPI_ symbols in order to use the vendor
@@ -279,43 +295,43 @@ int MPI_Type_create_darray(int size, int rank, int ndims, const int array_of_gsi
 #endif
 #endif
 /* above needed for some versions of mpi.h in MPICH!! */
-MPI_File MPI_File_f2c(MPI_Fint file);
-MPI_Fint MPI_File_c2f(MPI_File file);
+MPI_File MPI_File_f2c(MPI_Fint file) ROMIO_API_PUBLIC;
+MPI_Fint MPI_File_c2f(MPI_File file) ROMIO_API_PUBLIC;
 
 
 #ifndef HAVE_MPI_GREQUEST
 /* The following functions are required if generalized requests are not
    available, because in that case, an MPIO_Request object
    is currently used for nonblocking I/O. */
-int MPIO_Test(MPIO_Request *request, int *flag, MPI_Status *status);
-int MPIO_Wait(MPIO_Request *request, MPI_Status *status);
+int MPIO_Test(MPIO_Request *request, int *flag, MPI_Status *status) ROMIO_API_PUBLIC;
+int MPIO_Wait(MPIO_Request *request, MPI_Status *status) ROMIO_API_PUBLIC;
 int MPIO_Testall(int count, MPIO_Request array_of_requests[], int *flag,
-                 MPI_Status array_of_statuses[]);
-int MPIO_Waitall(int count, MPIO_Request array_of_requests[], MPI_Status array_of_statuses[]);
+                 MPI_Status array_of_statuses[]) ROMIO_API_PUBLIC;
+int MPIO_Waitall(int count, MPIO_Request array_of_requests[], MPI_Status array_of_statuses[]) ROMIO_API_PUBLIC;
 int MPIO_Testany(int count, MPIO_Request array_of_requests[], int *indx, int *flag,
-                 MPI_Status *status);
-int MPIO_Waitany(int count, MPIO_Request array_of_requests[], int *indx, MPI_Status *status);
+                 MPI_Status *status) ROMIO_API_PUBLIC;
+int MPIO_Waitany(int count, MPIO_Request array_of_requests[], int *indx, MPI_Status *status) ROMIO_API_PUBLIC;
 int MPIO_Waitsome(int incount, MPIO_Request array_of_requests[], int *outcount,
-                  int array_of_indices[], MPI_Status array_of_statuses[]);
+                  int array_of_indices[], MPI_Status array_of_statuses[]) ROMIO_API_PUBLIC;
 int MPIO_Testsome(int incount, MPIO_Request array_of_requests[], int *outcount,
-                  int array_of_indices[], MPI_Status array_of_statuses[]);
+                  int array_of_indices[], MPI_Status array_of_statuses[]) ROMIO_API_PUBLIC;
 
-MPI_Fint MPIO_Request_c2f(MPIO_Request request);
-MPIO_Request MPIO_Request_f2c(MPI_Fint request);
+MPI_Fint MPIO_Request_c2f(MPIO_Request request) ROMIO_API_PUBLIC;
+MPIO_Request MPIO_Request_f2c(MPI_Fint request) ROMIO_API_PUBLIC;
 #endif /* HAVE_MPI_GREQUEST */
 
 /* info functions if not defined in the MPI implementation */
 #ifndef HAVE_MPI_INFO
 
-int MPI_Info_create(MPI_Info *info);
-int MPI_Info_set(MPI_Info info, const char *key, const char *value);
-int MPI_Info_delete(MPI_Info info, const char *key);
-int MPI_Info_get(MPI_Info info, const char *key, int valuelen, char *value, int *flag);
-int MPI_Info_get_valuelen(MPI_Info info, const char *key, int *valuelen, int *flag);
-int MPI_Info_get_nkeys(MPI_Info info, int *nkeys);
-int MPI_Info_get_nthkey(MPI_Info info, int n, char *key);
-int MPI_Info_dup(MPI_Info info, MPI_Info *newinfo);
-int MPI_Info_free(MPI_Info *info);
+int MPI_Info_create(MPI_Info *info) ROMIO_API_PUBLIC;
+int MPI_Info_set(MPI_Info info, const char *key, const char *value) ROMIO_API_PUBLIC;
+int MPI_Info_delete(MPI_Info info, const char *key) ROMIO_API_PUBLIC;
+int MPI_Info_get(MPI_Info info, const char *key, int valuelen, char *value, int *flag) ROMIO_API_PUBLIC;
+int MPI_Info_get_valuelen(MPI_Info info, const char *key, int *valuelen, int *flag) ROMIO_API_PUBLIC;
+int MPI_Info_get_nkeys(MPI_Info info, int *nkeys) ROMIO_API_PUBLIC;
+int MPI_Info_get_nthkey(MPI_Info info, int n, char *key) ROMIO_API_PUBLIC;
+int MPI_Info_dup(MPI_Info info, MPI_Info *newinfo) ROMIO_API_PUBLIC;
+int MPI_Info_free(MPI_Info *info) ROMIO_API_PUBLIC;
 
 /* The globus2 device has to rename MPI_ symbols in order to use the vendor
    MPI as one of its transport mechanisms.  Therefore, the following undefines
@@ -329,8 +345,8 @@ int MPI_Info_free(MPI_Info *info);
 #endif
 #endif
 /* above needed for some versions of mpi.h in MPICH!! */
-MPI_Fint MPI_Info_c2f(MPI_Info info);
-MPI_Info MPI_Info_f2c(MPI_Fint info);
+MPI_Fint MPI_Info_c2f(MPI_Info info) ROMIO_API_PUBLIC;
+MPI_Info MPI_Info_f2c(MPI_Fint info) ROMIO_API_PUBLIC;
 #endif
 
 #endif   /* HAVE_PRAGMA_HP_SEC_DEF */
@@ -340,36 +356,36 @@ MPI_Info MPI_Info_f2c(MPI_Fint info);
 
 
 /* Section 9.2 */
-int PMPI_File_open(MPI_Comm, const char *, int, MPI_Info, MPI_File *);
-int PMPI_File_close(MPI_File *);
-int PMPI_File_delete(const char *, MPI_Info);
-int PMPI_File_set_size(MPI_File, MPI_Offset);
-int PMPI_File_preallocate(MPI_File, MPI_Offset);
-int PMPI_File_get_size(MPI_File, MPI_Offset *);
-int PMPI_File_get_group(MPI_File, MPI_Group *);
-int PMPI_File_get_amode(MPI_File, int *);
-int PMPI_File_set_info(MPI_File, MPI_Info);
-int PMPI_File_get_info(MPI_File, MPI_Info *);
+int PMPI_File_open(MPI_Comm, const char *, int, MPI_Info, MPI_File *) ROMIO_API_PUBLIC;
+int PMPI_File_close(MPI_File *) ROMIO_API_PUBLIC;
+int PMPI_File_delete(const char *, MPI_Info) ROMIO_API_PUBLIC;
+int PMPI_File_set_size(MPI_File, MPI_Offset) ROMIO_API_PUBLIC;
+int PMPI_File_preallocate(MPI_File, MPI_Offset) ROMIO_API_PUBLIC;
+int PMPI_File_get_size(MPI_File, MPI_Offset *) ROMIO_API_PUBLIC;
+int PMPI_File_get_group(MPI_File, MPI_Group *) ROMIO_API_PUBLIC;
+int PMPI_File_get_amode(MPI_File, int *) ROMIO_API_PUBLIC;
+int PMPI_File_set_info(MPI_File, MPI_Info) ROMIO_API_PUBLIC;
+int PMPI_File_get_info(MPI_File, MPI_Info *) ROMIO_API_PUBLIC;
 
 /* Section 9.3 */
 int PMPI_File_set_view(MPI_File, MPI_Offset, 
-    MPI_Datatype, MPI_Datatype, const char *, MPI_Info);
+    MPI_Datatype, MPI_Datatype, const char *, MPI_Info) ROMIO_API_PUBLIC;
 int PMPI_File_get_view(MPI_File, MPI_Offset *, 
-      MPI_Datatype *, MPI_Datatype *, char *);
+      MPI_Datatype *, MPI_Datatype *, char *) ROMIO_API_PUBLIC;
 
 /* Section 9.4.2 */
 int PMPI_File_read_at(MPI_File, MPI_Offset, void *,
 	      int, MPI_Datatype, MPI_Status *)
-              MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5);
+              MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5) ROMIO_API_PUBLIC;
 int PMPI_File_read_at_all(MPI_File, MPI_Offset, void *,
 	      int, MPI_Datatype, MPI_Status *)
-              MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5);
+              MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5) ROMIO_API_PUBLIC;
 int PMPI_File_write_at(MPI_File, MPI_Offset, const void *,
 	      int, MPI_Datatype, MPI_Status *)
-              MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5);
+              MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5) ROMIO_API_PUBLIC;
 int PMPI_File_write_at_all(MPI_File, MPI_Offset, const void *,
 	      int, MPI_Datatype, MPI_Status *)
-              MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5);
+              MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5) ROMIO_API_PUBLIC;
 
 /* nonblocking calls currently use MPIO_Request, because generalized
    requests not yet implemented. For the same reason, MPIO_Test and 
@@ -377,155 +393,155 @@ int PMPI_File_write_at_all(MPI_File, MPI_Offset, const void *,
 
 int PMPI_File_iread_at(MPI_File, MPI_Offset, void *,
 	      int, MPI_Datatype, MPIO_Request *)
-              MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5);
+              MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5) ROMIO_API_PUBLIC;
 int PMPI_File_iwrite_at(MPI_File, MPI_Offset, const void *,
 	      int, MPI_Datatype, MPIO_Request *)
-              MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5);
+              MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5) ROMIO_API_PUBLIC;
 
 /* Section 9.4.3 */
 int PMPI_File_read(MPI_File, void *, int, MPI_Datatype, MPI_Status *)
-                   MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                   MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
 int PMPI_File_read_all(MPI_File, void *, int, MPI_Datatype, MPI_Status *)
-                       MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                       MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
 int PMPI_File_write(MPI_File, const void *, int, MPI_Datatype, MPI_Status *)
-                    MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                    MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
 int PMPI_File_write_all(MPI_File, const void *, int, MPI_Datatype, MPI_Status *)
-                        MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                        MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
 
 /* nonblocking calls currently use MPIO_Request, because generalized
    requests not yet implemented. For the same reason, MPIO_Test and 
    MPIO_Wait are used to test and wait on nonblocking I/O requests */ 
 
 int PMPI_File_iread(MPI_File, void *, int, MPI_Datatype, MPIO_Request *)
-                    MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                    MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
 int PMPI_File_iwrite(MPI_File, const void *, int, MPI_Datatype, MPIO_Request *)
-                     MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                     MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
 
-int PMPI_File_seek(MPI_File, MPI_Offset, int);
-int PMPI_File_get_position(MPI_File, MPI_Offset *);
-int PMPI_File_get_byte_offset(MPI_File, MPI_Offset, MPI_Offset *);
+int PMPI_File_seek(MPI_File, MPI_Offset, int) ROMIO_API_PUBLIC;
+int PMPI_File_get_position(MPI_File, MPI_Offset *) ROMIO_API_PUBLIC;
+int PMPI_File_get_byte_offset(MPI_File, MPI_Offset, MPI_Offset *) ROMIO_API_PUBLIC;
 
 /* Section 9.4.4 */
 int PMPI_File_read_shared(MPI_File, void *, int, MPI_Datatype, MPI_Status *)
-                          MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                          MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
 int PMPI_File_write_shared(MPI_File, const void *, int, MPI_Datatype, MPI_Status *)
-                           MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                           MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
 int PMPI_File_iread_shared(MPI_File, void *, int, 
 			   MPI_Datatype, MPIO_Request *)
-                           MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                           MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
 int PMPI_File_iwrite_shared(MPI_File, const void *, int,
 			    MPI_Datatype, MPIO_Request *)
-                            MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                            MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
 int PMPI_File_read_ordered(MPI_File, void *, int, MPI_Datatype, MPI_Status *)
-                           MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+                           MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
 int PMPI_File_write_ordered(MPI_File, const void *, int, MPI_Datatype, MPI_Status *)
-                            MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
-int PMPI_File_seek_shared(MPI_File, MPI_Offset, int);
-int PMPI_File_get_position_shared(MPI_File, MPI_Offset *);
+                            MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
+int PMPI_File_seek_shared(MPI_File, MPI_Offset, int) ROMIO_API_PUBLIC;
+int PMPI_File_get_position_shared(MPI_File, MPI_Offset *) ROMIO_API_PUBLIC;
 
 /* Section 9.4.5 */
 int PMPI_File_read_at_all_begin(MPI_File, MPI_Offset, void *,
                                int, MPI_Datatype)
-                               MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5);
-int PMPI_File_read_at_all_end(MPI_File, void *, MPI_Status *);
+                               MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5) ROMIO_API_PUBLIC;
+int PMPI_File_read_at_all_end(MPI_File, void *, MPI_Status *) ROMIO_API_PUBLIC;
 int PMPI_File_write_at_all_begin(MPI_File, MPI_Offset, const void *,
                                  int, MPI_Datatype)
-                                 MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5);
-int PMPI_File_write_at_all_end(MPI_File, const void *, MPI_Status *);
+                                 MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5) ROMIO_API_PUBLIC;
+int PMPI_File_write_at_all_end(MPI_File, const void *, MPI_Status *) ROMIO_API_PUBLIC;
 int PMPI_File_read_all_begin(MPI_File, void *, int, MPI_Datatype)
-                             MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
-int PMPI_File_read_all_end(MPI_File, void *, MPI_Status *);
+                             MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
+int PMPI_File_read_all_end(MPI_File, void *, MPI_Status *) ROMIO_API_PUBLIC;
 int PMPI_File_write_all_begin(MPI_File, const void *, int, MPI_Datatype)
-                              MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
-int PMPI_File_write_all_end(MPI_File, const void *, MPI_Status *);
+                              MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
+int PMPI_File_write_all_end(MPI_File, const void *, MPI_Status *) ROMIO_API_PUBLIC;
 int PMPI_File_read_ordered_begin(MPI_File, void *, int, MPI_Datatype)
-                                 MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
-int PMPI_File_read_ordered_end(MPI_File, void *, MPI_Status *);
+                                 MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
+int PMPI_File_read_ordered_end(MPI_File, void *, MPI_Status *) ROMIO_API_PUBLIC;
 int PMPI_File_write_ordered_begin(MPI_File, const void *, int, MPI_Datatype)
-                                  MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
-int PMPI_File_write_ordered_end(MPI_File, const void *, MPI_Status *);
+                                  MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
+int PMPI_File_write_ordered_end(MPI_File, const void *, MPI_Status *) ROMIO_API_PUBLIC;
 
 /* Section 9.5.1 */
-int PMPI_File_get_type_extent(MPI_File, MPI_Datatype, MPI_Aint *);
+int PMPI_File_get_type_extent(MPI_File, MPI_Datatype, MPI_Aint *) ROMIO_API_PUBLIC;
 
 /* Section 9.5.3 */
 int PMPI_Register_datarep(const char *,
 			 MPI_Datarep_conversion_function *,
 			 MPI_Datarep_conversion_function *,
 			 MPI_Datarep_extent_function *,
-			 void *);
+			 void *) ROMIO_API_PUBLIC;
 
 /* Section 9.6.1 */
-int PMPI_File_set_atomicity(MPI_File, int);
-int PMPI_File_get_atomicity(MPI_File, int *);
-int PMPI_File_sync(MPI_File);
+int PMPI_File_set_atomicity(MPI_File, int) ROMIO_API_PUBLIC;
+int PMPI_File_get_atomicity(MPI_File, int *) ROMIO_API_PUBLIC;
+int PMPI_File_sync(MPI_File) ROMIO_API_PUBLIC;
 
 /* Section 4.13.3 */
 #ifndef MPICH
 /* MPICH provides these definitions */
-int PMPI_File_set_errhandler( MPI_File, MPI_Errhandler );
-int PMPI_File_get_errhandler( MPI_File, MPI_Errhandler * );
+int PMPI_File_set_errhandler( MPI_File, MPI_Errhandler ) ROMIO_API_PUBLIC;
+int PMPI_File_get_errhandler( MPI_File, MPI_Errhandler * ) ROMIO_API_PUBLIC;
 #endif
 
 /* For MPI 3.1 */
 int PMPI_File_iread_at_all(MPI_File fh, MPI_Offset offset, void *buf, int count,
                             MPI_Datatype datatype, MPI_Request *request)
-    MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5);
+    MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5) ROMIO_API_PUBLIC;
 int PMPI_File_iwrite_at_all(MPI_File fh, MPI_Offset offset, const void *buf, int count,
                              MPI_Datatype datatype, MPI_Request *request)
-    MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5);
+    MPICH_ATTR_POINTER_WITH_TYPE_TAG(3,5) ROMIO_API_PUBLIC;
 int PMPI_File_iread_all(MPI_File fh, void *buf, int count, MPI_Datatype datatype,
                          MPI_Request *request)
-    MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+    MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
 int PMPI_File_iwrite_all(MPI_File fh, const void *buf, int count, MPI_Datatype datatype,
                           MPI_Request *request)
-    MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4);
+    MPICH_ATTR_POINTER_WITH_TYPE_TAG(2,4) ROMIO_API_PUBLIC;
 
 #ifndef HAVE_MPI_DARRAY_SUBARRAY
 /* Section 4.14.4 */
 int PMPI_Type_create_subarray(int, int *, int *, int *, int, 
-                      MPI_Datatype, MPI_Datatype *);
+                      MPI_Datatype, MPI_Datatype *) ROMIO_API_PUBLIC;
 
 /* Section 4.14.5 */
 int PMPI_Type_create_darray(int, int, int, int *, int *, 
-                    int *, int *, int, MPI_Datatype, MPI_Datatype *);
+                    int *, int *, int, MPI_Datatype, MPI_Datatype *) ROMIO_API_PUBLIC;
 #endif
 
 /* Section 4.12.4 */
-MPI_File PMPI_File_f2c(MPI_Fint);
-MPI_Fint PMPI_File_c2f(MPI_File);
+MPI_File PMPI_File_f2c(MPI_Fint) ROMIO_API_PUBLIC;
+MPI_Fint PMPI_File_c2f(MPI_File) ROMIO_API_PUBLIC;
 
 #ifndef HAVE_MPI_GREQUEST
 /* The following functions are required if generalized requests are not
    available, because in that case, an MPIO_Request object
    is currently used for nonblocking I/O. */
-int PMPIO_Test(MPIO_Request *, int *, MPI_Status *);
-int PMPIO_Wait(MPIO_Request *, MPI_Status *);
-int PMPIO_Testall(int, MPIO_Request *, int *, MPI_Status *);
-int PMPIO_Waitall(int, MPIO_Request *, MPI_Status *);
-int PMPIO_Testany(int, MPIO_Request *, int *, int *, MPI_Status *);
-int PMPIO_Waitany(int, MPIO_Request *, int *, MPI_Status *);
-int PMPIO_Waitsome(int, MPIO_Request *, int *, int *, MPI_Status *);
-int PMPIO_Testsome(int, MPIO_Request *, int *, int *, MPI_Status *);
-MPI_Fint PMPIO_Request_c2f(MPIO_Request);
-MPIO_Request PMPIO_Request_f2c(MPI_Fint);
+int PMPIO_Test(MPIO_Request *, int *, MPI_Status *) ROMIO_API_PUBLIC;
+int PMPIO_Wait(MPIO_Request *, MPI_Status *) ROMIO_API_PUBLIC;
+int PMPIO_Testall(int, MPIO_Request *, int *, MPI_Status *) ROMIO_API_PUBLIC;
+int PMPIO_Waitall(int, MPIO_Request *, MPI_Status *) ROMIO_API_PUBLIC;
+int PMPIO_Testany(int, MPIO_Request *, int *, int *, MPI_Status *) ROMIO_API_PUBLIC;
+int PMPIO_Waitany(int, MPIO_Request *, int *, MPI_Status *) ROMIO_API_PUBLIC;
+int PMPIO_Waitsome(int, MPIO_Request *, int *, int *, MPI_Status *) ROMIO_API_PUBLIC;
+int PMPIO_Testsome(int, MPIO_Request *, int *, int *, MPI_Status *) ROMIO_API_PUBLIC;
+MPI_Fint PMPIO_Request_c2f(MPIO_Request) ROMIO_API_PUBLIC;
+MPIO_Request PMPIO_Request_f2c(MPI_Fint) ROMIO_API_PUBLIC;
 #endif /* HAVE_MPI_GREQUEST */
 
 /* info functions if not defined in the MPI implementation */
 #ifndef HAVE_MPI_INFO
 
-int PMPI_Info_create(MPI_Info *);
-int PMPI_Info_set(MPI_Info, char *, char *);
-int PMPI_Info_delete(MPI_Info, char *);
-int PMPI_Info_get(MPI_Info, char *, int, char *, int *);
-int PMPI_Info_get_valuelen(MPI_Info, char *, int *, int *);
-int PMPI_Info_get_nkeys(MPI_Info, int *);
-int PMPI_Info_get_nthkey(MPI_Info, int, char *);
-int PMPI_Info_dup(MPI_Info, MPI_Info *);
-int PMPI_Info_free(MPI_Info *);
+int PMPI_Info_create(MPI_Info *) ROMIO_API_PUBLIC;
+int PMPI_Info_set(MPI_Info, char *, char *) ROMIO_API_PUBLIC;
+int PMPI_Info_delete(MPI_Info, char *) ROMIO_API_PUBLIC;
+int PMPI_Info_get(MPI_Info, char *, int, char *, int *) ROMIO_API_PUBLIC;
+int PMPI_Info_get_valuelen(MPI_Info, char *, int *, int *) ROMIO_API_PUBLIC;
+int PMPI_Info_get_nkeys(MPI_Info, int *) ROMIO_API_PUBLIC;
+int PMPI_Info_get_nthkey(MPI_Info, int, char *) ROMIO_API_PUBLIC;
+int PMPI_Info_dup(MPI_Info, MPI_Info *) ROMIO_API_PUBLIC;
+int PMPI_Info_free(MPI_Info *) ROMIO_API_PUBLIC;
 
-MPI_Fint PMPI_Info_c2f(MPI_Info);
-MPI_Info PMPI_Info_f2c(MPI_Fint);
+MPI_Fint PMPI_Info_c2f(MPI_Info) ROMIO_API_PUBLIC;
+MPI_Info PMPI_Info_f2c(MPI_Fint) ROMIO_API_PUBLIC;
 #endif
 
 #if defined(__cplusplus)
diff --git a/linx64/mpi/mpich/include/opa_config.h b/linx64/mpi/mpich/include/opa_config.h
deleted file mode 100644
index 464c204a..00000000
--- a/linx64/mpi/mpich/include/opa_config.h
+++ /dev/null
@@ -1,241 +0,0 @@
-#ifndef _SRC_OPA_CONFIG_H
-#define _SRC_OPA_CONFIG_H 1
- 
-/* src/opa_config.h. Generated automatically at end of configure. */
-/* src/config.h.  Generated from config.h.in by configure.  */
-/* src/config.h.in.  Generated from configure.ac by autoheader.  */
-
-/* -*- Mode: C; c-basic-offset:4 ; indent-tabs-mode:nil ; -*- */
-/*
- *  (C) 2008 by Argonne National Laboratory.
- *      See COPYRIGHT in top-level directory.
- */
-
-
-/* define if lock-based emulation was explicitly requested at configure time
-   via --with-atomic-primitives=no */
-/* #undef EXPLICIT_EMULATION */
-
-/* Define to 1 if you have the <atomic.h> header file. */
-/* #undef HAVE_ATOMIC_H */
-
-/* Define to 1 if you have the <dlfcn.h> header file. */
-#ifndef OPA_HAVE_DLFCN_H 
-#define OPA_HAVE_DLFCN_H  1 
-#endif
-
-/* define to 1 if we have support for gcc ARM atomics */
-/* #undef HAVE_GCC_AND_ARM_ASM */
-
-/* define to 1 if we have support for gcc ia64 primitives */
-/* #undef HAVE_GCC_AND_IA64_ASM */
-
-/* define to 1 if we have support for gcc PowerPC atomics */
-/* #undef HAVE_GCC_AND_POWERPC_ASM */
-
-/* define to 1 if we have support for gcc SiCortex atomics */
-/* #undef HAVE_GCC_AND_SICORTEX_ASM */
-
-/* Define if GNU __attribute__ is supported */
-#ifndef OPA_HAVE_GCC_ATTRIBUTE 
-#define OPA_HAVE_GCC_ATTRIBUTE  1 
-#endif
-
-/* define to 1 if we have support for gcc atomic intrinsics */
-#ifndef OPA_HAVE_GCC_INTRINSIC_ATOMICS 
-#define OPA_HAVE_GCC_INTRINSIC_ATOMICS  1 
-#endif
-
-/* define to 1 if we have support for gcc x86/x86_64 primitives */
-#ifndef OPA_HAVE_GCC_X86_32_64 
-#define OPA_HAVE_GCC_X86_32_64  1 
-#endif
-
-/* define to 1 if we have support for gcc x86 primitives for pre-Pentium 4 */
-#ifndef OPA_HAVE_GCC_X86_32_64_P3 
-#define OPA_HAVE_GCC_X86_32_64_P3  1 
-#endif
-
-/* Define to 1 if you have the <intrin.h> header file. */
-/* #undef HAVE_INTRIN_H */
-
-/* Define to 1 if you have the <inttypes.h> header file. */
-#ifndef OPA_HAVE_INTTYPES_H 
-#define OPA_HAVE_INTTYPES_H  1 
-#endif
-
-/* Define to 1 if you have the `pthread' library (-lpthread). */
-#ifndef OPA_HAVE_LIBPTHREAD 
-#define OPA_HAVE_LIBPTHREAD  1 
-#endif
-
-/* Define to 1 if you have the <memory.h> header file. */
-#ifndef OPA_HAVE_MEMORY_H 
-#define OPA_HAVE_MEMORY_H  1 
-#endif
-
-/* define to 1 if we have support for Windows NT atomic intrinsics */
-/* #undef HAVE_NT_INTRINSICS */
-
-/* Define to 1 if you have the <pthread.h> header file. */
-#ifndef OPA_HAVE_PTHREAD_H 
-#define OPA_HAVE_PTHREAD_H  1 
-#endif
-
-/* Define to 1 if you have the `pthread_yield' function. */
-#ifndef OPA_HAVE_PTHREAD_YIELD 
-#define OPA_HAVE_PTHREAD_YIELD  1 
-#endif
-
-/* Define to 1 if you have the `sched_yield' function. */
-/* #undef HAVE_SCHED_YIELD */
-
-/* Define to 1 if you have the <stddef.h> header file. */
-#ifndef OPA_HAVE_STDDEF_H 
-#define OPA_HAVE_STDDEF_H  1 
-#endif
-
-/* Define to 1 if you have the <stdint.h> header file. */
-#ifndef OPA_HAVE_STDINT_H 
-#define OPA_HAVE_STDINT_H  1 
-#endif
-
-/* Define to 1 if you have the <stdlib.h> header file. */
-#ifndef OPA_HAVE_STDLIB_H 
-#define OPA_HAVE_STDLIB_H  1 
-#endif
-
-/* Define if strict checking of atomic operation fairness is desired */
-/* #undef HAVE_STRICT_FAIRNESS_CHECKS */
-
-/* Define to 1 if you have the <strings.h> header file. */
-#ifndef OPA_HAVE_STRINGS_H 
-#define OPA_HAVE_STRINGS_H  1 
-#endif
-
-/* Define to 1 if you have the <string.h> header file. */
-#ifndef OPA_HAVE_STRING_H 
-#define OPA_HAVE_STRING_H  1 
-#endif
-
-/* define to 1 if we have support for Sun atomic operations library */
-/* #undef HAVE_SUN_ATOMIC_OPS */
-
-/* Define to 1 if you have the <sys/stat.h> header file. */
-#ifndef OPA_HAVE_SYS_STAT_H 
-#define OPA_HAVE_SYS_STAT_H  1 
-#endif
-
-/* Define to 1 if you have the <sys/types.h> header file. */
-#ifndef OPA_HAVE_SYS_TYPES_H 
-#define OPA_HAVE_SYS_TYPES_H  1 
-#endif
-
-/* Define to 1 if you have the <unistd.h> header file. */
-#ifndef OPA_HAVE_UNISTD_H 
-#define OPA_HAVE_UNISTD_H  1 
-#endif
-
-/* Define to the sub-directory where libtool stores uninstalled libraries. */
-#ifndef OPA_LT_OBJDIR 
-#define OPA_LT_OBJDIR  ".libs/" 
-#endif
-
-/* define to the maximum number of simultaneous threads */
-#ifndef OPA_MAX_NTHREADS 
-#define OPA_MAX_NTHREADS  100 
-#endif
-
-/* Define to 1 if assertions should be disabled. */
-/* #undef NDEBUG */
-
-/* Name of package */
-#ifndef OPA_PACKAGE 
-#define OPA_PACKAGE  "openpa" 
-#endif
-
-/* Define to the address where bug reports for this package should be sent. */
-#ifndef OPA_PACKAGE_BUGREPORT 
-#define OPA_PACKAGE_BUGREPORT  "https://trac.mcs.anl.gov/projects/openpa/newticket" 
-#endif
-
-/* Define to the full name of this package. */
-#ifndef OPA_PACKAGE_NAME 
-#define OPA_PACKAGE_NAME  "OpenPA" 
-#endif
-
-/* Define to the full name and version of this package. */
-#ifndef OPA_PACKAGE_STRING 
-#define OPA_PACKAGE_STRING  "OpenPA 1.0.3" 
-#endif
-
-/* Define to the one symbol short name of this package. */
-#ifndef OPA_PACKAGE_TARNAME 
-#define OPA_PACKAGE_TARNAME  "openpa" 
-#endif
-
-/* Define to the home page for this package. */
-#ifndef OPA_PACKAGE_URL 
-#define OPA_PACKAGE_URL  "" 
-#endif
-
-/* Define to the version of this package. */
-#ifndef OPA_PACKAGE_VERSION 
-#define OPA_PACKAGE_VERSION  "1.0.3" 
-#endif
-
-/* The size of `int', as computed by sizeof. */
-#ifndef OPA_SIZEOF_INT 
-#define OPA_SIZEOF_INT  4 
-#endif
-
-/* The size of `void *', as computed by sizeof. */
-#ifndef OPA_SIZEOF_VOID_P 
-#define OPA_SIZEOF_VOID_P  8 
-#endif
-
-/* Define to 1 if you have the ANSI C header files. */
-#ifndef OPA_STDC_HEADERS 
-#define OPA_STDC_HEADERS  1 
-#endif
-
-/* define to 1 to force using lock-based atomic primitives */
-/* #undef USE_LOCK_BASED_PRIMITIVES */
-
-/* define to 1 if unsafe (non-atomic) primitives should be used */
-/* #undef USE_UNSAFE_PRIMITIVES */
-
-/* Version number of package */
-#ifndef OPA_VERSION 
-#define OPA_VERSION  "1.0.3" 
-#endif
-
-/* Define to empty if `const' does not conform to ANSI C. */
-/* #undef const */
-
-/* Define to `__inline__' or `__inline' if that's what the C compiler
-   calls it, or to nothing if 'inline' is not supported under any name.  */
-#ifndef __cplusplus
-/* #undef inline */
-#endif
-
-/* Define to the equivalent of the C99 'restrict' keyword, or to
-   nothing if this is not supported.  Do not define if restrict is
-   supported directly.  */
-#ifndef _opa_restrict 
-#define _opa_restrict  __restrict 
-#endif
-/* Work around a bug in Sun C++: it does not support _Restrict or
-   __restrict__, even though the corresponding Sun C compiler ends up with
-   "#define restrict _Restrict" or "#define restrict __restrict__" in the
-   previous line.  Perhaps some future version of Sun C++ will work with
-   restrict; if so, hopefully it defines __RESTRICT like Sun C does.  */
-#if defined __SUNPRO_CC && !defined __RESTRICT
-# define _Restrict
-# define __restrict__
-#endif
-
-
- 
-/* once: _SRC_OPA_CONFIG_H */
-#endif
diff --git a/linx64/mpi/mpich/include/opa_primitives.h b/linx64/mpi/mpich/include/opa_primitives.h
deleted file mode 100644
index 8e5d40b5..00000000
--- a/linx64/mpi/mpich/include/opa_primitives.h
+++ /dev/null
@@ -1,160 +0,0 @@
-/* -*- Mode: C; c-basic-offset:4 ; indent-tabs-mode:nil ; -*- */
-/*  
- *  (C) 2008 by Argonne National Laboratory.
- *      See COPYRIGHT in top-level directory.
- */
-
-#ifndef OPA_PRIMITIVES_H_INCLUDED
-#define OPA_PRIMITIVES_H_INCLUDED
-
-#include "opa_config.h"
-#include "opa_util.h"
-
-/* Clean up some of the opa_config.h definitions.  This is a consequence
-   of using the AX_PREFIX_CONFIG_H macro. Autoconf won't define inline
-   or _opa_inline when a real "inline" works.  Since we are
-   unconditionally using _opa_inline we must define it ourselves in this
-   case. */
-#ifndef _opa_inline
-#define _opa_inline inline
-#endif
-#ifndef _opa_restrict
-#define _opa_restrict restrict
-#endif
-#ifndef _opa_const
-#define _opa_const const
-#endif
-
-/*
-   Primitive atomic functions
-   --------------------------
-
-   The included file is responsible for defining the types of OPA_int_t and
-   OPA_ptr_t as well as a set of functions for operating on these
-   types.  If you have the following declaration:
-
-       OPA_int_t atomic_var;
-
-   Then in order for the emulation functions to compile, the underlying value of
-   atomic_var should be accessible via:
-
-       atomic_var.v;
-
-   The same goes for OPA_ptr_t.
-
-   The atomic functions that must be ported for each architecture: 
-
-   static _opa_inline int   OPA_load_int(_opa_const OPA_int_t *ptr);
-   static _opa_inline void  OPA_store_int(OPA_int_t *ptr, int val);
-   static _opa_inline void *OPA_load_ptr(_opa_const OPA_ptr_t *ptr);
-   static _opa_inline void  OPA_store_ptr(OPA_ptr_t *ptr, void *val);
-
-   static _opa_inline void OPA_add_int(OPA_int_t *ptr, int val);
-   static _opa_inline void OPA_incr_int(OPA_int_t *ptr);
-   static _opa_inline void OPA_decr_int(OPA_int_t *ptr);
-
-   static _opa_inline int OPA_decr_and_test_int(OPA_int_t *ptr);
-   static _opa_inline int OPA_fetch_and_add_int(OPA_int_t *ptr, int val);
-   static _opa_inline int OPA_fetch_and_incr_int(OPA_int_t *ptr);
-   static _opa_inline int OPA_fetch_and_decr_int(OPA_int_t *ptr);
-
-   static _opa_inline void *OPA_cas_ptr(OPA_ptr_t *ptr, void *oldv, void *newv);
-   static _opa_inline int   OPA_cas_int(OPA_int_t *ptr, int oldv, int newv);
-
-   static _opa_inline void *OPA_swap_ptr(OPA_ptr_t *ptr, void *val);
-   static _opa_inline int   OPA_swap_int(OPA_int_t *ptr, int val);
-
-   // (the memory barriers may be macros instead of inline functions)
-   static _opa_inline void OPA_write_barrier();
-   static _opa_inline void OPA_read_barrier();
-   static _opa_inline void OPA_read_write_barrier();
-
-   // Loads and stores with memory ordering guarantees (also may be macros):
-   static _opa_inline int   OPA_load_acquire_int(_opa_const OPA_int_t *ptr);
-   static _opa_inline void  OPA_store_release_int(OPA_int_t *ptr, int val);
-   static _opa_inline void *OPA_load_acquire_ptr(_opa_const OPA_ptr_t *ptr);
-   static _opa_inline void  OPA_store_release_ptr(OPA_ptr_t *ptr, void *val);
-
-   // Compiler barrier, only preventing compiler reordering, *not* CPU
-   // reordering (may be a macro):
-   static _opa_inline void OPA_compiler_barrier();
-
-   // The following need to be ported only for architectures supporting LL/SC:
-   static _opa_inline int OPA_LL_int(OPA_int_t *ptr);
-   static _opa_inline int OPA_SC_int(OPA_int_t *ptr, int val);
-   static _opa_inline void *OPA_LL_ptr(OPA_ptr_t *ptr);
-   static _opa_inline int OPA_SC_ptr(OPA_ptr_t *ptr, void *val);
-
-   // Additionally, the following initializer macros must be defined:
-   #define OPA_INT_T_INITIALIZER(val_) ...
-   #define OPA_PTR_T_INITIALIZER(val_) ...
-
-   // They should be useable as C89 static initializers like so:
-
-   struct { int x; OPA_int_t y; OPA_ptr_t z; } foo = { 35, OPA_INT_T_INITIALIZER(1), OPA_PTR_T_INITIALIZER(NULL) };
-*/
-
-/* Include the appropriate header for the architecture */
-#if defined(OPA_USE_UNSAFE_PRIMITIVES)
-/* comes first to permit user overrides in the style of NDEBUG */
-#include "primitives/opa_unsafe.h"
-#elif   defined(OPA_HAVE_GCC_AND_POWERPC_ASM)
-#include "primitives/opa_gcc_ppc.h"
-#elif   defined(OPA_HAVE_GCC_AND_ARM_ASM)
-#include "primitives/opa_gcc_arm.h"
-#elif defined(OPA_HAVE_GCC_X86_32_64)
-#include "primitives/opa_gcc_intel_32_64.h"
-#elif defined(OPA_HAVE_GCC_X86_32_64_P3)
-#include "primitives/opa_gcc_intel_32_64_p3.h"
-#elif defined(OPA_HAVE_GCC_AND_IA64_ASM)
-#include "primitives/opa_gcc_ia64.h"
-#elif defined(OPA_HAVE_GCC_AND_SICORTEX_ASM)
-#include "primitives/opa_gcc_sicortex.h"
-#elif defined(OPA_HAVE_GCC_INTRINSIC_ATOMICS)
-#include "primitives/opa_gcc_intrinsics.h"
-#elif defined(OPA_HAVE_SUN_ATOMIC_OPS)
-#include "primitives/opa_sun_atomic_ops.h"
-#elif defined(OPA_HAVE_NT_INTRINSICS)
-#include "primitives/opa_nt_intrinsics.h"
-#elif defined(OPA_USE_LOCK_BASED_PRIMITIVES)
-#include "primitives/opa_by_lock.h"
-#else
-#error no primitives implementation specified
-#endif
-
-/*
-    This routine is needed because the MPIU_THREAD_XXX_CS_{ENTER,EXIT} macros do
-    not provide synchronization across multiple processes, only across multiple
-    threads within a process.  In order to safely emulate atomic operations on a
-    shared memory region, we need a shared memory backed lock mechanism.
-
-    This routine must be called by any subsystem that intends to use the atomic
-    abstractions if the cpp directive OPA_USE_LOCK_BASED_PRIMITIVES is defined.  It must
-    be called exactly once by _all_ processes, not just a single leader.  This
-    function will initialize the contents of the lock variable if the caller
-    specifies (isLeader==true).  Note that multiple initialization is forbidden
-    by several lock implementations, especially pthreads.
-
-    Inputs:
-      shm_lock - A pointer to an allocated piece of shared memory that can hold
-                 a mutex (e.g., pthread_mutex_t).  This is not portable to
-                 non-pthreads systems at this time.
-      isLeader - This boolean value should be set to true for exactly one
-                 thread/process of the group that calls this function.
-*/
-#if defined(OPA_HAVE_PTHREAD_H)
-#  include <pthread.h>
-typedef pthread_mutex_t OPA_emulation_ipl_t;
-int OPA_Interprocess_lock_init(OPA_emulation_ipl_t *shm_lock, int isLeader);
-#endif
-
-
-/* FIXME This should probably be pushed down into the platform-specific headers. */
-#if defined(OPA_HAVE_SCHED_YIELD)
-#  include <sched.h>
-#  define OPA_busy_wait() sched_yield()
-#else
-#  define OPA_busy_wait() do { } while (0)
-#endif
-
-#endif /* defined(OPA_PRIMITIVES_H_INCLUDED) */
diff --git a/linx64/mpi/mpich/include/opa_queue.h b/linx64/mpi/mpich/include/opa_queue.h
deleted file mode 100644
index bba63677..00000000
--- a/linx64/mpi/mpich/include/opa_queue.h
+++ /dev/null
@@ -1,286 +0,0 @@
-/* -*- Mode: C; c-basic-offset:4 ; indent-tabs-mode:nil ; -*- */
-/*  
- *  (C) 2008 by Argonne National Laboratory.
- *      See COPYRIGHT in top-level directory.
- */
-
-/* Implements a fast, lockfree, multi-producer, single-consumer queue.  It's
- * important to note the *single-consumer* piece of this, since multithreaded
- * consumption will surely lead to data corruption and/or other problems. */
-
-#ifndef OPA_QUEUE_H_INCLUDED
-#define OPA_QUEUE_H_INCLUDED
-
-#include "opa_primitives.h"
-#ifdef OPA_HAVE_STDDEF_H
-#include <stddef.h>
-#endif /* OPA_HAVE_STDDEF_H */
-
-/* This value is used to indicate NULL in the OPA_Shm_asymm_base_addr
-   variable.  It is non-zero because one of the likely base addresses is zero
-   (indicating memory is actually symmetrically mapped).  The value 64 was used
-   because it is unlikely that mmap will choose an address this low for a
-   mapping.  */
-/* XXX DJG TODO put some conditionally compiled error checking in that uses this */
-#define OPA_SHM_ASYMM_NULL_VAL    64
-
-extern char *OPA_Shm_asymm_base_addr;
-
-/* Used to initialize the base address for relative pointers.  This interface
-   assumes that there is only one shared memory segment.  If this turns out to
-   not be the case in the future, we should probably add support for multiple
-   shm segments.
-   
-   This function will return an error if it has already been called. */
-int OPA_Shm_asymm_init(char *base);
-
-/* Relative addressing macros.  These are for manipulating addresses relative
-   to the start of a shared memory region. */
-#define OPA_SHM_REL_NULL (0x0)
-#define OPA_SHM_IS_REL_NULL(rel_ptr) (OPA_load_ptr(&(rel_ptr).offset) == OPA_SHM_REL_NULL)
-#define OPA_SHM_SET_REL_NULL(rel_ptr) (OPA_store_ptr(&(rel_ptr).offset, OPA_SHM_REL_NULL))
-#define OPA_SHM_REL_ARE_EQUAL(rel_ptr1, rel_ptr2) \
-    (OPA_load_ptr(&(rel_ptr1).offset) == OPA_load_ptr(&(rel_ptr2).offset))
-
-/* This structure exists such that it is possible to expand the expressiveness
-   of a relative address at some point in the future.  It also provides a
-   modicum of type safety to help prevent certain flavors of errors.
-   
-   For example, instead of referencing an offset from a global base address, it
-   might make sense for there to be multiple base addresses.  These base
-   addresses could correspond to the start of a segment or region of shared
-   memory.  This structure could store the segment number that is used to lookup
-   a base address in a non-shared table.  Note that you would have to be very
-   careful about all of this because if you add the segment number as a separate
-   field you can no longer (compare and) swap a relative address atomically.  So
-   you'll either have to shave bits from the pointer or make some sort of
-   requirement that relative addresses can only be swapped within the same
-   segment.  */
-typedef struct OPA_Shm_rel_addr_t {
-    OPA_ptr_t offset;
-} OPA_Shm_rel_addr_t;
-
-/* converts a relative pointer to an absolute pointer */
-static _opa_inline
-void *OPA_Shm_rel_to_abs(OPA_Shm_rel_addr_t r)
-{
-    void *offset = OPA_load_ptr(&r.offset);
-    OPA_assert((size_t)OPA_Shm_asymm_base_addr != OPA_SHM_ASYMM_NULL_VAL);
-    return (void*)(OPA_Shm_asymm_base_addr + (size_t)offset);
-}
-
-/* converts an absolute pointer to a relative pointer */
-static _opa_inline
-OPA_Shm_rel_addr_t OPA_Shm_abs_to_rel(void *a)
-{
-    OPA_Shm_rel_addr_t ret;
-
-    OPA_assert((size_t)OPA_Shm_asymm_base_addr != OPA_SHM_ASYMM_NULL_VAL);
-    OPA_store_ptr(&ret.offset, (void*)((size_t)a - (size_t)OPA_Shm_asymm_base_addr));
-    return ret;
-}
-
-static _opa_inline
-OPA_Shm_rel_addr_t OPA_Shm_swap_rel(OPA_Shm_rel_addr_t *addr, OPA_Shm_rel_addr_t newv) {
-    OPA_Shm_rel_addr_t oldv;
-    OPA_store_ptr(&oldv.offset, OPA_swap_ptr(&addr->offset, OPA_load_ptr(&newv.offset)));
-    return oldv;
-}
-
-/* Compare the relative pointer to (relative) null and swap if equal.  Prevents
-   the guts of the _rel_addr_t abstraction from bleeding up into the
-   enqueue/dequeue operations. */
-static _opa_inline
-OPA_Shm_rel_addr_t OPA_Shm_cas_rel_null(OPA_Shm_rel_addr_t *addr, OPA_Shm_rel_addr_t oldv) {
-    OPA_Shm_rel_addr_t prev;
-    OPA_store_ptr(&prev.offset, OPA_cas_ptr(&(addr->offset), OPA_load_ptr(&oldv.offset), (void*)OPA_SHM_REL_NULL));
-    return prev;
-}
-
-/* The shadow head pointer makes this queue implementation perform much better
-   than a standard queue.  Unfortunately, it also makes it a bit non-intuitive
-   when read the code.  The following is an excerpt from "Design and Evaluation
-   of Nemesis,  a Scalable, Low-Latency, Message-Passing Communication
-   Subsystem" by D. Buntinas, G.  Mercier, and W. Gropp that gives an
-   explanation:
-
-      A process must access both the head and tail of the queue when it is
-      enqueuing an element on an empty queue or when it is dequeuing an element
-      that is the last element in the queue. In these cases, if the head and
-      tail were in the same cache line, only one L2 cache miss would be
-      encountered. If the queue has more elements in it, however, then the
-      enqueuer only needs to access the tail, and the dequeuer only needs to
-      access the head. If the head and tail were in the same cache line, then
-      there would be L2 misses encountered as a result of false sharing each
-      time a process enqueues an element after another has been dequeued from
-      the same queue, and vice versa. In this case it would be better if the
-      head and tail were in separate cache lines.
-
-      Our solution is to put the head and tail in the same cache line and have a
-      shadow head pointer in a separate cache line. The shadow head is
-      initialized to NULL. The dequeuer uses the shadow head in place of the
-      real head except when the shadow head is NULL, meaning that the queue has
-      become empty. If the shadow head is NULL when the dequeuer tries to
-      dequeue, it checks the value of the real head. If the real head is not
-      NULL, meaning that an element has been enqueued on the queue since the
-      last time the queue became empty, the dequeuer initializes its shadow head
-      to the value of the real head and sets the real head to NULL. In this way,
-      only one L2 cache miss is encountered when enqueuing onto an empty queue
-      or dequeuing from a queue with one element. And because the tail and
-      shadow head are in separate cache lines, there are no L2 cache misses from
-      false sharing. 
-
-      We found that using a shadow head pointer reduced one-way latency by about
-      200 ns on a dual 2 GHz Xeon node.
-*/
-
-/* Pick an arbitrary cacheline size for now, we can setup a mechanism to detect
-   it at build time later on.  This should work well on most intel systems at
-   the very least. */
-#define OPA_QUEUE_CACHELINE_PADDING 128
-
-/* All absolute and relative pointers point to the start of the enclosing element. */
-typedef struct OPA_Queue_info_t {
-    OPA_Shm_rel_addr_t head; /* holds the offset pointer, not the abs ptr */
-    OPA_Shm_rel_addr_t tail; /* holds the offset pointer, not the abs ptr */
-    char padding1[OPA_QUEUE_CACHELINE_PADDING-2*sizeof(OPA_Shm_rel_addr_t)];
-    OPA_Shm_rel_addr_t  shadow_head; /* holds the offset pointer, not the abs ptr */
-    char padding2[OPA_QUEUE_CACHELINE_PADDING-sizeof(OPA_Shm_rel_addr_t)];
-} OPA_Queue_info_t;
-
-/* Using this header struct even though it's just one element gives us the
-   opportunity to vary the implementation more easily in the future without
-   updating all callers. */
-typedef struct OPA_Queue_element_hdr_t {
-    OPA_Shm_rel_addr_t next; /* holds the offset pointer, not the abs ptr */
-} OPA_Queue_element_hdr_t;
-
-
-/* Used to initialize a queue structure. */
-void OPA_Queue_init(OPA_Queue_info_t *qhead);
-
-/* Used to initialize a queue element header. */
-void OPA_Queue_header_init(OPA_Queue_element_hdr_t *hdr);
-
-static _opa_inline
-int OPA_Queue_is_empty(OPA_Queue_info_t *qhead)
-{
-    int __ret = 0;
-    if (OPA_SHM_IS_REL_NULL (qhead->shadow_head)) {
-        if (OPA_SHM_IS_REL_NULL(qhead->head)) {
-            __ret = 1;
-        }
-        else {
-            qhead->shadow_head = qhead->head;
-            OPA_SHM_SET_REL_NULL(qhead->head); /* reset it for next time */
-        }
-    }
-    return __ret;
-}
-
-/* Returns a pointer to the element at the head of the queue.  The current
-   implementation of these queue algorithms imposes several notable
-   restrictions on the use of this function:
-    - The caller must currently hold the critical section, just as if you were
-      calling OPA_Queue_dequeue.  Failure to do could easily produce incorrect
-      results.
-    - OPA_Queue_is_empty must be called on this queue prior to calling this
-      function.  Furthermore, there must be no intervening calls to any
-      OPA_Queue_* functions (for this queue) between _is_empty and _peek_head.
-      Failure to do so will produce incorrect results.
-
-   This operation is effectively the same as the dequeue operation (insofar as
-   it shares the same calling restrictions) but it does not disturb the actual
-   contents of the queue. */
-static _opa_inline
-void *OPA_Queue_peek_head(OPA_Queue_info_t *qhead_ptr)
-{
-    OPA_assert(qhead_ptr != NULL);
-
-    if (OPA_SHM_IS_REL_NULL(qhead_ptr->shadow_head)) {
-        return NULL;
-    }
-    return OPA_Shm_rel_to_abs(qhead_ptr->shadow_head);
-}
-
-/* This macro atomically enqueues an element (elt for short) into the queue
-   indicated by qhead_ptr.  You need to pass several arguments:
-     qhead_ptr - a pointer to a OPA_Queue_info_t structure to which the
-                 element should be enqueued
-     elt_ptr - a pointer to an element structure type that is to be enqueued
-     elt_type - The base type of elt_ptr.  That is, if elt_ptr is a
-                '(struct example_t *)' then elt_type is 'struct example_t'.
-     elt_hdr_field - This is the member name of elt_type that is a
-                     OPA_Queue_element_hdr_t.
-
-    This queue implementation is loosely modeled after the linked lists used in
-    the linux kernel.  You put the list header structure inside of the client
-    structure, rather than the other way around.
-   */
-#define OPA_Queue_enqueue(qhead_ptr, elt_ptr, elt_type, elt_hdr_field)    \
-do {                                                                      \
-    OPA_Shm_rel_addr_t r_prev;                                            \
-    OPA_Shm_rel_addr_t r_elt = OPA_Shm_abs_to_rel(elt_ptr);               \
-                                                                          \
-    OPA_SHM_SET_REL_NULL((elt_ptr)->elt_hdr_field.next);                  \
-                                                                          \
-    OPA_write_barrier();                                                  \
-                                                                          \
-    r_prev = OPA_Shm_swap_rel(&((qhead_ptr)->tail), r_elt);               \
-                                                                          \
-    if (OPA_SHM_IS_REL_NULL(r_prev)) {                                    \
-        (qhead_ptr)->head = r_elt;                                        \
-    }                                                                     \
-    else {                                                                \
-        elt_type *abs_prev = (elt_type *)OPA_Shm_rel_to_abs(r_prev);      \
-        abs_prev->elt_hdr_field.next = r_elt;                             \
-    }                                                                     \
-} while (0)
-
-/* This macro atomically dequeues an element (elt for short) from the queue
-   indicated by qhead_ptr.  You need to pass several arguments:
-     qhead_ptr - a pointer to a OPA_Queue_info_t structure to which the
-                 element should be dequeued
-     elt_ptr - A pointer to an element structure type that should be populated
-               with the dequeued value.  Must be an lvalue.
-     elt_type - The base type of elt_ptr.  That is, if elt_ptr is a
-                '(struct example_t *)' then elt_type is 'struct example_t'.
-     elt_hdr_field - This is the member name of elt_type that is a
-                     OPA_Queue_element_hdr_t.
-
-    This queue implementation is loosely modeled after the linked lists used in
-    the linux kernel.  You put the list header structure inside of the client
-    structure, rather than the other way around.
-
-    NOTE: you must *always* call _is_empty() prior to this function */
-#define OPA_Queue_dequeue(qhead_ptr, elt_ptr, elt_type, elt_hdr_field)        \
-do {                                                                          \
-    elt_type *_e;                                                             \
-    OPA_Shm_rel_addr_t _r_e;                                                  \
-                                                                              \
-    _r_e = (qhead_ptr)->shadow_head;                                          \
-    _e = OPA_Shm_rel_to_abs(_r_e);                                            \
-                                                                              \
-    if (!OPA_SHM_IS_REL_NULL(_e->elt_hdr_field.next)) {                       \
-        (qhead_ptr)->shadow_head = _e->elt_hdr_field.next;                    \
-    }                                                                         \
-    else {                                                                    \
-        OPA_Shm_rel_addr_t old_tail;                                          \
-                                                                              \
-        OPA_SHM_SET_REL_NULL((qhead_ptr)->shadow_head);                       \
-                                                                              \
-        old_tail = OPA_Shm_cas_rel_null(&((qhead_ptr)->tail), _r_e);          \
-                                                                              \
-        if (!OPA_SHM_REL_ARE_EQUAL(old_tail, _r_e)) {                         \
-            while (OPA_SHM_IS_REL_NULL(_e->elt_hdr_field.next)) {             \
-                OPA_busy_wait();                                              \
-            }                                                                 \
-            (qhead_ptr)->shadow_head = _e->elt_hdr_field.next;                \
-        }                                                                     \
-    }                                                                         \
-    OPA_SHM_SET_REL_NULL(_e->elt_hdr_field.next);                             \
-    OPA_read_barrier();                                                       \
-    elt_ptr = _e;                                                             \
-} while (0)
-
-#endif /* OPA_QUEUE_H_INCLUDED */
diff --git a/linx64/mpi/mpich/include/opa_util.h b/linx64/mpi/mpich/include/opa_util.h
deleted file mode 100644
index f6819ba1..00000000
--- a/linx64/mpi/mpich/include/opa_util.h
+++ /dev/null
@@ -1,27 +0,0 @@
-/* -*- Mode: C; c-basic-offset:4 ; indent-tabs-mode:nil ; -*- */
-/*
- *  (C) 2008 by Argonne National Laboratory.
- *      See COPYRIGHT in top-level directory.
- */
-
-#ifndef OPA_UTIL_H_INCLUDED
-#define OPA_UTIL_H_INCLUDED
-
-#define OPA_QUOTE(x_) OPA_QUOTE2(x_)
-#define OPA_QUOTE2(x_) #x_
-
-#if defined(OPA_HAVE_GCC_ATTRIBUTE)
-#  define OPA_ATTRIBUTE(x_) __attribute__ (x_)
-#else
-#  define OPA_ATTRIBUTE(x_)
-#endif
-
-/* FIXME this just needs a total rework in general with an OPA_NDEBUG or similar. */
-#define OPA_assert(expr_) do {} while (0)
-#define OPA_assertp(expr_) do { if (!(expr_)) ++((int *)NULL) } while (0) /* SEGV intentionally */
-
-/* A compile-time assertion macro.  It should cause a compilation error if (expr_) is false. */
-#define OPA_COMPILE_TIME_ASSERT(expr_) \
-    do { switch(0) { case 0: case (expr_): default: break; } } while (0)
-
-#endif /* OPA_UTIL_H_INCLUDED */
diff --git a/linx64/mpi/mpich/include/primitives/opa_by_lock.h b/linx64/mpi/mpich/include/primitives/opa_by_lock.h
deleted file mode 100644
index ea5d18c8..00000000
--- a/linx64/mpi/mpich/include/primitives/opa_by_lock.h
+++ /dev/null
@@ -1,205 +0,0 @@
-/* -*- Mode: C; c-basic-offset:4 ; indent-tabs-mode:nil ; -*- */
-/*
- *  (C) 2008 by Argonne National Laboratory.
- *      See COPYRIGHT in top-level directory.
- */
-
-#ifndef OPA_BY_LOCK_H_INCLUDED
-#define OPA_BY_LOCK_H_INCLUDED
-
-/* FIXME For now we rely on pthreads for our IPC locks.  This is fairly
-   portable, although it is obviously not 100% portable.  Some day when we
-   refactor the OPA_Process_locks code we should be able to use that again. */
-#if defined(OPA_HAVE_PTHREAD_H)
-#include <pthread.h>
-
-/* defined in opa_primitives.c */
-extern pthread_mutex_t *OPA_emulation_lock;
-
-/* FIXME these make less sense now that OPA is not inside of MPICH.  Is there a
-   simpler name/scheme that could be used here instead? [goodell@ 2009-02-19] */
-#define OPA_IPC_SINGLE_CS_ENTER(msg)          \
-    do {                                        \
-        OPA_assert(OPA_emulation_lock);    \
-        pthread_mutex_lock(OPA_emulation_lock);     \
-    } while (0)
-
-#define OPA_IPC_SINGLE_CS_EXIT(msg)           \
-    do {                                        \
-        OPA_assert(OPA_emulation_lock);    \
-        pthread_mutex_unlock(OPA_emulation_lock);   \
-    } while (0)
-
-typedef struct { volatile int v;  } OPA_int_t;
-typedef struct { int * volatile v; } OPA_ptr_t;
-
-#define OPA_INT_T_INITIALIZER(val_) { (val_) }
-#define OPA_PTR_T_INITIALIZER(val_) { (val_) }
-
-/*
-    Emulated atomic primitives
-    --------------------------
-
-    These are versions of the atomic primitives that emulate the proper behavior
-    via the use of an inter-process lock.  For more information on their
-    individual behavior, please see the comment on the corresponding top level
-    function.
-
-    In general, these emulated primitives should _not_ be used.  Most algorithms
-    can be more efficiently implemented by putting most or all of the algorithm
-    inside of a single critical section.  These emulated primitives exist to
-    ensure that there is always a fallback if no machine-dependent version of a
-    particular operation has been defined.  They also serve as a very readable
-    reference for the exact semantics of our OPA_* ops.
-*/
-
-static _opa_inline int OPA_load_int(_opa_const OPA_int_t *ptr)
-{
-    int retval;
-    OPA_IPC_SINGLE_CS_ENTER("atomic_add");
-    retval = ptr->v;
-    OPA_IPC_SINGLE_CS_EXIT("atomic_add");
-    return retval;
-}
-
-static _opa_inline void OPA_store_int(OPA_int_t *ptr, int val)
-{
-    OPA_IPC_SINGLE_CS_ENTER("atomic_add");
-    ptr->v = val;
-    OPA_IPC_SINGLE_CS_EXIT("atomic_add");
-}
-
-static _opa_inline void *OPA_load_ptr(_opa_const OPA_ptr_t *ptr)
-{
-    int *retval;
-    OPA_IPC_SINGLE_CS_ENTER("atomic_add");
-    retval = ptr->v;
-    OPA_IPC_SINGLE_CS_EXIT("atomic_add");
-    return retval;
-}
-
-static _opa_inline void OPA_store_ptr(OPA_ptr_t *ptr, void *val)
-{
-    OPA_IPC_SINGLE_CS_ENTER("atomic_add");
-    ptr->v = val;
-    OPA_IPC_SINGLE_CS_EXIT("atomic_add");
-}
-
-/* normal loads/stores are fully ordered, so just use them */
-#define OPA_load_acquire_int(ptr_)       OPA_load_int((ptr_))
-#define OPA_store_release_int(ptr_,val_) OPA_store_int((ptr_),(val_))
-#define OPA_load_acquire_ptr(ptr_)       OPA_load_ptr((ptr_))
-#define OPA_store_release_ptr(ptr_,val_) OPA_store_ptr((ptr_),(val_))
-
-static _opa_inline void OPA_add_int(OPA_int_t *ptr, int val)
-{
-    OPA_IPC_SINGLE_CS_ENTER("atomic_add");
-    ptr->v += val;
-    OPA_IPC_SINGLE_CS_EXIT("atomic_add");
-}
-
-static _opa_inline void *OPA_cas_ptr(OPA_ptr_t *ptr, int *oldv, int *newv)
-{
-    int *prev;
-    OPA_IPC_SINGLE_CS_ENTER("atomic_cas");
-    prev = ptr->v;
-    if (prev == oldv) {
-        ptr->v = newv;
-    }
-    OPA_IPC_SINGLE_CS_EXIT("atomic_cas");
-    return prev;
-}
-
-static _opa_inline int OPA_cas_int(OPA_int_t *ptr, int oldv, int newv)
-{
-    int prev;
-    OPA_IPC_SINGLE_CS_ENTER("atomic_cas");
-    prev = ptr->v;
-    if (prev == oldv) {
-        ptr->v = newv;
-    }
-    OPA_IPC_SINGLE_CS_EXIT("atomic_cas");
-    return prev;
-}
-
-static _opa_inline int OPA_decr_and_test_int(OPA_int_t *ptr)
-{
-    int new_val;
-    OPA_IPC_SINGLE_CS_ENTER("atomic_decr_and_test");
-    new_val = --(ptr->v);
-    OPA_IPC_SINGLE_CS_EXIT("atomic_decr_and_test");
-    return (0 == new_val);
-}
-
-static _opa_inline void OPA_decr_int(OPA_int_t *ptr)
-{
-    OPA_IPC_SINGLE_CS_ENTER("atomic_decr");
-    --(ptr->v);
-    OPA_IPC_SINGLE_CS_EXIT("atomic_decr");
-}
-
-static _opa_inline int OPA_fetch_and_add_int(OPA_int_t *ptr, int val)
-{
-    int prev;
-    OPA_IPC_SINGLE_CS_ENTER("atomic_fetch_and_add");
-    prev = ptr->v;
-    ptr->v += val;
-    OPA_IPC_SINGLE_CS_EXIT("atomic_fetch_and_add");
-    return prev;
-}
-
-static _opa_inline int OPA_fetch_and_decr_int(OPA_int_t *ptr)
-{
-    int prev;
-    OPA_IPC_SINGLE_CS_ENTER("atomic_fetch_and_decr");
-    prev = ptr->v;
-    --(ptr->v);
-    OPA_IPC_SINGLE_CS_EXIT("atomic_fetch_and_decr");
-    return prev;
-}
-
-static _opa_inline int OPA_fetch_and_incr_int(OPA_int_t *ptr)
-{
-    int prev;
-    OPA_IPC_SINGLE_CS_ENTER("atomic_fetch_and_incr");
-    prev = ptr->v;
-    ++(ptr->v);
-    OPA_IPC_SINGLE_CS_EXIT("atomic_fetch_and_incr");
-    return prev;
-}
-
-static _opa_inline void OPA_incr_int(OPA_int_t *ptr)
-{
-    OPA_IPC_SINGLE_CS_ENTER("atomic_incr");
-    ++(ptr->v);
-    OPA_IPC_SINGLE_CS_EXIT("atomic_incr");
-}
-
-static _opa_inline void *OPA_swap_ptr(OPA_ptr_t *ptr, void *val)
-{
-    int *prev;
-    OPA_IPC_SINGLE_CS_ENTER("atomic_swap_ptr");
-    prev = ptr->v;
-    ptr->v = val;
-    OPA_IPC_SINGLE_CS_EXIT("atomic_swap_ptr");
-    return prev;
-}
-
-static _opa_inline int OPA_swap_int(OPA_int_t *ptr, int val)
-{
-    int prev;
-    OPA_IPC_SINGLE_CS_ENTER("atomic_swap_int");
-    prev = ptr->v;
-    ptr->v = val;
-    OPA_IPC_SINGLE_CS_EXIT("atomic_swap_int");
-    return (int)prev;
-}
-
-/* lock/unlock provides barrier */
-#define OPA_write_barrier()      do {} while (0)
-#define OPA_read_barrier()       do {} while (0)
-#define OPA_read_write_barrier() do {} while (0)
-
-
-#endif /* defined(OPA_HAVE_PTHREAD_H) */
-#endif /* !defined(OPA_BY_LOCK_H_INCLUDED) */
diff --git a/linx64/mpi/mpich/include/primitives/opa_emulated.h b/linx64/mpi/mpich/include/primitives/opa_emulated.h
deleted file mode 100644
index c526fe43..00000000
--- a/linx64/mpi/mpich/include/primitives/opa_emulated.h
+++ /dev/null
@@ -1,192 +0,0 @@
-/* -*- Mode: C; c-basic-offset:4 ; indent-tabs-mode:nil ; -*- */
-/*
- *  (C) 2008 by Argonne National Laboratory.
- *      See COPYRIGHT in top-level directory.
- */
-
-#ifndef OPA_EMULATED_H_INCLUDED
-#define OPA_EMULATED_H_INCLUDED
-
-/* Functions emulated using other atomics
-
-   This header should be included at the bottom of any atomic
-   primitives header that needs to implement an atomic op in terms of
-   another atomic.
-*/
-
-/* Emulating using LL/SC */
-#if defined(OPA_LL_SC_SUPPORTED)
-static _opa_inline int OPA_fetch_and_add_int_by_llsc(OPA_int_t *ptr, int val)
-{
-    int prev;
-    do {
-        prev = OPA_LL_int(ptr);
-    } while (!OPA_SC_int(ptr, prev + val));
-    return prev;
-}
-
-
-static _opa_inline void OPA_add_int_by_llsc(OPA_int_t *ptr, int val)
-{
-    OPA_fetch_and_add_int_by_llsc(ptr, val);
-}
-
-static _opa_inline void OPA_incr_int_by_llsc(OPA_int_t *ptr)
-{
-    OPA_add_int_by_llsc(ptr, 1);
-}
-
-static _opa_inline void OPA_decr_int_by_llsc(OPA_int_t *ptr)
-{
-    OPA_add_int_by_llsc(ptr, -1);
-}
-
-
-static _opa_inline int OPA_fetch_and_decr_int_by_llsc(OPA_int_t *ptr)
-{
-    return OPA_fetch_and_add_int_by_llsc(ptr, -1);
-}
-
-static _opa_inline int OPA_fetch_and_incr_int_by_llsc(OPA_int_t *ptr)
-{
-    return OPA_fetch_and_add_int_by_llsc(ptr, 1);
-}
-
-static _opa_inline int OPA_decr_and_test_int_by_llsc(OPA_int_t *ptr)
-{
-    int prev = OPA_fetch_and_decr_int_by_llsc(ptr);
-    return prev == 1;
-}
-
-static _opa_inline void *OPA_cas_ptr_by_llsc(OPA_ptr_t *ptr, void *oldv, void *newv)
-{
-    void *prev;
-    do {
-        prev = OPA_LL_ptr(ptr);
-    } while (prev == oldv && !OPA_SC_ptr(ptr, newv));
-    return prev;
-}
-
-static _opa_inline int OPA_cas_int_by_llsc(OPA_int_t *ptr, int oldv, int newv)
-{
-    int prev;
-    do {
-        prev = OPA_LL_int(ptr);
-    } while (prev == oldv && !OPA_SC_int(ptr, newv));
-    return prev;
-}
-
-
-static _opa_inline void *OPA_swap_ptr_by_llsc(OPA_ptr_t *ptr, void *val)
-{
-    void *prev;
-    do {
-        prev = OPA_LL_ptr(ptr);
-    } while (!OPA_SC_ptr(ptr, val));
-    return prev;
-}
-
-static _opa_inline int OPA_swap_int_by_llsc(OPA_int_t *ptr, int val)
-{
-    int prev;
-    do {
-        prev = OPA_LL_int(ptr);
-    } while (!OPA_SC_int(ptr, val));
-    return prev;
-}
-
-#endif /* OPA_LL_SC_SUPPORTED */
-
-static _opa_inline int OPA_fetch_and_add_int_by_cas(OPA_int_t *ptr, int val)
-{
-    int cmp;
-    int prev = OPA_load_int(ptr);
-
-    do {
-        cmp = prev;
-        prev = OPA_cas_int(ptr, cmp, prev + val);
-    } while (prev != cmp);
-
-    return prev;
-}
-
-static _opa_inline int OPA_fetch_and_incr_int_by_faa(OPA_int_t *ptr)
-{
-    return OPA_fetch_and_add_int(ptr, 1);
-}
-
-static _opa_inline int OPA_fetch_and_decr_int_by_faa(OPA_int_t *ptr)
-{
-    return OPA_fetch_and_add_int(ptr, -1);
-}
-
-static _opa_inline int OPA_decr_and_test_int_by_fad(OPA_int_t *ptr)
-{
-    return OPA_fetch_and_decr_int(ptr) == 1;
-}
-
-static _opa_inline void OPA_add_int_by_faa(OPA_int_t *ptr, int val)
-{
-    OPA_fetch_and_add_int(ptr, val);
-}
-
-static _opa_inline int OPA_incr_int_by_faa(OPA_int_t *ptr)
-{
-    return OPA_fetch_and_add_int(ptr, 1);
-}
-
-static _opa_inline void OPA_incr_int_by_add(OPA_int_t *ptr)
-{
-    OPA_add_int(ptr, 1);
-}
-
-static _opa_inline void OPA_incr_int_by_fai(OPA_int_t *ptr)
-{
-    OPA_fetch_and_incr_int(ptr);
-}
-
-static _opa_inline int OPA_decr_int_by_faa(OPA_int_t *ptr)
-{
-    return OPA_fetch_and_add_int(ptr, -1);
-}
-
-static _opa_inline void OPA_decr_int_by_add(OPA_int_t *ptr)
-{
-    OPA_add_int(ptr, -1);
-}
-
-static _opa_inline void OPA_decr_int_by_fad(OPA_int_t *ptr)
-{
-    OPA_fetch_and_decr_int(ptr);
-}
-
-
-/* Swap using CAS */
-
-static _opa_inline void *OPA_swap_ptr_by_cas(OPA_ptr_t *ptr, void *val)
-{
-    void *cmp;
-    void *prev = OPA_load_ptr(ptr);
-
-    do {
-        cmp = prev;
-        prev = OPA_cas_ptr(ptr, cmp, val);
-    } while (prev != cmp);
-
-    return prev;
-}
-
-static _opa_inline int OPA_swap_int_by_cas(OPA_int_t *ptr, int val)
-{
-    int cmp;
-    int prev = OPA_load_int(ptr);
-
-    do {
-        cmp = prev;
-        prev = OPA_cas_int(ptr, cmp, val);
-    } while (prev != cmp);
-
-    return prev;
-}
-
-#endif /* OPA_EMULATED_H_INCLUDED */
diff --git a/linx64/mpi/mpich/include/primitives/opa_gcc_ia64.h b/linx64/mpi/mpich/include/primitives/opa_gcc_ia64.h
deleted file mode 100644
index 8f13523c..00000000
--- a/linx64/mpi/mpich/include/primitives/opa_gcc_ia64.h
+++ /dev/null
@@ -1,216 +0,0 @@
-/* -*- Mode: C; c-basic-offset:4 ; indent-tabs-mode:nil ; -*- */
-/*  
- *  (C) 2008 by Argonne National Laboratory.
- *      See COPYRIGHT in top-level directory.
- */
-
-/* NOTE: We (@ANL) do not have easy access to any ia64 hosts, so it is difficult
- * to develop and test updates to this file.  Any help in this regard is greatly
- * appreciated. */
-
-#ifndef OPA_GCC_IA64_H_INCLUDED
-#define OPA_GCC_IA64_H_INCLUDED
-
-/* FIXME do we need to align these? */
-typedef struct { volatile int v;    } OPA_int_t;
-typedef struct { void * volatile v; } OPA_ptr_t;
-
-#define OPA_INT_T_INITIALIZER(val_) { (val_) }
-#define OPA_PTR_T_INITIALIZER(val_) { (val_) }
-
-/* Aligned loads and stores are atomic on ia64. */
-static _opa_inline int OPA_load_int(_opa_const OPA_int_t *ptr)
-{
-    return ptr->v;
-}
-
-/* Aligned loads and stores are atomic on ia64. */
-static _opa_inline void OPA_store_int(OPA_int_t *ptr, int val)
-{
-    ptr->v = val;
-}
-
-/* Aligned loads and stores are atomic on ia64. */
-static _opa_inline void *OPA_load_ptr(_opa_const OPA_ptr_t *ptr)
-{
-    return ptr->v;
-}
-
-/* Aligned loads and stores are atomic on ia64. */
-static _opa_inline void OPA_store_ptr(OPA_ptr_t *ptr, void *val)
-{
-    ptr->v = val;
-}
-
-
-/* NOTE-IA64-1 ia64 suports half-fence suffixes to ld/st instructions.  It seems
- * that compilers also treat any C-language load/store from/to a volatile
- * variable as acquire/release and append the corresponding suffix accordingly.
- * But we don't have extensive testing to back this up, so we'll explicitly
- * force these instructions for now.  When using the C-level approach, it's not
- * clear what instructions the compiler is allowed to reorder. */
-
-#if 0
-/* acquire means operations after the acquire will see any memory opeations
- * performed before the corresponding paired release operation */
-static _opa_inline int   OPA_load_acquire_int(_opa_const OPA_int_t *ptr)
-{
-    int tmp;
-    __asm__ __volatile__ ("ld.acq %0=[%1]"
-                          : "=r" (tmp)
-                          : "r"  (ptr->v)
-                          : "memory");
-    return tmp;
-}
-static _opa_inline void  OPA_store_release_int(OPA_int_t *ptr, int val)
-{
-    __asm__ __volatile__ ("st.rel [%0]=%1"
-                          : "=m"  (ptr->v)
-                          : "r" (val)
-                          : "memory");
-}
-static _opa_inline void *OPA_load_acquire_ptr(_opa_const OPA_ptr_t *ptr)
-{
-    int tmp;
-    __asm__ __volatile__ ("ld.acq %0=[%1]"
-                          : "=r" (tmp)
-                          : "r"  (ptr->v)
-                          : "memory");
-    return tmp;
-}
-static _opa_inline void  OPA_store_release_ptr(OPA_ptr_t *ptr, void *val)
-{
-    __asm__ __volatile__ ("st.rel [%0]=%1"
-                          : "=m"  (ptr->v)
-                          : "r" (val)
-                          : "memory");
-}
-#else
-/* FIXME because we can't test these implementations, they are currently
- * disabled.  The above impls are rough starting points, but probably won't
- * compile/assemble correctly as-is.  Patches are welcome :) */
-#define OPA_load_acquire_int(ptr_)       ::"choke me"
-#define OPA_store_release_int(ptr_,val_) ::"choke me"
-#define OPA_load_acquire_ptr(ptr_)       ::"choke me"
-#define OPA_store_release_ptr(ptr_,val_) ::"choke me"
-#endif
-
-
-#define OPA_add_int_by_faa OPA_add_int
-#define OPA_incr_int_by_faa OPA_incr_int
-#define OPA_decr_int_by_faa OPA_decr_int
-#define OPA_fetch_and_decr_int_by_faa OPA_fetch_and_decr_int
-#define OPA_fetch_and_incr_int_by_faa OPA_fetch_and_incr_int
-
-static _opa_inline int OPA_decr_and_test_int(OPA_int_t *ptr)
-{
-    int val;
-    __asm__ __volatile__ ("fetchadd4.rel %0=[%2],%3"
-                          : "=r"(val), "=m"(ptr->v)
-                          : "r"(&ptr->v), "i"(-1));
-    return val == 1;
-}
-
-static _opa_inline int OPA_cas_int(OPA_int_t *ptr, int oldv, int newv)
-{
-    int prev;
-
-#if OPA_SIZEOF_INT == 8
-    __asm__ __volatile__ ("mov ar.ccv=%1;;"
-                          "cmpxchg8.rel %0=[%3],%4,ar.ccv"
-                          : "=r"(prev), "=m"(ptr->v)
-                          : "rO"(oldv), "r"(&ptr->v), "r"(newv)
-                          : "memory");
-    break;
-#elif OPA_SIZEOF_INT == 4
-    __asm__ __volatile__ ("zxt4 %1=%1;;" /* don't want oldv sign-extended to 64 bits */
-                          "mov ar.ccv=%1;;"
-                          "cmpxchg4.rel %0=[%3],%4,ar.ccv"
-                          : "=r"(prev), "=m"(ptr->v)
-                          : "r0"(oldv), "r"(&ptr->v), "r"(newv)
-                          : "memory");
-#else
-#error OPA_SIZEOF_INT is not 4 or 8
-#endif
-
-    return prev;
-}
-
-/* IA64 has a fetch-and-add instruction that only accepts immediate
-   values of -16, -8, -4, -1, 1, 4, 8, and 16.  So we check for these
-   values before falling back to the CAS implementation. */
-#define OPA_IA64_FAA_CASE_MACRO(ptr, val) case val: {   \
-    int prev;                                           \
-    __asm__ __volatile__ ("fetchadd4.rel %0=[%2],%3"    \
-                          : "=r"(prev), "=m"(ptr->v)    \
-                          : "r"(&ptr->v), "i"(val));    \
-    return prev;                                        \
-    }                                                   \
-    break
-
-
-static _opa_inline int OPA_fetch_and_add_int(OPA_int_t *ptr, int val)
-{
-    switch (val)
-    {
-        OPA_IA64_FAA_CASE_MACRO(ptr, -16);
-        OPA_IA64_FAA_CASE_MACRO(ptr,  -8);
-        OPA_IA64_FAA_CASE_MACRO(ptr,  -4);
-        OPA_IA64_FAA_CASE_MACRO(ptr,  -1);
-        OPA_IA64_FAA_CASE_MACRO(ptr,   1);
-        OPA_IA64_FAA_CASE_MACRO(ptr,   4);
-        OPA_IA64_FAA_CASE_MACRO(ptr,   8);
-        OPA_IA64_FAA_CASE_MACRO(ptr,  16);
-    default:
-        {
-            int cmp;
-            int prev = OPA_load_int(ptr);
-
-            do {
-                cmp = prev;
-                prev = OPA_cas_int(ptr, cmp, val);
-            } while (prev != cmp);
-
-            return prev;
-        }
-    }
-}
-#undef OPA_IA64_FAA_CASE_MACRO
-
-
-static _opa_inline void *OPA_cas_ptr(OPA_ptr_t *ptr, void *oldv, void *newv)
-{
-    void *prev;
-    __asm__ __volatile__ ("mov ar.ccv=%1;;"
-                          "cmpxchg8.rel %0=[%3],%4,ar.ccv"
-                          : "=r"(prev), "=m"(ptr->v)
-                          : "rO"(oldv), "r"(&ptr->v), "r"(newv));
-    return prev;
-}
-
-static _opa_inline void *OPA_swap_ptr(OPA_ptr_t *ptr, void *val)
-{
-    __asm__ __volatile__ ("xchg8 %0=[%2],%3"
-                          : "=r" (val), "=m" (ptr->v)
-                          : "r" (&ptr->v), "0" (val));
-    return val;
-}
-
-
-static _opa_inline int OPA_swap_int(OPA_int_t *ptr, int val)
-{
-    __asm__ __volatile__ ("xchg8 %0=[%2],%3"
-                          : "=r" (val), "=m" (ptr->v)
-                          : "r" (&ptr->v), "0" (val));
-    return val;
-}
-
-
-#define OPA_write_barrier()      __asm__ __volatile__  ("mf" ::: "memory" )
-#define OPA_read_barrier()       __asm__ __volatile__  ("mf" ::: "memory" )
-#define OPA_read_write_barrier() __asm__ __volatile__  ("mf" ::: "memory" )
-#define OPA_compiler_barrier()   __asm__ __volatile__  (""   ::: "memory" )
-
-#include "opa_emulated.h"
-
-#endif /* OPA_GCC_IA64_H_INCLUDED */
diff --git a/linx64/mpi/mpich/include/primitives/opa_gcc_intel_32_64.h b/linx64/mpi/mpich/include/primitives/opa_gcc_intel_32_64.h
deleted file mode 100644
index d435311f..00000000
--- a/linx64/mpi/mpich/include/primitives/opa_gcc_intel_32_64.h
+++ /dev/null
@@ -1,15 +0,0 @@
-/* -*- Mode: C; c-basic-offset:4 ; indent-tabs-mode:nil ; -*- */
-/*
- *  (C) 2008 by Argonne National Laboratory.
- *      See COPYRIGHT in top-level directory.
- */
-
-#ifndef OPA_GCC_INTEL_32_64_H_INCLUDED
-#define OPA_GCC_INTEL_32_64_H_INCLUDED
-
-#include "opa_gcc_intel_32_64_barrier.h"
-#include "opa_gcc_intel_32_64_ops.h"
-
-#include "opa_emulated.h"
-
-#endif /* OPA_GCC_INTEL_32_64_H_INCLUDED */
diff --git a/linx64/mpi/mpich/include/primitives/opa_gcc_intel_32_64_barrier.h b/linx64/mpi/mpich/include/primitives/opa_gcc_intel_32_64_barrier.h
deleted file mode 100644
index 36aaf474..00000000
--- a/linx64/mpi/mpich/include/primitives/opa_gcc_intel_32_64_barrier.h
+++ /dev/null
@@ -1,25 +0,0 @@
-/* -*- Mode: C; c-basic-offset:4 ; indent-tabs-mode:nil ; -*- */
-/*
- *  (C) 2008 by Argonne National Laboratory.
- *      See COPYRIGHT in top-level directory.
- */
-
-#ifndef OPA_GCC_INTEL_32_64_BARRIER_H_INCLUDED
-#define OPA_GCC_INTEL_32_64_BARRIER_H_INCLUDED
-
-#define OPA_compiler_barrier()   __asm__ __volatile__  ( "" ::: "memory" )
-
-/* For all regular memory (write-back cacheable, not driver/graphics
- * memory), there is only one general ordering relaxation permitted by
- * x86/x86_64 processors: earlier stores may be retired after later
- * stores.  The "clflush" and "movnt*" instructions also don't follow
- * general ordering constraints, although any code using these
- * instructions should be responsible for ensuring proper ordering
- * itself.  So our read and write barriers may be implemented as simple
- * compiler barriers. */
-#define OPA_write_barrier() OPA_compiler_barrier()
-#define OPA_read_barrier()  OPA_compiler_barrier()
-
-#define OPA_read_write_barrier() __asm__ __volatile__  ( "mfence" ::: "memory" )
-
-#endif /* OPA_GCC_INTEL_32_64_BARRIER_H_INCLUDED */
diff --git a/linx64/mpi/mpich/include/primitives/opa_gcc_intel_32_64_ops.h b/linx64/mpi/mpich/include/primitives/opa_gcc_intel_32_64_ops.h
deleted file mode 100644
index 6482c199..00000000
--- a/linx64/mpi/mpich/include/primitives/opa_gcc_intel_32_64_ops.h
+++ /dev/null
@@ -1,173 +0,0 @@
-/* -*- Mode: C; c-basic-offset:4 ; indent-tabs-mode:nil ; -*- */
-/*
- *  (C) 2008 by Argonne National Laboratory.
- *      See COPYRIGHT in top-level directory.
- */
-
-#ifndef OPA_GCC_INTEL_32_64_OPS_H_INCLUDED
-#define OPA_GCC_INTEL_32_64_OPS_H_INCLUDED
-
-#ifndef OPA_SIZEOF_INT
-#error OPA_SIZEOF_INT is not defined
-#endif
-
-/* Set OPA_SS (Size Suffix) which is to be appended to asm ops for
-   specifying 4 or 8 byte operands */
-#if OPA_SIZEOF_INT == 4
-#define OPA_SS "l"
-#elif OPA_SIZEOF_INT == 8
-#define OPA_SS "q"
-#else
-#error OPA_SIZEOF_INT is not 4 or 8
-#endif
-
-/* XXX DJG FIXME do we need to align these? */
-typedef struct { volatile int v;    } OPA_int_t;
-typedef struct { void * volatile v; } OPA_ptr_t;
-
-#define OPA_INT_T_INITIALIZER(val_) { (val_) }
-#define OPA_PTR_T_INITIALIZER(val_) { (val_) }
-
-/* Aligned loads and stores are atomic on x86(-64). */
-static _opa_inline int OPA_load_int(_opa_const OPA_int_t *ptr)
-{
-    return ptr->v;
-}
-
-/* Aligned loads and stores are atomic on x86(-64). */
-static _opa_inline void OPA_store_int(OPA_int_t *ptr, int val)
-{
-    ptr->v = val;
-}
-
-/* Aligned loads and stores are atomic on x86(-64). */
-static _opa_inline void *OPA_load_ptr(_opa_const OPA_ptr_t *ptr)
-{
-    return ptr->v;
-}
-
-/* Aligned loads and stores are atomic on x86(-64). */
-static _opa_inline void OPA_store_ptr(OPA_ptr_t *ptr, void *val)
-{
-    ptr->v = val;
-}
-
-/* NOTE-X86-1 x86 and x86_64 processors execute instructions such that their
- * effects are visible in issue order, with one exception:  earlier stores may
- * pass later loads.  Also, non-temporal stores (with the "movnt*" instructions)
- * do not follow these ordering constraints.  So all normal load/store
- * instructions on x86(_64) already have acquire/release semantics.  We just
- * have to make sure that the compiler does not reorder the instructions. */
-
-static _opa_inline int OPA_load_acquire_int(_opa_const OPA_int_t *ptr)
-{
-    int tmp;
-    tmp = ptr->v;
-    OPA_compiler_barrier(); /* NOTE-X86-1 */
-    return tmp;
-}
-
-static _opa_inline void OPA_store_release_int(OPA_int_t *ptr, int val)
-{
-    OPA_compiler_barrier(); /* NOTE-X86-1 */
-    ptr->v = val;
-}
-
-static _opa_inline void *OPA_load_acquire_ptr(_opa_const OPA_ptr_t *ptr)
-{
-    void *tmp;
-    tmp = ptr->v;
-    OPA_compiler_barrier(); /* NOTE-X86-1 */
-    return tmp;
-}
-
-static _opa_inline void OPA_store_release_ptr(OPA_ptr_t *ptr, void *val)
-{
-    OPA_compiler_barrier(); /* NOTE-X86-1 */
-    ptr->v = val;
-}
-
-
-static _opa_inline void OPA_add_int(OPA_int_t *ptr, int val)
-{
-    __asm__ __volatile__ ("lock ; add"OPA_SS" %1,%0"
-                          :"=m" (ptr->v)
-                          :"ir" (val), "m" (ptr->v));
-    return;
-}
-
-static _opa_inline void OPA_incr_int(OPA_int_t *ptr)
-{
-    __asm__ __volatile__ ("lock ; inc"OPA_SS" %0"
-                          :"=m" (ptr->v)
-                          :"m" (ptr->v));
-    return;
-}
-
-static _opa_inline void OPA_decr_int(OPA_int_t *ptr)
-{
-    __asm__ __volatile__ ("lock ; dec"OPA_SS" %0"
-                          :"=m" (ptr->v)
-                          :"m" (ptr->v));
-    return;
-}
-
-
-static _opa_inline int OPA_decr_and_test_int(OPA_int_t *ptr)
-{
-    char result;
-    __asm__ __volatile__ ("lock ; dec"OPA_SS" %0; setz %1"
-                          :"=m" (ptr->v), "=q" (result)
-                          :"m" (ptr->v));
-    return result;
-}
-
-static _opa_inline int OPA_fetch_and_add_int(OPA_int_t *ptr, int val)
-{
-    __asm__ __volatile__ ("lock ; xadd %0,%1"
-                          : "=r" (val), "=m" (ptr->v)
-                          :  "0" (val),  "m" (ptr->v));
-    return val;
-}
-
-#define OPA_fetch_and_incr_int_by_faa OPA_fetch_and_incr_int
-#define OPA_fetch_and_decr_int_by_faa OPA_fetch_and_decr_int
-
-
-static _opa_inline void *OPA_cas_ptr(OPA_ptr_t *ptr, void *oldv, void *newv)
-{
-    void *prev;
-    __asm__ __volatile__ ("lock ; cmpxchg %3,%4"
-                          : "=a" (prev), "=m" (ptr->v)
-                          : "0" (oldv), "q" (newv), "m" (ptr->v));
-    return prev;
-}
-
-static _opa_inline int OPA_cas_int(OPA_int_t *ptr, int oldv, int newv)
-{
-    int prev;
-    __asm__ __volatile__ ("lock ; cmpxchg %3,%4"
-                          : "=a" (prev), "=m" (ptr->v)
-                          : "0" (oldv), "q" (newv), "m" (ptr->v));
-    return prev;
-}
-
-static _opa_inline void *OPA_swap_ptr(OPA_ptr_t *ptr, void *val)
-{
-    __asm__ __volatile__ ("xchg %0,%1"
-                          :"=r" (val), "=m" (ptr->v)
-                          : "0" (val),  "m" (ptr->v));
-    return val;
-}
-
-static _opa_inline int OPA_swap_int(OPA_int_t *ptr, int val)
-{
-    __asm__ __volatile__ ("xchg %0,%1"
-                          :"=r" (val), "=m" (ptr->v)
-                          : "0" (val),  "m" (ptr->v));
-    return val;
-}
-
-#undef OPA_SS
-
-#endif /* OPA_GCC_INTEL_32_64_OPS_H_INCLUDED */
diff --git a/linx64/mpi/mpich/include/primitives/opa_gcc_intel_32_64_p3.h b/linx64/mpi/mpich/include/primitives/opa_gcc_intel_32_64_p3.h
deleted file mode 100644
index 7fad12a3..00000000
--- a/linx64/mpi/mpich/include/primitives/opa_gcc_intel_32_64_p3.h
+++ /dev/null
@@ -1,15 +0,0 @@
-/* -*- Mode: C; c-basic-offset:4 ; indent-tabs-mode:nil ; -*- */
-/*
- *  (C) 2008 by Argonne National Laboratory.
- *      See COPYRIGHT in top-level directory.
- */
-
-#ifndef OPA_GCC_INTEL_32_64_P3_H_INCLUDED
-#define OPA_GCC_INTEL_32_64_P3_H_INCLUDED
-
-#include "opa_gcc_intel_32_64_p3barrier.h"
-#include "opa_gcc_intel_32_64_ops.h"
-
-#include "opa_emulated.h"
-
-#endif /* OPA_GCC_INTEL_32_64_P3_H_INCLUDED */
diff --git a/linx64/mpi/mpich/include/primitives/opa_gcc_intel_32_64_p3barrier.h b/linx64/mpi/mpich/include/primitives/opa_gcc_intel_32_64_p3barrier.h
deleted file mode 100644
index ecd68527..00000000
--- a/linx64/mpi/mpich/include/primitives/opa_gcc_intel_32_64_p3barrier.h
+++ /dev/null
@@ -1,34 +0,0 @@
-/* -*- Mode: C; c-basic-offset:4 ; indent-tabs-mode:nil ; -*- */
-/*
- *  (C) 2008 by Argonne National Laboratory.
- *      See COPYRIGHT in top-level directory.
- */
-
-#ifndef OPA_GCC_INTEL_32_64_P3BARRIER_H_INCLUDED
-#define OPA_GCC_INTEL_32_64_P3BARRIER_H_INCLUDED
-
-#define OPA_compiler_barrier() __asm__ __volatile__ ( "" ::: "memory" )
-
-/* For all regular memory (write-back cacheable, not driver/graphics
- * memory), there is only one general ordering relaxation permitted by
- * x86/x86_64 processors: earlier stores may be retired after later
- * stores.  The "clflush" and "movnt*" instructions also don't follow
- * general ordering constraints, although any code using these
- * instructions should be responsible for ensuring proper ordering
- * itself.  So our read and write barriers may be implemented as simple
- * compiler barriers. */
-#define OPA_write_barrier() OPA_compiler_barrier()
-#define OPA_read_barrier()  OPA_compiler_barrier()
-
-/* Some Pentium III and earlier processors have store barriers
-   (sfence), but no full barrier or load barriers.  Some other very
-   recent x86-like processors don't seem to have sfence either.  A
-   lock-prefixed atomic instruction (operating on any memory) behaves as
-   a full memory barrier, so we use that here. */
-static inline void OPA_read_write_barrier(void)
-{
-    int a = 0;
-    __asm__ __volatile__ ("lock orl $0, %0" : "+m" (a) : /*no outputs*/ : "memory");
-}
-
-#endif /* OPA_GCC_INTEL_32_64_P3BARRIER_H_INCLUDED */
diff --git a/linx64/mpi/mpich/include/primitives/opa_gcc_intrinsics.h b/linx64/mpi/mpich/include/primitives/opa_gcc_intrinsics.h
deleted file mode 100644
index 9857770c..00000000
--- a/linx64/mpi/mpich/include/primitives/opa_gcc_intrinsics.h
+++ /dev/null
@@ -1,129 +0,0 @@
-/* -*- Mode: C; c-basic-offset:4 ; indent-tabs-mode:nil ; -*- */
-/*  
- *  (C) 2008 by Argonne National Laboratory.
- *      See COPYRIGHT in top-level directory.
- */
-
-/* FIXME needs to be converted to new style functions with OPA_int_t/OPA_ptr_t-types */
-#ifndef OPA_GCC_INTRINSICS_H_INCLUDED
-#define OPA_GCC_INTRINSICS_H_INCLUDED
-
-/* FIXME do we need to align these? */
-typedef struct { volatile int v;    } OPA_int_t;
-typedef struct { void * volatile v; } OPA_ptr_t;
-
-#define OPA_INT_T_INITIALIZER(val_) { (val_) }
-#define OPA_PTR_T_INITIALIZER(val_) { (val_) }
-
-/* Assume that loads/stores are atomic on the current platform, even though this
-   may not be true at all. */
-static _opa_inline int OPA_load_int(_opa_const OPA_int_t *ptr)
-{
-    return ptr->v;
-}
-
-static _opa_inline void OPA_store_int(OPA_int_t *ptr, int val)
-{
-    ptr->v = val;
-}
-
-static _opa_inline void *OPA_load_ptr(_opa_const OPA_ptr_t *ptr)
-{
-    return ptr->v;
-}
-
-static _opa_inline void OPA_store_ptr(OPA_ptr_t *ptr, void *val)
-{
-    ptr->v = val;
-}
-
-static _opa_inline int OPA_load_acquire_int(_opa_const OPA_int_t *ptr)
-{
-    volatile int i = 0;
-    int tmp;
-    tmp = ptr->v;
-    __sync_lock_test_and_set(&i, 1); /* guarantees acquire semantics */
-    return tmp;
-}
-
-static _opa_inline void OPA_store_release_int(OPA_int_t *ptr, int val)
-{
-    volatile int i = 1;
-    __sync_lock_release(&i); /* guarantees release semantics */
-    ptr->v = val;
-}
-
-static _opa_inline void *OPA_load_acquire_ptr(_opa_const OPA_ptr_t *ptr)
-{
-    volatile int i = 0;
-    void *tmp;
-    tmp = ptr->v;
-    __sync_lock_test_and_set(&i, 1); /* guarantees acquire semantics */
-    return tmp;
-}
-
-static _opa_inline void OPA_store_release_ptr(OPA_ptr_t *ptr, void *val)
-{
-    volatile int i = 1;
-    __sync_lock_release(&i); /* guarantees release semantics */
-    ptr->v = val;
-}
-
-
-/* gcc atomic intrinsics accept an optional list of variables to be
-   protected by a memory barrier.  These variables are labeled
-   below by "protected variables :". */
-
-static _opa_inline int OPA_fetch_and_add_int(OPA_int_t *ptr, int val)
-{
-    return __sync_fetch_and_add(&ptr->v, val, /* protected variables: */ &ptr->v);
-}
-
-static _opa_inline int OPA_decr_and_test_int(OPA_int_t *ptr)
-{
-    return __sync_sub_and_fetch(&ptr->v, 1, /* protected variables: */ &ptr->v) == 0;
-}
-
-#define OPA_fetch_and_incr_int_by_faa OPA_fetch_and_incr_int
-#define OPA_fetch_and_decr_int_by_faa OPA_fetch_and_decr_int
-#define OPA_add_int_by_faa OPA_add_int
-#define OPA_incr_int_by_fai OPA_incr_int
-#define OPA_decr_int_by_fad OPA_decr_int
-
-
-static _opa_inline void *OPA_cas_ptr(OPA_ptr_t *ptr, void *oldv, void *newv)
-{
-    return __sync_val_compare_and_swap(&ptr->v, oldv, newv, /* protected variables: */ &ptr->v);
-}
-
-static _opa_inline int OPA_cas_int(OPA_int_t *ptr, int oldv, int newv)
-{
-    return __sync_val_compare_and_swap(&ptr->v, oldv, newv, /* protected variables: */ &ptr->v);
-}
-
-#ifdef SYNC_LOCK_TEST_AND_SET_IS_SWAP
-static _opa_inline void *OPA_swap_ptr(OPA_ptr_t *ptr, void *val)
-{
-    return __sync_lock_test_and_set(&ptr->v, val, /* protected variables: */ &ptr->v);
-}
-
-static _opa_inline int OPA_swap_int(OPA_int_t *ptr, int val)
-{
-    return __sync_lock_test_and_set(&ptr->v, val, /* protected variables: */ &ptr->v);
-}
-
-#else
-#define OPA_swap_ptr_by_cas OPA_swap_ptr
-#define OPA_swap_int_by_cas OPA_swap_int 
-#endif
-
-#define OPA_write_barrier()      __sync_synchronize()
-#define OPA_read_barrier()       __sync_synchronize()
-#define OPA_read_write_barrier() __sync_synchronize()
-#define OPA_compiler_barrier()   __asm__ __volatile__  ( ""  ::: "memory" )
-
-
-
-#include"opa_emulated.h"
-
-#endif /* OPA_GCC_INTRINSICS_H_INCLUDED */
diff --git a/linx64/mpi/mpich/include/primitives/opa_gcc_ppc.h b/linx64/mpi/mpich/include/primitives/opa_gcc_ppc.h
deleted file mode 100644
index 410d5616..00000000
--- a/linx64/mpi/mpich/include/primitives/opa_gcc_ppc.h
+++ /dev/null
@@ -1,180 +0,0 @@
-/* -*- Mode: C; c-basic-offset:4 ; indent-tabs-mode:nil ; -*- */
-/*  
- *  (C) 2008 by Argonne National Laboratory.
- *      See COPYRIGHT in top-level directory.
- */
-
-#ifndef OPA_GCC_PPC_H_INCLUDED
-#define OPA_GCC_PPC_H_INCLUDED
-
-/* these need to be aligned on an 8-byte boundary to work on a BG/P */
-typedef struct { volatile int v    OPA_ATTRIBUTE((aligned (8))); } OPA_int_t;
-typedef struct { void * volatile v OPA_ATTRIBUTE((aligned (8))); } OPA_ptr_t;
-
-#define OPA_INT_T_INITIALIZER(val_) { (val_) }
-#define OPA_PTR_T_INITIALIZER(val_) { (val_) }
-
-/* Aligned loads and stores are atomic. */
-static _opa_inline int OPA_load_int(_opa_const OPA_int_t *ptr)
-{
-    return ptr->v;
-}
-
-/* Aligned loads and stores are atomic. */
-static _opa_inline void OPA_store_int(OPA_int_t *ptr, int val)
-{
-    ptr->v = val;
-}
-
-/* Aligned loads and stores are atomic. */
-static _opa_inline void *OPA_load_ptr(_opa_const OPA_ptr_t *ptr)
-{
-    return ptr->v;
-}
-
-/* Aligned loads and stores are atomic. */
-static _opa_inline void OPA_store_ptr(OPA_ptr_t *ptr, void *val)
-{
-    ptr->v = val;
-}
-
-/* a useful link for PPC memory ordering issues:
- *   http://www.rdrop.com/users/paulmck/scalability/paper/N2745r.2009.02.22a.html
- *
- * lwsync: orders L-L, S-S, L-S, but *not* S-L (i.e. gives x86-ish ordering)
- * eieio: orders S-S (but only for cacheable memory, not for MMIO)
- * sync: totally orders memops
- * isync: force all preceeding insns to appear complete before starting
- *        subsequent insns, but w/o cumulativity (very confusing)
- */
-/* helper macros */
-#define OPA_ppc_lwsync_() __asm__ __volatile__  ( "lwsync" ::: "memory" )
-#define OPA_ppc_hwsync_() __asm__ __volatile__  ( "sync"   ::: "memory" )
-#define OPA_ppc_eieio_()  __asm__ __volatile__  ( "eieio"  ::: "memory" )
-
-#define OPA_write_barrier()      OPA_ppc_eieio_()
-#define OPA_read_barrier()       OPA_ppc_lwsync_()
-#define OPA_read_write_barrier() OPA_ppc_hwsync_()
-#define OPA_compiler_barrier()   __asm__ __volatile__  ( "" ::: "memory" )
-
-/* NOTE-PPC-1 we use lwsync, although I think we might be able to use
- * conditional-branch+isync in some cases (load_acquire?) once we understand it
- * better */
-
-static _opa_inline int   OPA_load_acquire_int(_opa_const OPA_int_t *ptr)
-{
-    int tmp;
-    tmp = ptr->v;
-    OPA_ppc_lwsync_(); /* NOTE-PPC-1 */
-    return tmp;
-}
-static _opa_inline void  OPA_store_release_int(OPA_int_t *ptr, int val)
-{
-    OPA_ppc_lwsync_();
-    ptr->v = val;
-}
-static _opa_inline void *OPA_load_acquire_ptr(_opa_const OPA_ptr_t *ptr)
-{
-    void *tmp;
-    tmp = ptr->v;
-    OPA_ppc_lwsync_(); /* NOTE-PPC-1 */
-    return tmp;
-}
-static _opa_inline void  OPA_store_release_ptr(OPA_ptr_t *ptr, void *val)
-{
-    OPA_ppc_lwsync_();
-    ptr->v = val;
-}
-
-
-/*
-   load-link/store-conditional (LL/SC) primitives.  We LL/SC implement
-   these here, which are arch-specific, then use the generic
-   implementations from opa_emulated.h */
-
-static _opa_inline int OPA_LL_int(OPA_int_t *ptr)
-{
-    int val;
-    __asm__ __volatile__ ("lwarx %[val],0,%[ptr]"
-                          : [val] "=r" (val)
-                          : [ptr] "r" (&ptr->v)
-                          : "cc");
-
-    return val;
-}
-
-/* Returns non-zero if the store was successful, zero otherwise. */
-static _opa_inline int OPA_SC_int(OPA_int_t *ptr, int val)
-{
-    int ret = 1; /* init to non-zero, will be reset to 0 if SC was unsuccessful */
-    __asm__ __volatile__ ("stwcx. %[val],0,%[ptr];\n"
-                          "beq 1f;\n"
-                          "li %[ret], 0;\n"
-                          "1: ;\n"
-                          : [ret] "=r" (ret)
-                          : [ptr] "r" (&ptr->v), [val] "r" (val), "0" (ret)
-                          : "cc", "memory");
-    return ret;
-}
-
-
-/* Pointer versions of LL/SC. */
-
-/* Set OPA_SS (Size Suffix) which is used to choose between lwarx/stwcx and
- * ldarx/stdcx when using 4 or 8 byte pointer operands */
-#if OPA_SIZEOF_VOID_P == 4
-#define OPA_SS "w"
-#elif OPA_SIZEOF_VOID_P == 8
-#define OPA_SS "d"
-#else
-#error OPA_SIZEOF_VOID_P is not 4 or 8
-#endif
-
-
-static _opa_inline void *OPA_LL_ptr(OPA_ptr_t *ptr)
-{
-    void *val;
-    __asm__ __volatile__ ("l"OPA_SS"arx %[val],0,%[ptr]"
-                          : [val] "=r" (val)
-                          : [ptr] "r" (&ptr->v)
-                          : "cc");
-
-    return val;
-}
-
-/* Returns non-zero if the store was successful, zero otherwise. */
-static _opa_inline int OPA_SC_ptr(OPA_ptr_t *ptr, void *val)
-{
-    int ret = 1; /* init to non-zero, will be reset to 0 if SC was unsuccessful */
-    __asm__ __volatile__ ("st"OPA_SS"cx. %[val],0,%[ptr];\n"
-                          "beq 1f;\n"
-                          "li %[ret], 0;\n"
-                          "1: ;\n"
-                          : [ret] "=r" (ret)
-                          : [ptr] "r" (&ptr->v), [val] "r" (val), "0" (ret)
-                          : "cc", "memory");
-    return ret;
-}
-
-#undef OPA_SS
-
-/* necessary to enable LL/SC emulation support */
-#define OPA_LL_SC_SUPPORTED 1
-
-/* Implement all function using LL/SC */
-#define OPA_add_int_by_llsc            OPA_add_int
-#define OPA_incr_int_by_llsc           OPA_incr_int
-#define OPA_decr_int_by_llsc           OPA_decr_int
-#define OPA_decr_and_test_int_by_llsc  OPA_decr_and_test_int
-#define OPA_fetch_and_add_int_by_llsc  OPA_fetch_and_add_int
-#define OPA_fetch_and_decr_int_by_llsc OPA_fetch_and_decr_int
-#define OPA_fetch_and_incr_int_by_llsc OPA_fetch_and_incr_int
-#define OPA_cas_ptr_by_llsc        OPA_cas_ptr
-#define OPA_cas_int_by_llsc        OPA_cas_int
-#define OPA_swap_ptr_by_llsc       OPA_swap_ptr
-#define OPA_swap_int_by_llsc       OPA_swap_int
-
-
-#include "opa_emulated.h"
-
-#endif /* OPA_GCC_PPC_H_INCLUDED */
diff --git a/linx64/mpi/mpich/include/primitives/opa_gcc_sicortex.h b/linx64/mpi/mpich/include/primitives/opa_gcc_sicortex.h
deleted file mode 100644
index abe3dfdc..00000000
--- a/linx64/mpi/mpich/include/primitives/opa_gcc_sicortex.h
+++ /dev/null
@@ -1,443 +0,0 @@
-/* -*- Mode: C; c-basic-offset:4 ; indent-tabs-mode:nil ; -*- */
-/*
- *  (C) 2008 by Argonne National Laboratory.
- *      See COPYRIGHT in top-level directory.
- */
-
-/* Atomic primitives for SiCortex machines.
- * Originally contributed by Lawrence Stewart at SiCortex.
- */
-
-#ifndef OPA_GCC_SICORTEX_H
-#define OPA_GCC_SICORTEX_H
-
-/* FIXME do these need alignment? */
-typedef struct { volatile int v;  } OPA_int_t;
-typedef struct { int * volatile v; } OPA_ptr_t;
-
-#define OPA_INT_T_INITIALIZER(val_) { (val_) }
-#define OPA_PTR_T_INITIALIZER(val_) { (val_) }
-
-#define OPA_write_barrier()      __asm__ __volatile__  ("sync" ::: "memory" )
-#define OPA_read_barrier()       __asm__ __volatile__  ("sync" ::: "memory" )
-#define OPA_read_write_barrier() __asm__ __volatile__  ("sync" ::: "memory" )
-#define OPA_compiler_barrier()   __asm__ __volatile__  ( ""    ::: "memory" )
-
-/* Aligned loads and stores are atomic. */
-static _opa_inline int OPA_load_int(_opa_const OPA_int_t *ptr)
-{
-    return ptr->v;
-}
-
-/* Aligned loads and stores are atomic. */
-static _opa_inline void OPA_store_int(OPA_int_t *ptr, int val)
-{
-    ptr->v = val;
-}
-
-/* Aligned loads and stores are atomic. */
-static _opa_inline void *OPA_load_ptr(_opa_const OPA_ptr_t *ptr)
-{
-    return ptr->v;
-}
-
-/* Aligned loads and stores are atomic. */
-static _opa_inline void OPA_store_ptr(OPA_ptr_t *ptr, void *val)
-{
-    ptr->v = val;
-}
-
-/* NOTE: these acquire/release operations have not been optimized, I just threw
- * down a full memory barrier.  Spending much time working on the SiCortex platform
- * doesn't really make a lot of sense since there are so few machines in
- * existence and no more will ever be built. */
-static _opa_inline int OPA_load_acquire_int(_opa_const OPA_int_t *ptr)
-{
-    int tmp;
-    tmp = ptr->v;
-    OPA_read_write_barrier();
-    return tmp;
-}
-
-static _opa_inline void OPA_store_release_int(OPA_int_t *ptr, int val)
-{
-    OPA_read_write_barrier();
-    ptr->v = val;
-}
-
-static _opa_inline void *OPA_load_acquire_ptr(_opa_const OPA_ptr_t *ptr)
-{
-    void *tmp;
-    tmp = ptr->v;
-    OPA_read_write_barrier();
-    return tmp;
-}
-
-static _opa_inline void OPA_store_release_ptr(OPA_ptr_t *ptr, void *val)
-{
-    OPA_read_write_barrier();
-    ptr->v = val;
-}
-
-#include <stdint.h>
-
-/* ICE9 rev A1 chips have a low-frequency bug that causes LL to
-   fail. The workaround is to do the LL twice to make sure the data
-   is in L1
-
-   very few systems are affected
-
-   FIXME We should either remove the workaround entirely or make it
-   configurable/autodetected somehow. [goodell@ 2008/01/06]
- */
-#define ICE9A_LLSC_WAR 0
-
-/* For a description of the _opa_inline assembly constraints, see the MIPS section of:
-   http://gcc.gnu.org/onlinedocs/gcc-4.3.2/gcc/Machine-Constraints.html#Machine-Constraints
-
-   relevant excerpt:
-       I - A signed 16-bit constant (for arithmetic instructions).
-       J - Integer zero.
-
-   Other _opa_inline asm knowledge worth remembering:
-       r - a general register operand is allowed
-       m - a memory address operand
-       & - earlyclobber; operand is modified before instruction is finished using the input operands
-       = - this operand is write-only
-
-   general format:
-       asm volatile ("instructions" : [outputs] : [inputs] : [clobbered_regs]);
-       "memory" should be included as a clobbered reg for most of these operations.
- */
-
-/* Atomic increment of a 32 bit value, returning the old value */
-static _opa_inline int OPA_shmemi_fetch_add_4(volatile int * v, int inc)
-{
-        unsigned long result;
-        if (ICE9A_LLSC_WAR) {
-                unsigned long temp;
-
-                __asm__ __volatile__(
-                "       .set    mips3                                   \n"
-                "       .set    noreorder                               \n"
-                "1:     ll      %0, %2          # fetch_add_4           \n"
-                "       ll      %0, %2          # fetch_add_4           \n"
-                "       addu    %1, %0, %3                              \n"
-                "       sc      %1, %2                                  \n"
-                "       beqz    %1, 1b                                  \n"
-                "        nop                                            \n"
-                "       .set    reorder                                 \n"
-                "       .set    mips0                                   \n"
-                : "=&r" (result), "=&r" (temp), "=m" (*v)
-                : "Ir" (inc)
-                : "memory");
-        } else {
-                unsigned long temp;
-
-                __asm__ __volatile__(
-                "       .set    mips3                                   \n"
-                "       .set    noreorder                               \n"
-                "1:     ll      %0, %2          # fetch_add_4           \n"
-                "       addu    %1, %0, %3                              \n"
-                "       sc      %1, %2                                  \n"
-                "       beqz    %1, 1b                                  \n"
-                "        nop                                            \n"
-                "       .set    reorder                                 \n"
-                "       .set    mips0                                   \n"
-                : "=&r" (result), "=&r" (temp), "=m" (*v)
-                : "Ir" (inc)
-                : "memory");
-        }
-
-        return result;
-}
-
-/* Atomic increment of a 64 bit value, returning the old value */
-static _opa_inline long int OPA_shmemi_fetch_add_8(volatile long int * v, long int inc)
-{
-        unsigned long result;
-        if (ICE9A_LLSC_WAR) {
-                unsigned long temp;
-
-                __asm__ __volatile__(
-                "       .set    mips3                                   \n"
-                "       .set    noreorder                               \n"
-                "1:     lld     %0, %2          # fetch_add_8           \n"
-                "       lld     %0, %2          # fetch_add_8           \n"
-                "       daddu   %1, %0, %3                              \n"
-                "       scd     %1, %2                                  \n"
-                "       beqz    %1, 1b                                  \n"
-                "        nop                                            \n"
-                "       .set    reorder                                 \n"
-                "       .set    mips0                                   \n"
-                : "=&r" (result), "=&r" (temp), "=m" (*v)
-                : "Ir" (inc)
-                : "memory");
-        } else {
-                unsigned long temp;
-
-                __asm__ __volatile__(
-                "       .set    mips3                                   \n"
-                "       .set    noreorder                               \n"
-                "1:     lld     %0, %2          # fetch_add_8           \n"
-                "       daddu   %1, %0, %3                              \n"
-                "       scd     %1, %2                                  \n"
-                "       beqz    %1, 1b                                  \n"
-                "        nop                                            \n"
-                "       .set    reorder                                 \n"
-                "       .set    mips0                                   \n"
-                : "=&r" (result), "=&r" (temp), "=m" (*v)
-                : "Ir" (inc)
-                : "memory");
-        }
-
-        return result;
-}
-
-/* Atomic swap of a 32 bit value, returning the old contents */
-static _opa_inline int OPA_shmemi_swap_4(volatile int * v, int val)
-{
-        unsigned long result;
-        if (ICE9A_LLSC_WAR) {
-                unsigned long temp;
-
-                __asm__ __volatile__(
-                "       .set    mips3                                   \n"
-                "       .set    noreorder                               \n"
-                "1:     ll      %0, %2          # swap_4                \n"
-                "       ll      %0, %2          # swap_4                \n"
-                "       move    %1, %3                                  \n"
-                "       sc      %1, %2                                  \n"
-                "       beqz    %1, 1b                                  \n"
-                "        nop                                            \n"
-                "       .set    reorder                                 \n"
-                "       .set    mips0                                   \n"
-                : "=&r" (result), "=&r" (temp), "=m" (*v)
-                : "r" (val)
-                : "memory");
-        } else {
-                unsigned long temp;
-
-                __asm__ __volatile__(
-                "       .set    mips3                                   \n"
-                "       .set    noreorder                               \n"
-                "1:     ll      %0, %2          # swap_4                \n"
-                "       move    %1, %3                                  \n"
-                "       sc      %1, %2                                  \n"
-                "       beqz    %1, 1b                                  \n"
-                "        nop                                            \n"
-                "       .set    reorder                                 \n"
-                "       .set    mips0                                   \n"
-                : "=&r" (result), "=&r" (temp), "=m" (*v)
-                : "r" (val)
-                : "memory");
-        }
-
-        return result;
-}
-
-/* Atomic swap of a 64 bit value, returning the old contents */
-static _opa_inline long int OPA_shmemi_swap_8(volatile long int * v, long int val)
-{
-        unsigned long result;
-        if (ICE9A_LLSC_WAR) {
-                unsigned long temp;
-
-                __asm__ __volatile__(
-                "       .set    mips3                                   \n"
-                "       .set    noreorder                               \n"
-                "1:     lld     %0, %2          # swap_8                \n"
-                "       lld     %0, %2          # swap_8                \n"
-                "       move    %1, %3                                  \n"
-                "       scd     %1, %2                                  \n"
-                "       beqz    %1, 1b                                  \n"
-                "        nop                                            \n"
-                "       .set    reorder                                 \n"
-                "       .set    mips0                                   \n"
-                : "=&r" (result), "=&r" (temp), "=m" (*v)
-                : "r" (val)
-                : "memory");
-        } else {
-                unsigned long temp;
-
-                __asm__ __volatile__(
-                "       .set    mips3                                   \n"
-                "       .set    noreorder                               \n"
-                "1:     lld     %0, %2          # swap_8                \n"
-                "       move    %1, %3                                  \n"
-                "       scd     %1, %2                                  \n"
-                "       beqz    %1, 1b                                  \n"
-                "        nop                                            \n"
-                "       .set    reorder                                 \n"
-                "       .set    mips0                                   \n"
-                : "=&r" (result), "=&r" (temp), "=m" (*v)
-                : "r" (val)
-                : "memory");
-        }
-
-        return result;
-}
-
-/* Atomic compare and swap of a 32 bit value, returns the old value
- * but only does the store of the val value if the old value == expect */
-static _opa_inline int OPA_shmemi_cswap_4(volatile int * v, int expect, int val)
-{
-        unsigned long result;
-        if (ICE9A_LLSC_WAR) {
-                unsigned long temp;
-
-                __asm__ __volatile__(
-                "       .set    mips3                                   \n"
-                "       .set    noreorder                               \n"
-                "1:     ll      %0, %2          # cswap_4               \n"
-                "       ll      %0, %2          # cswap_4               \n"
-                "       bne     %0, %4, 1f                              \n"
-                "       move    %1, %3                                  \n"
-                "       sc      %1, %2                                  \n"
-                "       beqz    %1, 1b                                  \n"
-                "        nop                                            \n"
-                "       .set    reorder                                 \n"
-                "1:                                                     \n"
-                "       .set    mips0                                   \n"
-                : "=&r" (result), "=&r" (temp), "=m" (*v)
-                : "r" (val), "Jr" (expect)
-                : "memory");
-        } else {
-                unsigned long temp;
-
-                __asm__ __volatile__(
-                "       .set    mips3                                   \n"
-                "       .set    noreorder                               \n"
-                "1:     ll      %0, %2          # cswap_4               \n"
-                "       bne     %0, %4, 1f                              \n"
-                "       move    %1, %3                                  \n"
-                "       sc      %1, %2                                  \n"
-                "       beqz    %1, 1b                                  \n"
-                "        nop                                            \n"
-                "       .set    reorder                                 \n"
-                "1:                                                     \n"
-                "       .set    mips0                                   \n"
-                : "=&r" (result), "=&r" (temp), "=m" (*v)
-                : "r" (val), "Jr" (expect)
-                : "memory");
-        }
-
-        return result;
-}
-
-/* Atomic compare and swap of a 64 bit value, returns the old value
- * but only does the store of the val value if the old value == expect */
-static _opa_inline long int OPA_shmemi_cswap_8(volatile long int * v, long int expect, long int val)
-{
-        unsigned long result;
-        if (ICE9A_LLSC_WAR) {
-                unsigned long temp;
-
-                __asm__ __volatile__(
-                "       .set    mips3                                   \n"
-                "       .set    noreorder                               \n"
-                "1:     lld     %0, %2          # cswap_8               \n"
-                "       lld     %0, %2          # cswap_8               \n"
-                "       bne     %0, %4, 1f                              \n"
-                "       move    %1, %3                                  \n"
-                "       scd     %1, %2                                  \n"
-                "       beqz    %1, 1b                                  \n"
-                "        nop                                            \n"
-                "       .set    reorder                                 \n"
-                "1:                                                     \n"
-                "       .set    mips0                                   \n"
-                : "=&r" (result), "=&r" (temp), "=m" (*v)
-                : "r" (val), "Jr" (expect)
-                : "memory");
-        } else {
-                unsigned long temp;
-
-                __asm__ __volatile__(
-                "       .set    mips3                                   \n"
-                "       .set    noreorder                               \n"
-                "1:     lld     %0, %2          # cswap_8               \n"
-                "       bne     %0, %4, 1f                              \n"
-                "       move    %1, %3                                  \n"
-                "       scd     %1, %2                                  \n"
-                "       beqz    %1, 1b                                  \n"
-                "        nop                                            \n"
-                "       .set    reorder                                 \n"
-                "1:                                                     \n"
-                "       .set    mips0                                   \n"
-                : "=&r" (result), "=&r" (temp), "=m" (*v)
-                : "r" (val), "Jr" (expect)
-                : "memory");
-        }
-
-        return result;
-}
-
-static _opa_inline void OPA_add_int(OPA_int_t *ptr, int val)
-{
-    OPA_shmemi_fetch_add_4(&ptr->v, val);
-}
-
-static _opa_inline void *OPA_cas_ptr(OPA_ptr_t *ptr, void *oldv, void *newv)
-{
-#if (OPA_SIZEOF_VOID_P == 8)
-    return((int *) OPA_shmemi_cswap_8((volatile long int *) &ptr->v, (uintptr_t) oldv, (uintptr_t) newv));
-#elif (OPA_SIZEOF_VOID_P == 4)
-    return((int *) OPA_shmemi_cswap_4((volatile int *) &ptr->v, (uintptr_t) oldv, (uintptr_t) newv));
-#else
-#error "OPA_SIZEOF_VOID_P has an unexpected value :" OPA_QUOTE(OPA_SIZEOF_VOID_P);
-#endif
-}
-
-static _opa_inline int OPA_cas_int(OPA_int_t *ptr, int oldv, int newv)
-{
-    return(OPA_shmemi_cswap_4(&ptr->v, oldv, newv));
-}
-
-static _opa_inline void OPA_decr_int(OPA_int_t *ptr)
-{
-    OPA_shmemi_fetch_add_4(&ptr->v, -1);
-}
-
-static _opa_inline int OPA_decr_and_test_int(OPA_int_t *ptr)
-{
-    int old = OPA_shmemi_fetch_add_4(&ptr->v, -1);
-    return (old == 1);
-}
-
-static _opa_inline int OPA_fetch_and_add_int(OPA_int_t *ptr, int val)
-{
-    return(OPA_shmemi_fetch_add_4(&ptr->v, val));
-}
-
-static _opa_inline int OPA_fetch_and_decr_int(OPA_int_t *ptr)
-{
-    return(OPA_shmemi_fetch_add_4(&ptr->v, -1));
-}
-
-static _opa_inline int OPA_fetch_and_incr_int(OPA_int_t *ptr)
-{
-    return(OPA_shmemi_fetch_add_4(&ptr->v, 1));
-}
-
-static _opa_inline void OPA_incr_int(OPA_int_t *ptr)
-{
-    OPA_shmemi_fetch_add_4(&ptr->v, 1);
-}
-
-static _opa_inline int *OPA_swap_ptr(OPA_ptr_t *ptr, int *val)
-{
-#if (OPA_SIZEOF_VOID_P == 8)
-    return((int *) OPA_shmemi_swap_8((volatile long int *) &ptr->v, (uintptr_t) val));
-#elif (OPA_SIZEOF_VOID_P == 4)
-    return((int *) OPA_shmemi_swap_4((volatile int *) &ptr->v, (uintptr_t) val));
-#else
-#error "OPA_SIZEOF_VOID_P has an unexpected value :" OPA_QUOTE(OPA_SIZEOF_VOID_P);
-#endif
-}
-
-static _opa_inline int OPA_swap_int(OPA_int_t *ptr, int val)
-{
-    return(OPA_shmemi_swap_4(&ptr->v, val));
-}
-
-#endif /* OPA_GCC_SICORTEX_H */
diff --git a/linx64/mpi/mpich/include/primitives/opa_nt_intrinsics.h b/linx64/mpi/mpich/include/primitives/opa_nt_intrinsics.h
deleted file mode 100644
index 787cb0f1..00000000
--- a/linx64/mpi/mpich/include/primitives/opa_nt_intrinsics.h
+++ /dev/null
@@ -1,154 +0,0 @@
-/* -*- Mode: C; c-basic-offset:4 ; indent-tabs-mode:nil ; -*- */
-/*
- *  (C) 2008 by Argonne National Laboratory.
- *      See COPYRIGHT in top-level directory.
- */
-
-#ifndef OPA_NT_INTRINSICS_H_INCLUDED
-#define OPA_NT_INTRINSICS_H_INCLUDED
-
-#define WIN32_LEAN_AND_MEAN
-#include<windows.h>
-#include<intrin.h>
-#include "mpi.h"
-
-/* OPA_int_t uses a long because the compiler intrinsics operate on
- * longs instead of ints. */
-typedef struct { volatile long v;  } OPA_int_t;
-typedef struct { void * volatile v; } OPA_ptr_t;
-
-#define OPA_INT_T_INITIALIZER(val_) { (val_) }
-#define OPA_PTR_T_INITIALIZER(val_) { (val_) }
-
-#define OPA_write_barrier()      _WriteBarrier()
-#define OPA_read_barrier()       _ReadBarrier()
-#define OPA_read_write_barrier() _ReadWriteBarrier()
-/* FIXME there mut be a more efficient way to implement this.  Is "asm {};"
- * sufficient? */
-#define OPA_compiler_barrier()   _ReadWriteBarrier()
-
-static _opa_inline int OPA_load_int(_opa_const OPA_int_t *ptr)
-{
-    return ((int)ptr->v);
-}
-
-static _opa_inline void OPA_store_int(OPA_int_t *ptr, int val)
-{
-    ptr->v = (long)val;
-}
-
-static _opa_inline void *OPA_load_ptr(_opa_const OPA_ptr_t *ptr)
-{
-    return ((void *)ptr->v);
-}
-
-static _opa_inline void OPA_store_ptr(OPA_ptr_t *ptr, void *val)
-{
-    ptr->v = val;
-}
-
-/* NOTE: these acquire/release operations have not been optimized, I just threw
- * down a full memory barrier.  Someone with more Windows expertise should feel
- * free to improve these (for Windows on x86/x86_64 these almost certainly only
- * need to be compiler barriers). */
-static _opa_inline int OPA_load_acquire_int(_opa_const OPA_int_t *ptr)
-{
-    int tmp;
-    tmp = ptr->v;
-    OPA_read_write_barrier();
-    return tmp;
-}
-
-static _opa_inline void OPA_store_release_int(OPA_int_t *ptr, int val)
-{
-    OPA_read_write_barrier();
-    ptr->v = val;
-}
-
-static _opa_inline void *OPA_load_acquire_ptr(_opa_const OPA_ptr_t *ptr)
-{
-    void *tmp;
-    tmp = ptr->v;
-    OPA_read_write_barrier();
-    return tmp;
-}
-
-static _opa_inline void OPA_store_release_ptr(OPA_ptr_t *ptr, void *val)
-{
-    OPA_read_write_barrier();
-    ptr->v = val;
-}
-
-
-static _opa_inline void OPA_add_int(OPA_int_t *ptr, int val)
-{
-    _InterlockedExchangeAdd(&(ptr->v), val);
-}
-
-static _opa_inline void OPA_incr_int(OPA_int_t *ptr)
-{
-    _InterlockedIncrement(&(ptr->v));
-}
-
-static _opa_inline void OPA_decr_int(OPA_int_t *ptr)
-{
-    _InterlockedDecrement(&(ptr->v));
-}
-
-static _opa_inline int OPA_decr_and_test_int(OPA_int_t *ptr)
-{
-    return (_InterlockedDecrement(&(ptr->v)) == 0);
-}
-
-static _opa_inline int OPA_fetch_and_add_int(OPA_int_t *ptr, int val)
-{
-    return ((int)_InterlockedExchangeAdd(&(ptr->v), (long)val));
-}
-
-static _opa_inline void *OPA_cas_ptr(OPA_ptr_t *ptr, void *oldv, void *newv)
-{
-#if (OPA_SIZEOF_VOID_P == 4)
-    return ((void *)(LONG_PTR) _InterlockedCompareExchange((LONG volatile *)&(ptr->v),
-                                                   (LONG)(LONG_PTR)newv,
-                                                   (LONG)(LONG_PTR)oldv)
-           );
-#elif (OPA_SIZEOF_VOID_P == 8)
-    return ((void *)(LONG_PTR)_InterlockedCompareExchange64((__int64 *)&(ptr->v),
-                                                    (INT64)(LONG_PTR)newv,
-                                                    (INT64)(LONG_PTR)oldv)
-           );
-#else
-#error  "OPA_SIZEOF_VOID_P not valid"
-#endif
-}
-
-static _opa_inline void *OPA_swap_ptr(OPA_ptr_t *ptr, void *val)
-{
-#if (OPA_SIZEOF_VOID_P == 4)
-    return (void *)(LONG_PTR )_InterlockedExchange((LONG volatile *)&(ptr->v),
-                                                    (LONG)(LONG_PTR)val);
-#elif (OPA_SIZEOF_VOID_P == 8)
-    return (void *)(LONG_PTR)_InterlockedExchange64((LONG64 volatile *)&(ptr->v),
-                                                     (INT64)(LONG_PTR)val);
-#else
-#error  "OPA_SIZEOF_VOID_P not valid"
-#endif
-}
-
-static _opa_inline int OPA_cas_int(OPA_int_t *ptr, int oldv, int newv)
-{
-    return _InterlockedCompareExchange((long *)&(ptr->v), newv, oldv);
-}
-
-static _opa_inline int OPA_swap_int(OPA_int_t *ptr, int val)
-{
-    return _InterlockedExchange(&(ptr->v), val);
-}
-
-/* Implement fetch_and_incr/decr using fetch_and_add (*_faa) */
-#define OPA_fetch_and_incr_int_by_faa OPA_fetch_and_incr_int
-#define OPA_fetch_and_decr_int_by_faa OPA_fetch_and_decr_int
-
-#include "opa_emulated.h"
-
-#endif /* defined(OPA_NT_INTRINSICS_H_INCLUDED) */
diff --git a/linx64/mpi/mpich/include/primitives/opa_sun_atomic_ops.h b/linx64/mpi/mpich/include/primitives/opa_sun_atomic_ops.h
deleted file mode 100644
index e42d4c97..00000000
--- a/linx64/mpi/mpich/include/primitives/opa_sun_atomic_ops.h
+++ /dev/null
@@ -1,135 +0,0 @@
-/* -*- Mode: C; c-basic-offset:4 ; indent-tabs-mode:nil ; -*- */
-/*  
- *  (C) 2008 by Argonne National Laboratory.
- *      See COPYRIGHT in top-level directory.
- */
-
-
-#ifndef OPA_SUN_ATOMIC_OPS_H_INCLUDED
-#define OPA_SUN_ATOMIC_OPS_H_INCLUDED
-
-#include <atomic.h>
-
-typedef struct { volatile uint_t v;  } OPA_int_t;
-typedef struct { void * volatile v; } OPA_ptr_t;
-
-#define OPA_INT_T_INITIALIZER(val_) { (val_) }
-#define OPA_PTR_T_INITIALIZER(val_) { (val_) }
-
-static _opa_inline int OPA_load_int(_opa_const OPA_int_t *ptr)
-{
-    return (int)ptr->v;
-}
-
-static _opa_inline void OPA_store_int(OPA_int_t *ptr, int val)
-{
-    ptr->v = (uint)val;
-}
-
-static _opa_inline void *OPA_load_ptr(_opa_const OPA_ptr_t *ptr)
-{
-    return ptr->v;
-}
-
-static _opa_inline void OPA_store_ptr(OPA_ptr_t *ptr, void *val)
-{
-    ptr->v = val;
-}
-
-static _opa_inline int OPA_load_acquire_int(_opa_const OPA_int_t *ptr)
-{
-    int tmp;
-    tmp = ptr->v;
-    membar_enter();
-    return tmp;
-}
-
-static _opa_inline void OPA_store_release_int(OPA_int_t *ptr, int val)
-{
-    membar_exit();
-    ptr->v = val;
-}
-
-static _opa_inline void *OPA_load_acquire_ptr(_opa_const OPA_ptr_t *ptr)
-{
-    void *tmp;
-    tmp = ptr->v;
-    membar_enter();
-    return tmp;
-}
-
-static _opa_inline void OPA_store_release_ptr(OPA_ptr_t *ptr, void *val)
-{
-    membar_exit();
-    ptr->v = val;
-}
-
-
-static _opa_inline void OPA_add_int(OPA_int_t *ptr, int val)
-{
-    atomic_add_int(&ptr->v, val);
-}
-
-static _opa_inline void OPA_incr_int(OPA_int_t *ptr)
-{
-    atomic_inc_uint(&ptr->v);
-}
-
-static _opa_inline void OPA_decr_int(OPA_int_t *ptr)
-{
-    atomic_dec_uint(&ptr->v);
-}
-
-
-static _opa_inline int OPA_decr_and_test_int(OPA_int_t *ptr)
-{
-    return atomic_dec_uint_nv(&ptr->v) == 0;    
-}
-
-
-static _opa_inline int OPA_fetch_and_add_int(OPA_int_t *ptr, int val)
-{
-    return (int)atomic_add_int_nv(&ptr->v, val) - val;
-}
-
-static _opa_inline int OPA_fetch_and_decr_int(OPA_int_t *ptr)
-{
-    return (int)atomic_dec_uint_nv(&ptr->v) + 1;
-}
-
-static _opa_inline int OPA_fetch_and_incr_int(OPA_int_t *ptr)
-{
-    return (int)atomic_inc_uint_nv(&ptr->v) - 1;
-}
-
-
-static _opa_inline void *OPA_cas_ptr(OPA_ptr_t *ptr, void *oldv, void *newv)
-{
-    return atomic_cas_ptr(ptr, oldv, newv);
-}
-
-static _opa_inline int OPA_cas_int(OPA_int_t *ptr, int oldv, int newv)
-{
-    return (int)atomic_cas_uint(&ptr->v, (uint_t)oldv, (uint_t)newv);
-}
-
-
-static _opa_inline void *OPA_swap_ptr(OPA_ptr_t *ptr, void *val)
-{
-    return atomic_swap_ptr(ptr, val);
-}
-
-static _opa_inline int OPA_swap_int(OPA_int_t *ptr, int val)
-{
-    return (int)atomic_swap_uint(&ptr->v, (uint_t) val);
-}
-
-
-#define OPA_write_barrier()      membar_producer()
-#define OPA_read_barrier()       membar_consumer()
-#define OPA_read_write_barrier() do { membar_consumer(); membar_producer(); } while (0)
-
-/* is this portable enough? */
-#define OPA_compiler_barrier()   __asm__ __volatile__  ( ""  ::: "memory" )
-
-#endif /* OPA_SUN_ATOMIC_OPS_H_INCLUDED */
diff --git a/linx64/mpi/mpich/include/primitives/opa_unsafe.h b/linx64/mpi/mpich/include/primitives/opa_unsafe.h
deleted file mode 100644
index 99f3cd63..00000000
--- a/linx64/mpi/mpich/include/primitives/opa_unsafe.h
+++ /dev/null
@@ -1,152 +0,0 @@
-/* -*- Mode: C; c-basic-offset:4 ; indent-tabs-mode:nil ; -*- */
-/*
- *  (C) 2008 by Argonne National Laboratory.
- *      See COPYRIGHT in top-level directory.
- */
-
-#ifndef OPA_UNSAFE_H_INCLUDED
-#define OPA_UNSAFE_H_INCLUDED
-
-/* NOTE: These types intentionally do not use volatile in order to provide even
- * better performance.  If a good use case for having unsafe operations with
- * volatile types comes up, we can make two definitions that are conditional on
- * something sort of like NDEBUG. [goodell@ 2009-08-18] */
-typedef struct { int v;  } OPA_int_t;
-typedef struct { int *v; } OPA_ptr_t;
-
-#define OPA_INT_T_INITIALIZER(val_) { (val_) }
-#define OPA_PTR_T_INITIALIZER(val_) { (val_) }
-
-/*
-    Unsafe Primitives
-    -----------------
-
-    These are versions of the atomic primitives that emulate the single-threaded
-    behavior of the primitives but do not attempt to provide any safety against
-    concurrent use.  The primary use case for this implementation is to avoid
-    overhead without code changes in client libraries and applications that have
-    been compiled for single-threaded use only.  They might also be useful for
-    testing (and testing of tests) in some cases.
-
-    Thanks to Josh Haberman for inspiring this primitives implementation.
-*/
-
-static _opa_inline int OPA_load_int(const OPA_int_t *ptr)
-{
-    int retval;
-    retval = ptr->v;
-    return retval;
-}
-
-static _opa_inline void OPA_store_int(OPA_int_t *ptr, int val)
-{
-    ptr->v = val;
-}
-
-static _opa_inline void *OPA_load_ptr(const OPA_ptr_t *ptr)
-{
-    int *retval;
-    retval = ptr->v;
-    return retval;
-}
-
-static _opa_inline void OPA_store_ptr(OPA_ptr_t *ptr, void *val)
-{
-    ptr->v = val;
-}
-
-/* no barrier needed, not even a compiler barrier */
-#define OPA_load_acquire_int(ptr_)       OPA_load_int((ptr_))
-#define OPA_store_release_int(ptr_,val_) OPA_store_int((ptr_),(val_))
-#define OPA_load_acquire_ptr(ptr_)       OPA_load_ptr((ptr_))
-#define OPA_store_release_ptr(ptr_,val_) OPA_store_ptr((ptr_),(val_))
-
-static _opa_inline void OPA_add_int(OPA_int_t *ptr, int val)
-{
-    ptr->v += val;
-}
-
-static _opa_inline void *OPA_cas_ptr(OPA_ptr_t *ptr, int *oldv, int *newv)
-{
-    int *prev;
-    prev = ptr->v;
-    if (prev == oldv) {
-        ptr->v = newv;
-    }
-    return prev;
-}
-
-static _opa_inline int OPA_cas_int(OPA_int_t *ptr, int oldv, int newv)
-{
-    int prev;
-    prev = ptr->v;
-    if (prev == oldv) {
-        ptr->v = newv;
-    }
-    return prev;
-}
-
-static _opa_inline int OPA_decr_and_test_int(OPA_int_t *ptr)
-{
-    int new_val;
-    new_val = --(ptr->v);
-    return (0 == new_val);
-}
-
-static _opa_inline void OPA_decr_int(OPA_int_t *ptr)
-{
-    --(ptr->v);
-}
-
-static _opa_inline int OPA_fetch_and_add_int(OPA_int_t *ptr, int val)
-{
-    int prev;
-    prev = ptr->v;
-    ptr->v += val;
-    return prev;
-}
-
-static _opa_inline int OPA_fetch_and_decr_int(OPA_int_t *ptr)
-{
-    int prev;
-    prev = ptr->v;
-    --(ptr->v);
-    return prev;
-}
-
-static _opa_inline int OPA_fetch_and_incr_int(OPA_int_t *ptr)
-{
-    int prev;
-    prev = ptr->v;
-    ++(ptr->v);
-    return prev;
-}
-
-static _opa_inline void OPA_incr_int(OPA_int_t *ptr)
-{
-    ++(ptr->v);
-}
-
-static _opa_inline void *OPA_swap_ptr(OPA_ptr_t *ptr, void *val)
-{
-    int *prev;
-    prev = ptr->v;
-    ptr->v = val;
-    return prev;
-}
-
-static _opa_inline int OPA_swap_int(OPA_int_t *ptr, int val)
-{
-    int prev;
-    prev = ptr->v;
-    ptr->v = val;
-    return (int)prev;
-}
-
-/* null barriers */
-#define OPA_write_barrier()      do {} while (0)
-#define OPA_read_barrier()       do {} while (0)
-#define OPA_read_write_barrier() do {} while (0)
-#define OPA_compiler_barrier()   do {} while (0)
-
-#endif /* !defined(OPA_UNSAFE_H_INCLUDED) */
diff --git a/linx64/mpi/mpich/lib64/libmpi.a b/linx64/mpi/mpich/lib64/libmpi.a
index 932ca2b7..6a2562c6 100644
Binary files a/linx64/mpi/mpich/lib64/libmpi.a and b/linx64/mpi/mpich/lib64/libmpi.a differ
diff --git a/linx64/mpi/mpich/lib64/libmpi.la b/linx64/mpi/mpich/lib64/libmpi.la
index 00a5f81a..fe326c43 100755
--- a/linx64/mpi/mpich/lib64/libmpi.la
+++ b/linx64/mpi/mpich/lib64/libmpi.la
@@ -1,5 +1,5 @@
 # libmpi.la - a libtool library file
-# Generated by libtool (GNU libtool) 2.4.6 Debian-2.4.6-2
+# Generated by libtool (GNU libtool) 2.4.6
 #
 # Please DO NOT delete this file!
 # It is necessary for linking the library.
@@ -8,7 +8,7 @@
 dlname='libmpi.so.12'
 
 # Names of this library.
-library_names='libmpi.so.12.1.1 libmpi.so.12 libmpi.so'
+library_names='libmpi.so.12.1.7 libmpi.so.12 libmpi.so'
 
 # The name of the static archive.
 old_library='libmpi.a'
@@ -17,7 +17,7 @@ old_library='libmpi.a'
 inherited_linker_flags=''
 
 # Libraries that this one depends upon.
-dependency_libs=' -L/home/brgirgis/Documents/code/thirdparty/mpi/mpich_/build/src/mpl -lrt -lpthread'
+dependency_libs=' -lm -lpthread -lrt'
 
 # Names of additional weak libraries provided by this library
 weak_library_names=''
@@ -25,7 +25,7 @@ weak_library_names=''
 # Version information for libmpi.
 current=13
 age=1
-revision=1
+revision=7
 
 # Is this an already installed library?
 installed=yes
@@ -38,4 +38,4 @@ dlopen=''
 dlpreopen=''
 
 # Directory that this library needs to be installed in:
-libdir='/home/brgirgis/Documents/code/thirdparty/mpi/mpich_/build/../release_install/lib64'
+libdir='/home/brgirgis/Documents/code/idiscovery/cpp-thirdparty-src/mpi/mpich/install/3.3.1/lib64'
diff --git a/linx64/mpi/mpich/lib64/libmpi.so b/linx64/mpi/mpich/lib64/libmpi.so
index 9714b7cb..004c67b0 120000
--- a/linx64/mpi/mpich/lib64/libmpi.so
+++ b/linx64/mpi/mpich/lib64/libmpi.so
@@ -1 +1 @@
-libmpi.so.12.1.1
\ No newline at end of file
+libmpi.so.12.1.7
\ No newline at end of file
diff --git a/linx64/mpi/mpich/lib64/libmpi.so.12 b/linx64/mpi/mpich/lib64/libmpi.so.12
index 9714b7cb..004c67b0 120000
--- a/linx64/mpi/mpich/lib64/libmpi.so.12
+++ b/linx64/mpi/mpich/lib64/libmpi.so.12
@@ -1 +1 @@
-libmpi.so.12.1.1
\ No newline at end of file
+libmpi.so.12.1.7
\ No newline at end of file
diff --git a/linx64/mpi/mpich/lib64/libmpi.so.12.1.1 b/linx64/mpi/mpich/lib64/libmpi.so.12.1.1
deleted file mode 100755
index 7927394d..00000000
Binary files a/linx64/mpi/mpich/lib64/libmpi.so.12.1.1 and /dev/null differ
diff --git a/linx64/mpi/mpich/lib64/libmpi.so.12.1.7 b/linx64/mpi/mpich/lib64/libmpi.so.12.1.7
new file mode 100755
index 00000000..5d14365f
Binary files /dev/null and b/linx64/mpi/mpich/lib64/libmpi.so.12.1.7 differ
diff --git a/linx64/mpi/mpich/lib64/pkgconfig/mpich.pc b/linx64/mpi/mpich/lib64/pkgconfig/mpich.pc
index 45d69937..750e5b7a 100644
--- a/linx64/mpi/mpich/lib64/pkgconfig/mpich.pc
+++ b/linx64/mpi/mpich/lib64/pkgconfig/mpich.pc
@@ -1,15 +1,15 @@
 # this gives access to the mpich header files
-prefix=/home/brgirgis/Documents/code/thirdparty/mpi/mpich_/build/../release_install
+prefix=/home/brgirgis/Documents/code/idiscovery/cpp-thirdparty-src/mpi/mpich/install/3.3.1
 exec_prefix=${prefix}
 libdir=${exec_prefix}/lib64
 includedir=${prefix}/include
 
 Name: mpich
 Description: High Performance and portable MPI
-Version: 3.2.1
+Version: 3.3.1
 URL: http://www.mcs.anl.gov/research/projects/mpich
 Requires:
-Libs: -Wl,-rpath -Wl,${exec_prefix}/lib64  -L${libdir} -lmpi    -lrt -lpthread 
+Libs: -Wl,-rpath -Wl,${exec_prefix}/lib64  -L${libdir} -lmpi  -lm   -lpthread  -lrt 
 Cflags:   -I${includedir}
 
 # pkg-config does not understand Cxxflags, etc. So we allow users to
diff --git a/linx64/mpi/mpich/lib64/pkgconfig/openpa.pc b/linx64/mpi/mpich/lib64/pkgconfig/openpa.pc
index f42d18a3..d1275ec5 100644
--- a/linx64/mpi/mpich/lib64/pkgconfig/openpa.pc
+++ b/linx64/mpi/mpich/lib64/pkgconfig/openpa.pc
@@ -1,4 +1,4 @@
-prefix=/home/brgirgis/Documents/code/thirdparty/mpi/mpich_/build/../release_install
+prefix=/home/brgirgis/Documents/code/idiscovery/cpp-thirdparty-src/mpi/mpich/install/3.3.1
 exec_prefix=${prefix}
 libdir=${exec_prefix}/lib64
 includedir=${prefix}/include
diff --git a/linx64/mpi/mpich/share/doc/mpich/index.html b/linx64/mpi/mpich/share/doc/mpich/index.html
index 3ac04581..030549a3 100644
--- a/linx64/mpi/mpich/share/doc/mpich/index.html
+++ b/linx64/mpi/mpich/share/doc/mpich/index.html
@@ -1,551 +1,563 @@
-<HTML>
-<HEAD>
-<TITLE>Web pages for MPI</TITLE>
-<!-- This file generated by createhtmlindex on  -->
-</HEAD>
-<BODY BGCOLOR="FFFFFF">
-<H1>Web pages for MPI</H1>
-<H2>MPI Commands</H2>
-<TABLE>
-<TR><TD><A HREF="www1/mpicc.html">mpicc</A></TD>
-<TD><A HREF="www1/mpiexec.html">mpiexec</A></TD>
-<TD><A HREF="www1/mpifort.html">mpifort</A></TD>
-</TR>
-<TR><TD><A HREF="www1/mpicxx.html">mpicxx</A></TD>
-<TD><A HREF="www1/mpif77.html">mpif77</A></TD>
-<TD></TD>
-</TR>
-</TABLE>
-<H2>MPI Routines and Constants</H2>
-<TABLE>
-<TR><TD><A HREF="www3/Constants.html">Constants</A></TD>
-<TD><A HREF="www3/MPI_File_set_atomicity.html">MPI_File_set_atomicity</A></TD>
-<TD><A HREF="www3/MPI_Rput.html">MPI_Rput</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPIX_Comm_agree.html">MPIX_Comm_agree</A></TD>
-<TD><A HREF="www3/MPI_File_set_errhandler.html">MPI_File_set_errhandler</A></TD>
-<TD><A HREF="www3/MPI_Rsend.html">MPI_Rsend</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPIX_Comm_failure_ack.html">MPIX_Comm_failure_ack</A></TD>
-<TD><A HREF="www3/MPI_File_set_info.html">MPI_File_set_info</A></TD>
-<TD><A HREF="www3/MPI_Rsend_init.html">MPI_Rsend_init</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPIX_Comm_failure_get_acked.html">MPIX_Comm_failure_get_acked</A></TD>
-<TD><A HREF="www3/MPI_File_set_size.html">MPI_File_set_size</A></TD>
-<TD><A HREF="www3/MPI_Scan.html">MPI_Scan</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPIX_Comm_revoke.html">MPIX_Comm_revoke</A></TD>
-<TD><A HREF="www3/MPI_File_set_view.html">MPI_File_set_view</A></TD>
-<TD><A HREF="www3/MPI_Scatter.html">MPI_Scatter</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPIX_Comm_shrink.html">MPIX_Comm_shrink</A></TD>
-<TD><A HREF="www3/MPI_File_sync.html">MPI_File_sync</A></TD>
-<TD><A HREF="www3/MPI_Scatterv.html">MPI_Scatterv</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Abort.html">MPI_Abort</A></TD>
-<TD><A HREF="www3/MPI_File_write.html">MPI_File_write</A></TD>
-<TD><A HREF="www3/MPI_Send.html">MPI_Send</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Accumulate.html">MPI_Accumulate</A></TD>
-<TD><A HREF="www3/MPI_File_write_all.html">MPI_File_write_all</A></TD>
-<TD><A HREF="www3/MPI_Send_init.html">MPI_Send_init</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Add_error_class.html">MPI_Add_error_class</A></TD>
-<TD><A HREF="www3/MPI_File_write_all_begin.html">MPI_File_write_all_begin</A></TD>
-<TD><A HREF="www3/MPI_Sendrecv.html">MPI_Sendrecv</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Add_error_code.html">MPI_Add_error_code</A></TD>
-<TD><A HREF="www3/MPI_File_write_all_end.html">MPI_File_write_all_end</A></TD>
-<TD><A HREF="www3/MPI_Sendrecv_replace.html">MPI_Sendrecv_replace</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Add_error_string.html">MPI_Add_error_string</A></TD>
-<TD><A HREF="www3/MPI_File_write_at.html">MPI_File_write_at</A></TD>
-<TD><A HREF="www3/MPI_Ssend.html">MPI_Ssend</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Address.html">MPI_Address</A></TD>
-<TD><A HREF="www3/MPI_File_write_at_all.html">MPI_File_write_at_all</A></TD>
-<TD><A HREF="www3/MPI_Ssend_init.html">MPI_Ssend_init</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Aint_add.html">MPI_Aint_add</A></TD>
-<TD><A HREF="www3/MPI_File_write_at_all_begin.html">MPI_File_write_at_all_begin</A></TD>
-<TD><A HREF="www3/MPI_Start.html">MPI_Start</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Aint_diff.html">MPI_Aint_diff</A></TD>
-<TD><A HREF="www3/MPI_File_write_at_all_end.html">MPI_File_write_at_all_end</A></TD>
-<TD><A HREF="www3/MPI_Startall.html">MPI_Startall</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Allgather.html">MPI_Allgather</A></TD>
-<TD><A HREF="www3/MPI_File_write_ordered.html">MPI_File_write_ordered</A></TD>
-<TD><A HREF="www3/MPI_Status_set_cancelled.html">MPI_Status_set_cancelled</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Allgatherv.html">MPI_Allgatherv</A></TD>
-<TD><A HREF="www3/MPI_File_write_ordered_begin.html">MPI_File_write_ordered_begin</A></TD>
-<TD><A HREF="www3/MPI_Status_set_elements.html">MPI_Status_set_elements</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Alloc_mem.html">MPI_Alloc_mem</A></TD>
-<TD><A HREF="www3/MPI_File_write_ordered_end.html">MPI_File_write_ordered_end</A></TD>
-<TD><A HREF="www3/MPI_Status_set_elements_x.html">MPI_Status_set_elements_x</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Allreduce.html">MPI_Allreduce</A></TD>
-<TD><A HREF="www3/MPI_File_write_shared.html">MPI_File_write_shared</A></TD>
-<TD><A HREF="www3/MPI_T_category_changed.html">MPI_T_category_changed</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Alltoall.html">MPI_Alltoall</A></TD>
-<TD><A HREF="www3/MPI_Finalize.html">MPI_Finalize</A></TD>
-<TD><A HREF="www3/MPI_T_category_get_categories.html">MPI_T_category_get_categories</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Alltoallv.html">MPI_Alltoallv</A></TD>
-<TD><A HREF="www3/MPI_Finalized.html">MPI_Finalized</A></TD>
-<TD><A HREF="www3/MPI_T_category_get_cvars.html">MPI_T_category_get_cvars</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Alltoallw.html">MPI_Alltoallw</A></TD>
-<TD><A HREF="www3/MPI_Free_mem.html">MPI_Free_mem</A></TD>
-<TD><A HREF="www3/MPI_T_category_get_info.html">MPI_T_category_get_info</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Attr_delete.html">MPI_Attr_delete</A></TD>
-<TD><A HREF="www3/MPI_Gather.html">MPI_Gather</A></TD>
-<TD><A HREF="www3/MPI_T_category_get_num.html">MPI_T_category_get_num</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Attr_get.html">MPI_Attr_get</A></TD>
-<TD><A HREF="www3/MPI_Gatherv.html">MPI_Gatherv</A></TD>
-<TD><A HREF="www3/MPI_T_category_get_pvars.html">MPI_T_category_get_pvars</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Attr_put.html">MPI_Attr_put</A></TD>
-<TD><A HREF="www3/MPI_Get.html">MPI_Get</A></TD>
-<TD><A HREF="www3/MPI_T_cvar_get_info.html">MPI_T_cvar_get_info</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Barrier.html">MPI_Barrier</A></TD>
-<TD><A HREF="www3/MPI_Get_accumulate.html">MPI_Get_accumulate</A></TD>
-<TD><A HREF="www3/MPI_T_cvar_get_num.html">MPI_T_cvar_get_num</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Bcast.html">MPI_Bcast</A></TD>
-<TD><A HREF="www3/MPI_Get_address.html">MPI_Get_address</A></TD>
-<TD><A HREF="www3/MPI_T_cvar_handle_alloc.html">MPI_T_cvar_handle_alloc</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Bsend.html">MPI_Bsend</A></TD>
-<TD><A HREF="www3/MPI_Get_count.html">MPI_Get_count</A></TD>
-<TD><A HREF="www3/MPI_T_cvar_handle_free.html">MPI_T_cvar_handle_free</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Bsend_init.html">MPI_Bsend_init</A></TD>
-<TD><A HREF="www3/MPI_Get_elements.html">MPI_Get_elements</A></TD>
-<TD><A HREF="www3/MPI_T_cvar_read.html">MPI_T_cvar_read</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Buffer_attach.html">MPI_Buffer_attach</A></TD>
-<TD><A HREF="www3/MPI_Get_elements_x.html">MPI_Get_elements_x</A></TD>
-<TD><A HREF="www3/MPI_T_cvar_write.html">MPI_T_cvar_write</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Buffer_detach.html">MPI_Buffer_detach</A></TD>
-<TD><A HREF="www3/MPI_Get_library_version.html">MPI_Get_library_version</A></TD>
-<TD><A HREF="www3/MPI_T_enum_get_info.html">MPI_T_enum_get_info</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Cancel.html">MPI_Cancel</A></TD>
-<TD><A HREF="www3/MPI_Get_processor_name.html">MPI_Get_processor_name</A></TD>
-<TD><A HREF="www3/MPI_T_enum_get_item.html">MPI_T_enum_get_item</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Cart_coords.html">MPI_Cart_coords</A></TD>
-<TD><A HREF="www3/MPI_Get_version.html">MPI_Get_version</A></TD>
-<TD><A HREF="www3/MPI_T_finalize.html">MPI_T_finalize</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Cart_create.html">MPI_Cart_create</A></TD>
-<TD><A HREF="www3/MPI_Graph_create.html">MPI_Graph_create</A></TD>
-<TD><A HREF="www3/MPI_T_init_thread.html">MPI_T_init_thread</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Cart_get.html">MPI_Cart_get</A></TD>
-<TD><A HREF="www3/MPI_Graph_get.html">MPI_Graph_get</A></TD>
-<TD><A HREF="www3/MPI_T_pvar_get_info.html">MPI_T_pvar_get_info</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Cart_map.html">MPI_Cart_map</A></TD>
-<TD><A HREF="www3/MPI_Graph_map.html">MPI_Graph_map</A></TD>
-<TD><A HREF="www3/MPI_T_pvar_get_num.html">MPI_T_pvar_get_num</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Cart_rank.html">MPI_Cart_rank</A></TD>
-<TD><A HREF="www3/MPI_Graph_neighbors.html">MPI_Graph_neighbors</A></TD>
-<TD><A HREF="www3/MPI_T_pvar_handle_alloc.html">MPI_T_pvar_handle_alloc</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Cart_shift.html">MPI_Cart_shift</A></TD>
-<TD><A HREF="www3/MPI_Graph_neighbors_count.html">MPI_Graph_neighbors_count</A></TD>
-<TD><A HREF="www3/MPI_T_pvar_handle_free.html">MPI_T_pvar_handle_free</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Cart_sub.html">MPI_Cart_sub</A></TD>
-<TD><A HREF="www3/MPI_Graphdims_get.html">MPI_Graphdims_get</A></TD>
-<TD><A HREF="www3/MPI_T_pvar_read.html">MPI_T_pvar_read</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Cartdim_get.html">MPI_Cartdim_get</A></TD>
-<TD><A HREF="www3/MPI_Grequest_complete.html">MPI_Grequest_complete</A></TD>
-<TD><A HREF="www3/MPI_T_pvar_readreset.html">MPI_T_pvar_readreset</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Close_port.html">MPI_Close_port</A></TD>
-<TD><A HREF="www3/MPI_Grequest_start.html">MPI_Grequest_start</A></TD>
-<TD><A HREF="www3/MPI_T_pvar_reset.html">MPI_T_pvar_reset</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_accept.html">MPI_Comm_accept</A></TD>
-<TD><A HREF="www3/MPI_Group_compare.html">MPI_Group_compare</A></TD>
-<TD><A HREF="www3/MPI_T_pvar_session_create.html">MPI_T_pvar_session_create</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_call_errhandler.html">MPI_Comm_call_errhandler</A></TD>
-<TD><A HREF="www3/MPI_Group_difference.html">MPI_Group_difference</A></TD>
-<TD><A HREF="www3/MPI_T_pvar_session_free.html">MPI_T_pvar_session_free</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_compare.html">MPI_Comm_compare</A></TD>
-<TD><A HREF="www3/MPI_Group_excl.html">MPI_Group_excl</A></TD>
-<TD><A HREF="www3/MPI_T_pvar_start.html">MPI_T_pvar_start</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_connect.html">MPI_Comm_connect</A></TD>
-<TD><A HREF="www3/MPI_Group_free.html">MPI_Group_free</A></TD>
-<TD><A HREF="www3/MPI_T_pvar_stop.html">MPI_T_pvar_stop</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_create.html">MPI_Comm_create</A></TD>
-<TD><A HREF="www3/MPI_Group_incl.html">MPI_Group_incl</A></TD>
-<TD><A HREF="www3/MPI_T_pvar_write.html">MPI_T_pvar_write</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_create_errhandler.html">MPI_Comm_create_errhandler</A></TD>
-<TD><A HREF="www3/MPI_Group_intersection.html">MPI_Group_intersection</A></TD>
-<TD><A HREF="www3/MPI_Test.html">MPI_Test</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_create_group.html">MPI_Comm_create_group</A></TD>
-<TD><A HREF="www3/MPI_Group_range_excl.html">MPI_Group_range_excl</A></TD>
-<TD><A HREF="www3/MPI_Test_cancelled.html">MPI_Test_cancelled</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_create_keyval.html">MPI_Comm_create_keyval</A></TD>
-<TD><A HREF="www3/MPI_Group_range_incl.html">MPI_Group_range_incl</A></TD>
-<TD><A HREF="www3/MPI_Testall.html">MPI_Testall</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_delete_attr.html">MPI_Comm_delete_attr</A></TD>
-<TD><A HREF="www3/MPI_Group_rank.html">MPI_Group_rank</A></TD>
-<TD><A HREF="www3/MPI_Testany.html">MPI_Testany</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_disconnect.html">MPI_Comm_disconnect</A></TD>
-<TD><A HREF="www3/MPI_Group_size.html">MPI_Group_size</A></TD>
-<TD><A HREF="www3/MPI_Testsome.html">MPI_Testsome</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_dup.html">MPI_Comm_dup</A></TD>
-<TD><A HREF="www3/MPI_Group_translate_ranks.html">MPI_Group_translate_ranks</A></TD>
-<TD><A HREF="www3/MPI_Topo_test.html">MPI_Topo_test</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_dup_with_info.html">MPI_Comm_dup_with_info</A></TD>
-<TD><A HREF="www3/MPI_Group_union.html">MPI_Group_union</A></TD>
-<TD><A HREF="www3/MPI_Type_commit.html">MPI_Type_commit</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_free.html">MPI_Comm_free</A></TD>
-<TD><A HREF="www3/MPI_Iallgather.html">MPI_Iallgather</A></TD>
-<TD><A HREF="www3/MPI_Type_contiguous.html">MPI_Type_contiguous</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_free_keyval.html">MPI_Comm_free_keyval</A></TD>
-<TD><A HREF="www3/MPI_Iallgatherv.html">MPI_Iallgatherv</A></TD>
-<TD><A HREF="www3/MPI_Type_create_darray.html">MPI_Type_create_darray</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_get_attr.html">MPI_Comm_get_attr</A></TD>
-<TD><A HREF="www3/MPI_Iallreduce.html">MPI_Iallreduce</A></TD>
-<TD><A HREF="www3/MPI_Type_create_hindexed.html">MPI_Type_create_hindexed</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_get_errhandler.html">MPI_Comm_get_errhandler</A></TD>
-<TD><A HREF="www3/MPI_Ialltoall.html">MPI_Ialltoall</A></TD>
-<TD><A HREF="www3/MPI_Type_create_hindexed_block.html">MPI_Type_create_hindexed_block</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_get_info.html">MPI_Comm_get_info</A></TD>
-<TD><A HREF="www3/MPI_Ialltoallv.html">MPI_Ialltoallv</A></TD>
-<TD><A HREF="www3/MPI_Type_create_hvector.html">MPI_Type_create_hvector</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_get_name.html">MPI_Comm_get_name</A></TD>
-<TD><A HREF="www3/MPI_Ialltoallw.html">MPI_Ialltoallw</A></TD>
-<TD><A HREF="www3/MPI_Type_create_indexed_block.html">MPI_Type_create_indexed_block</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_get_parent.html">MPI_Comm_get_parent</A></TD>
-<TD><A HREF="www3/MPI_Ibarrier.html">MPI_Ibarrier</A></TD>
-<TD><A HREF="www3/MPI_Type_create_keyval.html">MPI_Type_create_keyval</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_group.html">MPI_Comm_group</A></TD>
-<TD><A HREF="www3/MPI_Ibcast.html">MPI_Ibcast</A></TD>
-<TD><A HREF="www3/MPI_Type_create_resized.html">MPI_Type_create_resized</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_idup.html">MPI_Comm_idup</A></TD>
-<TD><A HREF="www3/MPI_Ibsend.html">MPI_Ibsend</A></TD>
-<TD><A HREF="www3/MPI_Type_create_struct.html">MPI_Type_create_struct</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_join.html">MPI_Comm_join</A></TD>
-<TD><A HREF="www3/MPI_Iexscan.html">MPI_Iexscan</A></TD>
-<TD><A HREF="www3/MPI_Type_create_subarray.html">MPI_Type_create_subarray</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_rank.html">MPI_Comm_rank</A></TD>
-<TD><A HREF="www3/MPI_Igather.html">MPI_Igather</A></TD>
-<TD><A HREF="www3/MPI_Type_delete_attr.html">MPI_Type_delete_attr</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_remote_group.html">MPI_Comm_remote_group</A></TD>
-<TD><A HREF="www3/MPI_Igatherv.html">MPI_Igatherv</A></TD>
-<TD><A HREF="www3/MPI_Type_dup.html">MPI_Type_dup</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_remote_size.html">MPI_Comm_remote_size</A></TD>
-<TD><A HREF="www3/MPI_Improbe.html">MPI_Improbe</A></TD>
-<TD><A HREF="www3/MPI_Type_extent.html">MPI_Type_extent</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_set_attr.html">MPI_Comm_set_attr</A></TD>
-<TD><A HREF="www3/MPI_Imrecv.html">MPI_Imrecv</A></TD>
-<TD><A HREF="www3/MPI_Type_free.html">MPI_Type_free</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_set_errhandler.html">MPI_Comm_set_errhandler</A></TD>
-<TD><A HREF="www3/MPI_Ineighbor_allgather.html">MPI_Ineighbor_allgather</A></TD>
-<TD><A HREF="www3/MPI_Type_free_keyval.html">MPI_Type_free_keyval</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_set_info.html">MPI_Comm_set_info</A></TD>
-<TD><A HREF="www3/MPI_Ineighbor_allgatherv.html">MPI_Ineighbor_allgatherv</A></TD>
-<TD><A HREF="www3/MPI_Type_get_attr.html">MPI_Type_get_attr</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_set_name.html">MPI_Comm_set_name</A></TD>
-<TD><A HREF="www3/MPI_Ineighbor_alltoall.html">MPI_Ineighbor_alltoall</A></TD>
-<TD><A HREF="www3/MPI_Type_get_contents.html">MPI_Type_get_contents</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_size.html">MPI_Comm_size</A></TD>
-<TD><A HREF="www3/MPI_Ineighbor_alltoallv.html">MPI_Ineighbor_alltoallv</A></TD>
-<TD><A HREF="www3/MPI_Type_get_envelope.html">MPI_Type_get_envelope</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_spawn.html">MPI_Comm_spawn</A></TD>
-<TD><A HREF="www3/MPI_Ineighbor_alltoallw.html">MPI_Ineighbor_alltoallw</A></TD>
-<TD><A HREF="www3/MPI_Type_get_extent.html">MPI_Type_get_extent</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_spawn_multiple.html">MPI_Comm_spawn_multiple</A></TD>
-<TD><A HREF="www3/MPI_Info_create.html">MPI_Info_create</A></TD>
-<TD><A HREF="www3/MPI_Type_get_extent_x.html">MPI_Type_get_extent_x</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_split.html">MPI_Comm_split</A></TD>
-<TD><A HREF="www3/MPI_Info_delete.html">MPI_Info_delete</A></TD>
-<TD><A HREF="www3/MPI_Type_get_name.html">MPI_Type_get_name</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_split_type.html">MPI_Comm_split_type</A></TD>
-<TD><A HREF="www3/MPI_Info_dup.html">MPI_Info_dup</A></TD>
-<TD><A HREF="www3/MPI_Type_get_true_extent.html">MPI_Type_get_true_extent</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Comm_test_inter.html">MPI_Comm_test_inter</A></TD>
-<TD><A HREF="www3/MPI_Info_free.html">MPI_Info_free</A></TD>
-<TD><A HREF="www3/MPI_Type_get_true_extent_x.html">MPI_Type_get_true_extent_x</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Compare_and_swap.html">MPI_Compare_and_swap</A></TD>
-<TD><A HREF="www3/MPI_Info_get.html">MPI_Info_get</A></TD>
-<TD><A HREF="www3/MPI_Type_hindexed.html">MPI_Type_hindexed</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Dims_create.html">MPI_Dims_create</A></TD>
-<TD><A HREF="www3/MPI_Info_get_nkeys.html">MPI_Info_get_nkeys</A></TD>
-<TD><A HREF="www3/MPI_Type_hvector.html">MPI_Type_hvector</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Dist_graph_create.html">MPI_Dist_graph_create</A></TD>
-<TD><A HREF="www3/MPI_Info_get_nthkey.html">MPI_Info_get_nthkey</A></TD>
-<TD><A HREF="www3/MPI_Type_indexed.html">MPI_Type_indexed</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Dist_graph_create_adjacent.html">MPI_Dist_graph_create_adjacent</A></TD>
-<TD><A HREF="www3/MPI_Info_get_valuelen.html">MPI_Info_get_valuelen</A></TD>
-<TD><A HREF="www3/MPI_Type_lb.html">MPI_Type_lb</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Dist_graph_neighbors.html">MPI_Dist_graph_neighbors</A></TD>
-<TD><A HREF="www3/MPI_Info_set.html">MPI_Info_set</A></TD>
-<TD><A HREF="www3/MPI_Type_match_size.html">MPI_Type_match_size</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Dist_graph_neighbors_count.html">MPI_Dist_graph_neighbors_count</A></TD>
-<TD><A HREF="www3/MPI_Init.html">MPI_Init</A></TD>
-<TD><A HREF="www3/MPI_Type_set_attr.html">MPI_Type_set_attr</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Errhandler_create.html">MPI_Errhandler_create</A></TD>
-<TD><A HREF="www3/MPI_Init_thread.html">MPI_Init_thread</A></TD>
-<TD><A HREF="www3/MPI_Type_set_name.html">MPI_Type_set_name</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Errhandler_free.html">MPI_Errhandler_free</A></TD>
-<TD><A HREF="www3/MPI_Initialized.html">MPI_Initialized</A></TD>
-<TD><A HREF="www3/MPI_Type_size.html">MPI_Type_size</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Errhandler_get.html">MPI_Errhandler_get</A></TD>
-<TD><A HREF="www3/MPI_Intercomm_create.html">MPI_Intercomm_create</A></TD>
-<TD><A HREF="www3/MPI_Type_size_x.html">MPI_Type_size_x</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Errhandler_set.html">MPI_Errhandler_set</A></TD>
-<TD><A HREF="www3/MPI_Intercomm_merge.html">MPI_Intercomm_merge</A></TD>
-<TD><A HREF="www3/MPI_Type_struct.html">MPI_Type_struct</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Error_class.html">MPI_Error_class</A></TD>
-<TD><A HREF="www3/MPI_Iprobe.html">MPI_Iprobe</A></TD>
-<TD><A HREF="www3/MPI_Type_ub.html">MPI_Type_ub</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Error_string.html">MPI_Error_string</A></TD>
-<TD><A HREF="www3/MPI_Irecv.html">MPI_Irecv</A></TD>
-<TD><A HREF="www3/MPI_Type_vector.html">MPI_Type_vector</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Exscan.html">MPI_Exscan</A></TD>
-<TD><A HREF="www3/MPI_Ireduce.html">MPI_Ireduce</A></TD>
-<TD><A HREF="www3/MPI_Unpack.html">MPI_Unpack</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_Fetch_and_op.html">MPI_Fetch_and_op</A></TD>
-<TD><A HREF="www3/MPI_Ireduce_scatter.html">MPI_Ireduce_scatter</A></TD>
-<TD><A HREF="www3/MPI_Unpack_external.html">MPI_Unpack_external</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_c2f.html">MPI_File_c2f</A></TD>
-<TD><A HREF="www3/MPI_Ireduce_scatter_block.html">MPI_Ireduce_scatter_block</A></TD>
-<TD><A HREF="www3/MPI_Unpublish_name.html">MPI_Unpublish_name</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_call_errhandler.html">MPI_File_call_errhandler</A></TD>
-<TD><A HREF="www3/MPI_Irsend.html">MPI_Irsend</A></TD>
-<TD><A HREF="www3/MPI_Wait.html">MPI_Wait</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_close.html">MPI_File_close</A></TD>
-<TD><A HREF="www3/MPI_Is_thread_main.html">MPI_Is_thread_main</A></TD>
-<TD><A HREF="www3/MPI_Waitall.html">MPI_Waitall</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_create_errhandler.html">MPI_File_create_errhandler</A></TD>
-<TD><A HREF="www3/MPI_Iscan.html">MPI_Iscan</A></TD>
-<TD><A HREF="www3/MPI_Waitany.html">MPI_Waitany</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_delete.html">MPI_File_delete</A></TD>
-<TD><A HREF="www3/MPI_Iscatter.html">MPI_Iscatter</A></TD>
-<TD><A HREF="www3/MPI_Waitsome.html">MPI_Waitsome</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_f2c.html">MPI_File_f2c</A></TD>
-<TD><A HREF="www3/MPI_Iscatterv.html">MPI_Iscatterv</A></TD>
-<TD><A HREF="www3/MPI_Win_allocate.html">MPI_Win_allocate</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_get_amode.html">MPI_File_get_amode</A></TD>
-<TD><A HREF="www3/MPI_Isend.html">MPI_Isend</A></TD>
-<TD><A HREF="www3/MPI_Win_allocate_shared.html">MPI_Win_allocate_shared</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_get_atomicity.html">MPI_File_get_atomicity</A></TD>
-<TD><A HREF="www3/MPI_Issend.html">MPI_Issend</A></TD>
-<TD><A HREF="www3/MPI_Win_attach.html">MPI_Win_attach</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_get_byte_offset.html">MPI_File_get_byte_offset</A></TD>
-<TD><A HREF="www3/MPI_Keyval_create.html">MPI_Keyval_create</A></TD>
-<TD><A HREF="www3/MPI_Win_call_errhandler.html">MPI_Win_call_errhandler</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_get_errhandler.html">MPI_File_get_errhandler</A></TD>
-<TD><A HREF="www3/MPI_Keyval_free.html">MPI_Keyval_free</A></TD>
-<TD><A HREF="www3/MPI_Win_complete.html">MPI_Win_complete</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_get_group.html">MPI_File_get_group</A></TD>
-<TD><A HREF="www3/MPI_Lookup_name.html">MPI_Lookup_name</A></TD>
-<TD><A HREF="www3/MPI_Win_create.html">MPI_Win_create</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_get_info.html">MPI_File_get_info</A></TD>
-<TD><A HREF="www3/MPI_Mprobe.html">MPI_Mprobe</A></TD>
-<TD><A HREF="www3/MPI_Win_create_dynamic.html">MPI_Win_create_dynamic</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_get_position.html">MPI_File_get_position</A></TD>
-<TD><A HREF="www3/MPI_Mrecv.html">MPI_Mrecv</A></TD>
-<TD><A HREF="www3/MPI_Win_create_errhandler.html">MPI_Win_create_errhandler</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_get_position_shared.html">MPI_File_get_position_shared</A></TD>
-<TD><A HREF="www3/MPI_Neighbor_allgather.html">MPI_Neighbor_allgather</A></TD>
-<TD><A HREF="www3/MPI_Win_create_keyval.html">MPI_Win_create_keyval</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_get_size.html">MPI_File_get_size</A></TD>
-<TD><A HREF="www3/MPI_Neighbor_allgatherv.html">MPI_Neighbor_allgatherv</A></TD>
-<TD><A HREF="www3/MPI_Win_delete_attr.html">MPI_Win_delete_attr</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_get_type_extent.html">MPI_File_get_type_extent</A></TD>
-<TD><A HREF="www3/MPI_Neighbor_alltoall.html">MPI_Neighbor_alltoall</A></TD>
-<TD><A HREF="www3/MPI_Win_detach.html">MPI_Win_detach</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_get_view.html">MPI_File_get_view</A></TD>
-<TD><A HREF="www3/MPI_Neighbor_alltoallv.html">MPI_Neighbor_alltoallv</A></TD>
-<TD><A HREF="www3/MPI_Win_fence.html">MPI_Win_fence</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_iread.html">MPI_File_iread</A></TD>
-<TD><A HREF="www3/MPI_Neighbor_alltoallw.html">MPI_Neighbor_alltoallw</A></TD>
-<TD><A HREF="www3/MPI_Win_flush.html">MPI_Win_flush</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_iread_all.html">MPI_File_iread_all</A></TD>
-<TD><A HREF="www3/MPI_Op_commute.html">MPI_Op_commute</A></TD>
-<TD><A HREF="www3/MPI_Win_flush_all.html">MPI_Win_flush_all</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_iread_at.html">MPI_File_iread_at</A></TD>
-<TD><A HREF="www3/MPI_Op_create.html">MPI_Op_create</A></TD>
-<TD><A HREF="www3/MPI_Win_flush_local.html">MPI_Win_flush_local</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_iread_at_all.html">MPI_File_iread_at_all</A></TD>
-<TD><A HREF="www3/MPI_Op_free.html">MPI_Op_free</A></TD>
-<TD><A HREF="www3/MPI_Win_flush_local_all.html">MPI_Win_flush_local_all</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_iread_shared.html">MPI_File_iread_shared</A></TD>
-<TD><A HREF="www3/MPI_Open_port.html">MPI_Open_port</A></TD>
-<TD><A HREF="www3/MPI_Win_free.html">MPI_Win_free</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_iwrite.html">MPI_File_iwrite</A></TD>
-<TD><A HREF="www3/MPI_Pack.html">MPI_Pack</A></TD>
-<TD><A HREF="www3/MPI_Win_free_keyval.html">MPI_Win_free_keyval</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_iwrite_all.html">MPI_File_iwrite_all</A></TD>
-<TD><A HREF="www3/MPI_Pack_external.html">MPI_Pack_external</A></TD>
-<TD><A HREF="www3/MPI_Win_get_attr.html">MPI_Win_get_attr</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_iwrite_at.html">MPI_File_iwrite_at</A></TD>
-<TD><A HREF="www3/MPI_Pack_external_size.html">MPI_Pack_external_size</A></TD>
-<TD><A HREF="www3/MPI_Win_get_errhandler.html">MPI_Win_get_errhandler</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_iwrite_at_all.html">MPI_File_iwrite_at_all</A></TD>
-<TD><A HREF="www3/MPI_Pack_size.html">MPI_Pack_size</A></TD>
-<TD><A HREF="www3/MPI_Win_get_group.html">MPI_Win_get_group</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_iwrite_shared.html">MPI_File_iwrite_shared</A></TD>
-<TD><A HREF="www3/MPI_Pcontrol.html">MPI_Pcontrol</A></TD>
-<TD><A HREF="www3/MPI_Win_get_info.html">MPI_Win_get_info</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_open.html">MPI_File_open</A></TD>
-<TD><A HREF="www3/MPI_Probe.html">MPI_Probe</A></TD>
-<TD><A HREF="www3/MPI_Win_get_name.html">MPI_Win_get_name</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_preallocate.html">MPI_File_preallocate</A></TD>
-<TD><A HREF="www3/MPI_Publish_name.html">MPI_Publish_name</A></TD>
-<TD><A HREF="www3/MPI_Win_lock.html">MPI_Win_lock</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_read.html">MPI_File_read</A></TD>
-<TD><A HREF="www3/MPI_Put.html">MPI_Put</A></TD>
-<TD><A HREF="www3/MPI_Win_lock_all.html">MPI_Win_lock_all</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_read_all.html">MPI_File_read_all</A></TD>
-<TD><A HREF="www3/MPI_Query_thread.html">MPI_Query_thread</A></TD>
-<TD><A HREF="www3/MPI_Win_post.html">MPI_Win_post</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_read_all_begin.html">MPI_File_read_all_begin</A></TD>
-<TD><A HREF="www3/MPI_Raccumulate.html">MPI_Raccumulate</A></TD>
-<TD><A HREF="www3/MPI_Win_set_attr.html">MPI_Win_set_attr</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_read_all_end.html">MPI_File_read_all_end</A></TD>
-<TD><A HREF="www3/MPI_Recv.html">MPI_Recv</A></TD>
-<TD><A HREF="www3/MPI_Win_set_errhandler.html">MPI_Win_set_errhandler</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_read_at.html">MPI_File_read_at</A></TD>
-<TD><A HREF="www3/MPI_Recv_init.html">MPI_Recv_init</A></TD>
-<TD><A HREF="www3/MPI_Win_set_info.html">MPI_Win_set_info</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_read_at_all.html">MPI_File_read_at_all</A></TD>
-<TD><A HREF="www3/MPI_Reduce.html">MPI_Reduce</A></TD>
-<TD><A HREF="www3/MPI_Win_set_name.html">MPI_Win_set_name</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_read_at_all_begin.html">MPI_File_read_at_all_begin</A></TD>
-<TD><A HREF="www3/MPI_Reduce_local.html">MPI_Reduce_local</A></TD>
-<TD><A HREF="www3/MPI_Win_shared_query.html">MPI_Win_shared_query</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_read_at_all_end.html">MPI_File_read_at_all_end</A></TD>
-<TD><A HREF="www3/MPI_Reduce_scatter.html">MPI_Reduce_scatter</A></TD>
-<TD><A HREF="www3/MPI_Win_start.html">MPI_Win_start</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_read_ordered.html">MPI_File_read_ordered</A></TD>
-<TD><A HREF="www3/MPI_Reduce_scatter_block.html">MPI_Reduce_scatter_block</A></TD>
-<TD><A HREF="www3/MPI_Win_sync.html">MPI_Win_sync</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_read_ordered_begin.html">MPI_File_read_ordered_begin</A></TD>
-<TD><A HREF="www3/MPI_Register_datarep.html">MPI_Register_datarep</A></TD>
-<TD><A HREF="www3/MPI_Win_test.html">MPI_Win_test</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_read_ordered_end.html">MPI_File_read_ordered_end</A></TD>
-<TD><A HREF="www3/MPI_Request_free.html">MPI_Request_free</A></TD>
-<TD><A HREF="www3/MPI_Win_unlock.html">MPI_Win_unlock</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_read_shared.html">MPI_File_read_shared</A></TD>
-<TD><A HREF="www3/MPI_Request_get_status.html">MPI_Request_get_status</A></TD>
-<TD><A HREF="www3/MPI_Win_unlock_all.html">MPI_Win_unlock_all</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_seek.html">MPI_File_seek</A></TD>
-<TD><A HREF="www3/MPI_Rget.html">MPI_Rget</A></TD>
-<TD><A HREF="www3/MPI_Win_wait.html">MPI_Win_wait</A></TD>
-</TR>
-<TR><TD><A HREF="www3/MPI_File_seek_shared.html">MPI_File_seek_shared</A></TD>
-<TD><A HREF="www3/MPI_Rget_accumulate.html">MPI_Rget_accumulate</A></TD>
-<TD><A HREF="www3/MPI_Wtick.html">MPI_Wtick</A></TD>
-</TR>
-</TABLE>
-</BODY>
-</HTML>
+<HTML>
+<HEAD>
+<TITLE>Web pages for MPI</TITLE>
+<!-- This file generated by createhtmlindex on  -->
+</HEAD>
+<BODY BGCOLOR="FFFFFF">
+<H1>Web pages for MPI</H1>
+<H2>MPI Commands</H2>
+<TABLE>
+<TR><TD><A HREF="www1/mpicc.html">mpicc</A></TD>
+<TD><A HREF="www1/mpiexec.html">mpiexec</A></TD>
+<TD><A HREF="www1/mpifort.html">mpifort</A></TD>
+</TR>
+<TR><TD><A HREF="www1/mpicxx.html">mpicxx</A></TD>
+<TD><A HREF="www1/mpif77.html">mpif77</A></TD>
+<TD></TD>
+</TR>
+</TABLE>
+<H2>MPI Routines and Constants</H2>
+<TABLE>
+<TR><TD><A HREF="www3/Constants.html">Constants</A></TD>
+<TD><A HREF="www3/MPI_File_read_ordered_end.html">MPI_File_read_ordered_end</A></TD>
+<TD><A HREF="www3/MPI_Rget_accumulate.html">MPI_Rget_accumulate</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPIR_Type_commit.html">MPIR_Type_commit</A></TD>
+<TD><A HREF="www3/MPI_File_read_shared.html">MPI_File_read_shared</A></TD>
+<TD><A HREF="www3/MPI_Rput.html">MPI_Rput</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPIR_Type_contiguous.html">MPIR_Type_contiguous</A></TD>
+<TD><A HREF="www3/MPI_File_seek.html">MPI_File_seek</A></TD>
+<TD><A HREF="www3/MPI_Rsend.html">MPI_Rsend</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPIR_Type_dup.html">MPIR_Type_dup</A></TD>
+<TD><A HREF="www3/MPI_File_seek_shared.html">MPI_File_seek_shared</A></TD>
+<TD><A HREF="www3/MPI_Rsend_init.html">MPI_Rsend_init</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPIR_Type_get_contents.html">MPIR_Type_get_contents</A></TD>
+<TD><A HREF="www3/MPI_File_set_atomicity.html">MPI_File_set_atomicity</A></TD>
+<TD><A HREF="www3/MPI_Scan.html">MPI_Scan</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPIR_Type_indexed.html">MPIR_Type_indexed</A></TD>
+<TD><A HREF="www3/MPI_File_set_errhandler.html">MPI_File_set_errhandler</A></TD>
+<TD><A HREF="www3/MPI_Scatter.html">MPI_Scatter</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPIR_Type_struct.html">MPIR_Type_struct</A></TD>
+<TD><A HREF="www3/MPI_File_set_info.html">MPI_File_set_info</A></TD>
+<TD><A HREF="www3/MPI_Scatterv.html">MPI_Scatterv</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPIR_Type_vector.html">MPIR_Type_vector</A></TD>
+<TD><A HREF="www3/MPI_File_set_size.html">MPI_File_set_size</A></TD>
+<TD><A HREF="www3/MPI_Send.html">MPI_Send</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPIX_Comm_agree.html">MPIX_Comm_agree</A></TD>
+<TD><A HREF="www3/MPI_File_set_view.html">MPI_File_set_view</A></TD>
+<TD><A HREF="www3/MPI_Send_init.html">MPI_Send_init</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPIX_Comm_failure_ack.html">MPIX_Comm_failure_ack</A></TD>
+<TD><A HREF="www3/MPI_File_sync.html">MPI_File_sync</A></TD>
+<TD><A HREF="www3/MPI_Sendrecv.html">MPI_Sendrecv</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPIX_Comm_failure_get_acked.html">MPIX_Comm_failure_get_acked</A></TD>
+<TD><A HREF="www3/MPI_File_write.html">MPI_File_write</A></TD>
+<TD><A HREF="www3/MPI_Sendrecv_replace.html">MPI_Sendrecv_replace</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPIX_Comm_revoke.html">MPIX_Comm_revoke</A></TD>
+<TD><A HREF="www3/MPI_File_write_all.html">MPI_File_write_all</A></TD>
+<TD><A HREF="www3/MPI_Ssend.html">MPI_Ssend</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPIX_Comm_shrink.html">MPIX_Comm_shrink</A></TD>
+<TD><A HREF="www3/MPI_File_write_all_begin.html">MPI_File_write_all_begin</A></TD>
+<TD><A HREF="www3/MPI_Ssend_init.html">MPI_Ssend_init</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Abort.html">MPI_Abort</A></TD>
+<TD><A HREF="www3/MPI_File_write_all_end.html">MPI_File_write_all_end</A></TD>
+<TD><A HREF="www3/MPI_Start.html">MPI_Start</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Accumulate.html">MPI_Accumulate</A></TD>
+<TD><A HREF="www3/MPI_File_write_at.html">MPI_File_write_at</A></TD>
+<TD><A HREF="www3/MPI_Startall.html">MPI_Startall</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Add_error_class.html">MPI_Add_error_class</A></TD>
+<TD><A HREF="www3/MPI_File_write_at_all.html">MPI_File_write_at_all</A></TD>
+<TD><A HREF="www3/MPI_Status_set_cancelled.html">MPI_Status_set_cancelled</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Add_error_code.html">MPI_Add_error_code</A></TD>
+<TD><A HREF="www3/MPI_File_write_at_all_begin.html">MPI_File_write_at_all_begin</A></TD>
+<TD><A HREF="www3/MPI_Status_set_elements.html">MPI_Status_set_elements</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Add_error_string.html">MPI_Add_error_string</A></TD>
+<TD><A HREF="www3/MPI_File_write_at_all_end.html">MPI_File_write_at_all_end</A></TD>
+<TD><A HREF="www3/MPI_Status_set_elements_x.html">MPI_Status_set_elements_x</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Address.html">MPI_Address</A></TD>
+<TD><A HREF="www3/MPI_File_write_ordered.html">MPI_File_write_ordered</A></TD>
+<TD><A HREF="www3/MPI_T_category_changed.html">MPI_T_category_changed</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Aint_add.html">MPI_Aint_add</A></TD>
+<TD><A HREF="www3/MPI_File_write_ordered_begin.html">MPI_File_write_ordered_begin</A></TD>
+<TD><A HREF="www3/MPI_T_category_get_categories.html">MPI_T_category_get_categories</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Aint_diff.html">MPI_Aint_diff</A></TD>
+<TD><A HREF="www3/MPI_File_write_ordered_end.html">MPI_File_write_ordered_end</A></TD>
+<TD><A HREF="www3/MPI_T_category_get_cvars.html">MPI_T_category_get_cvars</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Allgather.html">MPI_Allgather</A></TD>
+<TD><A HREF="www3/MPI_File_write_shared.html">MPI_File_write_shared</A></TD>
+<TD><A HREF="www3/MPI_T_category_get_info.html">MPI_T_category_get_info</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Allgatherv.html">MPI_Allgatherv</A></TD>
+<TD><A HREF="www3/MPI_Finalize.html">MPI_Finalize</A></TD>
+<TD><A HREF="www3/MPI_T_category_get_num.html">MPI_T_category_get_num</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Alloc_mem.html">MPI_Alloc_mem</A></TD>
+<TD><A HREF="www3/MPI_Finalized.html">MPI_Finalized</A></TD>
+<TD><A HREF="www3/MPI_T_category_get_pvars.html">MPI_T_category_get_pvars</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Allreduce.html">MPI_Allreduce</A></TD>
+<TD><A HREF="www3/MPI_Free_mem.html">MPI_Free_mem</A></TD>
+<TD><A HREF="www3/MPI_T_cvar_get_info.html">MPI_T_cvar_get_info</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Alltoall.html">MPI_Alltoall</A></TD>
+<TD><A HREF="www3/MPI_Gather.html">MPI_Gather</A></TD>
+<TD><A HREF="www3/MPI_T_cvar_get_num.html">MPI_T_cvar_get_num</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Alltoallv.html">MPI_Alltoallv</A></TD>
+<TD><A HREF="www3/MPI_Gatherv.html">MPI_Gatherv</A></TD>
+<TD><A HREF="www3/MPI_T_cvar_handle_alloc.html">MPI_T_cvar_handle_alloc</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Alltoallw.html">MPI_Alltoallw</A></TD>
+<TD><A HREF="www3/MPI_Get.html">MPI_Get</A></TD>
+<TD><A HREF="www3/MPI_T_cvar_handle_free.html">MPI_T_cvar_handle_free</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Attr_delete.html">MPI_Attr_delete</A></TD>
+<TD><A HREF="www3/MPI_Get_accumulate.html">MPI_Get_accumulate</A></TD>
+<TD><A HREF="www3/MPI_T_cvar_read.html">MPI_T_cvar_read</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Attr_get.html">MPI_Attr_get</A></TD>
+<TD><A HREF="www3/MPI_Get_address.html">MPI_Get_address</A></TD>
+<TD><A HREF="www3/MPI_T_cvar_write.html">MPI_T_cvar_write</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Attr_put.html">MPI_Attr_put</A></TD>
+<TD><A HREF="www3/MPI_Get_count.html">MPI_Get_count</A></TD>
+<TD><A HREF="www3/MPI_T_enum_get_info.html">MPI_T_enum_get_info</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Barrier.html">MPI_Barrier</A></TD>
+<TD><A HREF="www3/MPI_Get_elements.html">MPI_Get_elements</A></TD>
+<TD><A HREF="www3/MPI_T_enum_get_item.html">MPI_T_enum_get_item</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Bcast.html">MPI_Bcast</A></TD>
+<TD><A HREF="www3/MPI_Get_elements_x.html">MPI_Get_elements_x</A></TD>
+<TD><A HREF="www3/MPI_T_finalize.html">MPI_T_finalize</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Bsend.html">MPI_Bsend</A></TD>
+<TD><A HREF="www3/MPI_Get_library_version.html">MPI_Get_library_version</A></TD>
+<TD><A HREF="www3/MPI_T_init_thread.html">MPI_T_init_thread</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Bsend_init.html">MPI_Bsend_init</A></TD>
+<TD><A HREF="www3/MPI_Get_processor_name.html">MPI_Get_processor_name</A></TD>
+<TD><A HREF="www3/MPI_T_pvar_get_info.html">MPI_T_pvar_get_info</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Buffer_attach.html">MPI_Buffer_attach</A></TD>
+<TD><A HREF="www3/MPI_Get_version.html">MPI_Get_version</A></TD>
+<TD><A HREF="www3/MPI_T_pvar_get_num.html">MPI_T_pvar_get_num</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Buffer_detach.html">MPI_Buffer_detach</A></TD>
+<TD><A HREF="www3/MPI_Graph_create.html">MPI_Graph_create</A></TD>
+<TD><A HREF="www3/MPI_T_pvar_handle_alloc.html">MPI_T_pvar_handle_alloc</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Cancel.html">MPI_Cancel</A></TD>
+<TD><A HREF="www3/MPI_Graph_get.html">MPI_Graph_get</A></TD>
+<TD><A HREF="www3/MPI_T_pvar_handle_free.html">MPI_T_pvar_handle_free</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Cart_coords.html">MPI_Cart_coords</A></TD>
+<TD><A HREF="www3/MPI_Graph_map.html">MPI_Graph_map</A></TD>
+<TD><A HREF="www3/MPI_T_pvar_read.html">MPI_T_pvar_read</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Cart_create.html">MPI_Cart_create</A></TD>
+<TD><A HREF="www3/MPI_Graph_neighbors.html">MPI_Graph_neighbors</A></TD>
+<TD><A HREF="www3/MPI_T_pvar_readreset.html">MPI_T_pvar_readreset</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Cart_get.html">MPI_Cart_get</A></TD>
+<TD><A HREF="www3/MPI_Graph_neighbors_count.html">MPI_Graph_neighbors_count</A></TD>
+<TD><A HREF="www3/MPI_T_pvar_reset.html">MPI_T_pvar_reset</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Cart_map.html">MPI_Cart_map</A></TD>
+<TD><A HREF="www3/MPI_Graphdims_get.html">MPI_Graphdims_get</A></TD>
+<TD><A HREF="www3/MPI_T_pvar_session_create.html">MPI_T_pvar_session_create</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Cart_rank.html">MPI_Cart_rank</A></TD>
+<TD><A HREF="www3/MPI_Grequest_complete.html">MPI_Grequest_complete</A></TD>
+<TD><A HREF="www3/MPI_T_pvar_session_free.html">MPI_T_pvar_session_free</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Cart_shift.html">MPI_Cart_shift</A></TD>
+<TD><A HREF="www3/MPI_Grequest_start.html">MPI_Grequest_start</A></TD>
+<TD><A HREF="www3/MPI_T_pvar_start.html">MPI_T_pvar_start</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Cart_sub.html">MPI_Cart_sub</A></TD>
+<TD><A HREF="www3/MPI_Group_compare.html">MPI_Group_compare</A></TD>
+<TD><A HREF="www3/MPI_T_pvar_stop.html">MPI_T_pvar_stop</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Cartdim_get.html">MPI_Cartdim_get</A></TD>
+<TD><A HREF="www3/MPI_Group_difference.html">MPI_Group_difference</A></TD>
+<TD><A HREF="www3/MPI_T_pvar_write.html">MPI_T_pvar_write</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Close_port.html">MPI_Close_port</A></TD>
+<TD><A HREF="www3/MPI_Group_excl.html">MPI_Group_excl</A></TD>
+<TD><A HREF="www3/MPI_Test.html">MPI_Test</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_accept.html">MPI_Comm_accept</A></TD>
+<TD><A HREF="www3/MPI_Group_free.html">MPI_Group_free</A></TD>
+<TD><A HREF="www3/MPI_Test_cancelled.html">MPI_Test_cancelled</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_call_errhandler.html">MPI_Comm_call_errhandler</A></TD>
+<TD><A HREF="www3/MPI_Group_incl.html">MPI_Group_incl</A></TD>
+<TD><A HREF="www3/MPI_Testall.html">MPI_Testall</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_compare.html">MPI_Comm_compare</A></TD>
+<TD><A HREF="www3/MPI_Group_intersection.html">MPI_Group_intersection</A></TD>
+<TD><A HREF="www3/MPI_Testany.html">MPI_Testany</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_connect.html">MPI_Comm_connect</A></TD>
+<TD><A HREF="www3/MPI_Group_range_excl.html">MPI_Group_range_excl</A></TD>
+<TD><A HREF="www3/MPI_Testsome.html">MPI_Testsome</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_create.html">MPI_Comm_create</A></TD>
+<TD><A HREF="www3/MPI_Group_range_incl.html">MPI_Group_range_incl</A></TD>
+<TD><A HREF="www3/MPI_Topo_test.html">MPI_Topo_test</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_create_errhandler.html">MPI_Comm_create_errhandler</A></TD>
+<TD><A HREF="www3/MPI_Group_rank.html">MPI_Group_rank</A></TD>
+<TD><A HREF="www3/MPI_Type_commit.html">MPI_Type_commit</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_create_group.html">MPI_Comm_create_group</A></TD>
+<TD><A HREF="www3/MPI_Group_size.html">MPI_Group_size</A></TD>
+<TD><A HREF="www3/MPI_Type_contiguous.html">MPI_Type_contiguous</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_create_keyval.html">MPI_Comm_create_keyval</A></TD>
+<TD><A HREF="www3/MPI_Group_translate_ranks.html">MPI_Group_translate_ranks</A></TD>
+<TD><A HREF="www3/MPI_Type_create_darray.html">MPI_Type_create_darray</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_delete_attr.html">MPI_Comm_delete_attr</A></TD>
+<TD><A HREF="www3/MPI_Group_union.html">MPI_Group_union</A></TD>
+<TD><A HREF="www3/MPI_Type_create_hindexed.html">MPI_Type_create_hindexed</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_disconnect.html">MPI_Comm_disconnect</A></TD>
+<TD><A HREF="www3/MPI_Iallgather.html">MPI_Iallgather</A></TD>
+<TD><A HREF="www3/MPI_Type_create_hindexed_block.html">MPI_Type_create_hindexed_block</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_dup.html">MPI_Comm_dup</A></TD>
+<TD><A HREF="www3/MPI_Iallgatherv.html">MPI_Iallgatherv</A></TD>
+<TD><A HREF="www3/MPI_Type_create_hvector.html">MPI_Type_create_hvector</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_dup_with_info.html">MPI_Comm_dup_with_info</A></TD>
+<TD><A HREF="www3/MPI_Iallreduce.html">MPI_Iallreduce</A></TD>
+<TD><A HREF="www3/MPI_Type_create_indexed_block.html">MPI_Type_create_indexed_block</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_free.html">MPI_Comm_free</A></TD>
+<TD><A HREF="www3/MPI_Ialltoall.html">MPI_Ialltoall</A></TD>
+<TD><A HREF="www3/MPI_Type_create_keyval.html">MPI_Type_create_keyval</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_free_keyval.html">MPI_Comm_free_keyval</A></TD>
+<TD><A HREF="www3/MPI_Ialltoallv.html">MPI_Ialltoallv</A></TD>
+<TD><A HREF="www3/MPI_Type_create_resized.html">MPI_Type_create_resized</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_get_attr.html">MPI_Comm_get_attr</A></TD>
+<TD><A HREF="www3/MPI_Ialltoallw.html">MPI_Ialltoallw</A></TD>
+<TD><A HREF="www3/MPI_Type_create_struct.html">MPI_Type_create_struct</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_get_errhandler.html">MPI_Comm_get_errhandler</A></TD>
+<TD><A HREF="www3/MPI_Ibarrier.html">MPI_Ibarrier</A></TD>
+<TD><A HREF="www3/MPI_Type_create_subarray.html">MPI_Type_create_subarray</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_get_info.html">MPI_Comm_get_info</A></TD>
+<TD><A HREF="www3/MPI_Ibcast.html">MPI_Ibcast</A></TD>
+<TD><A HREF="www3/MPI_Type_delete_attr.html">MPI_Type_delete_attr</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_get_name.html">MPI_Comm_get_name</A></TD>
+<TD><A HREF="www3/MPI_Ibsend.html">MPI_Ibsend</A></TD>
+<TD><A HREF="www3/MPI_Type_dup.html">MPI_Type_dup</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_get_parent.html">MPI_Comm_get_parent</A></TD>
+<TD><A HREF="www3/MPI_Iexscan.html">MPI_Iexscan</A></TD>
+<TD><A HREF="www3/MPI_Type_extent.html">MPI_Type_extent</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_group.html">MPI_Comm_group</A></TD>
+<TD><A HREF="www3/MPI_Igather.html">MPI_Igather</A></TD>
+<TD><A HREF="www3/MPI_Type_free.html">MPI_Type_free</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_idup.html">MPI_Comm_idup</A></TD>
+<TD><A HREF="www3/MPI_Igatherv.html">MPI_Igatherv</A></TD>
+<TD><A HREF="www3/MPI_Type_free_keyval.html">MPI_Type_free_keyval</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_join.html">MPI_Comm_join</A></TD>
+<TD><A HREF="www3/MPI_Improbe.html">MPI_Improbe</A></TD>
+<TD><A HREF="www3/MPI_Type_get_attr.html">MPI_Type_get_attr</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_rank.html">MPI_Comm_rank</A></TD>
+<TD><A HREF="www3/MPI_Imrecv.html">MPI_Imrecv</A></TD>
+<TD><A HREF="www3/MPI_Type_get_contents.html">MPI_Type_get_contents</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_remote_group.html">MPI_Comm_remote_group</A></TD>
+<TD><A HREF="www3/MPI_Ineighbor_allgather.html">MPI_Ineighbor_allgather</A></TD>
+<TD><A HREF="www3/MPI_Type_get_envelope.html">MPI_Type_get_envelope</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_remote_size.html">MPI_Comm_remote_size</A></TD>
+<TD><A HREF="www3/MPI_Ineighbor_allgatherv.html">MPI_Ineighbor_allgatherv</A></TD>
+<TD><A HREF="www3/MPI_Type_get_extent.html">MPI_Type_get_extent</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_set_attr.html">MPI_Comm_set_attr</A></TD>
+<TD><A HREF="www3/MPI_Ineighbor_alltoall.html">MPI_Ineighbor_alltoall</A></TD>
+<TD><A HREF="www3/MPI_Type_get_extent_x.html">MPI_Type_get_extent_x</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_set_errhandler.html">MPI_Comm_set_errhandler</A></TD>
+<TD><A HREF="www3/MPI_Ineighbor_alltoallv.html">MPI_Ineighbor_alltoallv</A></TD>
+<TD><A HREF="www3/MPI_Type_get_name.html">MPI_Type_get_name</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_set_info.html">MPI_Comm_set_info</A></TD>
+<TD><A HREF="www3/MPI_Ineighbor_alltoallw.html">MPI_Ineighbor_alltoallw</A></TD>
+<TD><A HREF="www3/MPI_Type_get_true_extent.html">MPI_Type_get_true_extent</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_set_name.html">MPI_Comm_set_name</A></TD>
+<TD><A HREF="www3/MPI_Info_create.html">MPI_Info_create</A></TD>
+<TD><A HREF="www3/MPI_Type_get_true_extent_x.html">MPI_Type_get_true_extent_x</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_size.html">MPI_Comm_size</A></TD>
+<TD><A HREF="www3/MPI_Info_delete.html">MPI_Info_delete</A></TD>
+<TD><A HREF="www3/MPI_Type_hindexed.html">MPI_Type_hindexed</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_spawn.html">MPI_Comm_spawn</A></TD>
+<TD><A HREF="www3/MPI_Info_dup.html">MPI_Info_dup</A></TD>
+<TD><A HREF="www3/MPI_Type_hvector.html">MPI_Type_hvector</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_spawn_multiple.html">MPI_Comm_spawn_multiple</A></TD>
+<TD><A HREF="www3/MPI_Info_free.html">MPI_Info_free</A></TD>
+<TD><A HREF="www3/MPI_Type_indexed.html">MPI_Type_indexed</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_split.html">MPI_Comm_split</A></TD>
+<TD><A HREF="www3/MPI_Info_get.html">MPI_Info_get</A></TD>
+<TD><A HREF="www3/MPI_Type_lb.html">MPI_Type_lb</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_split_type.html">MPI_Comm_split_type</A></TD>
+<TD><A HREF="www3/MPI_Info_get_nkeys.html">MPI_Info_get_nkeys</A></TD>
+<TD><A HREF="www3/MPI_Type_match_size.html">MPI_Type_match_size</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Comm_test_inter.html">MPI_Comm_test_inter</A></TD>
+<TD><A HREF="www3/MPI_Info_get_nthkey.html">MPI_Info_get_nthkey</A></TD>
+<TD><A HREF="www3/MPI_Type_set_attr.html">MPI_Type_set_attr</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Compare_and_swap.html">MPI_Compare_and_swap</A></TD>
+<TD><A HREF="www3/MPI_Info_get_valuelen.html">MPI_Info_get_valuelen</A></TD>
+<TD><A HREF="www3/MPI_Type_set_name.html">MPI_Type_set_name</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Dims_create.html">MPI_Dims_create</A></TD>
+<TD><A HREF="www3/MPI_Info_set.html">MPI_Info_set</A></TD>
+<TD><A HREF="www3/MPI_Type_size.html">MPI_Type_size</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Dist_graph_create.html">MPI_Dist_graph_create</A></TD>
+<TD><A HREF="www3/MPI_Init.html">MPI_Init</A></TD>
+<TD><A HREF="www3/MPI_Type_size_x.html">MPI_Type_size_x</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Dist_graph_create_adjacent.html">MPI_Dist_graph_create_adjacent</A></TD>
+<TD><A HREF="www3/MPI_Init_thread.html">MPI_Init_thread</A></TD>
+<TD><A HREF="www3/MPI_Type_struct.html">MPI_Type_struct</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Dist_graph_neighbors.html">MPI_Dist_graph_neighbors</A></TD>
+<TD><A HREF="www3/MPI_Initialized.html">MPI_Initialized</A></TD>
+<TD><A HREF="www3/MPI_Type_ub.html">MPI_Type_ub</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Dist_graph_neighbors_count.html">MPI_Dist_graph_neighbors_count</A></TD>
+<TD><A HREF="www3/MPI_Intercomm_create.html">MPI_Intercomm_create</A></TD>
+<TD><A HREF="www3/MPI_Type_vector.html">MPI_Type_vector</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Errhandler_create.html">MPI_Errhandler_create</A></TD>
+<TD><A HREF="www3/MPI_Intercomm_merge.html">MPI_Intercomm_merge</A></TD>
+<TD><A HREF="www3/MPI_Unpack.html">MPI_Unpack</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Errhandler_free.html">MPI_Errhandler_free</A></TD>
+<TD><A HREF="www3/MPI_Iprobe.html">MPI_Iprobe</A></TD>
+<TD><A HREF="www3/MPI_Unpack_external.html">MPI_Unpack_external</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Errhandler_get.html">MPI_Errhandler_get</A></TD>
+<TD><A HREF="www3/MPI_Irecv.html">MPI_Irecv</A></TD>
+<TD><A HREF="www3/MPI_Unpublish_name.html">MPI_Unpublish_name</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Errhandler_set.html">MPI_Errhandler_set</A></TD>
+<TD><A HREF="www3/MPI_Ireduce.html">MPI_Ireduce</A></TD>
+<TD><A HREF="www3/MPI_Wait.html">MPI_Wait</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Error_class.html">MPI_Error_class</A></TD>
+<TD><A HREF="www3/MPI_Ireduce_scatter.html">MPI_Ireduce_scatter</A></TD>
+<TD><A HREF="www3/MPI_Waitall.html">MPI_Waitall</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Error_string.html">MPI_Error_string</A></TD>
+<TD><A HREF="www3/MPI_Ireduce_scatter_block.html">MPI_Ireduce_scatter_block</A></TD>
+<TD><A HREF="www3/MPI_Waitany.html">MPI_Waitany</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Exscan.html">MPI_Exscan</A></TD>
+<TD><A HREF="www3/MPI_Irsend.html">MPI_Irsend</A></TD>
+<TD><A HREF="www3/MPI_Waitsome.html">MPI_Waitsome</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_Fetch_and_op.html">MPI_Fetch_and_op</A></TD>
+<TD><A HREF="www3/MPI_Is_thread_main.html">MPI_Is_thread_main</A></TD>
+<TD><A HREF="www3/MPI_Win_allocate.html">MPI_Win_allocate</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_c2f.html">MPI_File_c2f</A></TD>
+<TD><A HREF="www3/MPI_Iscan.html">MPI_Iscan</A></TD>
+<TD><A HREF="www3/MPI_Win_allocate_shared.html">MPI_Win_allocate_shared</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_call_errhandler.html">MPI_File_call_errhandler</A></TD>
+<TD><A HREF="www3/MPI_Iscatter.html">MPI_Iscatter</A></TD>
+<TD><A HREF="www3/MPI_Win_attach.html">MPI_Win_attach</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_close.html">MPI_File_close</A></TD>
+<TD><A HREF="www3/MPI_Iscatterv.html">MPI_Iscatterv</A></TD>
+<TD><A HREF="www3/MPI_Win_call_errhandler.html">MPI_Win_call_errhandler</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_create_errhandler.html">MPI_File_create_errhandler</A></TD>
+<TD><A HREF="www3/MPI_Isend.html">MPI_Isend</A></TD>
+<TD><A HREF="www3/MPI_Win_complete.html">MPI_Win_complete</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_delete.html">MPI_File_delete</A></TD>
+<TD><A HREF="www3/MPI_Issend.html">MPI_Issend</A></TD>
+<TD><A HREF="www3/MPI_Win_create.html">MPI_Win_create</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_f2c.html">MPI_File_f2c</A></TD>
+<TD><A HREF="www3/MPI_Keyval_create.html">MPI_Keyval_create</A></TD>
+<TD><A HREF="www3/MPI_Win_create_dynamic.html">MPI_Win_create_dynamic</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_get_amode.html">MPI_File_get_amode</A></TD>
+<TD><A HREF="www3/MPI_Keyval_free.html">MPI_Keyval_free</A></TD>
+<TD><A HREF="www3/MPI_Win_create_errhandler.html">MPI_Win_create_errhandler</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_get_atomicity.html">MPI_File_get_atomicity</A></TD>
+<TD><A HREF="www3/MPI_Lookup_name.html">MPI_Lookup_name</A></TD>
+<TD><A HREF="www3/MPI_Win_create_keyval.html">MPI_Win_create_keyval</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_get_byte_offset.html">MPI_File_get_byte_offset</A></TD>
+<TD><A HREF="www3/MPI_Mprobe.html">MPI_Mprobe</A></TD>
+<TD><A HREF="www3/MPI_Win_delete_attr.html">MPI_Win_delete_attr</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_get_errhandler.html">MPI_File_get_errhandler</A></TD>
+<TD><A HREF="www3/MPI_Mrecv.html">MPI_Mrecv</A></TD>
+<TD><A HREF="www3/MPI_Win_detach.html">MPI_Win_detach</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_get_group.html">MPI_File_get_group</A></TD>
+<TD><A HREF="www3/MPI_Neighbor_allgather.html">MPI_Neighbor_allgather</A></TD>
+<TD><A HREF="www3/MPI_Win_fence.html">MPI_Win_fence</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_get_info.html">MPI_File_get_info</A></TD>
+<TD><A HREF="www3/MPI_Neighbor_allgatherv.html">MPI_Neighbor_allgatherv</A></TD>
+<TD><A HREF="www3/MPI_Win_flush.html">MPI_Win_flush</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_get_position.html">MPI_File_get_position</A></TD>
+<TD><A HREF="www3/MPI_Neighbor_alltoall.html">MPI_Neighbor_alltoall</A></TD>
+<TD><A HREF="www3/MPI_Win_flush_all.html">MPI_Win_flush_all</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_get_position_shared.html">MPI_File_get_position_shared</A></TD>
+<TD><A HREF="www3/MPI_Neighbor_alltoallv.html">MPI_Neighbor_alltoallv</A></TD>
+<TD><A HREF="www3/MPI_Win_flush_local.html">MPI_Win_flush_local</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_get_size.html">MPI_File_get_size</A></TD>
+<TD><A HREF="www3/MPI_Neighbor_alltoallw.html">MPI_Neighbor_alltoallw</A></TD>
+<TD><A HREF="www3/MPI_Win_flush_local_all.html">MPI_Win_flush_local_all</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_get_type_extent.html">MPI_File_get_type_extent</A></TD>
+<TD><A HREF="www3/MPI_Op_commute.html">MPI_Op_commute</A></TD>
+<TD><A HREF="www3/MPI_Win_free.html">MPI_Win_free</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_get_view.html">MPI_File_get_view</A></TD>
+<TD><A HREF="www3/MPI_Op_create.html">MPI_Op_create</A></TD>
+<TD><A HREF="www3/MPI_Win_free_keyval.html">MPI_Win_free_keyval</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_iread.html">MPI_File_iread</A></TD>
+<TD><A HREF="www3/MPI_Op_free.html">MPI_Op_free</A></TD>
+<TD><A HREF="www3/MPI_Win_get_attr.html">MPI_Win_get_attr</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_iread_all.html">MPI_File_iread_all</A></TD>
+<TD><A HREF="www3/MPI_Open_port.html">MPI_Open_port</A></TD>
+<TD><A HREF="www3/MPI_Win_get_errhandler.html">MPI_Win_get_errhandler</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_iread_at.html">MPI_File_iread_at</A></TD>
+<TD><A HREF="www3/MPI_Pack.html">MPI_Pack</A></TD>
+<TD><A HREF="www3/MPI_Win_get_group.html">MPI_Win_get_group</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_iread_at_all.html">MPI_File_iread_at_all</A></TD>
+<TD><A HREF="www3/MPI_Pack_external.html">MPI_Pack_external</A></TD>
+<TD><A HREF="www3/MPI_Win_get_info.html">MPI_Win_get_info</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_iread_shared.html">MPI_File_iread_shared</A></TD>
+<TD><A HREF="www3/MPI_Pack_external_size.html">MPI_Pack_external_size</A></TD>
+<TD><A HREF="www3/MPI_Win_get_name.html">MPI_Win_get_name</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_iwrite.html">MPI_File_iwrite</A></TD>
+<TD><A HREF="www3/MPI_Pack_size.html">MPI_Pack_size</A></TD>
+<TD><A HREF="www3/MPI_Win_lock.html">MPI_Win_lock</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_iwrite_all.html">MPI_File_iwrite_all</A></TD>
+<TD><A HREF="www3/MPI_Pcontrol.html">MPI_Pcontrol</A></TD>
+<TD><A HREF="www3/MPI_Win_lock_all.html">MPI_Win_lock_all</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_iwrite_at.html">MPI_File_iwrite_at</A></TD>
+<TD><A HREF="www3/MPI_Probe.html">MPI_Probe</A></TD>
+<TD><A HREF="www3/MPI_Win_post.html">MPI_Win_post</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_iwrite_at_all.html">MPI_File_iwrite_at_all</A></TD>
+<TD><A HREF="www3/MPI_Publish_name.html">MPI_Publish_name</A></TD>
+<TD><A HREF="www3/MPI_Win_set_attr.html">MPI_Win_set_attr</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_iwrite_shared.html">MPI_File_iwrite_shared</A></TD>
+<TD><A HREF="www3/MPI_Put.html">MPI_Put</A></TD>
+<TD><A HREF="www3/MPI_Win_set_errhandler.html">MPI_Win_set_errhandler</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_open.html">MPI_File_open</A></TD>
+<TD><A HREF="www3/MPI_Query_thread.html">MPI_Query_thread</A></TD>
+<TD><A HREF="www3/MPI_Win_set_info.html">MPI_Win_set_info</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_preallocate.html">MPI_File_preallocate</A></TD>
+<TD><A HREF="www3/MPI_Raccumulate.html">MPI_Raccumulate</A></TD>
+<TD><A HREF="www3/MPI_Win_set_name.html">MPI_Win_set_name</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_read.html">MPI_File_read</A></TD>
+<TD><A HREF="www3/MPI_Recv.html">MPI_Recv</A></TD>
+<TD><A HREF="www3/MPI_Win_shared_query.html">MPI_Win_shared_query</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_read_all.html">MPI_File_read_all</A></TD>
+<TD><A HREF="www3/MPI_Recv_init.html">MPI_Recv_init</A></TD>
+<TD><A HREF="www3/MPI_Win_start.html">MPI_Win_start</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_read_all_begin.html">MPI_File_read_all_begin</A></TD>
+<TD><A HREF="www3/MPI_Reduce.html">MPI_Reduce</A></TD>
+<TD><A HREF="www3/MPI_Win_sync.html">MPI_Win_sync</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_read_all_end.html">MPI_File_read_all_end</A></TD>
+<TD><A HREF="www3/MPI_Reduce_local.html">MPI_Reduce_local</A></TD>
+<TD><A HREF="www3/MPI_Win_test.html">MPI_Win_test</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_read_at.html">MPI_File_read_at</A></TD>
+<TD><A HREF="www3/MPI_Reduce_scatter.html">MPI_Reduce_scatter</A></TD>
+<TD><A HREF="www3/MPI_Win_unlock.html">MPI_Win_unlock</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_read_at_all.html">MPI_File_read_at_all</A></TD>
+<TD><A HREF="www3/MPI_Reduce_scatter_block.html">MPI_Reduce_scatter_block</A></TD>
+<TD><A HREF="www3/MPI_Win_unlock_all.html">MPI_Win_unlock_all</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_read_at_all_begin.html">MPI_File_read_at_all_begin</A></TD>
+<TD><A HREF="www3/MPI_Register_datarep.html">MPI_Register_datarep</A></TD>
+<TD><A HREF="www3/MPI_Win_wait.html">MPI_Win_wait</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_read_at_all_end.html">MPI_File_read_at_all_end</A></TD>
+<TD><A HREF="www3/MPI_Request_free.html">MPI_Request_free</A></TD>
+<TD><A HREF="www3/MPI_Wtick.html">MPI_Wtick</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_read_ordered.html">MPI_File_read_ordered</A></TD>
+<TD><A HREF="www3/MPI_Request_get_status.html">MPI_Request_get_status</A></TD>
+<TD><A HREF="www3/MPI_Wtime.html">MPI_Wtime</A></TD>
+</TR>
+<TR><TD><A HREF="www3/MPI_File_read_ordered_begin.html">MPI_File_read_ordered_begin</A></TD>
+<TD><A HREF="www3/MPI_Rget.html">MPI_Rget</A></TD>
+<TD></TD>
+</TR>
+</TABLE>
+</BODY>
+</HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/install.pdf b/linx64/mpi/mpich/share/doc/mpich/install.pdf
index 51e909a3..3b6b8220 100644
Binary files a/linx64/mpi/mpich/share/doc/mpich/install.pdf and b/linx64/mpi/mpich/share/doc/mpich/install.pdf differ
diff --git a/linx64/mpi/mpich/share/doc/mpich/logging.pdf b/linx64/mpi/mpich/share/doc/mpich/logging.pdf
index 9dfe52a4..0115b9ad 100644
Binary files a/linx64/mpi/mpich/share/doc/mpich/logging.pdf and b/linx64/mpi/mpich/share/doc/mpich/logging.pdf differ
diff --git a/linx64/mpi/mpich/share/doc/mpich/user.pdf b/linx64/mpi/mpich/share/doc/mpich/user.pdf
index 09ec91a5..a8ed99f0 100644
Binary files a/linx64/mpi/mpich/share/doc/mpich/user.pdf and b/linx64/mpi/mpich/share/doc/mpich/user.pdf differ
diff --git a/linx64/mpi/mpich/share/doc/mpich/www1/index.htm b/linx64/mpi/mpich/share/doc/mpich/www1/index.htm
index 98f83cc6..665ebe1e 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www1/index.htm
+++ b/linx64/mpi/mpich/share/doc/mpich/www1/index.htm
@@ -1,19 +1,19 @@
-<HTML>
-<HEAD>
-<TITLE>Manpages for MPICH</TITLE>
-<!-- This file generated by createhtmlindex on  -->
-</HEAD>
-<BODY BGCOLOR="FFFFFF">
-<H1>Manpages for MPICH</H1>
-<TABLE>
-<TR><TD><A HREF="mpicc.html">mpicc</A></TD>
-<TD><A HREF="mpiexec.html">mpiexec</A></TD>
-<TD><A HREF="mpifort.html">mpifort</A></TD>
-</TR>
-<TR><TD><A HREF="mpicxx.html">mpicxx</A></TD>
-<TD><A HREF="mpif77.html">mpif77</A></TD>
-<TD></TD>
-</TR>
-</TABLE>
-</BODY>
-</HTML>
+<HTML>
+<HEAD>
+<TITLE>Manpages for MPICH</TITLE>
+<!-- This file generated by createhtmlindex on  -->
+</HEAD>
+<BODY BGCOLOR="FFFFFF">
+<H1>Manpages for MPICH</H1>
+<TABLE>
+<TR><TD><A HREF="mpicc.html">mpicc</A></TD>
+<TD><A HREF="mpiexec.html">mpiexec</A></TD>
+<TD><A HREF="mpifort.html">mpifort</A></TD>
+</TR>
+<TR><TD><A HREF="mpicxx.html">mpicxx</A></TD>
+<TD><A HREF="mpif77.html">mpif77</A></TD>
+<TD></TD>
+</TR>
+</TABLE>
+</BODY>
+</HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www1/mpicc.html b/linx64/mpi/mpich/share/doc/mpich/www1/mpicc.html
index 131ad04b..76150b9f 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www1/mpicc.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www1/mpicc.html
@@ -22,12 +22,12 @@ running them
 
 <DT><B>-help      </B><DD>Give short help
 
-<DT><B>-cc=name   </B><DD>Use compiler <tt>name</tt> instead of the default choice.  Use
+<DT><B>-cc=name   </B><DD>Use compiler <TT>name</TT> instead of the default choice.  Use
 this only if the compiler is compatible with the MPICH
 library (see below)
 
 <DT><B>-config=name </B><DD>Load a configuration file for a particular compiler.
-This allows a single <tt>mpicc</tt> command to be used with 
+This allows a single <TT>mpicc</TT> command to be used with 
 multiple compilers.
 
 <DT><B>-compile_info </B><DD>Show the steps for compiling a program.  This option
@@ -44,37 +44,40 @@ details
 <DT><B>-echo      </B><DD>Show exactly what this program is doing.
 This option should normally not be used.
 
-<DT><B>others     </B><DD>are passed to the compiler or linker.  For example, <tt>\-c
-</tt>causes files to be compiled, <tt>\-g</tt> selects compilation with
-debugging on most systems, and <tt>\-o name</tt> causes linking
-with the output executable given the name <tt>name</tt>.
+<DT><B>-static</B><DD>mpi - Use a statically compile MPI library, but shared libraries
+for all of the other dependencies.
+
+<DT><B>others     </B><DD>are passed to the compiler or linker.  For example, <TT>\-c
+</TT>causes files to be compiled, <TT>\-g</TT> selects compilation with
+debugging on most systems, and <TT>\-o name</TT> causes linking
+with the output executable given the name <TT>name</TT>.
 </DL>
 <P>
 <H2>Environment Variables</H2>
-The environment variable <tt>MPICH_CC</tt> may be used
+The environment variable <TT>MPICH_CC</TT> may be used
 to select different C compiler and linker.  Note that since
 MPICH is built with a particular C and Fortran compiler, changing the
 compilers used can cause problems.  Use this only if you could intermix
 code compiled with the different compilers.
 <P>
-The environment variable <tt>MPICC_PROFILE</tt> specifies a profile library
-and has the same effect as if <tt>\-profile=$MPICC_PROFILE</tt> were used as
-an argument to <tt>mpicc</tt>.  See the discussion of <tt>\-profile</tt> below for more
+The environment variable <TT>MPICC_PROFILE</TT> specifies a profile library
+and has the same effect as if <TT>\-profile=$MPICC_PROFILE</TT> were used as
+an argument to <TT>mpicc</TT>.  See the discussion of <TT>\-profile</TT> below for more
 details.
 <P>
 <H2>Compatible Compilers</H2>
 The MPI library may be used with any compiler that uses the same
-lengths for basic data objects (such as <tt>long double</tt>) and that
+lengths for basic data objects (such as <TT>long double</TT>) and that
 uses compatible run-time libraries.  On many systems, the various
 compilers are compatible and may be used interchangably.  There are
-exceptions; if you use the <tt>MPICH_CC</tt> environment variable or the
-<tt>\-cc=name</tt> command-line argument to override the choice of compiler
+exceptions; if you use the <TT>MPICH_CC</TT> environment variable or the
+<TT>\-cc=name</TT> command-line argument to override the choice of compiler
 and encounter problems, try reconfiguring MPICH with the new compiler
 and installing MPICH in a separate location.  See the installation manual
 for more details.
 <P>
 <H2>Examples</H2>
-To compile a single file <tt>foo.c</tt>, use
+To compile a single file <TT>foo.c</TT>, use
 <PRE>
    mpicc -c foo.c
 </PRE>
@@ -93,19 +96,19 @@ Combining compilation and linking in a single command
 is a convenient way to build simple programs.
 <P>
 <H2>Selecting a Profiling Library</H2>
-The <tt>\-profile=name</tt> argument allows you to specify an MPI profiling
-library to be used.  <tt>name</tt> can have two forms:
+The <TT>\-profile=name</TT> argument allows you to specify an MPI profiling
+library to be used.  <TT>name</TT> can have two forms:
 <P>
-<br>A library in the same directory as the MPI library
-<br>The name of a profile configuration file
-<br>
+<BR>A library in the same directory as the MPI library
+<BR>The name of a profile configuration file
+<BR>
 <P>
-If <tt>name</tt> is a library, then this library is included before the MPI
+If <TT>name</TT> is a library, then this library is included before the MPI
 library.  This allows the simple use of libraries that make use of the
 MPI profiling interface and that are installed in the same directory as
 the MPI library.
 <P>
-If <tt>name.conf</tt> is the name of a file in the sysconfdir directory, then this
+If <TT>name.conf</TT> is the name of a file in the sysconfdir directory, then this
 is read and may define the following variables:
 <DL>
 <DT><B>PROFILE_PRELIB </B><DD>Libraries (and paths) to include before the MPI library
@@ -113,9 +116,9 @@ is read and may define the following variables:
 <DT><B>PROFILE_POSTLIB </B><DD>Libraries to include after the MPI library
 
 <DT><B>PROFILE_INCPATHS </B><DD>C preprocessor arguments for any include files
-For example, to add <tt>/usr/local/myprof/include</tt> to the include path and
-the library <tt>libmyprof.a</tt> in <tt>/usr/local/myprof/lib</tt> to the link step, 
-you could create the file <tt>myprof.conf</tt> with the lines
+For example, to add <TT>/usr/local/myprof/include</TT> to the include path and
+the library <TT>libmyprof.a</TT> in <TT>/usr/local/myprof/lib</TT> to the link step, 
+you could create the file <TT>myprof.conf</TT> with the lines
 </DL>
 <P>
 <PRE>
@@ -125,10 +128,10 @@ you could create the file <tt>myprof.conf</tt> with the lines
 
 and place it in the sysconfdir directory (this directory is set at
 configure time when MPICH is built).  Then using the command-line
-argument <tt>\-profile=myprof</tt> will cause these
+argument <TT>\-profile=myprof</TT> will cause these
 definitions to be added to the relevant compile commands.
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  mpicxx, mpifort, mpiexec
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www1/mpicxx.html b/linx64/mpi/mpich/share/doc/mpich/www1/mpicxx.html
index 1877f3a5..5d301224 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www1/mpicxx.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www1/mpicxx.html
@@ -22,12 +22,12 @@ running them
 
 <DT><B>-help      </B><DD>Give short help
 
-<DT><B>-cxx=name   </B><DD>Use compiler <tt>name</tt> instead of the default choice.  Use
+<DT><B>-cxx=name   </B><DD>Use compiler <TT>name</TT> instead of the default choice.  Use
 this only if the compiler is compatible with the MPICH
 library (see below)
 
 <DT><B>-config=name </B><DD>Load a configuration file for a particular compiler.
-This allows a single <tt>mpicxx</tt> command to be used with 
+This allows a single <TT>mpicxx</TT> command to be used with 
 multiple compilers.
 
 <DT><B>-compile_info </B><DD>Show the steps for compiling a program.  This option
@@ -44,37 +44,40 @@ details
 <DT><B>-echo      </B><DD>Show exactly what this program is doing.
 This option should normally not be used.
 
-<DT><B>others     </B><DD>are passed to the compiler or linker.  For example, <tt>\-c
-</tt>causes files to be compiled, <tt>\-g</tt> selects compilation with
-debugging on most systems, and <tt>\-o name</tt> causes linking
-with the output executable given the name <tt>name</tt>.
+<DT><B>-static</B><DD>mpi - Use a statically compile MPI library, but shared libraries
+for all of the other dependencies.
+
+<DT><B>others     </B><DD>are passed to the compiler or linker.  For example, <TT>\-c
+</TT>causes files to be compiled, <TT>\-g</TT> selects compilation with
+debugging on most systems, and <TT>\-o name</TT> causes linking
+with the output executable given the name <TT>name</TT>.
 </DL>
 <P>
 <H2>Environment Variables</H2>
-The environment variables <tt>MPICH_CXX</tt> may be used
+The environment variables <TT>MPICH_CXX</TT> may be used
 to select different C++ compiler and linker.  Note that since
 MPICH is built with a particular C and Fortran compiler, changing the
 compilers used can cause problems.  Use this only if you could intermix
 code compiled with the different compilers.
 <P>
-The environment variable <tt>MPICC_PROFILE</tt> specifies a profile library
-and has the same effect as if <tt>\-profile=$MPICC_PROFILE</tt> were used as
-an argument to <tt>mpicc</tt>.  See the discussion of <tt>\-profile</tt> below for more
+The environment variable <TT>MPICC_PROFILE</TT> specifies a profile library
+and has the same effect as if <TT>\-profile=$MPICC_PROFILE</TT> were used as
+an argument to <TT>mpicc</TT>.  See the discussion of <TT>\-profile</TT> below for more
 details.
 <P>
 <H2>Compatible Compilers</H2>
 The MPI library may be used with any compiler that uses the same
-lengths for basic data objects (such as <tt>long double</tt>) and that
+lengths for basic data objects (such as <TT>long double</TT>) and that
 uses compatible run-time libraries.  On many systems, the various
 compilers are compatible and may be used interchangably.  There are
-exceptions; if you use the <tt>MPICH_CXX</tt> environment variable or the
-<tt>\-cxx=name</tt> command-line argument to override the choice of compiler
+exceptions; if you use the <TT>MPICH_CXX</TT> environment variable or the
+<TT>\-cxx=name</TT> command-line argument to override the choice of compiler
 and encounter problems, try reconfiguring MPICH with the new compiler,
 and installing MPICH in a separate location.  See the installation manual
 for more details.
 <P>
 <H2>Examples</H2>
-To compile a single file <tt>foo.c</tt>, use
+To compile a single file <TT>foo.c</TT>, use
 <PRE>
    mpicxx -c foo.cxx
 </PRE>
@@ -93,19 +96,19 @@ Combining compilation and linking in a single command
 is a convenient way to build simple programs.
 <P>
 <H2>Selecting a Profiling Library</H2>
-The <tt>\-profile=name</tt> argument allows you to specify an MPI profiling
-library to be used.  <tt>name</tt> can have two forms:
+The <TT>\-profile=name</TT> argument allows you to specify an MPI profiling
+library to be used.  <TT>name</TT> can have two forms:
 <P>
-<br>A library in the same directory as the MPI library
-<br>The name of a profile configuration file
-<br>
+<BR>A library in the same directory as the MPI library
+<BR>The name of a profile configuration file
+<BR>
 <P>
-If <tt>name</tt> is a library, then this library is included before the MPI
+If <TT>name</TT> is a library, then this library is included before the MPI
 library.  This allows the simple use of libraries that make use of the
 MPI profiling interface and that are installed in the same directory as
 the MPI library.
 <P>
-If <tt>name.conf</tt> is the name of a file in the sysconfdir directory, then this
+If <TT>name.conf</TT> is the name of a file in the sysconfdir directory, then this
 is read and may define the following variables:
 <DL>
 <DT><B>PROFILE_PRELIB </B><DD>Libraries (and paths) to include before the MPI library
@@ -113,9 +116,9 @@ is read and may define the following variables:
 <DT><B>PROFILE_POSTLIB </B><DD>Libraries to include after the MPI library
 
 <DT><B>PROFILE_INCPATHS </B><DD>C preprocessor arguments for any include files
-For example, to add <tt>/usr/local/myprof/include</tt> to the include path and
-the library <tt>libmyprof.a</tt> in <tt>/usr/local/myprof/lib</tt> to the link step, 
-you could create the file <tt>myprof.conf</tt> with the lines
+For example, to add <TT>/usr/local/myprof/include</TT> to the include path and
+the library <TT>libmyprof.a</TT> in <TT>/usr/local/myprof/lib</TT> to the link step, 
+you could create the file <TT>myprof.conf</TT> with the lines
 </DL>
 <P>
 <PRE>
@@ -125,10 +128,10 @@ you could create the file <tt>myprof.conf</tt> with the lines
 
 and place it in the sysconfdir directory (this directory is set at
 configure time when MPICH is built).  Then using the command-line
-argument <tt>\-profile=myprof</tt> will cause these
+argument <TT>\-profile=myprof</TT> will cause these
 definitions to be added to the relevant compile commands.
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  mpicc, mpifort, mpiexec
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www1/mpiexec.html b/linx64/mpi/mpich/share/doc/mpich/www1/mpiexec.html
index 5d11c9af..270c44ba 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www1/mpiexec.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www1/mpiexec.html
@@ -14,12 +14,12 @@ Run an MPI program
     mpiexec args executable pgmargs [ : args executable pgmargs ... ]
 </PRE>
 
-where <tt>args</tt> are command line arguments for <tt>mpiexec</tt> (see below),
-<tt>executable</tt> is the name of an executable MPI program, and <tt>pgmargs
-</tt>are command line arguments for the executable.  Multiple executables
+where <TT>args</TT> are command line arguments for <TT>mpiexec</TT> (see below),
+<TT>executable</TT> is the name of an executable MPI program, and <TT>pgmargs
+</TT>are command line arguments for the executable.  Multiple executables
 can be specified by using the colon notation (for MPMD - Multiple Program
 Multiple Data applications).   For example, the following command will run
-the MPI program <tt>a.out</tt> on 4 processes:
+the MPI program <TT>a.out</TT> on 4 processes:
 <PRE>
     mpiexec -n 4 a.out
 </PRE>
@@ -34,7 +34,7 @@ The MPI standard specifies the following arguments and their meanings:
 
 <DT><B>-arch &lt;architecture name&gt; </B><DD>Pick hosts with this architecture type
 
-<DT><B>-wdir &lt;working directory&gt; </B><DD>cd to this one <em>before</em> running executable
+<DT><B>-wdir &lt;working directory&gt; </B><DD>cd to this one <EM>before</EM> running executable
 
 <DT><B>-path &lt;pathlist&gt; </B><DD>use this to find the executable
 
@@ -53,13 +53,13 @@ Additional arguments that are specific to the MPICH implementation
 are discussed below.
 <P>
 Note that not all of these parameters are meaningful for all
-systems.  For example, the <tt>gforker</tt> version of <tt>mpiexec</tt> creates all
+systems.  For example, the <TT>gforker</TT> version of <TT>mpiexec</TT> creates all
 processes on the same system on which it is running; in that case, the
-<tt>\-arch</tt> and <tt>\-host</tt> options are ignored.
+<TT>\-arch</TT> and <TT>\-host</TT> options are ignored.
 <P>
-The colon character (<tt>:</tt>) may be used to separate different executables
+The colon character (<TT>:</TT>) may be used to separate different executables
 for MPMD (multiple program multiple data) programming.  For example,
-to run the program <tt>ocean</tt> on 4 processes and <tt>air</tt> on 8 processes, use:
+to run the program <TT>ocean</TT> on 4 processes and <TT>air</TT> on 8 processes, use:
 <P>
 <PRE>
     mpiexec -n 4 ocean : -n 8 air
@@ -70,40 +70,40 @@ to run the program <tt>ocean</tt> on 4 processes and <tt>air</tt> on 8 processes
 <H2>MPICH-Specific Arguments</H2>
 <P>
 Many of the implementations of process managers in MPICH support the
-following arguments to <tt>mpiexec</tt>:
+following arguments to <TT>mpiexec</TT>:
 <P>
 <DL>
-<DT><B>-np &lt;num&gt; </B><DD>A synonym for the standard <tt>\-n</tt> argument
+<DT><B>-np &lt;num&gt; </B><DD>A synonym for the standard <TT>\-n</TT> argument
 
-<DT><B>-env &lt;name&gt; &lt;value&gt; </B><DD>Set the environment variable <tt>&lt;name&gt;</tt> to <tt>&lt;value&gt;</tt> for
-the processes being run by <tt>mpiexec
-</tt>
+<DT><B>-env &lt;name&gt; &lt;value&gt; </B><DD>Set the environment variable <TT>&lt;name&gt;</TT> to <TT>&lt;value&gt;</TT> for
+the processes being run by <TT>mpiexec
+</TT>
 <DT><B>-envnone </B><DD>Pass no environment variables (other than ones specified with
-other <tt>\-env</tt> or <tt>\-genv</tt> arguments) to the processes being run by <tt>mpiexec</tt>.
+other <TT>\-env</TT> or <TT>\-genv</TT> arguments) to the processes being run by <TT>mpiexec</TT>.
 By default, all environment
 variables are provided to each MPI process (rationale: principle of
 least surprise for the user)
 
 <DT><B>-envlist &lt;list&gt; </B><DD>Pass the listed environment variables (names separated
 by commas), with their current values, to the processes being run by
-<tt>mpiexec</tt>.
+<TT>mpiexec</TT>.
 
-<DT><B>-genv &lt;name&gt; &lt;value&gt; </B><DD>The <tt>\-genv</tt> options have the same meaning as their
-corresponding <tt>\-env</tt> version, except they apply to all executables, not just
+<DT><B>-genv &lt;name&gt; &lt;value&gt; </B><DD>The <TT>\-genv</TT> options have the same meaning as their
+corresponding <TT>\-env</TT> version, except they apply to all executables, not just
 the current executable (in the case that the colon syntax is used to specify
 multiple execuables).
 
-<DT><B>-genvnone </B><DD>Like <tt>\-envnone</tt>, but for all executables
+<DT><B>-genvnone </B><DD>Like <TT>\-envnone</TT>, but for all executables
 
-<DT><B>-genvlist &lt;list&gt; </B><DD>Like <tt>\-envlist</tt>, but for all executables
+<DT><B>-genvlist &lt;list&gt; </B><DD>Like <TT>\-envlist</TT>, but for all executables
 
 <DT><B>-usize &lt;n&gt; </B><DD>Specify the value returned for the value of the attribute
-<tt>MPI_UNIVERSE_SIZE</tt>.
+<TT>MPI_UNIVERSE_SIZE</TT>.
 
-<DT><B>-l </B><DD>Label standard out and standard error (<tt>stdout</tt> and <tt>stderr</tt>) with
+<DT><B>-l </B><DD>Label standard out and standard error (<TT>stdout</TT> and <TT>stderr</TT>) with
 the rank of the process
 
-<DT><B>-maxtime &lt;n&gt; </B><DD>Set a timelimit of <tt>&lt;n&gt;</tt> seconds.
+<DT><B>-maxtime &lt;n&gt; </B><DD>Set a timelimit of <TT>&lt;n&gt;</TT> seconds.
 
 <DT><B>-exitinfo </B><DD>Provide more information on the reason each process exited if
 there is an abnormal exit
@@ -111,42 +111,42 @@ there is an abnormal exit
 <P>
 <H2>Environment variables for mpiexec</H2>
 The following environment variables are understood by some versions of
-<tt>mpiexec</tt>.  The command line arguments have priority over these; that is,
+<TT>mpiexec</TT>.  The command line arguments have priority over these; that is,
 if both the environment variable and command line argument are used, the
 value specified by the command line argument is used.
 <P>
 <DL>
-<DT><B>MPIEXEC_TIMEOUT  </B><DD>Maximum running time in seconds.  <tt>mpiexec</tt> will
+<DT><B>MPIEXEC_TIMEOUT  </B><DD>Maximum running time in seconds.  <TT>mpiexec</TT> will
 terminate MPI programs that take longer than the value specified by
-<tt>MPIEXEC_TIMEOUT</tt>.  
+<TT>MPIEXEC_TIMEOUT</TT>.  
 
 <DT><B>MPIEXEC_UNIVERSE_SIZE </B><DD>Set the universe size
 
-<DT><B>MPIEXEC_PORT_RANGE </B><DD>Set the range of ports that <tt>mpiexec</tt> will use 
+<DT><B>MPIEXEC_PORT_RANGE </B><DD>Set the range of ports that <TT>mpiexec</TT> will use 
 in communicating with the processes that it starts.  The format of 
-this is <tt>&lt;low&gt;:&lt;high&gt;</tt>.  For example, to specify any port between
-10000 and 10100, use <tt>10000:10100</tt>.  
+this is <TT>&lt;low&gt;:&lt;high&gt;</TT>.  For example, to specify any port between
+10000 and 10100, use <TT>10000:10100</TT>.  
 
-<DT><B>MPICH_PORT_RANGE </B><DD>Has the same meaning as <tt>MPIEXEC_PORT_RANGE</tt> and 
-is used if <tt>MPIEXEC_PORT_RANGE</tt> is not set.
+<DT><B>MPICH_PORT_RANGE </B><DD>Has the same meaning as <TT>MPIEXEC_PORT_RANGE</TT> and 
+is used if <TT>MPIEXEC_PORT_RANGE</TT> is not set.
 
 <DT><B>MPIEXEC_PREFIX_DEFAULT </B><DD>If this environment variable is set, output
-to standard output is prefixed by the rank in <tt>MPI_COMM_WORLD</tt> of the 
+to standard output is prefixed by the rank in <TT>MPI_COMM_WORLD</TT> of the 
 process and output to standard error is prefixed by the rank and the 
-text <tt>(err)</tt>; both are followed by an angle bracket (<tt>&gt;</tt>).  If
+text <TT>(err)</TT>; both are followed by an angle bracket (<TT>&gt;</TT>).  If
 this variable is not set, there is no prefix.
 
 <DT><B>MPIEXEC_PREFIX_STDOUT </B><DD>Set the prefix used for lines sent to standard
-output.  A <tt>%d</tt> is replaced with the rank in <tt>MPI_COMM_WORLD</tt>; a <tt>%w</tt> is 
-replaced with an indication of which <tt>MPI_COMM_WORLD</tt> in MPI jobs that
-involve multiple <tt>MPI_COMM_WORLD</tt>s (e.g., ones that use <tt>MPI_Comm_spawn</tt> or
-<tt>MPI_Comm_connect</tt>).
+output.  A <TT>%d</TT> is replaced with the rank in <TT>MPI_COMM_WORLD</TT>; a <TT>%w</TT> is 
+replaced with an indication of which <TT>MPI_COMM_WORLD</TT> in MPI jobs that
+involve multiple <TT>MPI_COMM_WORLD</TT>s (e.g., ones that use <TT>MPI_Comm_spawn</TT> or
+<TT>MPI_Comm_connect</TT>).
 
-<DT><B>MPIEXEC_PREFIX_STDERR </B><DD>Like <tt>MPIEXEC_PREFIX_STDOUT</tt>, but for standard error.
+<DT><B>MPIEXEC_PREFIX_STDERR </B><DD>Like <TT>MPIEXEC_PREFIX_STDOUT</TT>, but for standard error.
 </DL>
 <P>
 <H2>Return Status</H2>
-<tt>mpiexec</tt> returns the maximum of the exit status values of all of the
-processes created by <tt>mpiexec</tt>.
+<TT>mpiexec</TT> returns the maximum of the exit status values of all of the
+processes created by <TT>mpiexec</TT>.
 <P>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www1/mpif77.html b/linx64/mpi/mpich/share/doc/mpich/www1/mpif77.html
index a282d8a9..98649881 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www1/mpif77.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www1/mpif77.html
@@ -22,12 +22,12 @@ running them
 
 <DT><B>-help      </B><DD>Give short help
 
-<DT><B>-f77=name   </B><DD>Use compiler <tt>name</tt> instead of the default choice.  Use
+<DT><B>-f77=name   </B><DD>Use compiler <TT>name</TT> instead of the default choice.  Use
 this only if the compiler is compatible with the MPICH
 library (see below)
 
 <DT><B>-config=name </B><DD>Load a configuration file for a particular compiler.
-This allows a single <tt>mpif77</tt> command to be used with 
+This allows a single <TT>mpif77</TT> command to be used with 
 multiple compilers.
 
 <DT><B>-compile_info </B><DD>Show the steps for compiling a program.  This option
@@ -44,14 +44,17 @@ details
 <DT><B>-echo      </B><DD>Show exactly what this program is doing.
 This option should normally not be used.
 
-<DT><B>others     </B><DD>are passed to the compiler or linker.  For example, <tt>\-c
-</tt>causes files to be compiled, <tt>\-g</tt> selects compilation with
-debugging on most systems, and <tt>\-o name</tt> causes linking
-with the output executable given the name <tt>name</tt>.
+<DT><B>-static</B><DD>mpi - Use a statically compile MPI library, but shared libraries
+for all of the other dependencies.
+
+<DT><B>others     </B><DD>are passed to the compiler or linker.  For example, <TT>\-c
+</TT>causes files to be compiled, <TT>\-g</TT> selects compilation with
+debugging on most systems, and <TT>\-o name</TT> causes linking
+with the output executable given the name <TT>name</TT>.
 </DL>
 <P>
 <H2>Environment Variables</H2>
-The environment variables <tt>MPICH_F77</tt> may be used
+The environment variables <TT>MPICH_F77</TT> may be used
 to select different Fortran compiler and linker.  Note that since
 MPICH is built with a particular C and Fortran compiler, change the
 compilers used can cause problems.  Use this only if you could intermix
@@ -59,17 +62,17 @@ code compiled with the different compilers.
 <P>
 <H2>Compatible Compilers</H2>
 The MPI library may be used with any compiler that uses the same
-lengths for basic data objects (such as <tt>long double</tt>) and that
+lengths for basic data objects (such as <TT>long double</TT>) and that
 uses compatible run-time libraries.  On many systems, the various
 compilers are compatible and may be used interchangably.  There are
-exceptions; if you use the <tt>MPICH_F77</tt> environment variable or the
-<tt>\-f77=name</tt> command-line argument to override the choice of compiler
+exceptions; if you use the <TT>MPICH_F77</TT> environment variable or the
+<TT>\-f77=name</TT> command-line argument to override the choice of compiler
 and encounter problems, try reconfiguring MPICH with the new compiler
 and installing MPICH in a separate location.  See the installation manual
 for more details.
 <P>
 <H2>Examples</H2>
-To compile a single file <tt>foo.f</tt>, use
+To compile a single file <TT>foo.f</TT>, use
 <PRE>
    mpif77 -c foo.f
 </PRE>
@@ -88,19 +91,19 @@ Combining compilation and linking in a single command
 is a convenient way to build simple programs.
 <P>
 <H2>Selecting a Profiling Library</H2>
-The <tt>\-profile=name</tt> argument allows you to specify an MPI profiling
-library to be used.  <tt>name</tt> can have two forms:
+The <TT>\-profile=name</TT> argument allows you to specify an MPI profiling
+library to be used.  <TT>name</TT> can have two forms:
 <P>
-<br>A library in the same directory as the MPI library
-<br>The name of a profile configuration file
-<br>
+<BR>A library in the same directory as the MPI library
+<BR>The name of a profile configuration file
+<BR>
 <P>
-If <tt>name</tt> is a library, then this library is included before the MPI
+If <TT>name</TT> is a library, then this library is included before the MPI
 library.  This allows the simple use of libraries that make use of the
 MPI profiling interface and that are installed in the same directory as
 the MPI library.
 <P>
-If <tt>name.conf</tt> is the name of a file in the sysconfdir directory, then this
+If <TT>name.conf</TT> is the name of a file in the sysconfdir directory, then this
 is read and may define the following variables:
 <DL>
 <DT><B>PROFILE_PRELIB </B><DD>Libraries (and paths) to include before the MPI library
@@ -108,9 +111,9 @@ is read and may define the following variables:
 <DT><B>PROFILE_POSTLIB </B><DD>Libraries to include after the MPI library
 
 <DT><B>PROFILE_INCPATHS </B><DD>C preprocessor arguments for any include files
-For example, to add <tt>/usr/local/myprof/include</tt> to the include path and
-the library <tt>libmyprof.a</tt> in <tt>/usr/local/myprof/lib</tt> to the link step, 
-you could create the file <tt>myprof.conf</tt> with the lines
+For example, to add <TT>/usr/local/myprof/include</TT> to the include path and
+the library <TT>libmyprof.a</TT> in <TT>/usr/local/myprof/lib</TT> to the link step, 
+you could create the file <TT>myprof.conf</TT> with the lines
 </DL>
 <P>
 <PRE>
@@ -120,10 +123,10 @@ you could create the file <tt>myprof.conf</tt> with the lines
 
 and place it in the sysconfdir directory (this directory is set at
 configure time when MPICH is built).  Then using the command-line
-argument <tt>\-profile=myprof</tt> will cause these
+argument <TT>\-profile=myprof</TT> will cause these
 definitions to be added to the relevant compile commands.
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  mpicc, mpicxx, mpifort, mpiexec
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www1/mpifort.html b/linx64/mpi/mpich/share/doc/mpich/www1/mpifort.html
index e2491c5a..d9a9d287 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www1/mpifort.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www1/mpifort.html
@@ -22,12 +22,12 @@ running them
 
 <DT><B>-help      </B><DD>Give short help
 
-<DT><B>-fc=name   </B><DD>Use compiler <tt>name</tt> instead of the default choice.  Use
+<DT><B>-fc=name   </B><DD>Use compiler <TT>name</TT> instead of the default choice.  Use
 this only if the compiler is compatible with the MPICH
 library (see below)
 
 <DT><B>-config=name </B><DD>Load a configuration file for a particular compiler.
-This allows a single <tt>mpifort</tt> command to be used with
+This allows a single <TT>mpifort</TT> command to be used with
 multiple compilers.
 
 <DT><B>-compile_info </B><DD>Show the steps for compiling a program.  This option
@@ -44,14 +44,17 @@ details
 <DT><B>-echo      </B><DD>Show exactly what this program is doing.
 This option should normally not be used.
 
-<DT><B>others     </B><DD>are passed to the compiler or linker.  For example, <tt>\-c
-</tt>causes files to be compiled, <tt>\-g</tt> selects compilation with
-debugging on most systems, and <tt>\-o name</tt> causes linking
-with the output executable given the name <tt>name</tt>.
+<DT><B>-static</B><DD>mpi - Use a statically compile MPI library, but shared libraries
+for all of the other dependencies.
+
+<DT><B>others     </B><DD>are passed to the compiler or linker.  For example, <TT>\-c
+</TT>causes files to be compiled, <TT>\-g</TT> selects compilation with
+debugging on most systems, and <TT>\-o name</TT> causes linking
+with the output executable given the name <TT>name</TT>.
 </DL>
 <P>
 <H2>Environment Variables</H2>
-The environment variables <tt>MPICH_FC</tt> may be used
+The environment variables <TT>MPICH_FC</TT> may be used
 to select different Fortran compiler and linker.  Note that since
 MPICH is built with a particular C and Fortran compiler, change the
 compilers used can cause problems.  Use this only if you could intermix
@@ -59,17 +62,17 @@ code compiled with the different compilers.
 <P>
 <H2>Compatible Compilers</H2>
 The MPI library may be used with any compiler that uses the same
-lengths for basic data objects (such as <tt>long double</tt>) and that
+lengths for basic data objects (such as <TT>long double</TT>) and that
 uses compatible run-time libraries.  On many systems, the various
 compilers are compatible and may be used interchangably.  There are
-exceptions; if you use the <tt>MPICH_FC</tt> environment variable or the
-<tt>\-fc=name</tt> command-line argument to override the choice of compiler
+exceptions; if you use the <TT>MPICH_FC</TT> environment variable or the
+<TT>\-fc=name</TT> command-line argument to override the choice of compiler
 and encounter problems, try reconfiguring MPICH with the new compiler
 and installing MPICH in a separate location.  See the installation manual
 for more details.
 <P>
 <H2>Examples</H2>
-To compile a single file <tt>foo.f</tt>, use
+To compile a single file <TT>foo.f</TT>, use
 <PRE>
    mpifort -c foo.f
 </PRE>
@@ -88,19 +91,19 @@ Combining compilation and linking in a single command
 is a convenient way to build simple programs.
 <P>
 <H2>Selecting a Profiling Library</H2>
-The <tt>\-profile=name</tt> argument allows you to specify an MPI profiling
-library to be used.  <tt>name</tt> can have two forms:
+The <TT>\-profile=name</TT> argument allows you to specify an MPI profiling
+library to be used.  <TT>name</TT> can have two forms:
 <P>
-<br>A library in the same directory as the MPI library
-<br>The name of a profile configuration file
-<br>
+<BR>A library in the same directory as the MPI library
+<BR>The name of a profile configuration file
+<BR>
 <P>
-If <tt>name</tt> is a library, then this library is included before the MPI
+If <TT>name</TT> is a library, then this library is included before the MPI
 library.  This allows the simple use of libraries that make use of the
 MPI profiling interface and that are installed in the same directory as
 the MPI library.
 <P>
-If <tt>name.conf</tt> is the name of a file in the sysconfdir directory, then this
+If <TT>name.conf</TT> is the name of a file in the sysconfdir directory, then this
 is read and may define the following variables:
 <DL>
 <DT><B>PROFILE_PRELIB </B><DD>Libraries (and paths) to include before the MPI library
@@ -108,9 +111,9 @@ is read and may define the following variables:
 <DT><B>PROFILE_POSTLIB </B><DD>Libraries to include after the MPI library
 
 <DT><B>PROFILE_INCPATHS </B><DD>C preprocessor arguments for any include files
-For example, to add <tt>/usr/local/myprof/include</tt> to the include path and
-the library <tt>libmyprof.a</tt> in <tt>/usr/local/myprof/lib</tt> to the link step,
-you could create the file <tt>myprof.conf</tt> with the lines
+For example, to add <TT>/usr/local/myprof/include</TT> to the include path and
+the library <TT>libmyprof.a</TT> in <TT>/usr/local/myprof/lib</TT> to the link step,
+you could create the file <TT>myprof.conf</TT> with the lines
 </DL>
 <P>
 <PRE>
@@ -120,10 +123,10 @@ you could create the file <tt>myprof.conf</tt> with the lines
 
 and place it in the sysconfdir directory (this directory is set at
 configure time when MPICH is built).  Then using the command-line
-argument <tt>\-profile=myprof</tt> will cause these
+argument <TT>\-profile=myprof</TT> will cause these
 definitions to be added to the relevant compile commands.
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  mpicc, mpicxx, mpifort, mpiexec
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/Constants.html b/linx64/mpi/mpich/share/doc/mpich/www3/Constants.html
index cdaf0aa8..45642d5e 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/Constants.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/Constants.html
@@ -10,9 +10,9 @@ Meaning of MPI's defined constants
 <H2>Data types</H2>
 Note that the Fortran types should only be used in Fortran programs,
 and the C types should only be used in C programs.  For example,
-it is in error to use <tt>MPI_INT</tt> for a Fortran INTEGER.
-Datatypes are of type <tt>MPI_Datatype</tt> in C, type <tt>INTEGER</tt> in Fortran,
-and <tt>Type(MPI_Datatype)</tt> in Fortran08
+it is in error to use <TT>MPI_INT</TT> for a Fortran INTEGER.
+Datatypes are of type <TT>MPI_Datatype</TT> in C, type <TT>INTEGER</TT> in Fortran,
+and <TT>Type(MPI_Datatype)</TT> in Fortran08
 <P>
 <H2>C datatypes</H2>
 MPI_CHAR - char
@@ -38,8 +38,8 @@ MPI_CHAR - char
 </DL>
 <DL><DT><B>MPI_LONG_LONG_INT </B> <DD> long long
 </DL>
-<DL><DT><B>MPI_LONG_LONG </B> <DD> synonyn for <tt>MPI_LONG_LONG_INT
-</tt>
+<DL><DT><B>MPI_LONG_LONG </B> <DD> synonyn for <TT>MPI_LONG_LONG_INT
+</TT>
 </DL>
 <DL><DT><B>MPI_UNSIGNED_LONG_LONG </B> <DD> unsigned long long
 </DL>
@@ -78,103 +78,103 @@ MPI_CHAR - char
 </DL>
 <P>
 <P>
-The following are datatypes for the MPI functions <tt>MPI_MAXLOC</tt> and
-<tt>MPI_MINLOC</tt>.
-MPI_FLOAT_INT - <tt>struct { float, int }
-</tt>
-<DL><DT><B>MPI_LONG_INT  </B> <DD> <tt>struct { long, int }
-</tt>
+The following are datatypes for the MPI functions <TT>MPI_MAXLOC</TT> and
+<TT>MPI_MINLOC</TT>.
+MPI_FLOAT_INT - <TT>struct { float, int }
+</TT>
+<DL><DT><B>MPI_LONG_INT  </B> <DD> <TT>struct { long, int }
+</TT>
 </DL>
-<DL><DT><B>MPI_DOUBLE_INT </B> <DD> <tt>struct { double, int }
-</tt>
+<DL><DT><B>MPI_DOUBLE_INT </B> <DD> <TT>struct { double, int }
+</TT>
 </DL>
-<DL><DT><B>MPI_SHORT_INT  </B> <DD> <tt>struct { short, int }
-</tt>
+<DL><DT><B>MPI_SHORT_INT  </B> <DD> <TT>struct { short, int }
+</TT>
 </DL>
-<DL><DT><B>MPI_2INT       </B> <DD> <tt>struct { int, int }
-</tt>
+<DL><DT><B>MPI_2INT       </B> <DD> <TT>struct { int, int }
+</TT>
 </DL>
-<DL><DT><B>MPI_LONG_DOUBLE_INT </B> <DD> <tt>struct { long double, int }</tt>; this
-is an <em>optional</em> type, and may be set to <tt>MPI_DATATYPE_NULL
-</tt>
+<DL><DT><B>MPI_LONG_DOUBLE_INT </B> <DD> <TT>struct { long double, int }</TT>; this
+is an <EM>optional</EM> type, and may be set to <TT>MPI_DATATYPE_NULL
+</TT>
 </DL>
 </DL>
 <P>
 <P>
 Special datatypes for C and Fortran
-MPI_PACKED - For <tt>MPI_Pack</tt> and <tt>MPI_Unpack
-</tt>
-<DL><DT><B>MPI_UB </B> <DD> For <tt>MPI_Type_struct</tt>; an upper-bound indicator.  Removed in MPI 3
+MPI_PACKED - For <TT>MPI_Pack</TT> and <TT>MPI_Unpack
+</TT>
+<DL><DT><B>MPI_UB </B> <DD> For <TT>MPI_Type_struct</TT>; an upper-bound indicator.  Removed in MPI 3
 </DL>
-<DL><DT><B>MPI_LB </B> <DD> For <tt>MPI_Type_struct</tt>; a lower-bound indicator. Removed in MPI 3
+<DL><DT><B>MPI_LB </B> <DD> For <TT>MPI_Type_struct</TT>; a lower-bound indicator. Removed in MPI 3
 </DL>
 </DL>
 <P>
 <H2>Fortran datatypes</H2>
-MPI_REAL - <tt>REAL
-</tt>
-<DL><DT><B>MPI_INTEGER </B> <DD> <tt>INTEGER
-</tt>
+MPI_REAL - <TT>REAL
+</TT>
+<DL><DT><B>MPI_INTEGER </B> <DD> <TT>INTEGER
+</TT>
 </DL>
-<DL><DT><B>MPI_LOGICAL </B> <DD> <tt>LOGICAL
-</tt>
+<DL><DT><B>MPI_LOGICAL </B> <DD> <TT>LOGICAL
+</TT>
 </DL>
-<DL><DT><B>MPI_DOUBLE_PRECISION </B> <DD> <tt>DOUBLE PRECISION
-</tt>
+<DL><DT><B>MPI_DOUBLE_PRECISION </B> <DD> <TT>DOUBLE PRECISION
+</TT>
 </DL>
-<DL><DT><B>MPI_COMPLEX </B> <DD> <tt>COMPLEX
-</tt>
+<DL><DT><B>MPI_COMPLEX </B> <DD> <TT>COMPLEX
+</TT>
 </DL>
-<DL><DT><B>MPI_DOUBLE_COMPLEX </B> <DD> <tt>complex*16</tt> (or <tt>complex*32</tt>) where supported.
+<DL><DT><B>MPI_DOUBLE_COMPLEX </B> <DD> <TT>complex*16</TT> (or <TT>complex*32</TT>) where supported.
 </DL>
 </DL>
 <P>
 The following datatypes are optional
-MPI_INTEGER1  - <tt>integer*1</tt> if supported
-<DL><DT><B>MPI_INTEGER2  </B> <DD> <tt>integer*2</tt> if supported
+MPI_INTEGER1  - <TT>integer*1</TT> if supported
+<DL><DT><B>MPI_INTEGER2  </B> <DD> <TT>integer*2</TT> if supported
 </DL>
-<DL><DT><B>MPI_INTEGER4  </B> <DD> <tt>integer*4</tt> if supported
+<DL><DT><B>MPI_INTEGER4  </B> <DD> <TT>integer*4</TT> if supported
 </DL>
-<DL><DT><B>MPI_INTEGER8  </B> <DD> <tt>integer*8</tt> if supported
+<DL><DT><B>MPI_INTEGER8  </B> <DD> <TT>integer*8</TT> if supported
 </DL>
-<DL><DT><B>MPI_INTEGER16 </B> <DD> <tt>integer*16</tt> if supported
+<DL><DT><B>MPI_INTEGER16 </B> <DD> <TT>integer*16</TT> if supported
 </DL>
-<DL><DT><B>MPI_REAL4     </B> <DD> <tt>real*4</tt> if supported
+<DL><DT><B>MPI_REAL4     </B> <DD> <TT>real*4</TT> if supported
 </DL>
-<DL><DT><B>MPI_REAL8     </B> <DD> <tt>real*8</tt> if supported
+<DL><DT><B>MPI_REAL8     </B> <DD> <TT>real*8</TT> if supported
 </DL>
 </DL>
-<DL><DT><B>MPI_REAL16    </B> <DD> <tt>real*16</tt> if supported
+<DL><DT><B>MPI_REAL16    </B> <DD> <TT>real*16</TT> if supported
 </DL>
-<DL><DT><B>MPI_COMPLEX8  </B> <DD> <tt>complex*8</tt> if supported
+<DL><DT><B>MPI_COMPLEX8  </B> <DD> <TT>complex*8</TT> if supported
 </DL>
-<DL><DT><B>MPI_COMPLEX16 </B> <DD> <tt>complex*16</tt> if supported
+<DL><DT><B>MPI_COMPLEX16 </B> <DD> <TT>complex*16</TT> if supported
 </DL>
-<DL><DT><B>MPI_COMPLEX32 </B> <DD> <tt>complex*32</tt> if supported
+<DL><DT><B>MPI_COMPLEX32 </B> <DD> <TT>complex*32</TT> if supported
 </DL>
 </DL>
 <P>
-The following are datatypes for the MPI functions <tt>MPI_MAXLOC</tt> and
-<tt>MPI_MINLOC</tt>.  In Fortran, these datatype always consist of
+The following are datatypes for the MPI functions <TT>MPI_MAXLOC</TT> and
+<TT>MPI_MINLOC</TT>.  In Fortran, these datatype always consist of
 two elements of the same Fortran type.
-MPI_2INTEGER - <tt>INTEGER,INTEGER
-</tt>
-<DL><DT><B>MPI_2REAL    </B> <DD> <tt>REAL, REAL
-</tt>
+MPI_2INTEGER - <TT>INTEGER,INTEGER
+</TT>
+<DL><DT><B>MPI_2REAL    </B> <DD> <TT>REAL, REAL
+</TT>
 </DL>
-<DL><DT><B>MPI_2DOUBLE_PRECISION </B> <DD> <tt>DOUBLE PRECISION, DOUBLE PRECISION
-</tt>
+<DL><DT><B>MPI_2DOUBLE_PRECISION </B> <DD> <TT>DOUBLE PRECISION, DOUBLE PRECISION
+</TT>
 </DL>
 </DL>
 <P>
 MPI Datatypes for MPI Types
-MPI_AINT - Datatype for an <tt>MPI_Aint
-</tt>
-<DL><DT><B>MPI_OFFSET </B> <DD> Datatype for an <tt>MPI_Offset
-</tt>
+MPI_AINT - Datatype for an <TT>MPI_Aint
+</TT>
+<DL><DT><B>MPI_OFFSET </B> <DD> Datatype for an <TT>MPI_Offset
+</TT>
 </DL>
-<DL><DT><B>MPI_COUNT </B> <DD> Datatype for an <tt>MPI_Count
-</tt>
+<DL><DT><B>MPI_COUNT </B> <DD> Datatype for an <TT>MPI_Count
+</TT>
 </DL>
 </DL>
 <P>
@@ -221,19 +221,19 @@ MPI_COMBINER_NAMED            - a named predefined datatype
 <H2>MPI Datatype Type Classes</H2>
 MPI Type classes used with routines to return Fortran types with defined
 precision and range
-MPI_TYPECLASS_REAL    - <tt>REAL
-</tt>
-<DL><DT><B>MPI_TYPECLASS_INTEGER </B> <DD> <tt>INTEGER
-</tt>
+MPI_TYPECLASS_REAL    - <TT>REAL
+</TT>
+<DL><DT><B>MPI_TYPECLASS_INTEGER </B> <DD> <TT>INTEGER
+</TT>
 </DL>
-<DL><DT><B>MPI_TYPECLASS_COMPLEX </B> <DD> <tt>COMPLEX
-</tt>
+<DL><DT><B>MPI_TYPECLASS_COMPLEX </B> <DD> <TT>COMPLEX
+</TT>
 </DL>
 </DL>
 <P>
 <H2>MPI Darray and Subarray Values</H2>
-These values are used to create a datatype with the <tt>DARRAY</tt> and <tt>SUBARRAY
-</tt>constructors.
+These values are used to create a datatype with the <TT>DARRAY</TT> and <TT>SUBARRAY
+</TT>constructors.
 MPI_ORDER_C              - Row-major order (as used by C)
 <DL><DT><B>MPI_ORDER_FORTRAN        </B> <DD> Column-major order (as used by Fortran)
 </DL>
@@ -248,8 +248,8 @@ MPI_ORDER_C              - Row-major order (as used by C)
 </DL>
 <P>
 <H2>Communicators</H2>
-Communicators are of type <tt>MPI_Comm</tt> in C, <tt>INTEGER</tt> in Fortran, and
-<tt>Type(MPI_Comm)</tt> in Fortran08
+Communicators are of type <TT>MPI_Comm</TT> in C, <TT>INTEGER</TT> in Fortran, and
+<TT>Type(MPI_Comm)</TT> in Fortran08
 MPI_COMM_WORLD - Contains all of the processes
 <DL><DT><B>MPI_COMM_SELF </B> <DD> Contains only the calling process
 </DL>
@@ -260,14 +260,14 @@ MPI_COMM_TYPE_SHARED - All processes that can share memory are grouped into
 the same communicator.
 <P>
 <H2>Groups</H2>
-Groups are of type <tt>MPI_Group</tt> in C, <tt>INTEGER</tt> in Fortran,
-and <tt>Type(MPI_Group)</tt> in Fortran08
+Groups are of type <TT>MPI_Group</TT> in C, <TT>INTEGER</TT> in Fortran,
+and <TT>Type(MPI_Group)</TT> in Fortran08
 <P>
 MPI_GROUP_EMPTY - A group containing no members.
 <P>
 <H2>Results of the compare operations on groups and communicators</H2>
 MPI_IDENT - Identical
-<DL><DT><B>MPI_CONGRUENT  </B> <DD> (only for <tt>MPI_COMM_COMPARE</tt>) The groups are identical
+<DL><DT><B>MPI_CONGRUENT  </B> <DD> (only for <TT>MPI_COMM_COMPARE</TT>) The groups are identical
 </DL>
 <DL><DT><B>MPI_SIMILAR </B> <DD> Same members, but in a different order
 </DL>
@@ -277,9 +277,9 @@ MPI_IDENT - Identical
 <P>
 <P>
 <H2>Collective operations</H2>
-The collective combination operations (e.g., <tt>MPI_REDUCE</tt>, <tt>MPI_ALLREDUCE</tt>,
-<tt>MPI_REDUCE_SCATTER</tt>, and <tt>MPI_SCAN</tt>) take a combination operation.
-This operation is of type <tt>MPI_Op</tt> in C and of type <tt>INTEGER</tt> in Fortran.
+The collective combination operations (e.g., <TT>MPI_REDUCE</TT>, <TT>MPI_ALLREDUCE</TT>,
+<TT>MPI_REDUCE_SCATTER</TT>, and <TT>MPI_SCAN</TT>) take a combination operation.
+This operation is of type <TT>MPI_Op</TT> in C and of type <TT>INTEGER</TT> in Fortran.
 The predefined operations are
 <P>
 MPI_MAX - return the maximum
@@ -315,24 +315,24 @@ the first is found)
 <P>
 <H2>Notes on collective operations</H2>
 <P>
-The reduction functions (<tt>MPI_Op</tt>) do not return an error value.  As a result,
-if the functions detect an error, all they can do is either call <tt>MPI_Abort
-</tt>or silently skip the problem.  Thus, if you change the error handler from
-<tt>MPI_ERRORS_ARE_FATAL</tt> to something else, for example, <tt>MPI_ERRORS_RETURN</tt>,
+The reduction functions (<TT>MPI_Op</TT>) do not return an error value.  As a result,
+if the functions detect an error, all they can do is either call <TT>MPI_Abort
+</TT>or silently skip the problem.  Thus, if you change the error handler from
+<TT>MPI_ERRORS_ARE_FATAL</TT> to something else, for example, <TT>MPI_ERRORS_RETURN</TT>,
 then no error may be indicated.
 <P>
 The reason for this is the performance problems in ensuring that
 all collective routines return the same error value.
 <P>
 Note that not all datatypes are valid for these functions.  For example,
-<tt>MPI_COMPLEX</tt> is not valid for <tt>MPI_MAX</tt> and <tt>MPI_MIN</tt>.  In addition, the MPI
-1.1 standard did not include the C types <tt>MPI_CHAR</tt> and <tt>MPI_UNSIGNED_CHAR
-</tt>among the lists of arithmetic types for operations like <tt>MPI_SUM</tt>.  However,
-since the C type <tt>char</tt> is an integer type (like <tt>short</tt>), it should have been
-included.  The MPI Forum will probably include <tt>char</tt> and <tt>unsigned char
-</tt>as a clarification to MPI 1.1; until then, users are advised that MPI
-implementations may not accept <tt>MPI_CHAR</tt> and <tt>MPI_UNSIGNED_CHAR</tt> as valid
-datatypes for <tt>MPI_SUM</tt>, <tt>MPI_PROD</tt>, etc.  MPICH does allow these datatypes.
+<TT>MPI_COMPLEX</TT> is not valid for <TT>MPI_MAX</TT> and <TT>MPI_MIN</TT>.  In addition, the MPI
+1.1 standard did not include the C types <TT>MPI_CHAR</TT> and <TT>MPI_UNSIGNED_CHAR
+</TT>among the lists of arithmetic types for operations like <TT>MPI_SUM</TT>.  However,
+since the C type <TT>char</TT> is an integer type (like <TT>short</TT>), it should have been
+included.  The MPI Forum will probably include <TT>char</TT> and <TT>unsigned char
+</TT>as a clarification to MPI 1.1; until then, users are advised that MPI
+implementations may not accept <TT>MPI_CHAR</TT> and <TT>MPI_UNSIGNED_CHAR</TT> as valid
+datatypes for <TT>MPI_SUM</TT>, <TT>MPI_PROD</TT>, etc.  MPICH does allow these datatypes.
 <P>
 <H2>Permanent key values</H2>
 These are the same in C and Fortran
@@ -342,7 +342,7 @@ MPI_TAG_UB - Largest tag value
 </DL>
 <DL><DT><B>MPI_IO </B> <DD> Rank of process that can do I/O
 </DL>
-<DL><DT><B>MPI_WTIME_IS_GLOBAL </B> <DD> Has value 1 if <tt>MPI_WTIME</tt> is globally synchronized.
+<DL><DT><B>MPI_WTIME_IS_GLOBAL </B> <DD> Has value 1 if <TT>MPI_WTIME</TT> is globally synchronized.
 </DL>
 <DL><DT><B>MPI_UNIVERSE_SIZE </B> <DD> Number of available processes.  See the standard for
 a description of limitations on this value
@@ -350,7 +350,7 @@ a description of limitations on this value
 <DL><DT><B>MPI_LASTUSEDCODE </B> <DD> Last used MPI error code (check - code or class?)
 </DL>
 <DL><DT><B>MPI_APPNUM </B> <DD> Application number, starting from 0.  See the standard for
-<tt>MPI_COMM_SPAWN_MULTIPLE</tt> and <tt>mpiexec</tt> for details
+<TT>MPI_COMM_SPAWN_MULTIPLE</TT> and <TT>mpiexec</TT> for details
 </DL>
 </DL>
 <P>
@@ -390,14 +390,14 @@ MPI_COMM_NULL          - Null communicator
 <P>
 <H2>Predefined Constants</H2>
 MPI_MAX_PROCESSOR_NAME         - Maximum length of name returned by
-<tt>MPI_GET_PROCESSOR_NAME
-</tt>
+<TT>MPI_GET_PROCESSOR_NAME
+</TT>
 <DL><DT><B>MPI_MAX_ERROR_STRING           </B> <DD> Maximum length of string return by
-<tt>MPI_ERROR_STRING
-</tt>
+<TT>MPI_ERROR_STRING
+</TT>
 </DL>
 <DL><DT><B>MPI_MAX_LIBRARY_VERSION_STRING </B> <DD> Maximum length of string returned by
-<tt>MPI_GET_LIBRARY_VERSION_STRING</tt>???
+<TT>MPI_GET_LIBRARY_VERSION_STRING</TT>???
 </DL>
 <DL><DT><B>MPI_MAX_PORT_NAME              </B> <DD> Maximum length of a port
 </DL>
@@ -415,8 +415,8 @@ undefined or unknown integer value
 <DL><DT><B>MPI_KEYVAL_INVALID             </B> <DD> Special keyval that may be used to detect
 uninitialized keyvals.
 </DL>
-<DL><DT><B>MPI_BSEND_OVERHEAD             </B> <DD> Add this to the size of a <tt>MPI_BSEND
-</tt>buffer for each outstanding message
+<DL><DT><B>MPI_BSEND_OVERHEAD             </B> <DD> Add this to the size of a <TT>MPI_BSEND
+</TT>buffer for each outstanding message
 </DL>
 <DL><DT><B>MPI_PROC_NULL                  </B> <DD> This rank may be used to send or receive from no-one.
 </DL>
@@ -474,17 +474,17 @@ the end of the file
 <P>
 <H2>File Displacement</H2>
 MPI_DISPLACEMENT_CURRENT - Use with files opened with mode
-<tt>MPI_MODE_SEQUENTIAL</tt> in calls to <tt>MPI_FILE_SET_VIEW
-</tt>
+<TT>MPI_MODE_SEQUENTIAL</TT> in calls to <TT>MPI_FILE_SET_VIEW
+</TT>
 <P>
 <H2>File Positioning</H2>
-MPI_SEEK_SET             - Set the pointer to <tt>offset
-</tt>
-<DL><DT><B>MPI_SEEK_CUR             </B> <DD> Set the pointer to the current position plus <tt>offset
-</tt>
+MPI_SEEK_SET             - Set the pointer to <TT>offset
+</TT>
+<DL><DT><B>MPI_SEEK_CUR             </B> <DD> Set the pointer to the current position plus <TT>offset
+</TT>
 </DL>
-<DL><DT><B>MPI_SEEK_END             </B> <DD> Set the pointer to the end of the file plus <tt>offset
-</tt>
+<DL><DT><B>MPI_SEEK_END             </B> <DD> Set the pointer to the end of the file plus <TT>offset
+</TT>
 </DL>
 </DL>
 <P>
@@ -548,19 +548,19 @@ calls
 MPI_INFO_ENV - Contains the execution environment
 <P>
 <H2>MPI Status</H2>
-The <tt>MPI_Status</tt> datatype is a structure in C.  The three elements for use
+The <TT>MPI_Status</TT> datatype is a structure in C.  The three elements for use
 by programmers are
 MPI_SOURCE - Who sent the message
 <DL><DT><B>MPI_TAG </B> <DD> What tag the message was sent with
 </DL>
 <DL><DT><B>MPI_ERROR </B> <DD> Any error return (only when the error returned by the routine
-has error class <tt>MPI_ERR_IN_STATUS</tt>)
+has error class <TT>MPI_ERR_IN_STATUS</TT>)
 </DL>
 </DL>
 <P>
-MPI_STATUS_IGNORE   - Ignore a single <tt>MPI_Status</tt> argument
-<DL><DT><B>MPI_STATUSES_IGNORE </B> <DD> Ignore an array of <tt>MPI_Status
-</tt>
+MPI_STATUS_IGNORE   - Ignore a single <TT>MPI_Status</TT> argument
+<DL><DT><B>MPI_STATUSES_IGNORE </B> <DD> Ignore an array of <TT>MPI_Status
+</TT>
 </DL>
 </DL>
 <P>
@@ -671,14 +671,14 @@ MPI_Aint   - C type that holds any valid address.
 <DL><DT><B>MPI_Offset </B> <DD> C type that holds any valid file offset.
 </DL>
 <DL><DT><B>MPI_Handler_function </B> <DD> C function for handling errors (see
-<tt>MPI_Errhandler_create</tt>) .
+<TT>MPI_Errhandler_create</TT>) .
 </DL>
 <DL><DT><B>MPI_User_function </B> <DD> C function to combine values (see collective operations
-and <tt>MPI_Op_create</tt>)
+and <TT>MPI_Op_create</TT>)
 </DL>
-<DL><DT><B>MPI_Copy_function </B> <DD> Function to copy attributes (see <tt>MPI_Keyval_create</tt>)
+<DL><DT><B>MPI_Copy_function </B> <DD> Function to copy attributes (see <TT>MPI_Keyval_create</TT>)
 </DL>
-<DL><DT><B>MPI_Delete_function </B> <DD> Function to delete attributes (see <tt>MPI_Keyval_create</tt>)
+<DL><DT><B>MPI_Delete_function </B> <DD> Function to delete attributes (see <TT>MPI_Keyval_create</TT>)
 </DL>
 <DL><DT><B>MPI_ERRORS_ARE_FATAL </B> <DD> Error handler that forces exit on error
 </DL>
@@ -758,8 +758,8 @@ MPI_SUCCESS               - Successful return code
 <DL><DT><B>MPI_ERR_ACCESS            </B> <DD> Permission denied
 </DL>
 <DL><DT><B>MPI_ERR_AMODE             </B> <DD> Error related to the amode passed to
-<tt>MPI_FILE_OPEN
-</tt>
+<TT>MPI_FILE_OPEN
+</TT>
 </DL>
 <DL><DT><B>MPI_ERR_BAD_FILE          </B> <DD> Invalid file name (e.g., path name too long)
 </DL>
@@ -768,8 +768,8 @@ conversion function
 </DL>
 <DL><DT><B>MPI_ERR_DUP_DATAREP       </B> <DD> Conversion functions could not be registered
 because a data representation identifier that was already defined was passed
-to <tt>MPI_REGISTER_DATAREP
-</tt>
+to <TT>MPI_REGISTER_DATAREP
+</TT>
 </DL>
 <DL><DT><B>MPI_ERR_FILE_EXISTS       </B> <DD> File exists
 </DL>
@@ -787,8 +787,8 @@ the file is currently open by some process
 <DL><DT><B>MPI_ERR_READ_ONLY         </B> <DD> Read-only file or file system
 </DL>
 <DL><DT><B>MPI_ERR_UNSUPPORTED_DATAREP </B> <DD> Unsupported datarep passed to
-<tt>MPI_FILE_SET_VIEW
-</tt>
+<TT>MPI_FILE_SET_VIEW
+</TT>
 </DL>
 <DL><DT><B>MPI_ERR_INFO              </B> <DD> Invalid info argument
 </DL>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPIR_Type_commit.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPIR_Type_commit.html
new file mode 100644
index 00000000..7e50e381
--- /dev/null
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPIR_Type_commit.html
@@ -0,0 +1,18 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML3.2 EN">
+<HTML>
+<HEAD>
+<META NAME="GENERATOR" CONTENT="DOCTEXT">
+<TITLE>MPIR_Type_commit</TITLE>
+</HEAD>
+<BODY BGCOLOR="FFFFFF">
+<A NAME="MPIR_Type_commit"><H1>MPIR_Type_commit</H1></A>
+nput Parameters: . datatype_p - pointer to MPI datatype 
+<H2>Synopsis</H2>
+<PRE>
+int MPIR_Type_commit(MPI_Datatype * datatype_p)
+</PRE>
+<H2>Output Parameters</H2>
+<P>
+<H2>Return Value</H2>
+0 on success, -1 on failure.
+</BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPIR_Type_contiguous.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPIR_Type_contiguous.html
new file mode 100644
index 00000000..e457dcc3
--- /dev/null
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPIR_Type_contiguous.html
@@ -0,0 +1,27 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML3.2 EN">
+<HTML>
+<HEAD>
+<META NAME="GENERATOR" CONTENT="DOCTEXT">
+<TITLE>MPIR_Type_contiguous</TITLE>
+</HEAD>
+<BODY BGCOLOR="FFFFFF">
+<A NAME="MPIR_Type_contiguous"><H1>MPIR_Type_contiguous</H1></A>
+create a contiguous datatype 
+<H2>Synopsis</H2>
+<PRE>
+int MPIR_Type_contiguous(int count, MPI_Datatype oldtype, MPI_Datatype * newtype)
+</PRE>
+<H2>Input Parameters</H2>
+<DL>
+<DT><B>count </B><DD>number of elements in the contiguous block
+
+<DT><B>oldtype </B><DD>type (using handle) of datatype on which vector is based
+</DL>
+<P>
+<H2>Output Parameters</H2>
+<DL><DT><B>newtype </B> <DD> handle of new contiguous datatype
+</DL>
+<P>
+<H2>Return Value</H2>
+MPI_SUCCESS on success, MPI error code on failure.
+</BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPIR_Type_dup.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPIR_Type_dup.html
new file mode 100644
index 00000000..100f2b14
--- /dev/null
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPIR_Type_dup.html
@@ -0,0 +1,29 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML3.2 EN">
+<HTML>
+<HEAD>
+<META NAME="GENERATOR" CONTENT="DOCTEXT">
+<TITLE>MPIR_Type_dup</TITLE>
+</HEAD>
+<BODY BGCOLOR="FFFFFF">
+<A NAME="MPIR_Type_dup"><H1>MPIR_Type_dup</H1></A>
+create a copy of a datatype 
+<H2>Synopsis</H2>
+<PRE>
+#undef FUNCNAME
+#define FUNCNAME MPIR_Type_dup
+#undef FCNAME
+#define FCNAME MPL_QUOTE(FUNCNAME)
+int MPIR_Type_dup(MPI_Datatype oldtype, MPI_Datatype * newtype)
+</PRE>
+<H2>Input Parameters</H2>
+<DL><DT><B>oldtype </B> <DD> handle of original datatype
+</DL>
+</DL>
+<P>
+<H2>Output Parameters</H2>
+<DL><DT><B>newtype </B> <DD> handle of newly created copy of datatype
+</DL>
+<P>
+<H2>Return Value</H2>
+0 on success, MPI error code on failure.
+</BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPIR_Type_get_contents.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPIR_Type_get_contents.html
new file mode 100644
index 00000000..cda637cc
--- /dev/null
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPIR_Type_get_contents.html
@@ -0,0 +1,39 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML3.2 EN">
+<HTML>
+<HEAD>
+<META NAME="GENERATOR" CONTENT="DOCTEXT">
+<TITLE>MPIR_Type_get_contents</TITLE>
+</HEAD>
+<BODY BGCOLOR="FFFFFF">
+<A NAME="MPIR_Type_get_contents"><H1>MPIR_Type_get_contents</H1></A>
+get content information from datatype 
+<H2>Synopsis</H2>
+<PRE>
+int MPIR_Type_get_contents(MPI_Datatype datatype,
+                           int max_integers,
+                           int max_addresses,
+                           int max_datatypes,
+                           int array_of_integers[],
+                           MPI_Aint array_of_addresses[], MPI_Datatype array_of_datatypes[])
+</PRE>
+<H2>Input Parameters</H2>
+<DL>
+<DT><B>datatype </B><DD>MPI datatype
+
+<DT><B>max_integers </B><DD>size of array_of_integers
+
+<DT><B>max_addresses </B><DD>size of array_of_addresses
+
+<DT><B>max_datatypes </B><DD>size of array_of_datatypes
+</DL>
+<P>
+<H2>Output Parameters</H2>
+<DL>
+<DT><B>array_of_integers </B><DD>integers used in creating type
+
+<DT><B>array_of_addresses </B><DD>MPI_Aints used in creating type
+
+<DT><B>array_of_datatypes </B><DD>MPI_Datatypes used in creating type
+</DL>
+<P>
+</BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPIR_Type_indexed.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPIR_Type_indexed.html
new file mode 100644
index 00000000..75c51e8d
--- /dev/null
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPIR_Type_indexed.html
@@ -0,0 +1,39 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML3.2 EN">
+<HTML>
+<HEAD>
+<META NAME="GENERATOR" CONTENT="DOCTEXT">
+<TITLE>MPIR_Type_indexed</TITLE>
+</HEAD>
+<BODY BGCOLOR="FFFFFF">
+<A NAME="MPIR_Type_indexed"><H1>MPIR_Type_indexed</H1></A>
+create an indexed datatype 
+<H2>Synopsis</H2>
+<PRE>
+int MPIR_Type_indexed(int count,
+                      const int *blocklength_array,
+                      const void *displacement_array,
+                      int dispinbytes, MPI_Datatype oldtype, MPI_Datatype * newtype)
+</PRE>
+<H2>Input Parameters</H2>
+<DL>
+<DT><B>count </B><DD>number of blocks in type
+
+<DT><B>blocklength_array </B><DD>number of elements in each block
+
+<DT><B>displacement_array </B><DD>offsets of blocks from start of type (see next
+parameter for units)
+
+<DT><B>dispinbytes </B><DD>if nonzero, then displacements are in bytes (the
+displacement_array is an array of ints), otherwise they in terms of
+extent of oldtype (the displacement_array is an array of MPI_Aints)
+
+<DT><B>oldtype </B><DD>type (using handle) of datatype on which new type is based
+</DL>
+<P>
+<H2>Output Parameters</H2>
+<DL><DT><B>newtype </B> <DD> handle of new indexed datatype
+</DL>
+<P>
+<H2>Return Value</H2>
+0 on success, -1 on failure.
+</BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPIR_Type_struct.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPIR_Type_struct.html
new file mode 100644
index 00000000..f2b533e7
--- /dev/null
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPIR_Type_struct.html
@@ -0,0 +1,38 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML3.2 EN">
+<HTML>
+<HEAD>
+<META NAME="GENERATOR" CONTENT="DOCTEXT">
+<TITLE>MPIR_Type_struct</TITLE>
+</HEAD>
+<BODY BGCOLOR="FFFFFF">
+<A NAME="MPIR_Type_struct"><H1>MPIR_Type_struct</H1></A>
+create a struct datatype 
+<H2>Synopsis</H2>
+<PRE>
+#undef FUNCNAME
+#define FUNCNAME MPIR_Type_struct
+#undef FCNAME
+#define FCNAME MPL_QUOTE(FUNCNAME)
+int MPIR_Type_struct(int count,
+                     const int *blocklength_array,
+                     const MPI_Aint * displacement_array,
+                     const MPI_Datatype * oldtype_array, MPI_Datatype * newtype)
+</PRE>
+<H2>Input Parameters</H2>
+<DL>
+<DT><B>count </B><DD>number of blocks in vector
+
+<DT><B>blocklength_array </B><DD>number of elements in each block
+
+<DT><B>displacement_array </B><DD>offsets of blocks from start of type in bytes
+
+<DT><B>oldtype_array </B><DD>types (using handle) of datatypes on which vector is based
+</DL>
+<P>
+<H2>Output Parameters</H2>
+<DL><DT><B>newtype </B> <DD> handle of new struct datatype
+</DL>
+<P>
+<H2>Return Value</H2>
+MPI_SUCCESS on success, MPI errno on failure.
+</BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPIR_Type_vector.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPIR_Type_vector.html
new file mode 100644
index 00000000..fb27532c
--- /dev/null
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPIR_Type_vector.html
@@ -0,0 +1,38 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML3.2 EN">
+<HTML>
+<HEAD>
+<META NAME="GENERATOR" CONTENT="DOCTEXT">
+<TITLE>MPIR_Type_vector</TITLE>
+</HEAD>
+<BODY BGCOLOR="FFFFFF">
+<A NAME="MPIR_Type_vector"><H1>MPIR_Type_vector</H1></A>
+create a vector datatype 
+<H2>Synopsis</H2>
+<PRE>
+int MPIR_Type_vector(int count,
+                     int blocklength,
+                     MPI_Aint stride,
+                     int strideinbytes, MPI_Datatype oldtype, MPI_Datatype * newtype)
+</PRE>
+<H2>Input Parameters</H2>
+<DL>
+<DT><B>count </B><DD>number of blocks in vector
+
+<DT><B>blocklength </B><DD>number of elements in each block
+
+<DT><B>stride </B><DD>distance from beginning of one block to the next (see next
+parameter for units)
+
+<DT><B>strideinbytes </B><DD>if nonzero, then stride is in bytes, otherwise stride
+is in terms of extent of oldtype
+
+<DT><B>oldtype </B><DD>type (using handle) of datatype on which vector is based
+</DL>
+<P>
+<H2>Output Parameters</H2>
+<DL><DT><B>newtype </B> <DD> handle of new vector datatype
+</DL>
+<P>
+<H2>Return Value</H2>
+0 on success, MPI error code on failure.
+</BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPIX_Comm_agree.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPIX_Comm_agree.html
index ad413daa..e508d59f 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPIX_Comm_agree.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPIX_Comm_agree.html
@@ -24,38 +24,38 @@ int MPIX_Comm_agree(MPI_Comm comm, int *flag)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <P>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPIX_Comm_failure_ack.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPIX_Comm_failure_ack.html
index b8ad2cad..30d17451 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPIX_Comm_failure_ack.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPIX_Comm_failure_ack.html
@@ -9,53 +9,53 @@
 Acknowledge the current group of failed processes 
 <H2>Synopsis</H2>
 <PRE>
-int MPIX_Comm_failure_ack( MPI_Comm comm )
+int MPIX_Comm_failure_ack(MPI_Comm comm)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>comm </B> <DD> Communicator (handle)
 </DL>
 <P>
 <H2>Notes</H2>
-Because MPI specifies that null objects (e.g., <tt>MPI_COMM_NULL</tt>) are invalid
-as input to MPI routines unless otherwise specified, using <tt>MPI_COMM_NULL
-</tt>as input to this routine is an error.
+Because MPI specifies that null objects (e.g., <TT>MPI_COMM_NULL</TT>) are invalid
+as input to MPI routines unless otherwise specified, using <TT>MPI_COMM_NULL
+</TT>as input to this routine is an error.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPIX_Comm_failure_get_acked.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPIX_Comm_failure_get_acked.html
index e80df47c..3617a7d1 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPIX_Comm_failure_get_acked.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPIX_Comm_failure_get_acked.html
@@ -9,7 +9,7 @@
 Get the group of acknowledged failures. 
 <H2>Synopsis</H2>
 <PRE>
-int MPIX_Comm_failure_get_acked( MPI_Comm comm, MPI_Group *failedgrp )
+int MPIX_Comm_failure_get_acked(MPI_Comm comm, MPI_Group * failedgrp)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>comm </B> <DD> Communicator (handle)
@@ -20,46 +20,46 @@ int MPIX_Comm_failure_get_acked( MPI_Comm comm, MPI_Group *failedgrp )
 </DL>
 <P>
 <H2>Notes</H2>
-Because MPI specifies that null objects (e.g., <tt>MPI_COMM_NULL</tt>) are invalid
-as input to MPI routines unless otherwise specified, using <tt>MPI_COMM_NULL
-</tt>as input to this routine is an error.
+Because MPI specifies that null objects (e.g., <TT>MPI_COMM_NULL</TT>) are invalid
+as input to MPI routines unless otherwise specified, using <TT>MPI_COMM_NULL
+</TT>as input to this routine is an error.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPIX_Comm_revoke.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPIX_Comm_revoke.html
index bc568e73..1aab166d 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPIX_Comm_revoke.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPIX_Comm_revoke.html
@@ -16,32 +16,32 @@ int MPIX_Comm_revoke(MPI_Comm comm)
 </DL>
 <P>
 <H2>Notes</H2>
-Asynchronously notifies all MPI processes associated with the communicator <tt>comm</tt>.
+Asynchronously notifies all MPI processes associated with the communicator <TT>comm</TT>.
 This will be manifest by returning the MPIX_ERR_REVOKED during a subsequent MPI
 call.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPIX_Comm_shrink.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPIX_Comm_shrink.html
index 68a63fa8..1af75a68 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPIX_Comm_shrink.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPIX_Comm_shrink.html
@@ -9,7 +9,7 @@
 Creates a new communitor from an existing communicator while excluding failed processes 
 <H2>Synopsis</H2>
 <PRE>
-int MPIX_Comm_shrink(MPI_Comm comm, MPI_Comm *newcomm)
+int MPIX_Comm_shrink(MPI_Comm comm, MPI_Comm * newcomm)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>comm </B> <DD> communicator (handle)
@@ -24,38 +24,38 @@ int MPIX_Comm_shrink(MPI_Comm comm, MPI_Comm *newcomm)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <P>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Abort.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Abort.html
index d8a58215..70337d1d 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Abort.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Abort.html
@@ -13,14 +13,14 @@ int MPI_Abort(MPI_Comm comm, int errorcode)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>comm </B><DD>communicator of tasks to abort 
+<DT><B>comm </B><DD>communicator of tasks to abort
 
-<DT><B>errorcode </B><DD>error code to return to invoking environment 
+<DT><B>errorcode </B><DD>error code to return to invoking environment
 </DL>
 <P>
 <H2>Notes</H2>
-Terminates all MPI processes associated with the communicator <tt>comm</tt>; in
-most systems (all to date), terminates <em>all</em> processes.
+Terminates all MPI processes associated with the communicator <TT>comm</TT>; in
+most systems (all to date), terminates <EM>all</EM> processes.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
@@ -31,35 +31,35 @@ not be used from within a signal handler.
 The MPI standard defined a thread-safe interface but this does not
 mean that all routines may be called without any thread locks.  For
 example, two threads must not attempt to change the contents of the
-same <tt>MPI_Info</tt> object concurrently.  The user is responsible in this
+same <TT>MPI_Info</TT> object concurrently.  The user is responsible in this
 case for using some mechanism, such as thread locks, to ensure that
 only one thread at a time makes use of this routine.
-Because the <tt>MPI_Abort</tt> routine is intended to ensure that an MPI
+Because the <TT>MPI_Abort</TT> routine is intended to ensure that an MPI
 process (and possibly an entire job), it cannot wait for a thread to
 release a lock or other mechanism for atomic access.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Accumulate.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Accumulate.html
index f3b564b7..b0cbc0f7 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Accumulate.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Accumulate.html
@@ -6,85 +6,85 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Accumulate"><H1>MPI_Accumulate</H1></A>
-Accumulate data into the target process using remote  memory access  
+Accumulate data into the target process using remote memory access 
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Accumulate(const void *origin_addr, int origin_count, MPI_Datatype
                    origin_datatype, int target_rank, MPI_Aint
                    target_disp, int target_count, MPI_Datatype
-                   target_datatype, MPI_Op op, MPI_Win win) 
+                   target_datatype, MPI_Op op, MPI_Win win)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>origin_addr </B><DD>initial address of buffer (choice) 
+<DT><B>origin_addr </B><DD>initial address of buffer (choice)
 
-<DT><B>origin_count </B><DD>number of entries in buffer (nonnegative integer) 
+<DT><B>origin_count </B><DD>number of entries in buffer (nonnegative integer)
 
-<DT><B>origin_datatype </B><DD>datatype of each buffer entry (handle) 
+<DT><B>origin_datatype </B><DD>datatype of each buffer entry (handle)
 
-<DT><B>target_rank </B><DD>rank of target (nonnegative integer) 
+<DT><B>target_rank </B><DD>rank of target (nonnegative integer)
 
-<DT><B>target_disp </B><DD>displacement from start of window to beginning of target 
-buffer (nonnegative integer)  
+<DT><B>target_disp </B><DD>displacement from start of window to beginning of target
+buffer (nonnegative integer)
 
-<DT><B>target_count </B><DD>number of entries in target buffer (nonnegative integer) 
+<DT><B>target_count </B><DD>number of entries in target buffer (nonnegative integer)
 
-<DT><B>target_datatype </B><DD>datatype of each entry in target buffer (handle) 
+<DT><B>target_datatype </B><DD>datatype of each entry in target buffer (handle)
 
-<DT><B>op </B><DD>predefined reduce operation (handle) 
+<DT><B>op </B><DD>predefined reduce operation (handle)
 
-<DT><B>win </B><DD>window object (handle) 
+<DT><B>win </B><DD>window object (handle)
 </DL>
 <P>
 <H2>Notes</H2>
 The basic components of both the origin and target datatype must be the same
-predefined datatype (e.g., all <tt>MPI_INT</tt> or all <tt>MPI_DOUBLE_PRECISION</tt>).
+predefined datatype (e.g., all <TT>MPI_INT</TT> or all <TT>MPI_DOUBLE_PRECISION</TT>).
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Raccumulate
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Add_error_class.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Add_error_class.html
index 43b439a0..bd255739 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Add_error_class.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Add_error_class.html
@@ -20,37 +20,37 @@ int MPI_Add_error_class(int *errorclass)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Add_error_code.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Add_error_code.html
index ae809889..cb617ffd 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Add_error_code.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Add_error_code.html
@@ -24,37 +24,37 @@ int MPI_Add_error_code(int errorclass, int *errorcode)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Add_error_string.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Add_error_string.html
index 577bd882..00d62996 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Add_error_string.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Add_error_string.html
@@ -6,28 +6,28 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Add_error_string"><H1>MPI_Add_error_string</H1></A>
-Associates an error string with an MPI error code or  class 
+Associates an error string with an MPI error code or class 
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Add_error_string(int errorcode, const char *string)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>errorcode </B><DD>error code or class (integer) 
+<DT><B>errorcode </B><DD>error code or class (integer)
 
-<DT><B>string </B><DD>text corresponding to errorcode (string) 
+<DT><B>string </B><DD>text corresponding to errorcode (string)
 </DL>
 <P>
 <H2>Notes</H2>
-The string must be no more than <tt>MPI_MAX_ERROR_STRING</tt> characters long.
+The string must be no more than <TT>MPI_MAX_ERROR_STRING</TT> characters long.
 The length of the string is as defined in the calling language.
 The length of the string does not include the null terminator in C or C++.
-Note that the string is <tt>const</tt> even though the MPI standard does not
+Note that the string is <TT>const</TT> even though the MPI standard does not
 specify it that way.
 <P>
-According to the MPI-2 standard, it is erroneous to call <tt>MPI_Add_error_string
-</tt>for an error code or class with a value less than or equal
-to <tt>MPI_ERR_LASTCODE</tt>.  Thus, you cannot replace the predefined error messages
+According to the MPI-2 standard, it is erroneous to call <TT>MPI_Add_error_string
+</TT>for an error code or class with a value less than or equal
+to <TT>MPI_ERR_LASTCODE</TT>.  Thus, you cannot replace the predefined error messages
 with this routine.
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -35,31 +35,31 @@ with this routine.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Address.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Address.html
index 60dd1b6b..d88b8449 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Address.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Address.html
@@ -9,7 +9,7 @@
 Gets the address of a location in memory 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Address(void *location, MPI_Aint *address)
+int MPI_Address(void *location, MPI_Aint * address)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>location </B> <DD> location in caller memory (choice)
@@ -22,7 +22,7 @@ int MPI_Address(void *location, MPI_Aint *address)
 <H2>Note</H2>
 This routine is provided for both the Fortran and C programmers.
 On many systems, the address returned by this routine will be the same
-as produced by the C <tt>&amp;</tt> operator, but this is not required in C and
+as produced by the C <TT>&amp;</TT> operator, but this is not required in C and
 may not be true of systems with word- rather than byte-oriented
 instructions or systems with segmented address spaces.
 <P>
@@ -37,36 +37,36 @@ The MPI-2 standard deprecated a number of routines because MPI-2 provides
 better versions.  This routine is one of those that was deprecated.  The
 routine may continue to be used, but new code should use the replacement
 routine.
-The replacement for this routine is <tt>MPI_Get_address</tt>.
+The replacement for this routine is <TT>MPI_Get_address</TT>.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Aint_add.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Aint_add.html
index ea33fed5..e0ac4e15 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Aint_add.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Aint_add.html
@@ -34,7 +34,7 @@ as if the process that originally produced base had called:
 </PRE>
 
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Aint_diff
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Aint_diff.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Aint_diff.html
index f2bbabb2..a261165d 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Aint_diff.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Aint_diff.html
@@ -35,7 +35,7 @@ process that originally produced the addresses had called
 
 on the addresses initially passed to MPI_GET_ADDRESS.
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Aint_add
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Allgather.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Allgather.html
index d2a85257..49ba74fb 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Allgather.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Allgather.html
@@ -10,50 +10,49 @@ Gathers data from all tasks and distribute the combined data to all tasks
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Allgather(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
-                  void *recvbuf, int recvcount, MPI_Datatype recvtype,
-                  MPI_Comm comm)
+                  void *recvbuf, int recvcount, MPI_Datatype recvtype, MPI_Comm comm)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>sendbuf </B><DD>starting address of send buffer (choice) 
+<DT><B>sendbuf </B><DD>starting address of send buffer (choice)
 
-<DT><B>sendcount </B><DD>number of elements in send buffer (integer) 
+<DT><B>sendcount </B><DD>number of elements in send buffer (integer)
 
-<DT><B>sendtype </B><DD>data type of send buffer elements (handle) 
+<DT><B>sendtype </B><DD>data type of send buffer elements (handle)
 
-<DT><B>recvcount </B><DD>number of elements received from any process (integer) 
+<DT><B>recvcount </B><DD>number of elements received from any process (integer)
 
-<DT><B>recvtype </B><DD>data type of receive buffer elements (handle) 
+<DT><B>recvtype </B><DD>data type of receive buffer elements (handle)
 
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>recvbuf </B> <DD> address of receive buffer (choice) 
+<DL><DT><B>recvbuf </B> <DD> address of receive buffer (choice)
 </DL>
 <P>
 <H2>Notes</H2>
 The MPI standard (1.0 and 1.1) says that
-<br>
+<BR>
 <P>
-<br>
+<BR>
 <P>
 The jth block of data sent from  each process is received by every process
-and placed in the jth block of the buffer <tt>recvbuf</tt>.
-<br>
+and placed in the jth block of the buffer <TT>recvbuf</TT>.
+<BR>
 <P>
-<br>
+<BR>
 <P>
 This is misleading; a better description is
-<br>
+<BR>
 <P>
-<br>
+<BR>
 <P>
 The block of data sent from the jth process is received by every
-process and placed in the jth block of the buffer <tt>recvbuf</tt>.
-<br>
+process and placed in the jth block of the buffer <TT>recvbuf</TT>.
+<BR>
 <P>
-<br>
+<BR>
 <P>
 This text was suggested by Rajeev Thakur and has been adopted as a
 clarification by the MPI Forum.
@@ -63,42 +62,42 @@ clarification by the MPI Forum.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_BUFFER </B> <DD> Invalid buffer pointer.  Usually a null buffer where
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Allgatherv.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Allgatherv.html
index de8a6504..f7dc7360 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Allgatherv.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Allgatherv.html
@@ -15,51 +15,51 @@ int MPI_Allgatherv(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>sendbuf </B><DD>starting address of send buffer (choice) 
+<DT><B>sendbuf </B><DD>starting address of send buffer (choice)
 
-<DT><B>sendcount </B><DD>number of elements in send buffer (integer) 
+<DT><B>sendcount </B><DD>number of elements in send buffer (integer)
 
-<DT><B>sendtype </B><DD>data type of send buffer elements (handle) 
+<DT><B>sendtype </B><DD>data type of send buffer elements (handle)
 
-<DT><B>recvcounts </B><DD>integer array (of length group size) 
-containing the number of elements that are to be received from each process 
+<DT><B>recvcounts </B><DD>integer array (of length group size)
+containing the number of elements that are to be received from each process
 
-<DT><B>displs </B><DD>integer array (of length group size). Entry 
-<tt>i</tt>  specifies the displacement (relative to recvbuf ) at
-which to place the incoming data from process  <tt>i</tt>  
+<DT><B>displs </B><DD>integer array (of length group size). Entry
+<TT>i</TT>  specifies the displacement (relative to recvbuf) at
+which to place the incoming data from process  <TT>i
+</TT>
+<DT><B>recvtype </B><DD>data type of receive buffer elements (handle)
 
-<DT><B>recvtype </B><DD>data type of receive buffer elements (handle) 
-
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>recvbuf </B> <DD> address of receive buffer (choice) 
+<DL><DT><B>recvbuf </B> <DD> address of receive buffer (choice)
 </DL>
 <P>
 <H2>Notes</H2>
 The MPI standard (1.0 and 1.1) says that
-<br>
+<BR>
 <P>
-<br>
+<BR>
 <P>
 The jth block of data sent from
 each process is received by every process and placed in the jth block of the
-buffer <tt>recvbuf</tt>.
-<br>
+buffer <TT>recvbuf</TT>.
+<BR>
 <P>
-<br>
+<BR>
 <P>
 This is misleading; a better description is
-<br>
+<BR>
 <P>
-<br>
+<BR>
 <P>
 The block of data sent from the jth process is received by every
-process and placed in the jth block of the buffer <tt>recvbuf</tt>.
-<br>
+process and placed in the jth block of the buffer <TT>recvbuf</TT>.
+<BR>
 <P>
-<br>
+<BR>
 <P>
 This text was suggested by Rajeev Thakur, and has been adopted as a
 clarification to the MPI standard by the MPI-Forum.
@@ -69,31 +69,31 @@ clarification to the MPI standard by the MPI-Forum.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -104,7 +104,7 @@ one is not valid.
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Alloc_mem.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Alloc_mem.html
index 5710eff4..f4698e10 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Alloc_mem.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Alloc_mem.html
@@ -13,13 +13,13 @@ int MPI_Alloc_mem(MPI_Aint size, MPI_Info info, void *baseptr)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>size </B><DD>size of memory segment in bytes (nonnegative integer) 
+<DT><B>size </B><DD>size of memory segment in bytes (nonnegative integer)
 
-<DT><B>info </B><DD>info argument (handle) 
+<DT><B>info </B><DD>info argument (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>baseptr </B> <DD> pointer to beginning of memory segment allocated 
+<DL><DT><B>baseptr </B> <DD> pointer to beginning of memory segment allocated
 </DL>
 <P>
 <H2>Notes</H2>
@@ -27,9 +27,9 @@ Using this routine from Fortran requires that the Fortran compiler accept
 a common pointer extension.  See Section 4.11 (Memory Allocation) in the
 MPI-2 standard for more information and examples.
 <P>
-Also note that while <tt>baseptr</tt> is a <tt>void *</tt> type, this is
+Also note that while <TT>baseptr</TT> is a <TT>void *</TT> type, this is
 simply to allow easy use of any pointer object for this parameter.
-In fact, this argument is really a <tt>void **</tt> type, that is, a
+In fact, this argument is really a <TT>void **</TT> type, that is, a
 pointer to a pointer.
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -37,31 +37,31 @@ pointer to a pointer.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -70,10 +70,10 @@ possible.
 <DL><DT><B>MPI_ERR_INFO </B> <DD> Invalid Info 
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_NO_MEM </B> <DD> Insufficient memory available for allocation by 
-<tt>MPI_Alloc_mem
-</tt>
+<TT>MPI_Alloc_mem
+</TT>
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Allreduce.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Allreduce.html
index 00fb0fda..65dccf04 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Allreduce.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Allreduce.html
@@ -14,19 +14,19 @@ int MPI_Allreduce(const void *sendbuf, void *recvbuf, int count,
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>sendbuf </B><DD>starting address of send buffer (choice) 
+<DT><B>sendbuf </B><DD>starting address of send buffer (choice)
 
-<DT><B>count </B><DD>number of elements in send buffer (integer) 
+<DT><B>count </B><DD>number of elements in send buffer (integer)
 
-<DT><B>datatype </B><DD>data type of elements of send buffer (handle) 
+<DT><B>datatype </B><DD>data type of elements of send buffer (handle)
 
-<DT><B>op </B><DD>operation (handle) 
+<DT><B>op </B><DD>operation (handle)
 
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>recvbuf </B> <DD> starting address of receive buffer (choice) 
+<DL><DT><B>recvbuf </B> <DD> starting address of receive buffer (choice)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -34,25 +34,25 @@ int MPI_Allreduce(const void *sendbuf, void *recvbuf, int count,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Notes on collective operations</H2>
 <P>
-The reduction functions (<tt>MPI_Op</tt>) do not return an error value.  As a result,
-if the functions detect an error, all they can do is either call <tt>MPI_Abort
-</tt>or silently skip the problem.  Thus, if you change the error handler from
-<tt>MPI_ERRORS_ARE_FATAL</tt> to something else, for example, <tt>MPI_ERRORS_RETURN</tt>,
+The reduction functions (<TT>MPI_Op</TT>) do not return an error value.  As a result,
+if the functions detect an error, all they can do is either call <TT>MPI_Abort
+</TT>or silently skip the problem.  Thus, if you change the error handler from
+<TT>MPI_ERRORS_ARE_FATAL</TT> to something else, for example, <TT>MPI_ERRORS_RETURN</TT>,
 then no error may be indicated.
 <P>
 The reason for this is the performance problems in ensuring that
@@ -60,16 +60,16 @@ all collective routines return the same error value.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -80,14 +80,14 @@ one is not valid.
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
-<DL><DT><B>MPI_ERR_OP </B> <DD> Invalid operation.  MPI operations (objects of type <tt>MPI_Op</tt>)
-must either be one of the predefined operations (e.g., <tt>MPI_SUM</tt>) or
-created with <tt>MPI_Op_create</tt>.
+<DL><DT><B>MPI_ERR_OP </B> <DD> Invalid operation.  MPI operations (objects of type <TT>MPI_Op</TT>)
+must either be one of the predefined operations (e.g., <TT>MPI_SUM</TT>) or
+created with <TT>MPI_Op_create</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Alltoall.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Alltoall.html
index 78645dbf..da8b3271 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Alltoall.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Alltoall.html
@@ -10,26 +10,25 @@ Sends data from all to all processes
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Alltoall(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
-                 void *recvbuf, int recvcount, MPI_Datatype recvtype,
-                 MPI_Comm comm)
+                 void *recvbuf, int recvcount, MPI_Datatype recvtype, MPI_Comm comm)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>sendbuf </B><DD>starting address of send buffer (choice) 
+<DT><B>sendbuf </B><DD>starting address of send buffer (choice)
 
-<DT><B>sendcount </B><DD>number of elements to send to each process (integer) 
+<DT><B>sendcount </B><DD>number of elements to send to each process (integer)
 
-<DT><B>sendtype </B><DD>data type of send buffer elements (handle) 
+<DT><B>sendtype </B><DD>data type of send buffer elements (handle)
 
-<DT><B>recvcount </B><DD>number of elements received from any process (integer) 
+<DT><B>recvcount </B><DD>number of elements received from any process (integer)
 
-<DT><B>recvtype </B><DD>data type of receive buffer elements (handle) 
+<DT><B>recvtype </B><DD>data type of receive buffer elements (handle)
 
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>recvbuf </B> <DD> address of receive buffer (choice) 
+<DL><DT><B>recvbuf </B> <DD> address of receive buffer (choice)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -37,42 +36,42 @@ int MPI_Alltoall(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_BUFFER </B> <DD> Invalid buffer pointer.  Usually a null buffer where
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Alltoallv.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Alltoallv.html
index 788965a1..719e5bf0 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Alltoallv.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Alltoallv.html
@@ -6,42 +6,41 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Alltoallv"><H1>MPI_Alltoallv</H1></A>
-Sends data from all to all processes; each process may  send a different amount of data and provide displacements for the input and output data. 
+Sends data from all to all processes; each process may send a different amount of data and provide displacements for the input and output data. 
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Alltoallv(const void *sendbuf, const int *sendcounts,
                   const int *sdispls, MPI_Datatype sendtype, void *recvbuf,
-                  const int *recvcounts, const int *rdispls, MPI_Datatype recvtype,
-                  MPI_Comm comm)
+                  const int *recvcounts, const int *rdispls, MPI_Datatype recvtype, MPI_Comm comm)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>sendbuf </B><DD>starting address of send buffer (choice) 
+<DT><B>sendbuf </B><DD>starting address of send buffer (choice)
 
-<DT><B>sendcounts </B><DD>integer array equal to the group size 
-specifying the number of elements to send to each processor 
+<DT><B>sendcounts </B><DD>integer array equal to the group size
+specifying the number of elements to send to each processor
 
-<DT><B>sdispls </B><DD>integer array (of length group size). Entry 
-<tt>j</tt>  specifies the displacement (relative to sendbuf  from
-which to take the outgoing data destined for process  <tt>j</tt>  
+<DT><B>sdispls </B><DD>integer array (of length group size). Entry
+<TT>j</TT>  specifies the displacement (relative to sendbuf  from
+which to take the outgoing data destined for process  <TT>j
+</TT>
+<DT><B>sendtype </B><DD>data type of send buffer elements (handle)
 
-<DT><B>sendtype </B><DD>data type of send buffer elements (handle) 
-
-<DT><B>recvcounts </B><DD>integer array equal to the group size 
+<DT><B>recvcounts </B><DD>integer array equal to the group size
 specifying the maximum number of elements that can be received from
-each processor 
+each processor
 
-<DT><B>rdispls </B><DD>integer array (of length group size). Entry 
-<tt>i</tt>  specifies the displacement (relative to recvbuf  at
-which to place the incoming data from process  <tt>i</tt>  
+<DT><B>rdispls </B><DD>integer array (of length group size). Entry
+<TT>i</TT>  specifies the displacement (relative to recvbuf  at
+which to place the incoming data from process  <TT>i
+</TT>
+<DT><B>recvtype </B><DD>data type of receive buffer elements (handle)
 
-<DT><B>recvtype </B><DD>data type of receive buffer elements (handle) 
-
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>recvbuf </B> <DD> address of receive buffer (choice) 
+<DL><DT><B>recvbuf </B> <DD> address of receive buffer (choice)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -49,42 +48,42 @@ which to place the incoming data from process  <tt>i</tt>
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_BUFFER </B> <DD> Invalid buffer pointer.  Usually a null buffer where
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Alltoallw.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Alltoallw.html
index 8db162e0..0aa56e21 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Alltoallw.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Alltoallw.html
@@ -16,33 +16,33 @@ int MPI_Alltoallw(const void *sendbuf, const int sendcounts[],
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>sendbuf </B><DD>starting address of send buffer (choice) 
+<DT><B>sendbuf </B><DD>starting address of send buffer (choice)
 
-<DT><B>sendcounts </B><DD>integer array equal to the group size specifying the number of 
-elements to send to each processor (integer) 
+<DT><B>sendcounts </B><DD>integer array equal to the group size specifying the number of
+elements to send to each processor (integer)
 
-<DT><B>sdispls </B><DD>integer array (of length group size). Entry j specifies the 
-displacement in bytes (relative to sendbuf) from which to take the outgoing 
-data destined for process j 
+<DT><B>sdispls </B><DD>integer array (of length group size). Entry j specifies the
+displacement in bytes (relative to sendbuf) from which to take the outgoing
+data destined for process j
 
-<DT><B>sendtypes </B><DD>array of datatypes (of length group size). Entry j specifies the 
-type of data to send to process j (handle) 
+<DT><B>sendtypes </B><DD>array of datatypes (of length group size). Entry j specifies the
+type of data to send to process j (handle)
 
 <DT><B>recvcounts </B><DD>integer array equal to the group size specifying the number of
-elements that can be received from each processor (integer) 
+elements that can be received from each processor (integer)
 
-<DT><B>rdispls </B><DD>integer array (of length group size). Entry i specifies the 
-displacement in bytes (relative to recvbuf) at which to place the incoming 
-data from process i 
+<DT><B>rdispls </B><DD>integer array (of length group size). Entry i specifies the
+displacement in bytes (relative to recvbuf) at which to place the incoming
+data from process i
 
-<DT><B>recvtypes </B><DD>array of datatypes (of length group size). Entry i specifies 
-the type of data received from process i (handle) 
+<DT><B>recvtypes </B><DD>array of datatypes (of length group size). Entry i specifies
+the type of data received from process i (handle)
 
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>recvbuf </B> <DD> address of receive buffer (choice) 
+<DL><DT><B>recvbuf </B> <DD> address of receive buffer (choice)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -50,47 +50,47 @@ the type of data received from process i (handle)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Attr_delete.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Attr_delete.html
index 892e02a5..16b800d4 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Attr_delete.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Attr_delete.html
@@ -6,16 +6,16 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Attr_delete"><H1>MPI_Attr_delete</H1></A>
-Deletes an attribute value associated with a key on a  communicator 
+Deletes an attribute value associated with a key on a communicator 
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Attr_delete(MPI_Comm comm, int keyval)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>comm </B><DD>communicator to which attribute is attached (handle) 
+<DT><B>comm </B><DD>communicator to which attribute is attached (handle)
 
-<DT><B>keyval </B><DD>The key value of the deleted attribute (integer) 
+<DT><B>keyval </B><DD>The key value of the deleted attribute (integer)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -23,45 +23,45 @@ int MPI_Attr_delete(MPI_Comm comm, int keyval)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Deprecated Function</H2>
 The MPI-2 standard deprecated a number of routines because MPI-2 provides
 better versions.  This routine is one of those that was deprecated.  The
 routine may continue to be used, but new code should use the replacement
 routine.
-The replacement for this routine is <tt>MPI_Comm_delete_attr</tt>.
+The replacement for this routine is <TT>MPI_Comm_delete_attr</TT>.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> This error class is associated with an error code that 
 indicates that an attempt was made to free one of the permanent keys.
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Attr_get.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Attr_get.html
index 7ec85c9a..a590c5ba 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Attr_get.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Attr_get.html
@@ -13,27 +13,27 @@ int MPI_Attr_get(MPI_Comm comm, int keyval, void *attribute_val, int *flag)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>comm </B><DD>communicator to which attribute is attached (handle) 
+<DT><B>comm </B><DD>communicator to which attribute is attached (handle)
 
-<DT><B>keyval </B><DD>key value (integer) 
+<DT><B>keyval </B><DD>key value (integer)
 </DL>
 <P>
 <H2>Output Parameters</H2>
 <DL>
-<DT><B>attribute_val </B><DD>attribute value, unless <tt>flag</tt> = false
+<DT><B>attribute_val </B><DD>attribute value, unless <TT>flag</TT> = false
 
 <DT><B>flag </B><DD>true if an attribute value was extracted;  false if no attribute is
-associated with the key 
+associated with the key
 </DL>
 <P>
 <H2>Notes</H2>
 Attributes must be extracted from the same language as they were inserted
-in with <tt>MPI_ATTR_PUT</tt>.  The notes for C and Fortran below explain why.
+in with <TT>MPI_ATTR_PUT</TT>.  The notes for C and Fortran below explain why.
 <P>
 <H2>Notes for C</H2>
-Even though the <tt>attribute_val</tt> argument is declared as <tt>void *</tt>, it is
-really the address of a void pointer (i.e., a <tt>void **</tt>).  Using
-a <tt>void *</tt>, however, is more in keeping with C idiom and allows the
+Even though the <TT>attribute_val</TT> argument is declared as <TT>void *</TT>, it is
+really the address of a void pointer (i.e., a <TT>void **</TT>).  Using
+a <TT>void *</TT>, however, is more in keeping with C idiom and allows the
 pointer to be passed without additional casts.
 <P>
 <P>
@@ -42,53 +42,53 @@ pointer to be passed without additional casts.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Deprecated Function</H2>
 The MPI-2 standard deprecated a number of routines because MPI-2 provides
 better versions.  This routine is one of those that was deprecated.  The
 routine may continue to be used, but new code should use the replacement
 routine.
-The replacement for this routine is <tt>MPI_Comm_get_attr</tt>.
+The replacement for this routine is <TT>MPI_Comm_get_attr</TT>.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
-The <tt>attribute_val</tt> in Fortran is a pointer to a Fortran integer, not
-a pointer to a <tt>void *</tt>.
+The <TT>attribute_val</TT> in Fortran is a pointer to a Fortran integer, not
+a pointer to a <TT>void *</TT>.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_KEYVAL </B> <DD> Invalid keyval
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
 MPI_Attr_put, MPI_Keyval_create, MPI_Attr_delete, MPI_Comm_get_attr
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Attr_put.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Attr_put.html
index a66416ee..5e299684 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Attr_put.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Attr_put.html
@@ -13,25 +13,25 @@ int MPI_Attr_put(MPI_Comm comm, int keyval, void *attribute_val)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>comm </B><DD>communicator to which attribute will be attached (handle) 
+<DT><B>comm </B><DD>communicator to which attribute will be attached (handle)
 
-<DT><B>keyval </B><DD>key value, as returned by  <tt>MPI_KEYVAL_CREATE</tt> (integer) 
+<DT><B>keyval </B><DD>key value, as returned by  <TT>MPI_KEYVAL_CREATE</TT> (integer)
 
-<DT><B>attribute_val </B><DD>attribute value 
+<DT><B>attribute_val </B><DD>attribute value
 </DL>
 <P>
 <H2>Notes</H2>
-Values of the permanent attributes <tt>MPI_TAG_UB</tt>, <tt>MPI_HOST</tt>, <tt>MPI_IO</tt>,
-<tt>MPI_WTIME_IS_GLOBAL</tt>, <tt>MPI_UNIVERSE_SIZE</tt>, <tt>MPI_LASTUSEDCODE</tt>, and
-<tt>MPI_APPNUM</tt>  may not be changed.
+Values of the permanent attributes <TT>MPI_TAG_UB</TT>, <TT>MPI_HOST</TT>, <TT>MPI_IO</TT>,
+<TT>MPI_WTIME_IS_GLOBAL</TT>, <TT>MPI_UNIVERSE_SIZE</TT>, <TT>MPI_LASTUSEDCODE</TT>, and
+<TT>MPI_APPNUM</TT>  may not be changed.
 <P>
 The type of the attribute value depends on whether C, C++, or Fortran
 is being used.
-In C and C++, an attribute value is a pointer (<tt>void *</tt>); in Fortran,
+In C and C++, an attribute value is a pointer (<TT>void *</TT>); in Fortran,
 it is a single
-integer (<em>not</em> a pointer, since Fortran has no pointers and there are systems
+integer (<EM>not</EM> a pointer, since Fortran has no pointers and there are systems
 for which a pointer does not fit in an integer (e.g., any &gt; 32 bit address
-system that uses 64 bits for Fortran <tt>DOUBLE PRECISION</tt>).
+system that uses 64 bits for Fortran <TT>DOUBLE PRECISION</TT>).
 <P>
 If an attribute is already present, the delete function (specified when the
 corresponding keyval was created) will be called.
@@ -41,45 +41,45 @@ corresponding keyval was created) will be called.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Deprecated Function</H2>
 The MPI-2 standard deprecated a number of routines because MPI-2 provides
 better versions.  This routine is one of those that was deprecated.  The
 routine may continue to be used, but new code should use the replacement
 routine.
-The replacement for this routine is <tt>MPI_Comm_set_attr</tt>.
+The replacement for this routine is <TT>MPI_Comm_set_attr</TT>.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_KEYVAL </B> <DD> Invalid keyval
 </DL>
@@ -87,7 +87,7 @@ communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
 indicates that an attempt was made to free one of the permanent keys.
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
 MPI_Attr_get, MPI_Keyval_create, MPI_Attr_delete, MPI_Comm_set_attr
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Barrier.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Barrier.html
index 34facec8..afefaa96 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Barrier.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Barrier.html
@@ -6,13 +6,13 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Barrier"><H1>MPI_Barrier</H1></A>
-Blocks until all processes in the communicator have reached this routine.   
+Blocks until all processes in the communicator have reached this routine. 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Barrier( MPI_Comm comm )
+int MPI_Barrier(MPI_Comm comm)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>comm </B> <DD> communicator (handle) 
+<DL><DT><B>comm </B> <DD> communicator (handle)
 </DL>
 <P>
 <H2>Notes</H2>
@@ -25,37 +25,37 @@ communicator have entered the call.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Bcast.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Bcast.html
index 6391bb88..7aadfeae 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Bcast.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Bcast.html
@@ -9,22 +9,21 @@
 Broadcasts a message from the process with rank "root" to all other processes of the communicator 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Bcast( void *buffer, int count, MPI_Datatype datatype, int root, 
-               MPI_Comm comm )
+int MPI_Bcast(void *buffer, int count, MPI_Datatype datatype, int root, MPI_Comm comm)
 </PRE>
 <H2>Input/Output Parameters</H2>
-<DL><DT><B>buffer </B> <DD> starting address of buffer (choice) 
+<DL><DT><B>buffer </B> <DD> starting address of buffer (choice)
 </DL>
 <P>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>count </B><DD>number of entries in buffer (integer) 
+<DT><B>count </B><DD>number of entries in buffer (integer)
 
-<DT><B>datatype </B><DD>data type of buffer (handle) 
+<DT><B>datatype </B><DD>data type of buffer (handle)
 
-<DT><B>root </B><DD>rank of broadcast root (integer) 
+<DT><B>root </B><DD>rank of broadcast root (integer)
 
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -32,44 +31,44 @@ int MPI_Bcast( void *buffer, int count, MPI_Datatype datatype, int root,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_BUFFER </B> <DD> Invalid buffer pointer.  Usually a null buffer where
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Bsend.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Bsend.html
index 61cb8999..7cf3d331 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Bsend.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Bsend.html
@@ -9,53 +9,52 @@
 Basic send with user-provided buffering 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Bsend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-              MPI_Comm comm)
+int MPI_Bsend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag, MPI_Comm comm)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>buf </B><DD>initial address of send buffer (choice) 
+<DT><B>buf </B><DD>initial address of send buffer (choice)
 
-<DT><B>count </B><DD>number of elements in send buffer (nonnegative integer) 
+<DT><B>count </B><DD>number of elements in send buffer (nonnegative integer)
 
-<DT><B>datatype </B><DD>datatype of each send buffer element (handle) 
+<DT><B>datatype </B><DD>datatype of each send buffer element (handle)
 
-<DT><B>dest </B><DD>rank of destination (integer) 
+<DT><B>dest </B><DD>rank of destination (integer)
 
-<DT><B>tag </B><DD>message tag (integer) 
+<DT><B>tag </B><DD>message tag (integer)
 
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Notes</H2>
 This send is provided as a convenience function; it allows the user to
 send messages without worring about where they are buffered (because the
-user <em>must</em> have provided buffer space with <tt>MPI_Buffer_attach</tt>).
+user <EM>must</EM> have provided buffer space with <TT>MPI_Buffer_attach</TT>).
 <P>
 In deciding how much buffer space to allocate, remember that the buffer space
-is not available for reuse by subsequent <tt>MPI_Bsend</tt>s unless you are certain
+is not available for reuse by subsequent <TT>MPI_Bsend</TT>s unless you are certain
 that the message
 has been received (not just that it should have been received).  For example,
 this code does not allocate enough buffer space
 <PRE>
-    MPI_Buffer_attach( b, n*sizeof(double) + MPI_BSEND_OVERHEAD );
+    MPI_Buffer_attach(b, n*sizeof(double) + MPI_BSEND_OVERHEAD);
     for (i=0; i&lt;m; i++) {
-        MPI_Bsend( buf, n, MPI_DOUBLE, ... );
+        MPI_Bsend(buf, n, MPI_DOUBLE, ...);
     }
 </PRE>
 
 because only enough buffer space is provided for a single send, and the
-loop may start a second <tt>MPI_Bsend</tt> before the first is done making use of the
+loop may start a second <TT>MPI_Bsend</TT> before the first is done making use of the
 buffer.
 <P>
 In C, you can
 force the messages to be delivered by
 <PRE>
-    MPI_Buffer_detach( &amp;b, &amp;n );
-    MPI_Buffer_attach( b, n );
+    MPI_Buffer_detach(&amp;b, &amp;n);
+    MPI_Buffer_attach(b, n);
 </PRE>
 
-(The <tt>MPI_Buffer_detach</tt> will not complete until all buffered messages are
+(The <TT>MPI_Buffer_detach</TT> will not complete until all buffered messages are
 delivered.)
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -63,57 +62,57 @@ delivered.)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_TAG </B> <DD> Invalid tag argument.  Tags must be non-negative; tags
-in a receive (<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may
-also be <tt>MPI_ANY_TAG</tt>.  The largest tag value is available through the 
-the attribute <tt>MPI_TAG_UB</tt>.
+in a receive (<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may
+also be <TT>MPI_ANY_TAG</TT>.  The largest tag value is available through the 
+the attribute <TT>MPI_TAG_UB</TT>.
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Buffer_attach, MPI_Ibsend, MPI_Bsend_init
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Bsend_init.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Bsend_init.html
index 9f45a90c..8bb0ae81 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Bsend_init.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Bsend_init.html
@@ -10,25 +10,25 @@ Builds a handle for a buffered send
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Bsend_init(const void *buf, int count, MPI_Datatype datatype,
-                   int dest, int tag, MPI_Comm comm, MPI_Request *request)
+                   int dest, int tag, MPI_Comm comm, MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>buf </B><DD>initial address of send buffer (choice) 
+<DT><B>buf </B><DD>initial address of send buffer (choice)
 
-<DT><B>count </B><DD>number of elements sent (integer) 
+<DT><B>count </B><DD>number of elements sent (integer)
 
-<DT><B>datatype </B><DD>type of each element (handle) 
+<DT><B>datatype </B><DD>type of each element (handle)
 
-<DT><B>dest </B><DD>rank of destination (integer) 
+<DT><B>dest </B><DD>rank of destination (integer)
 
-<DT><B>tag </B><DD>message tag (integer) 
+<DT><B>tag </B><DD>message tag (integer)
 
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>request </B> <DD> communication request (handle) 
+<DL><DT><B>request </B> <DD> communication request (handle)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -36,57 +36,57 @@ int MPI_Bsend_init(const void *buf, int count, MPI_Datatype datatype,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_TAG </B> <DD> Invalid tag argument.  Tags must be non-negative; tags
-in a receive (<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may
-also be <tt>MPI_ANY_TAG</tt>.  The largest tag value is available through the 
-the attribute <tt>MPI_TAG_UB</tt>.
+in a receive (<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may
+also be <TT>MPI_ANY_TAG</TT>.  The largest tag value is available through the 
+the attribute <TT>MPI_TAG_UB</TT>.
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Buffer_attach
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Buffer_attach.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Buffer_attach.html
index cac7e642..558ca1fd 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Buffer_attach.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Buffer_attach.html
@@ -6,41 +6,41 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Buffer_attach"><H1>MPI_Buffer_attach</H1></A>
-Attaches a user-provided buffer for sending  
+Attaches a user-provided buffer for sending 
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Buffer_attach(void *buffer, int size)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>buffer </B><DD>initial buffer address (choice) 
+<DT><B>buffer </B><DD>initial buffer address (choice)
 
-<DT><B>size </B><DD>buffer size, in bytes (integer) 
+<DT><B>size </B><DD>buffer size, in bytes (integer)
 </DL>
 <P>
 <H2>Notes</H2>
 The size given should be the sum of the sizes of all outstanding Bsends that
-you intend to have, plus <tt>MPI_BSEND_OVERHEAD</tt> for each Bsend that you do.
-For the purposes of calculating size, you should use <tt>MPI_Pack_size</tt>.
+you intend to have, plus <TT>MPI_BSEND_OVERHEAD</TT> for each Bsend that you do.
+For the purposes of calculating size, you should use <TT>MPI_Pack_size</TT>.
 In other words, in the code
 <PRE>
-     MPI_Buffer_attach( buffer, size );
-     MPI_Bsend( ..., count=20, datatype=type1,  ... );
+     MPI_Buffer_attach(buffer, size);
+     MPI_Bsend(..., count=20, datatype=type1,  ...);
      ...
-     MPI_Bsend( ..., count=40, datatype=type2, ... );
+     MPI_Bsend(..., count=40, datatype=type2, ...);
 </PRE>
 
-the value of <tt>size</tt> in the <tt>MPI_Buffer_attach</tt> call should be greater than
+the value of <TT>size</TT> in the <TT>MPI_Buffer_attach</TT> call should be greater than
 the value computed by
 <PRE>
-     MPI_Pack_size( 20, type1, comm, &amp;s1 );
-     MPI_Pack_size( 40, type2, comm, &amp;s2 );
+     MPI_Pack_size(20, type1, comm, &amp;s1);
+     MPI_Pack_size(40, type2, comm, &amp;s2);
      size = s1 + s2 + 2 * MPI_BSEND_OVERHEAD;
 </PRE>
 
-The <tt>MPI_BSEND_OVERHEAD</tt> gives the maximum amount of space that may be used in
+The <TT>MPI_BSEND_OVERHEAD</TT> gives the maximum amount of space that may be used in
 the buffer for use by the BSEND routines in using the buffer.  This value
-is in <tt>mpi.h</tt> (for C) and <tt>mpif.h</tt> (for Fortran).
+is in <TT>mpi.h</TT> (for C) and <TT>mpif.h</TT> (for Fortran).
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
@@ -51,35 +51,35 @@ not be used from within a signal handler.
 The MPI standard defined a thread-safe interface but this does not
 mean that all routines may be called without any thread locks.  For
 example, two threads must not attempt to change the contents of the
-same <tt>MPI_Info</tt> object concurrently.  The user is responsible in this
+same <TT>MPI_Info</TT> object concurrently.  The user is responsible in this
 case for using some mechanism, such as thread locks, to ensure that
 only one thread at a time makes use of this routine.
-Because the buffer for buffered sends (e.g., <tt>MPI_Bsend</tt>) is shared by all
+Because the buffer for buffered sends (e.g., <TT>MPI_Bsend</TT>) is shared by all
 threads in a process, the user is responsible for ensuring that only
-one thread at a time calls this routine or <tt>MPI_Buffer_detach</tt>.
+one thread at a time calls this routine or <TT>MPI_Buffer_detach</TT>.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -89,10 +89,10 @@ possible.
 one is not valid.
 </DL>
 <DL><DT><B>MPI_ERR_INTERN </B> <DD> An internal error has been detected.  This is fatal.
-Please send a bug report to <tt>mpi-bugs@mcs.anl.gov</tt>.
+Please send a bug report to <TT>mpi-bugs@mcs.anl.gov</TT>.
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Buffer_detach, MPI_Bsend
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Buffer_detach.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Buffer_detach.html
index 35b7dee5..41021de7 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Buffer_detach.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Buffer_detach.html
@@ -15,24 +15,24 @@ int MPI_Buffer_detach(void *buffer_addr, int *size)
 <DL>
 <DT><B>buffer_addr </B><DD>initial buffer address (choice)
 
-<DT><B>size </B><DD>buffer size, in bytes (integer) 
+<DT><B>size </B><DD>buffer size, in bytes (integer)
 </DL>
 <P>
 <H2>Notes</H2>
-The reason that <tt>MPI_Buffer_detach</tt> returns the address and size of the
+The reason that <TT>MPI_Buffer_detach</TT> returns the address and size of the
 buffer being detached is to allow nested libraries to replace and restore
 the buffer.  For example, consider
 <P>
 <PRE>
     int size, mysize, idummy;
-    void *ptr, *myptr, *dummy;     
-    MPI_Buffer_detach( &amp;ptr, &amp;size );
-    MPI_Buffer_attach( myptr, mysize );
+    void *ptr, *myptr, *dummy;
+    MPI_Buffer_detach(&amp;ptr, &amp;size);
+    MPI_Buffer_attach(myptr, mysize);
     ...
     ... library code ...
     ...
-    MPI_Buffer_detach( &amp;dummy, &amp;idummy );
-    MPI_Buffer_attach( ptr, size );
+    MPI_Buffer_detach(&amp;dummy, &amp;idummy);
+    MPI_Buffer_attach(ptr, size);
 </PRE>
 
 <P>
@@ -41,18 +41,18 @@ strengths (it is simple) and weaknesses (it only works for nested usages).
 <P>
 Note that for this approach to work, MPI_Buffer_detach must return MPI_SUCCESS
 even when there is no buffer to detach.  In that case, it returns a size of
-zero.  The MPI 1.1 standard for <tt>MPI_BUFFER_DETACH</tt> contains the text
+zero.  The MPI 1.1 standard for <TT>MPI_BUFFER_DETACH</TT> contains the text
 <P>
 <PRE>
    The statements made in this section describe the behavior of MPI for
-   buffered-mode sends. When no buffer is currently associated, MPI behaves 
+   buffered-mode sends. When no buffer is currently associated, MPI behaves
    as if a zero-sized buffer is associated with the process.
 </PRE>
 
 <P>
 This could be read as applying only to the various Bsend routines.  This
-implementation takes the position that this applies to <tt>MPI_BUFFER_DETACH
-</tt>as well.
+implementation takes the position that this applies to <TT>MPI_BUFFER_DETACH
+</TT>as well.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
@@ -63,22 +63,22 @@ not be used from within a signal handler.
 The MPI standard defined a thread-safe interface but this does not
 mean that all routines may be called without any thread locks.  For
 example, two threads must not attempt to change the contents of the
-same <tt>MPI_Info</tt> object concurrently.  The user is responsible in this
+same <TT>MPI_Info</TT> object concurrently.  The user is responsible in this
 case for using some mechanism, such as thread locks, to ensure that
 only one thread at a time makes use of this routine.
-Because the buffer for buffered sends (e.g., <tt>MPI_Bsend</tt>) is shared by all
+Because the buffer for buffered sends (e.g., <TT>MPI_Bsend</TT>) is shared by all
 threads in a process, the user is responsible for ensuring that only
-one thread at a time calls this routine or <tt>MPI_Buffer_attach</tt>.
+one thread at a time calls this routine or <TT>MPI_Buffer_attach</TT>.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 The Fortran binding for this routine is different.  Because Fortran
 does not have pointers, it is impossible to provide a way to use the
@@ -86,11 +86,11 @@ output of this routine to exchange buffers.  In this case, only the
 size field is set.
 <P>
 <H2>Notes for C</H2>
-Even though the <tt>bufferptr</tt> argument is declared as <tt>void *</tt>, it is
+Even though the <TT>bufferptr</TT> argument is declared as <TT>void *</TT>, it is
 really the address of a void pointer.  See the rationale in the
 standard for more details.
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Buffer_attach
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cancel.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cancel.html
index dc8e7ba8..98ba3d5e 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cancel.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cancel.html
@@ -9,16 +9,16 @@
 Cancels a communication request 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Cancel(MPI_Request *request)
+int MPI_Cancel(MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>request </B> <DD> communication request (handle) 
+<DL><DT><B>request </B> <DD> communication request (handle)
 </DL>
 <P>
 <H2>Notes</H2>
-The primary expected use of <tt>MPI_Cancel</tt> is in multi-buffering
-schemes, where speculative <tt>MPI_Irecvs</tt> are made.  When the computation
-completes, some of these receive requests may remain; using <tt>MPI_Cancel</tt> allows
+The primary expected use of <TT>MPI_Cancel</TT> is in multi-buffering
+schemes, where speculative <TT>MPI_Irecvs</TT> are made.  When the computation
+completes, some of these receive requests may remain; using <TT>MPI_Cancel</TT> allows
 the user to cancel these unsatisfied requests.
 <P>
 Cancelling a send operation is much more difficult, in large part because the
@@ -34,18 +34,18 @@ messages).
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Null Handles</H2>
 The MPI 1.1 specification, in the section on opaque objects, explicitly
@@ -62,25 +62,25 @@ disallows freeing a null communicator.  The text from the standard is:
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
-<DL><DT><B>MPI_ERR_REQUEST </B> <DD> Invalid <tt>MPI_Request</tt>.  Either null or, in the case of a
-<tt>MPI_Start</tt> or <tt>MPI_Startall</tt>, not a persistent request.
+<DL><DT><B>MPI_ERR_REQUEST </B> <DD> Invalid <TT>MPI_Request</TT>.  Either null or, in the case of a
+<TT>MPI_Start</TT> or <TT>MPI_Startall</TT>, not a persistent request.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cart_coords.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cart_coords.html
index 1e590fbf..367352d9 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cart_coords.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cart_coords.html
@@ -13,16 +13,16 @@ int MPI_Cart_coords(MPI_Comm comm, int rank, int maxdims, int coords[])
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>comm </B><DD>communicator with cartesian structure (handle) 
+<DT><B>comm </B><DD>communicator with cartesian structure (handle)
 
-<DT><B>rank </B><DD>rank of a process within group of <tt>comm</tt> (integer) 
+<DT><B>rank </B><DD>rank of a process within group of <TT>comm</TT> (integer)
 
-<DT><B>maxdims </B><DD>length of vector <tt>coords</tt> in the calling program (integer) 
+<DT><B>maxdims </B><DD>length of vector <TT>coords</TT> in the calling program (integer)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>coords </B> <DD> integer array (of size <tt>ndims</tt>) containing the Cartesian 
-coordinates of specified process (integer) 
+<DL><DT><B>coords </B> <DD> integer array (of size <TT>ndims</TT>) containing the Cartesian
+coordinates of specified process (integer)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -32,27 +32,27 @@ This means that this routine may safely be used by multiple threads and
 from within a signal handler.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -60,16 +60,16 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_TOPOLOGY </B> <DD> Invalid topology.  Either there is no topology 
 associated with this communicator, or it is not the correct type (e.g.,
-<tt>MPI_CART</tt> when expecting <tt>MPI_GRAPH</tt>).
+<TT>MPI_CART</TT> when expecting <TT>MPI_GRAPH</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_DIMS </B> <DD> Invalid dimension argument.  A dimension argument
 is null or its length is less than or equal to zero.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cart_create.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cart_create.html
index e9c7aff9..435ba675 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cart_create.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cart_create.html
@@ -10,60 +10,60 @@ Makes a new communicator to which topology information has been attached
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Cart_create(MPI_Comm comm_old, int ndims, const int dims[],
-                    const int periods[], int reorder, MPI_Comm *comm_cart)
+                    const int periods[], int reorder, MPI_Comm * comm_cart)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>comm_old </B><DD>input communicator (handle) 
+<DT><B>comm_old </B><DD>input communicator (handle)
 
-<DT><B>ndims </B><DD>number of dimensions of cartesian grid (integer) 
+<DT><B>ndims </B><DD>number of dimensions of cartesian grid (integer)
 
-<DT><B>dims </B><DD>integer array of size ndims specifying the number of processes in 
-each dimension 
+<DT><B>dims </B><DD>integer array of size ndims specifying the number of processes in
+each dimension
 
-<DT><B>periods </B><DD>logical array of size ndims specifying whether the grid is 
-periodic (true) or not (false) in each dimension 
+<DT><B>periods </B><DD>logical array of size ndims specifying whether the grid is
+periodic (true) or not (false) in each dimension
 
-<DT><B>reorder </B><DD>ranking may be reordered (true) or not (false) (logical) 
+<DT><B>reorder </B><DD>ranking may be reordered (true) or not (false) (logical)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>comm_cart </B> <DD> communicator with new cartesian topology (handle) 
+<DL><DT><B>comm_cart </B> <DD> communicator with new cartesian topology (handle)
 </DL>
 <P>
 <H2>Algorithm</H2>
-We ignore <tt>reorder</tt> info currently.
+We ignore <TT>reorder</TT> info currently.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -71,12 +71,12 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_TOPOLOGY </B> <DD> Invalid topology.  Either there is no topology 
 associated with this communicator, or it is not the correct type (e.g.,
-<tt>MPI_CART</tt> when expecting <tt>MPI_GRAPH</tt>).
+<TT>MPI_CART</TT> when expecting <TT>MPI_GRAPH</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_DIMS </B> <DD> Invalid dimension argument.  A dimension argument
 is null or its length is less than or equal to zero.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cart_get.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cart_get.html
index ccafe294..76682cc9 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cart_get.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cart_get.html
@@ -6,29 +6,28 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Cart_get"><H1>MPI_Cart_get</H1></A>
-Retrieves Cartesian topology information associated with a  communicator 
+Retrieves Cartesian topology information associated with a communicator 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Cart_get(MPI_Comm comm, int maxdims, int dims[], int periods[],
-                 int coords[])
+int MPI_Cart_get(MPI_Comm comm, int maxdims, int dims[], int periods[], int coords[])
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>comm </B><DD>communicator with cartesian structure (handle) 
+<DT><B>comm </B><DD>communicator with cartesian structure (handle)
 
-<DT><B>maxdims </B><DD>length of vectors  <tt>dims</tt>, <tt>periods</tt>, and <tt>coords
-</tt>in the calling program (integer) 
+<DT><B>maxdims </B><DD>length of vectors  <TT>dims</TT>, <TT>periods</TT>, and <TT>coords
+</TT>in the calling program (integer)
 </DL>
 <P>
 <H2>Output Parameters</H2>
 <DL>
-<DT><B>dims </B><DD>number of processes for each cartesian dimension (array of integer) 
+<DT><B>dims </B><DD>number of processes for each cartesian dimension (array of integer)
 
-<DT><B>periods </B><DD>periodicity (true/false) for each cartesian dimension 
-(array of logical) 
+<DT><B>periods </B><DD>periodicity (true/false) for each cartesian dimension
+(array of logical)
 
-<DT><B>coords </B><DD>coordinates of calling process in cartesian structure 
-(array of integer) 
+<DT><B>coords </B><DD>coordinates of calling process in cartesian structure
+(array of integer)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -36,31 +35,31 @@ int MPI_Cart_get(MPI_Comm comm, int maxdims, int dims[], int periods[],
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -68,12 +67,12 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_TOPOLOGY </B> <DD> Invalid topology.  Either there is no topology 
 associated with this communicator, or it is not the correct type (e.g.,
-<tt>MPI_CART</tt> when expecting <tt>MPI_GRAPH</tt>).
+<TT>MPI_CART</TT> when expecting <TT>MPI_GRAPH</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cart_map.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cart_map.html
index ff5a3cac..310a7640 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cart_map.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cart_map.html
@@ -6,28 +6,27 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Cart_map"><H1>MPI_Cart_map</H1></A>
-Maps process to Cartesian topology information  
+Maps process to Cartesian topology information 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Cart_map(MPI_Comm comm, int ndims, const int dims[], const int periods[],
-                int *newrank)
+int MPI_Cart_map(MPI_Comm comm, int ndims, const int dims[], const int periods[], int *newrank)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>comm </B><DD>input communicator (handle) 
+<DT><B>comm </B><DD>input communicator (handle)
 
-<DT><B>ndims </B><DD>number of dimensions of Cartesian structure (integer) 
+<DT><B>ndims </B><DD>number of dimensions of Cartesian structure (integer)
 
-<DT><B>dims </B><DD>integer array of size <tt>ndims</tt> specifying the number of processes in 
-each coordinate direction 
+<DT><B>dims </B><DD>integer array of size <TT>ndims</TT> specifying the number of processes in
+each coordinate direction
 
-<DT><B>periods </B><DD>logical array of size <tt>ndims</tt> specifying the periodicity 
-specification in each coordinate direction 
+<DT><B>periods </B><DD>logical array of size <TT>ndims</TT> specifying the periodicity
+specification in each coordinate direction
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>newrank </B> <DD> reordered rank of the calling process; <tt>MPI_UNDEFINED</tt> if 
-calling process does not belong to grid (integer) 
+<DL><DT><B>newrank </B> <DD> reordered rank of the calling process; <TT>MPI_UNDEFINED</TT> if
+calling process does not belong to grid (integer)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -37,39 +36,39 @@ This means that this routine may safely be used by multiple threads and
 from within a signal handler.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_DIMS </B> <DD> Invalid dimension argument.  A dimension argument
 is null or its length is less than or equal to zero.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cart_rank.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cart_rank.html
index 8156312e..53907aa3 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cart_rank.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cart_rank.html
@@ -13,20 +13,20 @@ int MPI_Cart_rank(MPI_Comm comm, const int coords[], int *rank)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>comm </B><DD>communicator with cartesian structure (handle) 
+<DT><B>comm </B><DD>communicator with cartesian structure (handle)
 
-<DT><B>coords </B><DD>integer array (of size <tt>ndims</tt>, the number of dimensions of
-the Cartesian topology associated with <tt>comm</tt>) specifying the cartesian 
-coordinates of a process 
+<DT><B>coords </B><DD>integer array (of size <TT>ndims</TT>, the number of dimensions of
+the Cartesian topology associated with <TT>comm</TT>) specifying the cartesian
+coordinates of a process
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>rank </B> <DD> rank of specified process (integer) 
+<DL><DT><B>rank </B> <DD> rank of specified process (integer)
 </DL>
 <P>
 <H2>Notes</H2>
 Out-of-range coordinates are erroneous for non-periodic dimensions.
-Versions of MPICH before 1.2.2 returned <tt>MPI_PROC_NULL</tt> for the rank in this
+Versions of MPICH before 1.2.2 returned <TT>MPI_PROC_NULL</TT> for the rank in this
 case.
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -36,27 +36,27 @@ This means that this routine may safely be used by multiple threads and
 from within a signal handler.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -64,13 +64,13 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_TOPOLOGY </B> <DD> Invalid topology.  Either there is no topology 
 associated with this communicator, or it is not the correct type (e.g.,
-<tt>MPI_CART</tt> when expecting <tt>MPI_GRAPH</tt>).
+<TT>MPI_CART</TT> when expecting <TT>MPI_GRAPH</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cart_shift.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cart_shift.html
index 6df35714..06bcdd8f 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cart_shift.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cart_shift.html
@@ -6,17 +6,16 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Cart_shift"><H1>MPI_Cart_shift</H1></A>
-Returns the shifted source and destination ranks, given a  shift direction and amount 
+Returns the shifted source and destination ranks, given a shift direction and amount 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Cart_shift(MPI_Comm comm, int direction, int disp, int *rank_source,
-                  int *rank_dest)
+int MPI_Cart_shift(MPI_Comm comm, int direction, int disp, int *rank_source, int *rank_dest)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>comm </B><DD>communicator with cartesian structure (handle) 
+<DT><B>comm </B><DD>communicator with cartesian structure (handle)
 
-<DT><B>direction </B><DD>coordinate dimension of shift (integer) 
+<DT><B>direction </B><DD>coordinate dimension of shift (integer)
 
 <DT><B>disp </B><DD>displacement (&gt; 0: upwards shift, &lt; 0: downwards shift) (integer)
 </DL>
@@ -29,7 +28,7 @@ int MPI_Cart_shift(MPI_Comm comm, int direction, int disp, int *rank_source,
 </DL>
 <P>
 <H2>Notes</H2>
-The <tt>direction</tt> argument is in the range <tt>[0,n-1]</tt> for an n-dimensional
+The <TT>direction</TT> argument is in the range <TT>[0,n-1]</TT> for an n-dimensional
 Cartesian mesh.
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -39,27 +38,27 @@ This means that this routine may safely be used by multiple threads and
 from within a signal handler.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -67,12 +66,12 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_TOPOLOGY </B> <DD> Invalid topology.  Either there is no topology 
 associated with this communicator, or it is not the correct type (e.g.,
-<tt>MPI_CART</tt> when expecting <tt>MPI_GRAPH</tt>).
+<TT>MPI_CART</TT> when expecting <TT>MPI_GRAPH</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cart_sub.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cart_sub.html
index 859bd41e..c89e1718 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cart_sub.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cart_sub.html
@@ -6,23 +6,23 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Cart_sub"><H1>MPI_Cart_sub</H1></A>
-Partitions a communicator into subgroups which  form lower-dimensional cartesian subgrids 
+Partitions a communicator into subgroups which form lower-dimensional cartesian subgrids 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Cart_sub(MPI_Comm comm, const int remain_dims[], MPI_Comm *newcomm)
+int MPI_Cart_sub(MPI_Comm comm, const int remain_dims[], MPI_Comm * newcomm)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>comm </B><DD>communicator with cartesian structure (handle) 
+<DT><B>comm </B><DD>communicator with cartesian structure (handle)
 
-<DT><B>remain_dims </B><DD>the  <tt>i</tt>th entry of remain_dims specifies whether the <tt>i</tt>th 
-dimension is kept in the subgrid (true) or is dropped (false) (logical 
-vector) 
+<DT><B>remain_dims </B><DD>the  <TT>i</TT>th entry of remain_dims specifies whether the <TT>i</TT>th
+dimension is kept in the subgrid (true) or is dropped (false) (logical
+vector)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>newcomm </B> <DD> communicator containing the subgrid that includes the calling 
-process (handle) 
+<DL><DT><B>newcomm </B> <DD> communicator containing the subgrid that includes the calling
+process (handle)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -30,31 +30,31 @@ process (handle)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -62,12 +62,12 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_TOPOLOGY </B> <DD> Invalid topology.  Either there is no topology 
 associated with this communicator, or it is not the correct type (e.g.,
-<tt>MPI_CART</tt> when expecting <tt>MPI_GRAPH</tt>).
+<TT>MPI_CART</TT> when expecting <TT>MPI_GRAPH</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cartdim_get.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cartdim_get.html
index 1c08a466..faddd09a 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cartdim_get.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Cartdim_get.html
@@ -6,17 +6,17 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Cartdim_get"><H1>MPI_Cartdim_get</H1></A>
-Retrieves Cartesian topology information associated with a  communicator 
+Retrieves Cartesian topology information associated with a communicator 
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Cartdim_get(MPI_Comm comm, int *ndims)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>comm </B> <DD> communicator with cartesian structure (handle) 
+<DL><DT><B>comm </B> <DD> communicator with cartesian structure (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>ndims </B> <DD> number of dimensions of the cartesian structure (integer) 
+<DL><DT><B>ndims </B> <DD> number of dimensions of the cartesian structure (integer)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -26,36 +26,36 @@ This means that this routine may safely be used by multiple threads and
 from within a signal handler.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Close_port.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Close_port.html
index 139890c2..e17d1569 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Close_port.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Close_port.html
@@ -24,32 +24,32 @@ not be used from within a signal handler.
 The MPI standard defined a thread-safe interface but this does not
 mean that all routines may be called without any thread locks.  For
 example, two threads must not attempt to change the contents of the
-same <tt>MPI_Info</tt> object concurrently.  The user is responsible in this
+same <TT>MPI_Info</TT> object concurrently.  The user is responsible in this
 case for using some mechanism, such as thread locks, to ensure that
 only one thread at a time makes use of this routine.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_accept.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_accept.html
index 0b17b57a..01a9e0a1 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_accept.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_accept.html
@@ -10,21 +10,21 @@ Accept a request to form a new intercommunicator
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Comm_accept(const char *port_name, MPI_Info info, int root, MPI_Comm comm,
-                    MPI_Comm *newcomm)
+                    MPI_Comm * newcomm)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>port_name </B><DD>port name (string, used only on root) 
+<DT><B>port_name </B><DD>port name (string, used only on root)
 
-<DT><B>info </B><DD>implementation-dependent information (handle, used only on root) 
+<DT><B>info </B><DD>implementation-dependent information (handle, used only on root)
 
-<DT><B>root </B><DD>rank in comm of root node (integer) 
+<DT><B>root </B><DD>rank in comm of root node (integer)
 
 <DT><B>comm </B><DD>intracommunicator over which call is collective (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>newcomm </B> <DD> intercommunicator with client as remote group (handle) 
+<DL><DT><B>newcomm </B> <DD> intercommunicator with client as remote group (handle)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -32,31 +32,31 @@ int MPI_Comm_accept(const char *port_name, MPI_Info info, int root, MPI_Comm com
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -65,6 +65,6 @@ possible.
 <DL><DT><B>MPI_ERR_INFO </B> <DD> Invalid Info 
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_call_errhandler.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_call_errhandler.html
index 297cd55c..c0b08719 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_call_errhandler.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_call_errhandler.html
@@ -6,16 +6,16 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Comm_call_errhandler"><H1>MPI_Comm_call_errhandler</H1></A>
-Call the error handler installed on a  communicator 
+Call the error handler installed on a communicator 
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Comm_call_errhandler(MPI_Comm comm, int errorcode)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>comm </B><DD>communicator with error handler (handle) 
+<DT><B>comm </B><DD>communicator with error handler (handle)
 
-<DT><B>errorcode </B><DD>error code (integer) 
+<DT><B>errorcode </B><DD>error code (integer)
 </DL>
 <P>
 <H2>Note</H2>
@@ -32,39 +32,39 @@ with this routine.
 The MPI standard defined a thread-safe interface but this does not
 mean that all routines may be called without any thread locks.  For
 example, two threads must not attempt to change the contents of the
-same <tt>MPI_Info</tt> object concurrently.  The user is responsible in this
+same <TT>MPI_Info</TT> object concurrently.  The user is responsible in this
 case for using some mechanism, such as thread locks, to ensure that
 only one thread at a time makes use of this routine.
 <P>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_compare.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_compare.html
index 21c9e445..3b910b51 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_compare.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_compare.html
@@ -13,68 +13,68 @@ int MPI_Comm_compare(MPI_Comm comm1, MPI_Comm comm2, int *result)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>comm1 </B><DD>comm1 (handle) 
+<DT><B>comm1 </B><DD>comm1 (handle)
 
-<DT><B>comm2 </B><DD>comm2 (handle) 
+<DT><B>comm2 </B><DD>comm2 (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>result </B> <DD> integer which is <tt>MPI_IDENT</tt> if the contexts and groups are the
-same, <tt>MPI_CONGRUENT</tt> if different contexts but identical groups, <tt>MPI_SIMILAR
-</tt>if different contexts but similar groups, and <tt>MPI_UNEQUAL</tt> otherwise
+<DL><DT><B>result </B> <DD> integer which is <TT>MPI_IDENT</TT> if the contexts and groups are the
+same, <TT>MPI_CONGRUENT</TT> if different contexts but identical groups, <TT>MPI_SIMILAR
+</TT>if different contexts but similar groups, and <TT>MPI_UNEQUAL</TT> otherwise
 </DL>
 <P>
 <H2>Using 'MPI_COMM_NULL' with 'MPI_Comm_compare'</H2>
 <P>
-It is an error to use <tt>MPI_COMM_NULL</tt> as one of the arguments to
-<tt>MPI_Comm_compare</tt>.  The relevant sections of the MPI standard are
+It is an error to use <TT>MPI_COMM_NULL</TT> as one of the arguments to
+<TT>MPI_Comm_compare</TT>.  The relevant sections of the MPI standard are
 <P>
 .(2.4.1 Opaque Objects)
-A null handle argument is an erroneous <tt>IN</tt> argument in MPI calls, unless an
+A null handle argument is an erroneous <TT>IN</TT> argument in MPI calls, unless an
 exception is explicitly stated in the text that defines the function.
 <P>
 .(5.4.1. Communicator Accessors)
-where there is no text in <tt>MPI_COMM_COMPARE</tt> allowing a null handle.
+where there is no text in <TT>MPI_COMM_COMPARE</TT> allowing a null handle.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 (To perform the communicator comparisions, this routine may need to
 allocate some memory.  Memory allocation is not interrupt-safe, and hence
 this routine is only thread-safe.)
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_connect.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_connect.html
index 97602406..f5dbebb4 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_connect.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_connect.html
@@ -10,21 +10,21 @@ Make a request to form a new intercommunicator
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Comm_connect(const char *port_name, MPI_Info info, int root, MPI_Comm comm,
-                     MPI_Comm *newcomm)
+                     MPI_Comm * newcomm)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>port_name </B><DD>network address (string, used only on root) 
+<DT><B>port_name </B><DD>network address (string, used only on root)
 
-<DT><B>info </B><DD>implementation-dependent information (handle, used only on root) 
+<DT><B>info </B><DD>implementation-dependent information (handle, used only on root)
 
-<DT><B>root </B><DD>rank in comm of root node (integer) 
+<DT><B>root </B><DD>rank in comm of root node (integer)
 
-<DT><B>comm </B><DD>intracommunicator over which call is collective (handle) 
+<DT><B>comm </B><DD>intracommunicator over which call is collective (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>newcomm </B> <DD> intercommunicator with server as remote group (handle) 
+<DL><DT><B>newcomm </B> <DD> intercommunicator with server as remote group (handle)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -32,38 +32,38 @@ int MPI_Comm_connect(const char *port_name, MPI_Info info, int root, MPI_Comm co
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_INFO </B> <DD> Invalid Info 
 </DL>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_create.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_create.html
index b4a874b3..03e780e6 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_create.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_create.html
@@ -9,13 +9,13 @@
 Creates a new communicator 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Comm_create(MPI_Comm comm, MPI_Group group, MPI_Comm *newcomm)
+int MPI_Comm_create(MPI_Comm comm, MPI_Group group, MPI_Comm * newcomm)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 
-<DT><B>group </B><DD>group, which is a subset of the group of <tt>comm</tt>  (handle) 
+<DT><B>group </B><DD>group, which is a subset of the group of <TT>comm</TT>  (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
@@ -27,43 +27,43 @@ int MPI_Comm_create(MPI_Comm comm, MPI_Group group, MPI_Comm *newcomm)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_GROUP </B> <DD> Null or invalid group passed to function.  
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Comm_free
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_create_errhandler.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_create_errhandler.html
index d56b1ee3..b2d9a247 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_create_errhandler.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_create_errhandler.html
@@ -9,15 +9,15 @@
 Create a communicator error handler 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Comm_create_errhandler(MPI_Comm_errhandler_function *comm_errhandler_fn,
-                               MPI_Errhandler *errhandler)
+int MPI_Comm_create_errhandler(MPI_Comm_errhandler_function * comm_errhandler_fn,
+                               MPI_Errhandler * errhandler)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>comm_errhandler_fn </B> <DD> user defined error handling procedure (function)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>errhandler </B> <DD> MPI error handler (handle) 
+<DL><DT><B>errhandler </B> <DD> MPI error handler (handle)
 </DL>
 <P>
 <H2>Error Handler</H2>
@@ -30,40 +30,40 @@ void MPI_Comm_errhandler_function(MPI_Comm *comm, int *rc);
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_create_group.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_create_group.html
index e4920b95..05573dcd 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_create_group.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_create_group.html
@@ -15,7 +15,7 @@ int MPI_Comm_create_group(MPI_Comm comm, MPI_Group group, int tag, MPI_Comm * ne
 <DL>
 <DT><B>comm </B><DD>communicator (handle)
 
-<DT><B>group </B><DD>group, which is a subset of the group of <tt>comm</tt>  (handle)
+<DT><B>group </B><DD>group, which is a subset of the group of <TT>comm</TT>  (handle)
 
 <DT><B>tag </B><DD>safe tag unused by other communication
 </DL>
@@ -29,43 +29,43 @@ int MPI_Comm_create_group(MPI_Comm comm, MPI_Group group, int tag, MPI_Comm * ne
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_GROUP </B> <DD> Null or invalid group passed to function.  
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Comm_free
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_create_keyval.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_create_keyval.html
index 4f360666..4703cb4d 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_create_keyval.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_create_keyval.html
@@ -6,24 +6,24 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Comm_create_keyval"><H1>MPI_Comm_create_keyval</H1></A>
-Create a new attribute key  
+Create a new attribute key 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Comm_create_keyval(MPI_Comm_copy_attr_function *comm_copy_attr_fn, 
-                         MPI_Comm_delete_attr_function *comm_delete_attr_fn, 
-                         int *comm_keyval, void *extra_state)
+int MPI_Comm_create_keyval(MPI_Comm_copy_attr_function * comm_copy_attr_fn,
+                           MPI_Comm_delete_attr_function * comm_delete_attr_fn,
+                           int *comm_keyval, void *extra_state)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>comm_copy_attr_fn </B><DD>Copy callback function for <tt>keyval
-</tt>
-<DT><B>comm_delete_attr_fn </B><DD>Delete callback function for <tt>keyval
-</tt>
-<DT><B>extra_state </B><DD>Extra state for callback functions 
+<DT><B>comm_copy_attr_fn </B><DD>Copy callback function for <TT>keyval
+</TT>
+<DT><B>comm_delete_attr_fn </B><DD>Delete callback function for <TT>keyval
+</TT>
+<DT><B>extra_state </B><DD>Extra state for callback functions
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>comm_keyval </B> <DD> key value for future access (integer) 
+<DL><DT><B>comm_keyval </B> <DD> key value for future access (integer)
 </DL>
 <P>
 <H2>Notes</H2>
@@ -39,17 +39,17 @@ Default copy and delete functions are available.  These are
 </DL>
 <P>
 There are subtle differences between C and Fortran that require that the
-copy_fn be written in the same language from which <tt>MPI_Comm_create_keyval
-</tt>is called.
+copy_fn be written in the same language from which <TT>MPI_Comm_create_keyval
+</TT>is called.
 This should not be a problem for most users; only programmers using both
 Fortran and C in the same program need to be sure that they follow this rule.
 <P>
 <P>
 <H2>Return value from attribute callbacks</H2>
 The MPI-2 versions of the attribute callbacks should return either
-<tt>MPI_SUCCESS</tt> on success or a valid MPI error code or class on failure.
+<TT>MPI_SUCCESS</TT> on success or a valid MPI error code or class on failure.
 The MPI standard is ambiguous on this point, but as MPI-2 provides
-the routines <tt>MPI_Add_error_class</tt> and <tt>MPI_Add_error_code</tt> that allow the
+the routines <TT>MPI_Add_error_class</TT> and <TT>MPI_Add_error_code</TT> that allow the
 user to define and use MPI error codes and classes.
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -57,38 +57,38 @@ user to define and use MPI error codes and classes.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
 MPI_Comm_free_keyval
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_delete_attr.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_delete_attr.html
index 28901504..c37c27c5 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_delete_attr.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_delete_attr.html
@@ -6,16 +6,16 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Comm_delete_attr"><H1>MPI_Comm_delete_attr</H1></A>
-Deletes an attribute value associated with a key on  a  communicator 
+Deletes an attribute value associated with a key on a  communicator 
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Comm_delete_attr(MPI_Comm comm, int comm_keyval)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>comm </B><DD>communicator to which attribute is attached (handle) 
+<DT><B>comm </B><DD>communicator to which attribute is attached (handle)
 
-<DT><B>comm_keyval </B><DD>The key value of the deleted attribute (integer) 
+<DT><B>comm_keyval </B><DD>The key value of the deleted attribute (integer)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -23,44 +23,44 @@ int MPI_Comm_delete_attr(MPI_Comm comm, int comm_keyval)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> This error class is associated with an error code that 
 indicates that an attempt was made to free one of the permanent keys.
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
 MPI_Comm_set_attr, MPI_Comm_create_keyval
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_disconnect.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_disconnect.html
index 04535204..d4ff7c90 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_disconnect.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_disconnect.html
@@ -12,51 +12,51 @@ Disconnect from a communicator
 int MPI_Comm_disconnect(MPI_Comm * comm)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>comm </B> <DD> communicator (handle) 
+<DL><DT><B>comm </B> <DD> communicator (handle)
 </DL>
 <P>
 <H2>Notes</H2>
 This routine waits for all pending communication to complete, then frees the
-communicator and sets <tt>comm</tt> to <tt>MPI_COMM_NULL</tt>.  It may not be called
-with <tt>MPI_COMM_WORLD</tt> or <tt>MPI_COMM_SELF</tt>.
+communicator and sets <TT>comm</TT> to <TT>MPI_COMM_NULL</TT>.  It may not be called
+with <TT>MPI_COMM_WORLD</TT> or <TT>MPI_COMM_SELF</TT>.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
 MPI_Comm_connect, MPI_Comm_join
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_dup.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_dup.html
index 8ff8dd72..88f16a45 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_dup.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_dup.html
@@ -9,25 +9,25 @@
 Duplicates an existing communicator with all its cached information 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Comm_dup(MPI_Comm comm, MPI_Comm *newcomm)
+int MPI_Comm_dup(MPI_Comm comm, MPI_Comm * newcomm)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>comm </B> <DD> Communicator to be duplicated (handle) 
+<DL><DT><B>comm </B> <DD> Communicator to be duplicated (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>newcomm </B> <DD> A new communicator over the same group as <tt>comm</tt> but with a new
-context. See notes.  (handle) 
+<DL><DT><B>newcomm </B> <DD> A new communicator over the same group as <TT>comm</TT> but with a new
+context. See notes.  (handle)
 </DL>
 <P>
 <H2>Notes</H2>
 This routine is used to create a new communicator that has a new
 communication context but contains the same group of processes as
 the input communicator.  Since all MPI communication is performed
-within a communicator (specifies as the group of processes <em>plus
-</em>the context), this routine provides an effective way to create a
+within a communicator (specifies as the group of processes <EM>plus
+</EM>the context), this routine provides an effective way to create a
 private communicator for use by a software module or library.  In
-particular, no library routine should use <tt>MPI_COMM_WORLD</tt> as the
+particular, no library routine should use <TT>MPI_COMM_WORLD</TT> as the
 communicator; instead, a duplicate of a user-specified communicator
 should always be used.  For more information, see Using MPI, 2nd
 edition.
@@ -35,53 +35,53 @@ edition.
 Because this routine essentially produces a copy of a communicator,
 it also copies any attributes that have been defined on the input
 communicator, using the attribute copy function specified by the
-<tt>copy_function</tt> argument to <tt>MPI_Keyval_create</tt>.  This is
+<TT>copy_function</TT> argument to <TT>MPI_Keyval_create</TT>.  This is
 particularly useful for (a) attributes that describe some property
 of the group associated with the communicator, such as its
 interconnection topology and (b) communicators that are given back
 to the user; the attibutes in this case can track subsequent
-<tt>MPI_Comm_dup</tt> operations on this communicator.
+<TT>MPI_Comm_dup</TT> operations on this communicator.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Comm_free, MPI_Keyval_create, MPI_Attr_put, MPI_Attr_delete,
-<br>MPI_Comm_create_keyval, MPI_Comm_set_attr, MPI_Comm_delete_attr
+<BR>MPI_Comm_create_keyval, MPI_Comm_set_attr, MPI_Comm_delete_attr
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_dup_with_info.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_dup_with_info.html
index e1aa72fc..6b48da91 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_dup_with_info.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_dup_with_info.html
@@ -19,7 +19,7 @@ int MPI_Comm_dup_with_info(MPI_Comm comm, MPI_Info info, MPI_Comm * newcomm)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>newcomm </B> <DD> A new communicator over the same group as <tt>comm</tt> but with a new
+<DL><DT><B>newcomm </B> <DD> A new communicator over the same group as <TT>comm</TT> but with a new
 context. See notes.  (handle)
 </DL>
 <P>
@@ -34,42 +34,42 @@ associated with the output communicator newcomm instead.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Comm_dup, MPI_Comm_free, MPI_Keyval_create,
-<br>MPI_Attr_put, MPI_Attr_delete, MPI_Comm_create_keyval,
+<BR>MPI_Attr_put, MPI_Attr_delete, MPI_Comm_create_keyval,
 MPI_Comm_set_attr, MPI_Comm_delete_attr
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_free.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_free.html
index 5c6c5e39..56c20007 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_free.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_free.html
@@ -9,14 +9,14 @@
 Marks the communicator object for deallocation 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Comm_free(MPI_Comm *comm)
+int MPI_Comm_free(MPI_Comm * comm)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>comm </B> <DD> Communicator to be destroyed (handle) 
+<DL><DT><B>comm </B> <DD> Communicator to be destroyed (handle)
 </DL>
 <P>
 <H2>Notes</H2>
-This routine <em>frees</em> a communicator.  Because the communicator may still
+This routine <EM>frees</EM> a communicator.  Because the communicator may still
 be in use by other MPI routines, the actual communicator storage will not
 be freed until all references to this communicator are removed.  For most
 users, the effect of this routine is the same as if it was in fact freed
@@ -29,7 +29,7 @@ The MPI 1.1 specification, in the section on opaque objects, explicitly
  A null handle argument is an erroneous IN argument in MPI calls, unless an
  exception is explicitly stated in the text that defines the function. Such
  exception is allowed for handles to request objects in Wait and Test calls
- (sections Communication Completion and Multiple Completions ). Otherwise, a
+ (sections Communication Completion and Multiple Completions). Otherwise, a
  null handle can only be passed to a function that allocates a new object and
  returns a reference to it in the handle.
 </PRE>
@@ -40,40 +40,40 @@ The MPI 1.1 specification, in the section on opaque objects, explicitly
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_free_keyval.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_free_keyval.html
index b3bc9e1c..6f70dcbb 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_free_keyval.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_free_keyval.html
@@ -12,7 +12,7 @@ Frees an attribute key for communicators
 int MPI_Comm_free_keyval(int *comm_keyval)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>comm_keyval </B> <DD> Frees the integer key value (integer) 
+<DL><DT><B>comm_keyval </B> <DD> Frees the integer key value (integer)
 </DL>
 <P>
 <H2>Notes</H2>
@@ -23,38 +23,38 @@ Key values are global (they can be used with any and all communicators)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> This error class is associated with an error code that 
 indicates that an attempt was made to free one of the permanent keys.
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_get_attr.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_get_attr.html
index a1e283a0..df18985c 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_get_attr.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_get_attr.html
@@ -9,31 +9,30 @@
 Retrieves attribute value by key 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Comm_get_attr(MPI_Comm comm, int comm_keyval, void *attribute_val, 
-                     int *flag)
+int MPI_Comm_get_attr(MPI_Comm comm, int comm_keyval, void *attribute_val, int *flag)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>comm </B><DD>communicator to which attribute is attached (handle) 
+<DT><B>comm </B><DD>communicator to which attribute is attached (handle)
 
 <DT><B>comm_keyval </B><DD>key value (integer)
 </DL>
 <P>
 <H2>Output Parameters</H2>
 <DL>
-<DT><B>attribute_val </B><DD>attribute value, unless <tt>flag</tt> = false
+<DT><B>attribute_val </B><DD>attribute value, unless <TT>flag</TT> = false
 
 <DT><B>flag </B><DD>true if an attribute value was extracted;  false if no attribute is
-associated with the key 
+associated with the key
 </DL>
 <P>
 <H2>Notes</H2>
 Attributes must be extracted from the same language as they were inserted
-in with <tt>MPI_Comm_set_attr</tt>.  The notes for C and Fortran below explain
+in with <TT>MPI_Comm_set_attr</TT>.  The notes for C and Fortran below explain
 why.
 <P>
 <H2>Notes for C</H2>
-Even though the <tt>attr_value</tt> argument is declared as <tt>void *</tt>, it is
+Even though the <TT>attr_value</TT> argument is declared as <TT>void *</TT>, it is
 really the address of a void pointer.  See the rationale in the
 standard for more details.
 <P>
@@ -42,38 +41,38 @@ standard for more details.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_KEYVAL </B> <DD> Invalid keyval
 </DL>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_get_errhandler.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_get_errhandler.html
index 1ed4b5ff..f288c430 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_get_errhandler.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_get_errhandler.html
@@ -9,14 +9,14 @@
 Get the error handler attached to a communicator 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Comm_get_errhandler(MPI_Comm comm, MPI_Errhandler *errhandler)
+int MPI_Comm_get_errhandler(MPI_Comm comm, MPI_Errhandler * errhandler)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>comm </B> <DD> communicator (handle) 
+<DL><DT><B>comm </B> <DD> communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>errhandler </B> <DD> handler currently associated with communicator (handle) 
+<DL><DT><B>errhandler </B> <DD> handler currently associated with communicator (handle)
 </DL>
 <P>
 <P>
@@ -29,39 +29,39 @@ with this routine.
 The MPI standard defined a thread-safe interface but this does not
 mean that all routines may be called without any thread locks.  For
 example, two threads must not attempt to change the contents of the
-same <tt>MPI_Info</tt> object concurrently.  The user is responsible in this
+same <TT>MPI_Info</TT> object concurrently.  The user is responsible in this
 case for using some mechanism, such as thread locks, to ensure that
 only one thread at a time makes use of this routine.
 <P>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_get_info.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_get_info.html
index 491e0b0e..b35fd6ca 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_get_info.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_get_info.html
@@ -24,41 +24,41 @@ int MPI_Comm_get_info(MPI_Comm comm, MPI_Info * info_used)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_INFO </B> <DD> Invalid Info 
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_get_name.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_get_name.html
index bd80580c..a2ba4338 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_get_name.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_get_name.html
@@ -18,16 +18,16 @@ int MPI_Comm_get_name(MPI_Comm comm, char *comm_name, int *resultlen)
 <H2>Output Parameters</H2>
 <DL>
 <DT><B>comm_name </B><DD>On output, contains the name of the communicator.  It must
-be an array of size at least <tt>MPI_MAX_OBJECT_NAME</tt>.
+be an array of size at least <TT>MPI_MAX_OBJECT_NAME</TT>.
 
 <DT><B>resultlen </B><DD>Number of characters in name
 </DL>
 <P>
 <H2>Notes</H2>
 <P>
-Because MPI specifies that null objects (e.g., <tt>MPI_COMM_NULL</tt>) are invalid
-as input to MPI routines unless otherwise specified, using <tt>MPI_COMM_NULL
-</tt>as input to this routine is an error.
+Because MPI specifies that null objects (e.g., <TT>MPI_COMM_NULL</TT>) are invalid
+as input to MPI routines unless otherwise specified, using <TT>MPI_COMM_NULL
+</TT>as input to this routine is an error.
 <P>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -39,39 +39,39 @@ with this routine.
 The MPI standard defined a thread-safe interface but this does not
 mean that all routines may be called without any thread locks.  For
 example, two threads must not attempt to change the contents of the
-same <tt>MPI_Info</tt> object concurrently.  The user is responsible in this
+same <TT>MPI_Info</TT> object concurrently.  The user is responsible in this
 case for using some mechanism, such as thread locks, to ensure that
 only one thread at a time makes use of this routine.
 <P>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_get_parent.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_get_parent.html
index 6bb11cc2..da04bdd0 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_get_parent.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_get_parent.html
@@ -9,25 +9,25 @@
 Return the parent communicator for this process 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Comm_get_parent(MPI_Comm *parent)
+int MPI_Comm_get_parent(MPI_Comm * parent)
 </PRE>
 <H2>Output Parameters</H2>
-<DL><DT><B>parent </B> <DD> the parent communicator (handle) 
+<DL><DT><B>parent </B> <DD> the parent communicator (handle)
 </DL>
 <P>
 <H2>Notes</H2>
 <P>
-If a process was started with <tt>MPI_Comm_spawn</tt> or <tt>MPI_Comm_spawn_multiple</tt>,
-<tt>MPI_Comm_get_parent</tt> returns the parent intercommunicator of the current
+If a process was started with <TT>MPI_Comm_spawn</TT> or <TT>MPI_Comm_spawn_multiple</TT>,
+<TT>MPI_Comm_get_parent</TT> returns the parent intercommunicator of the current
 process. This parent intercommunicator is created implicitly inside of
-<tt>MPI_Init</tt> and is the same intercommunicator returned by <tt>MPI_Comm_spawn
-</tt>in the parents.
+<TT>MPI_Init</TT> and is the same intercommunicator returned by <TT>MPI_Comm_spawn
+</TT>in the parents.
 <P>
-If the process was not spawned, <tt>MPI_Comm_get_parent</tt> returns
-<tt>MPI_COMM_NULL</tt>.
+If the process was not spawned, <TT>MPI_Comm_get_parent</TT> returns
+<TT>MPI_COMM_NULL</TT>.
 <P>
-After the parent communicator is freed or disconnected, <tt>MPI_Comm_get_parent
-</tt>returns <tt>MPI_COMM_NULL</tt>.
+After the parent communicator is freed or disconnected, <TT>MPI_Comm_get_parent
+</TT>returns <TT>MPI_COMM_NULL</TT>.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
@@ -36,33 +36,33 @@ This means that this routine may safely be used by multiple threads and
 from within a signal handler.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_group.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_group.html
index 369c0788..1549cf5f 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_group.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_group.html
@@ -9,7 +9,7 @@
 Accesses the group associated with given communicator 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Comm_group(MPI_Comm comm, MPI_Group *group)
+int MPI_Comm_group(MPI_Comm comm, MPI_Group * group)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>comm </B> <DD> Communicator (handle)
@@ -20,46 +20,46 @@ int MPI_Comm_group(MPI_Comm comm, MPI_Group *group)
 </DL>
 <P>
 <H2>Notes</H2>
-Because MPI specifies that null objects (e.g., <tt>MPI_COMM_NULL</tt>) are invalid
-as input to MPI routines unless otherwise specified, using <tt>MPI_COMM_NULL
-</tt>as input to this routine is an error.
+Because MPI specifies that null objects (e.g., <TT>MPI_COMM_NULL</TT>) are invalid
+as input to MPI routines unless otherwise specified, using <TT>MPI_COMM_NULL
+</TT>as input to this routine is an error.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_idup.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_idup.html
index b0997188..afca3193 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_idup.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_idup.html
@@ -9,7 +9,7 @@
 nonblocking communicator duplication 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Comm_idup(MPI_Comm comm, MPI_Comm *newcomm, MPI_Request *request)
+int MPI_Comm_idup(MPI_Comm comm, MPI_Comm * newcomm, MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>comm </B> <DD> communicator (handle)
@@ -27,31 +27,31 @@ int MPI_Comm_idup(MPI_Comm comm, MPI_Comm *newcomm, MPI_Request *request)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_join.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_join.html
index 7bc72a02..438e5823 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_join.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_join.html
@@ -6,61 +6,61 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Comm_join"><H1>MPI_Comm_join</H1></A>
-Create a communicator by joining two processes connected by  a socket. 
+Create a communicator by joining two processes connected by a socket. 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Comm_join(int fd, MPI_Comm *intercomm)
+int MPI_Comm_join(int fd, MPI_Comm * intercomm)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>fd </B> <DD> socket file descriptor 
+<DL><DT><B>fd </B> <DD> socket file descriptor
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>intercomm </B> <DD> new intercommunicator (handle) 
+<DL><DT><B>intercomm </B> <DD> new intercommunicator (handle)
 </DL>
 <P>
 <H2>Notes</H2>
-The socket must be quiescent before <tt>MPI_COMM_JOIN</tt> is called and after
-<tt>MPI_COMM_JOIN</tt> returns. More specifically, on entry to <tt>MPI_COMM_JOIN</tt>, a
+The socket must be quiescent before <TT>MPI_COMM_JOIN</TT> is called and after
+<TT>MPI_COMM_JOIN</TT> returns. More specifically, on entry to <TT>MPI_COMM_JOIN</TT>, a
 read on the socket will not read any data that was written to the socket
-before the remote process called <tt>MPI_COMM_JOIN</tt>.
+before the remote process called <TT>MPI_COMM_JOIN</TT>.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_rank.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_rank.html
index 5e509936..79450eba 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_rank.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_rank.html
@@ -9,14 +9,14 @@
 Determines the rank of the calling process in the communicator 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Comm_rank( MPI_Comm comm, int *rank ) 
+int MPI_Comm_rank(MPI_Comm comm, int *rank)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>comm </B> <DD> communicator (handle) 
+<DL><DT><B>comm </B> <DD> communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>rank </B> <DD> rank of the calling process in the group of <tt>comm</tt>  (integer) 
+<DL><DT><B>rank </B> <DD> rank of the calling process in the group of <TT>comm</TT>  (integer)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -26,33 +26,33 @@ This means that this routine may safely be used by multiple threads and
 from within a signal handler.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_remote_group.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_remote_group.html
index 214eb2ac..a2f06bcc 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_remote_group.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_remote_group.html
@@ -6,10 +6,10 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Comm_remote_group"><H1>MPI_Comm_remote_group</H1></A>
-Accesses the remote group associated with  the given inter-communicator 
+Accesses the remote group associated with the given inter-communicator 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Comm_remote_group(MPI_Comm comm, MPI_Group *group)
+int MPI_Comm_remote_group(MPI_Comm comm, MPI_Group * group)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>comm </B> <DD> Communicator (must be an intercommunicator) (handle)
@@ -27,41 +27,41 @@ The user is responsible for freeing the group when it is no longer needed.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
 MPI_Group_free
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_remote_size.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_remote_size.html
index 730534cf..9890fe96 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_remote_size.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_remote_size.html
@@ -6,17 +6,17 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Comm_remote_size"><H1>MPI_Comm_remote_size</H1></A>
-Determines the size of the remote group  associated with an inter-communictor 
+Determines the size of the remote group associated with an inter-communictor 
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Comm_remote_size(MPI_Comm comm, int *size)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>comm </B> <DD> communicator (handle) 
+<DL><DT><B>comm </B> <DD> communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>size </B> <DD> number of processes in the remote group of <tt>comm</tt>  (integer) 
+<DL><DT><B>size </B> <DD> number of processes in the remote group of <TT>comm</TT>  (integer)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -26,36 +26,36 @@ This means that this routine may safely be used by multiple threads and
 from within a signal handler.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_set_attr.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_set_attr.html
index dd0c8c80..24de743d 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_set_attr.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_set_attr.html
@@ -13,21 +13,21 @@ int MPI_Comm_set_attr(MPI_Comm comm, int comm_keyval, void *attribute_val)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>comm </B><DD>communicator to which attribute will be attached (handle) 
+<DT><B>comm </B><DD>communicator to which attribute will be attached (handle)
 
-<DT><B>comm_keyval </B><DD>key value, as returned by  <tt>MPI_Comm_create_keyval</tt> (integer)
+<DT><B>comm_keyval </B><DD>key value, as returned by  <TT>MPI_Comm_create_keyval</TT> (integer)
 
-<DT><B>attribute_val </B><DD>attribute value 
+<DT><B>attribute_val </B><DD>attribute value
 </DL>
 <P>
 <H2>Notes</H2>
-Values of the permanent attributes <tt>MPI_TAG_UB</tt>, <tt>MPI_HOST</tt>, <tt>MPI_IO</tt>,
-<tt>MPI_WTIME_IS_GLOBAL</tt>, <tt>MPI_UNIVERSE_SIZE</tt>, <tt>MPI_LASTUSEDCODE</tt>, and
-<tt>MPI_APPNUM</tt> may not be changed.
+Values of the permanent attributes <TT>MPI_TAG_UB</TT>, <TT>MPI_HOST</TT>, <TT>MPI_IO</TT>,
+<TT>MPI_WTIME_IS_GLOBAL</TT>, <TT>MPI_UNIVERSE_SIZE</TT>, <TT>MPI_LASTUSEDCODE</TT>, and
+<TT>MPI_APPNUM</TT> may not be changed.
 <P>
 The type of the attribute value depends on whether C, C++, or Fortran
 is being used.
-In C and C++, an attribute value is a pointer (<tt>void *</tt>); in Fortran, it is an
+In C and C++, an attribute value is a pointer (<TT>void *</TT>); in Fortran, it is an
 address-sized integer.
 <P>
 If an attribute is already present, the delete function (specified when the
@@ -38,38 +38,38 @@ corresponding keyval was created) will be called.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_KEYVAL </B> <DD> Invalid keyval
 </DL>
@@ -77,7 +77,7 @@ communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
 indicates that an attempt was made to free one of the permanent keys.
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
 MPI_Comm_create_keyval, MPI_Comm_delete_attr
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_set_errhandler.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_set_errhandler.html
index 93e3836c..c2283589 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_set_errhandler.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_set_errhandler.html
@@ -13,9 +13,9 @@ int MPI_Comm_set_errhandler(MPI_Comm comm, MPI_Errhandler errhandler)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 
-<DT><B>errhandler </B><DD>new error handler for communicator (handle) 
+<DT><B>errhandler </B><DD>new error handler for communicator (handle)
 </DL>
 <P>
 <P>
@@ -28,46 +28,46 @@ with this routine.
 The MPI standard defined a thread-safe interface but this does not
 mean that all routines may be called without any thread locks.  For
 example, two threads must not attempt to change the contents of the
-same <tt>MPI_Info</tt> object concurrently.  The user is responsible in this
+same <TT>MPI_Info</TT> object concurrently.  The user is responsible in this
 case for using some mechanism, such as thread locks, to ensure that
 only one thread at a time makes use of this routine.
 <P>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
 MPI_Comm_get_errhandler, MPI_Comm_call_errhandler
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_set_info.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_set_info.html
index f2694693..4f44628c 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_set_info.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_set_info.html
@@ -23,41 +23,41 @@ int MPI_Comm_set_info(MPI_Comm comm, MPI_Info info)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_INFO </B> <DD> Invalid Info 
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_set_name.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_set_name.html
index e3f817fb..c5a44209 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_set_name.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_set_name.html
@@ -28,39 +28,39 @@ with this routine.
 The MPI standard defined a thread-safe interface but this does not
 mean that all routines may be called without any thread locks.  For
 example, two threads must not attempt to change the contents of the
-same <tt>MPI_Info</tt> object concurrently.  The user is responsible in this
+same <TT>MPI_Info</TT> object concurrently.  The user is responsible in this
 case for using some mechanism, such as thread locks, to ensure that
 only one thread at a time makes use of this routine.
 <P>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_size.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_size.html
index a5c05881..c473e439 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_size.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_size.html
@@ -9,14 +9,14 @@
 Determines the size of the group associated with a communicator 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Comm_size( MPI_Comm comm, int *size ) 
+int MPI_Comm_size(MPI_Comm comm, int *size)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>comm </B> <DD> communicator (handle) 
+<DL><DT><B>comm </B> <DD> communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>size </B> <DD> number of processes in the group of <tt>comm</tt>  (integer) 
+<DL><DT><B>size </B> <DD> number of processes in the group of <TT>comm</TT>  (integer)
 </DL>
 <P>
 <H2>Notes</H2>
@@ -41,36 +41,36 @@ This means that this routine may safely be used by multiple threads and
 from within a signal handler.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_spawn.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_spawn.html
index adb81190..ebd10f5f 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_spawn.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_spawn.html
@@ -10,32 +10,31 @@ Spawn up to maxprocs instances of a single MPI application
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Comm_spawn(const char *command, char *argv[], int maxprocs, MPI_Info info,
-                  int root, MPI_Comm comm, MPI_Comm *intercomm,
-                  int array_of_errcodes[])
+                   int root, MPI_Comm comm, MPI_Comm * intercomm, int array_of_errcodes[])
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>command </B><DD>name of program to be spawned (string, significant only at root) 
+<DT><B>command </B><DD>name of program to be spawned (string, significant only at root)
 
-<DT><B>argv </B><DD>arguments to command (array of strings, significant only at root) 
+<DT><B>argv </B><DD>arguments to command (array of strings, significant only at root)
 
-<DT><B>maxprocs </B><DD>maximum number of processes to start (integer, significant only 
-at root) 
+<DT><B>maxprocs </B><DD>maximum number of processes to start (integer, significant only
+at root)
 
-<DT><B>info </B><DD>a set of key-value pairs telling the runtime system where and how 
-to start the processes (handle, significant only at root) 
+<DT><B>info </B><DD>a set of key-value pairs telling the runtime system where and how
+to start the processes (handle, significant only at root)
 
-<DT><B>root </B><DD>rank of process in which previous arguments are examined (integer) 
+<DT><B>root </B><DD>rank of process in which previous arguments are examined (integer)
 
-<DT><B>comm </B><DD>intracommunicator containing group of spawning processes (handle) 
+<DT><B>comm </B><DD>intracommunicator containing group of spawning processes (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
 <DL>
-<DT><B>intercomm </B><DD>intercommunicator between original group and the 
-newly spawned group (handle) 
+<DT><B>intercomm </B><DD>intercommunicator between original group and the
+newly spawned group (handle)
 
-<DT><B>array_of_errcodes </B><DD>one code per process (array of integer) 
+<DT><B>array_of_errcodes </B><DD>one code per process (array of integer)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -43,41 +42,41 @@ newly spawned group (handle)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_INFO </B> <DD> Invalid Info 
 </DL>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_spawn_multiple.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_spawn_multiple.html
index cea99b31..ae28af6b 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_spawn_multiple.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_spawn_multiple.html
@@ -10,72 +10,72 @@ short description
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Comm_spawn_multiple(int count, char *array_of_commands[],
-                          char **array_of_argv[], const int array_of_maxprocs[],
-                          const MPI_Info array_of_info[], int root, MPI_Comm comm,
-                          MPI_Comm *intercomm, int array_of_errcodes[])
+                            char **array_of_argv[], const int array_of_maxprocs[],
+                            const MPI_Info array_of_info[], int root, MPI_Comm comm,
+                            MPI_Comm * intercomm, int array_of_errcodes[])
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>count </B><DD>number of commands (positive integer, significant to MPI only at 
-root 
+<DT><B>count </B><DD>number of commands (positive integer, significant to MPI only at
+root
 
-<DT><B>array_of_commands </B><DD>programs to be executed (array of strings, significant 
-only at root) 
+<DT><B>array_of_commands </B><DD>programs to be executed (array of strings, significant
+only at root)
 
-<DT><B>array_of_argv </B><DD>arguments for commands (array of array of strings, 
-significant only at root) 
+<DT><B>array_of_argv </B><DD>arguments for commands (array of array of strings,
+significant only at root)
 
-<DT><B>array_of_maxprocs </B><DD>maximum number of processes to start for each command 
-(array of integer, significant only at root) 
+<DT><B>array_of_maxprocs </B><DD>maximum number of processes to start for each command
+(array of integer, significant only at root)
 
-<DT><B>array_of_info </B><DD>info objects telling the runtime system where and how to 
-start processes (array of handles, significant only at root) 
+<DT><B>array_of_info </B><DD>info objects telling the runtime system where and how to
+start processes (array of handles, significant only at root)
 
-<DT><B>root </B><DD>rank of process in which previous arguments are examined (integer) 
+<DT><B>root </B><DD>rank of process in which previous arguments are examined (integer)
 
-<DT><B>comm </B><DD>intracommunicator containing group of spawning processes (handle) 
+<DT><B>comm </B><DD>intracommunicator containing group of spawning processes (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
 <DL>
 <DT><B>intercomm </B><DD>intercommunicator between original group and newly spawned group
-(handle) 
+(handle)
 
-<DT><B>array_of_errcodes </B><DD>one error code per process (array of integer) 
+<DT><B>array_of_errcodes </B><DD>one error code per process (array of integer)
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_INFO </B> <DD> Invalid Info 
 </DL>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_split.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_split.html
index e0aa6e6f..d5c2a40a 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_split.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_split.html
@@ -9,78 +9,78 @@
 Creates new communicators based on colors and keys 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Comm_split(MPI_Comm comm, int color, int key, MPI_Comm *newcomm)
+int MPI_Comm_split(MPI_Comm comm, int color, int key, MPI_Comm * newcomm)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 
-<DT><B>color </B><DD>control of subset assignment (nonnegative integer).  Processes 
-with the same color are in the same new communicator 
+<DT><B>color </B><DD>control of subset assignment (nonnegative integer).  Processes
+with the same color are in the same new communicator
 
 <DT><B>key </B><DD>control of rank assignment (integer)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>newcomm </B> <DD> new communicator (handle) 
+<DL><DT><B>newcomm </B> <DD> new communicator (handle)
 </DL>
 <P>
 <H2>Notes</H2>
-The <tt>color</tt> must be non-negative or <tt>MPI_UNDEFINED</tt>.
+The <TT>color</TT> must be non-negative or <TT>MPI_UNDEFINED</TT>.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Algorithm</H2>
 <PRE>
   1. Use MPI_Allgather to get the color and key from each process
-  2. Count the number of processes with the same color; create a 
+  2. Count the number of processes with the same color; create a
      communicator with that many processes.  If this process has
-     <tt>MPI_UNDEFINED</tt> as the color, create a process with a single member.
+     <TT>MPI_UNDEFINED</TT> as the color, create a process with a single member.
   3. Use key to order the ranks
 </PRE>
 
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_INTERN </B> <DD> This error is returned when some part of the MPICH 
 implementation is unable to acquire memory.  
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Comm_free
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_split_type.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_split_type.html
index b98d03a1..d187ae78 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_split_type.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_split_type.html
@@ -9,8 +9,7 @@
 Creates new communicators based on split types and keys 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Comm_split_type(MPI_Comm comm, int split_type, int key, MPI_Info info,
-                        MPI_Comm * newcomm)
+int MPI_Comm_split_type(MPI_Comm comm, int split_type, int key, MPI_Info info, MPI_Comm * newcomm)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -28,51 +27,51 @@ int MPI_Comm_split_type(MPI_Comm comm, int split_type, int key, MPI_Info info,
 </DL>
 <P>
 <H2>Notes</H2>
-The <tt>split_type</tt> must be non-negative or <tt>MPI_UNDEFINED</tt>.
+The <TT>split_type</TT> must be non-negative or <TT>MPI_UNDEFINED</TT>.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_INTERN </B> <DD> This error is returned when some part of the MPICH 
 implementation is unable to acquire memory.  
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Comm_free
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_test_inter.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_test_inter.html
index b46d3b16..1b3888f7 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_test_inter.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Comm_test_inter.html
@@ -12,11 +12,11 @@ Tests to see if a comm is an inter-communicator
 int MPI_Comm_test_inter(MPI_Comm comm, int *flag)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>comm </B> <DD> communicator to test (handle) 
+<DL><DT><B>comm </B> <DD> communicator to test (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>flag </B> <DD> true if this is an inter-communicator(logical) 
+<DL><DT><B>flag </B> <DD> true if this is an inter-communicator(logical)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -26,36 +26,36 @@ This means that this routine may safely be used by multiple threads and
 from within a signal handler.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Compare_and_swap.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Compare_and_swap.html
index bfdb096a..3c13264c 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Compare_and_swap.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Compare_and_swap.html
@@ -10,8 +10,8 @@ Perform one-sided atomic compare-and-swap.
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Compare_and_swap(const void *origin_addr, const void *compare_addr,
-        void *result_addr, MPI_Datatype datatype, int target_rank,
-        MPI_Aint target_disp, MPI_Win win)
+                         void *result_addr, MPI_Datatype datatype, int target_rank,
+                         MPI_Aint target_disp, MPI_Win win)
 </PRE>
 <P>
 This function compares one element of type datatype in the compare buffer
@@ -47,48 +47,48 @@ types, or Byte as specified in Section 5.9.2 on page 176. The origin and result
 buffers (origin_addr and result_addr) must be disjoint.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
-<DL><DT><B>MPI_ERR_OP </B> <DD> Invalid operation.  MPI operations (objects of type <tt>MPI_Op</tt>)
-must either be one of the predefined operations (e.g., <tt>MPI_SUM</tt>) or
-created with <tt>MPI_Op_create</tt>.
+<DL><DT><B>MPI_ERR_OP </B> <DD> Invalid operation.  MPI operations (objects of type <TT>MPI_Op</TT>)
+must either be one of the predefined operations (e.g., <TT>MPI_SUM</TT>) or
+created with <TT>MPI_Op_create</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Dims_create.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Dims_create.html
index d94259a4..ee2bb469 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Dims_create.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Dims_create.html
@@ -13,14 +13,14 @@ int MPI_Dims_create(int nnodes, int ndims, int dims[])
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>nnodes </B><DD>number of nodes in a grid (integer) 
+<DT><B>nnodes </B><DD>number of nodes in a grid (integer)
 
-<DT><B>ndims </B><DD>number of cartesian dimensions (integer) 
+<DT><B>ndims </B><DD>number of cartesian dimensions (integer)
 </DL>
 <P>
 <H2>Input/Output Parameters</H2>
-<DL><DT><B>dims </B> <DD> integer array of size  <tt>ndims</tt> specifying the number of nodes in each 
-dimension.  A value of 0 indicates that <tt>MPI_Dims_create</tt> should fill in a
+<DL><DT><B>dims </B> <DD> integer array of size  <TT>ndims</TT> specifying the number of nodes in each
+dimension.  A value of 0 indicates that <TT>MPI_Dims_create</TT> should fill in a
 suitable value.
 </DL>
 <P>
@@ -29,31 +29,31 @@ suitable value.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Dist_graph_create.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Dist_graph_create.html
index 038540f2..196c5654 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Dist_graph_create.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Dist_graph_create.html
@@ -12,25 +12,25 @@ MPI_DIST_GRAPH_CREATE returns a handle to a new communicator to which the distri
 int MPI_Dist_graph_create(MPI_Comm comm_old, int n, const int sources[],
                           const int degrees[], const int destinations[],
                           const int weights[],
-                          MPI_Info info, int reorder, MPI_Comm *comm_dist_graph)
+                          MPI_Info info, int reorder, MPI_Comm * comm_dist_graph)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
 <DT><B>comm_old </B><DD>input communicator (handle)
 
-<DT><B>n </B><DD>number of source nodes for which this process specifies edges 
+<DT><B>n </B><DD>number of source nodes for which this process specifies edges
 (non-negative integer)
 
-<DT><B>sources </B><DD>array containing the n source nodes for which this process 
+<DT><B>sources </B><DD>array containing the n source nodes for which this process
 specifies edges (array of non-negative integers)
 
-<DT><B>degrees </B><DD>array specifying the number of destinations for each source node 
+<DT><B>degrees </B><DD>array specifying the number of destinations for each source node
 in the source node array (array of non-negative integers)
 
-<DT><B>destinations </B><DD>destination nodes for the source nodes in the source node 
+<DT><B>destinations </B><DD>destination nodes for the source nodes in the source node
 array (array of non-negative integers)
 
-<DT><B>weights </B><DD>weights for source to destination edges (array of non-negative 
+<DT><B>weights </B><DD>weights for source to destination edges (array of non-negative
 integers or MPI_UNWEIGHTED)
 
 <DT><B>info </B><DD>hints on optimization and interpretation of weights (handle)
@@ -47,40 +47,40 @@ integers or MPI_UNWEIGHTED)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Dist_graph_create_adjacent.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Dist_graph_create_adjacent.html
index f729a7ab..357ddfd8 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Dist_graph_create_adjacent.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Dist_graph_create_adjacent.html
@@ -14,7 +14,7 @@ int MPI_Dist_graph_create_adjacent(MPI_Comm comm_old,
                                    const int sourceweights[],
                                    int outdegree, const int destinations[],
                                    const int destweights[],
-                                   MPI_Info info, int reorder, MPI_Comm *comm_dist_graph)
+                                   MPI_Info info, int reorder, MPI_Comm * comm_dist_graph)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -33,7 +33,7 @@ process (array of non-negative integers or MPI_UNWEIGHTED)
 <DT><B>destinations </B><DD>ranks of processes for which the calling process is a
 source (array of non-negative integers)
 
-<DT><B>destweights </B><DD>weights of the edges out of the calling process 
+<DT><B>destweights </B><DD>weights of the edges out of the calling process
 (array of non-negative integers or MPI_UNWEIGHTED)
 
 <DT><B>info </B><DD>hints on optimization and interpretation of weights (handle)
@@ -50,40 +50,40 @@ source (array of non-negative integers)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Dist_graph_neighbors.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Dist_graph_neighbors.html
index 92af1f23..f946cab0 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Dist_graph_neighbors.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Dist_graph_neighbors.html
@@ -38,31 +38,31 @@ int MPI_Dist_graph_neighbors(MPI_Comm comm,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Dist_graph_neighbors_count.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Dist_graph_neighbors_count.html
index 436733ee..d0d65616 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Dist_graph_neighbors_count.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Dist_graph_neighbors_count.html
@@ -29,31 +29,31 @@ int MPI_Dist_graph_neighbors_count(MPI_Comm comm, int *indegree, int *outdegree,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Errhandler_create.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Errhandler_create.html
index a6b64dbc..a57d46f0 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Errhandler_create.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Errhandler_create.html
@@ -9,22 +9,21 @@
 Creates an MPI-style errorhandler 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Errhandler_create(MPI_Handler_function *function, 
-                          MPI_Errhandler *errhandler)
+int MPI_Errhandler_create(MPI_Handler_function * function, MPI_Errhandler * errhandler)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>function </B> <DD> user defined error handling procedure 
+<DL><DT><B>function </B> <DD> user defined error handling procedure
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>errhandler </B> <DD> MPI error handler (handle) 
+<DL><DT><B>errhandler </B> <DD> MPI error handler (handle)
 </DL>
 <P>
 <H2>Notes</H2>
 The MPI Standard states that an implementation may make the output value
 (errhandler) simply the address of the function.  However, the action of
-<tt>MPI_Errhandler_free</tt> makes this impossible, since it is required to set the
-value of the argument to <tt>MPI_ERRHANDLER_NULL</tt>.  In addition, the actual
+<TT>MPI_Errhandler_free</TT> makes this impossible, since it is required to set the
+value of the argument to <TT>MPI_ERRHANDLER_NULL</TT>.  In addition, the actual
 error handler must remain until all communicators that use it are
 freed.
 <P>
@@ -33,38 +32,38 @@ freed.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Deprecated Function</H2>
 The MPI-2 standard deprecated a number of routines because MPI-2 provides
 better versions.  This routine is one of those that was deprecated.  The
 routine may continue to be used, but new code should use the replacement
 routine.
-The replacement routine for this function is <tt>MPI_Comm_create_errhandler</tt>.
+The replacement routine for this function is <TT>MPI_Comm_create_errhandler</TT>.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -74,7 +73,7 @@ possible.
 implementation is unable to acquire memory.  
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Comm_create_errhandler, MPI_Errhandler_free
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Errhandler_free.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Errhandler_free.html
index 8036801d..b72e11dd 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Errhandler_free.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Errhandler_free.html
@@ -9,10 +9,10 @@
 Frees an MPI-style errorhandler 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Errhandler_free(MPI_Errhandler *errhandler)
+int MPI_Errhandler_free(MPI_Errhandler * errhandler)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>errhandler </B> <DD> MPI error handler (handle).  Set to <tt>MPI_ERRHANDLER_NULL</tt> on 
+<DL><DT><B>errhandler </B> <DD> MPI error handler (handle).  Set to <TT>MPI_ERRHANDLER_NULL</TT> on
 exit.
 </DL>
 <P>
@@ -21,37 +21,37 @@ exit.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Errhandler_get.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Errhandler_get.html
index bc597fd4..14ca679d 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Errhandler_get.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Errhandler_get.html
@@ -9,15 +9,15 @@
 Gets the error handler for a communicator 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Errhandler_get(MPI_Comm comm, MPI_Errhandler *errhandler)
+int MPI_Errhandler_get(MPI_Comm comm, MPI_Errhandler * errhandler)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>comm </B> <DD> communicator to get the error handler from (handle) 
+<DL><DT><B>comm </B> <DD> communicator to get the error handler from (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
 <DL><DT><B>errhandler </B> <DD> MPI error handler currently associated with communicator
-(handle) 
+(handle)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -25,51 +25,51 @@ int MPI_Errhandler_get(MPI_Comm comm, MPI_Errhandler *errhandler)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Note on Implementation</H2>
 <P>
 The MPI Standard was unclear on whether this routine required the user to call
-<tt>MPI_Errhandler_free</tt> once for each call made to this routine in order to
+<TT>MPI_Errhandler_free</TT> once for each call made to this routine in order to
 free the error handler.  After some debate, the MPI Forum added an explicit
-statement that users are required to call <tt>MPI_Errhandler_free</tt> when the
+statement that users are required to call <TT>MPI_Errhandler_free</TT> when the
 return value from this routine is no longer needed.  This behavior is similar
-to the other MPI routines for getting objects; for example, <tt>MPI_Comm_group
-</tt>requires that the user call <tt>MPI_Group_free</tt> when the group returned
-by <tt>MPI_Comm_group</tt> is no longer needed.
+to the other MPI routines for getting objects; for example, <TT>MPI_Comm_group
+</TT>requires that the user call <TT>MPI_Group_free</TT> when the group returned
+by <TT>MPI_Comm_group</TT> is no longer needed.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Errhandler_set.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Errhandler_set.html
index 941ee6cc..53e3500e 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Errhandler_set.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Errhandler_set.html
@@ -13,9 +13,9 @@ int MPI_Errhandler_set(MPI_Comm comm, MPI_Errhandler errhandler)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>comm </B><DD>communicator to set the error handler for (handle) 
+<DT><B>comm </B><DD>communicator to set the error handler for (handle)
 
-<DT><B>errhandler </B><DD>new MPI error handler for communicator (handle) 
+<DT><B>errhandler </B><DD>new MPI error handler for communicator (handle)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -23,51 +23,51 @@ int MPI_Errhandler_set(MPI_Comm comm, MPI_Errhandler errhandler)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Deprecated Function</H2>
 The MPI-2 standard deprecated a number of routines because MPI-2 provides
 better versions.  This routine is one of those that was deprecated.  The
 routine may continue to be used, but new code should use the replacement
 routine.
-The replacement for this routine is <tt>MPI_Comm_set_errhandler</tt>.
+The replacement for this routine is <TT>MPI_Comm_set_errhandler</TT>.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Comm_set_errhandler, MPI_Errhandler_create, MPI_Comm_create_errhandler
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Error_class.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Error_class.html
index 70eedacb..88c31877 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Error_class.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Error_class.html
@@ -12,12 +12,12 @@ Converts an error code into an error class
 int MPI_Error_class(int errorcode, int *errorclass)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>errorcode </B> <DD> Error code returned by an MPI routine 
+<DL><DT><B>errorcode </B> <DD> Error code returned by an MPI routine
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>errorclass </B> <DD> Error class associated with <tt>errorcode
-</tt>
+<DL><DT><B>errorclass </B> <DD> Error class associated with <TT>errorcode
+</TT>
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -27,27 +27,27 @@ This means that this routine may safely be used by multiple threads and
 from within a signal handler.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Error_string.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Error_string.html
index 88eb072d..a4cd2ada 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Error_string.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Error_string.html
@@ -17,51 +17,51 @@ int MPI_Error_string(int errorcode, char *string, int *resultlen)
 <P>
 <H2>Output Parameters</H2>
 <DL>
-<DT><B>string </B><DD>Text that corresponds to the errorcode 
+<DT><B>string </B><DD>Text that corresponds to the errorcode
 
-<DT><B>resultlen </B><DD>Length of string 
+<DT><B>resultlen </B><DD>Length of string
 </DL>
 <P>
 Notes:  Error codes are the values return by MPI routines (in C) or in the
-<tt>ierr</tt> argument (in Fortran).  These can be converted into error classes
-with the routine <tt>MPI_Error_class</tt>.
+<TT>ierr</TT> argument (in Fortran).  These can be converted into error classes
+with the routine <TT>MPI_Error_class</TT>.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Exscan.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Exscan.html
index d58aa0db..98c8478d 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Exscan.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Exscan.html
@@ -6,7 +6,7 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Exscan"><H1>MPI_Exscan</H1></A>
-Computes the exclusive scan (partial reductions) of data on a  collection of processes 
+Computes the exclusive scan (partial reductions) of data on a collection of processes 
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Exscan(const void *sendbuf, void *recvbuf, int count, MPI_Datatype datatype,
@@ -14,23 +14,23 @@ int MPI_Exscan(const void *sendbuf, void *recvbuf, int count, MPI_Datatype datat
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>sendbuf </B><DD>starting address of send buffer (choice) 
+<DT><B>sendbuf </B><DD>starting address of send buffer (choice)
 
-<DT><B>count </B><DD>number of elements in input buffer (integer) 
+<DT><B>count </B><DD>number of elements in input buffer (integer)
 
-<DT><B>datatype </B><DD>data type of elements of input buffer (handle) 
+<DT><B>datatype </B><DD>data type of elements of input buffer (handle)
 
-<DT><B>op </B><DD>operation (handle) 
+<DT><B>op </B><DD>operation (handle)
 
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>recvbuf </B> <DD> starting address of receive buffer (choice) 
+<DL><DT><B>recvbuf </B> <DD> starting address of receive buffer (choice)
 </DL>
 <P>
 <H2>Notes</H2>
-<tt>MPI_Exscan</tt> is like <tt>MPI_Scan</tt>, except that the contribution from the
+<TT>MPI_Exscan</TT> is like <TT>MPI_Scan</TT>, except that the contribution from the
 calling process is not included in the result at the calling process
 (it is contributed to the subsequent processes, of course).
 <P>
@@ -39,25 +39,25 @@ calling process is not included in the result at the calling process
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Notes on collective operations</H2>
 <P>
-The reduction functions (<tt>MPI_Op</tt>) do not return an error value.  As a result,
-if the functions detect an error, all they can do is either call <tt>MPI_Abort
-</tt>or silently skip the problem.  Thus, if you change the error handler from
-<tt>MPI_ERRORS_ARE_FATAL</tt> to something else, for example, <tt>MPI_ERRORS_RETURN</tt>,
+The reduction functions (<TT>MPI_Op</TT>) do not return an error value.  As a result,
+if the functions detect an error, all they can do is either call <TT>MPI_Abort
+</TT>or silently skip the problem.  Thus, if you change the error handler from
+<TT>MPI_ERRORS_ARE_FATAL</TT> to something else, for example, <TT>MPI_ERRORS_RETURN</TT>,
 then no error may be indicated.
 <P>
 The reason for this is the performance problems in ensuring that
@@ -65,36 +65,36 @@ all collective routines return the same error value.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_BUFFER </B> <DD> Invalid buffer pointer.  Usually a null buffer where
 one is not valid.
 </DL>
 <DL><DT><B>MPI_ERR_BUFFER </B> <DD> This error class is associcated with an error code that
-indicates that two buffer arguments are <em>aliased</em>; that is, the 
+indicates that two buffer arguments are <EM>aliased</EM>; that is, the 
 describe overlapping storage (often the exact same storage).  This
 is prohibited in MPI (because it is prohibited by the Fortran 
 standard, and rather than have a separate case for C and Fortran, the
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Fetch_and_op.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Fetch_and_op.html
index 0ba8e7cf..56a14bf5 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Fetch_and_op.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Fetch_and_op.html
@@ -10,8 +10,8 @@ Perform one-sided read-modify-write.
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Fetch_and_op(const void *origin_addr, void *result_addr,
-        MPI_Datatype datatype, int target_rank, MPI_Aint target_disp,
-        MPI_Op op, MPI_Win win)
+                     MPI_Datatype datatype, int target_rank, MPI_Aint target_disp,
+                     MPI_Op op, MPI_Win win)
 </PRE>
 <P>
 Accumulate one element of type datatype from the origin buffer (origin_addr) to
@@ -39,65 +39,65 @@ content of the target buffer before the accumulation.
 <H2>Notes</H2>
 This operations is atomic with respect to other "accumulate" operations.
 <P>
-The generic functionality of <tt>MPI_Get_accumulate</tt> might limit the performance of
+The generic functionality of <TT>MPI_Get_accumulate</TT> might limit the performance of
 fetch-and-increment or fetch-and-add calls that might be supported by special
-hardware operations. <tt>MPI_Fetch_and_op</tt> thus allows for a fast implementation
-of a commonly used subset of the functionality of <tt>MPI_Get_accumulate</tt>.
+hardware operations. <TT>MPI_Fetch_and_op</TT> thus allows for a fast implementation
+of a commonly used subset of the functionality of <TT>MPI_Get_accumulate</TT>.
 <P>
 The origin and result buffers (origin_addr and result_addr) must be disjoint.
-Any of the predefined operations for <tt>MPI_Reduce</tt>, as well as <tt>MPI_NO_OP</tt> or
-<tt>MPI_REPLACE</tt>, can be specified as op; user-defined functions cannot be used. The
+Any of the predefined operations for <TT>MPI_Reduce</TT>, as well as <TT>MPI_NO_OP</TT> or
+<TT>MPI_REPLACE</TT>, can be specified as op; user-defined functions cannot be used. The
 datatype argument must be a predefined datatype.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
-<DL><DT><B>MPI_ERR_OP </B> <DD> Invalid operation.  MPI operations (objects of type <tt>MPI_Op</tt>)
-must either be one of the predefined operations (e.g., <tt>MPI_SUM</tt>) or
-created with <tt>MPI_Op_create</tt>.
+<DL><DT><B>MPI_ERR_OP </B> <DD> Invalid operation.  MPI operations (objects of type <TT>MPI_Op</TT>)
+must either be one of the predefined operations (e.g., <TT>MPI_SUM</TT>) or
+created with <TT>MPI_Op_create</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Get_accumulate
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_call_errhandler.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_call_errhandler.html
index 945b0f6b..8650a4fc 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_call_errhandler.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_call_errhandler.html
@@ -6,16 +6,16 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_File_call_errhandler"><H1>MPI_File_call_errhandler</H1></A>
-Call the error handler installed on a  file 
+Call the error handler installed on a file 
 <H2>Synopsis</H2>
 <PRE>
 int MPI_File_call_errhandler(MPI_File fh, int errorcode)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>fh </B><DD>MPI file with error handler (handle) 
+<DT><B>fh </B><DD>MPI file with error handler (handle)
 
-<DT><B>errorcode </B><DD>error code (integer) 
+<DT><B>errorcode </B><DD>error code (integer)
 </DL>
 <P>
 <P>
@@ -28,33 +28,33 @@ with this routine.
 The MPI standard defined a thread-safe interface but this does not
 mean that all routines may be called without any thread locks.  For
 example, two threads must not attempt to change the contents of the
-same <tt>MPI_Info</tt> object concurrently.  The user is responsible in this
+same <TT>MPI_Info</TT> object concurrently.  The user is responsible in this
 case for using some mechanism, such as thread locks, to ensure that
 only one thread at a time makes use of this routine.
 <P>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_close.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_close.html
index 36b1ff92..e2e56b1d 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_close.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_close.html
@@ -9,19 +9,19 @@
 Closes a file 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_File_close(MPI_File *fh)
+int MPI_File_close(MPI_File * fh)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_create_errhandler.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_create_errhandler.html
index 8bab9beb..cf0f6e31 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_create_errhandler.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_create_errhandler.html
@@ -9,15 +9,15 @@
 Create a file error handler 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_File_create_errhandler(MPI_File_errhandler_function *file_errhandler_fn,
-                               MPI_Errhandler *errhandler)
+int MPI_File_create_errhandler(MPI_File_errhandler_function * file_errhandler_fn,
+                               MPI_Errhandler * errhandler)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>file_errhandler_fn </B> <DD> user defined error handling procedure (function)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>errhandler </B> <DD> MPI error handler (handle) 
+<DL><DT><B>errhandler </B> <DD> MPI error handler (handle)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -25,31 +25,31 @@ int MPI_File_create_errhandler(MPI_File_errhandler_function *file_errhandler_fn,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_delete.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_delete.html
index a59af27d..6de5220d 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_delete.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_delete.html
@@ -18,12 +18,12 @@ int MPI_File_delete(ROMIO_CONST char *filename, MPI_Info info)
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_amode.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_amode.html
index 2a4d81d7..cc488686 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_amode.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_amode.html
@@ -20,12 +20,12 @@ int MPI_File_get_amode(MPI_File fh, int *amode)
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_atomicity.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_atomicity.html
index e168d7bd..8a4549f3 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_atomicity.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_atomicity.html
@@ -20,12 +20,12 @@ int MPI_File_get_atomicity(MPI_File fh, int *flag)
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_byte_offset.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_byte_offset.html
index ccaba477..31f471ee 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_byte_offset.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_byte_offset.html
@@ -6,10 +6,10 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_File_get_byte_offset"><H1>MPI_File_get_byte_offset</H1></A>
-Returns the absolute byte position in  the file corresponding to "offset" etypes relative to the current view 
+Returns the absolute byte position in the file corresponding to "offset" etypes relative to the current view 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_File_get_byte_offset(MPI_File fh, MPI_Offset offset, MPI_Offset *disp)
+int MPI_File_get_byte_offset(MPI_File fh, MPI_Offset offset, MPI_Offset * disp)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -22,12 +22,12 @@ int MPI_File_get_byte_offset(MPI_File fh, MPI_Offset offset, MPI_Offset *disp)
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_errhandler.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_errhandler.html
index 0c48088b..b88cd315 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_errhandler.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_errhandler.html
@@ -9,14 +9,14 @@
 Get the error handler attached to a file 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_File_get_errhandler(MPI_File file, MPI_Errhandler *errhandler)
+int MPI_File_get_errhandler(MPI_File file, MPI_Errhandler * errhandler)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>file </B> <DD> MPI file (handle) 
+<DL><DT><B>file </B> <DD> MPI file (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>errhandler </B> <DD> handler currently associated with file (handle) 
+<DL><DT><B>errhandler </B> <DD> handler currently associated with file (handle)
 </DL>
 <P>
 <P>
@@ -29,33 +29,33 @@ with this routine.
 The MPI standard defined a thread-safe interface but this does not
 mean that all routines may be called without any thread locks.  For
 example, two threads must not attempt to change the contents of the
-same <tt>MPI_Info</tt> object concurrently.  The user is responsible in this
+same <TT>MPI_Info</TT> object concurrently.  The user is responsible in this
 case for using some mechanism, such as thread locks, to ensure that
 only one thread at a time makes use of this routine.
 <P>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_group.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_group.html
index 09f3875e..2b42e5b8 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_group.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_group.html
@@ -6,10 +6,10 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_File_get_group"><H1>MPI_File_get_group</H1></A>
-Returns the group of processes that  opened the file 
+Returns the group of processes that opened the file 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_File_get_group(MPI_File fh, MPI_Group *group)
+int MPI_File_get_group(MPI_File fh, MPI_Group * group)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -20,12 +20,12 @@ int MPI_File_get_group(MPI_File fh, MPI_Group *group)
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_info.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_info.html
index fd914ed9..10f29d5a 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_info.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_info.html
@@ -9,7 +9,7 @@
 Returns the hints for a file that are actually being used by MPI 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_File_get_info(MPI_File fh, MPI_Info *info_used)
+int MPI_File_get_info(MPI_File fh, MPI_Info * info_used)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -20,12 +20,12 @@ int MPI_File_get_info(MPI_File fh, MPI_Info *info_used)
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_position.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_position.html
index 7265fe23..828f73be 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_position.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_position.html
@@ -6,10 +6,10 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_File_get_position"><H1>MPI_File_get_position</H1></A>
-Returns the current position of the  individual file pointer in etype units relative to the current view 
+Returns the current position of the individual file pointer in etype units relative to the current view 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_File_get_position(MPI_File fh, MPI_Offset *offset)
+int MPI_File_get_position(MPI_File fh, MPI_Offset * offset)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -20,12 +20,12 @@ int MPI_File_get_position(MPI_File fh, MPI_Offset *offset)
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_position_shared.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_position_shared.html
index 19c1fbf9..7beced94 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_position_shared.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_position_shared.html
@@ -6,10 +6,10 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_File_get_position_shared"><H1>MPI_File_get_position_shared</H1></A>
-Returns the current position of the  shared file pointer in etype units relative to the current view 
+Returns the current position of the shared file pointer in etype units relative to the current view 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_File_get_position_shared(MPI_File fh, MPI_Offset *offset)
+int MPI_File_get_position_shared(MPI_File fh, MPI_Offset * offset)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -20,12 +20,12 @@ int MPI_File_get_position_shared(MPI_File fh, MPI_Offset *offset)
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_size.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_size.html
index 65cb4e0d..c34452ae 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_size.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_size.html
@@ -9,7 +9,7 @@
 Returns the file size 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_File_get_size(MPI_File fh, MPI_Offset *size)
+int MPI_File_get_size(MPI_File fh, MPI_Offset * size)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -20,12 +20,12 @@ int MPI_File_get_size(MPI_File fh, MPI_Offset *size)
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_type_extent.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_type_extent.html
index 5b71655f..428028b2 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_type_extent.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_type_extent.html
@@ -9,7 +9,7 @@
 Returns the extent of datatype in the file 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_File_get_type_extent(MPI_File fh, MPI_Datatype datatype, MPI_Aint *extent)
+int MPI_File_get_type_extent(MPI_File fh, MPI_Datatype datatype, MPI_Aint * extent)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -22,12 +22,12 @@ int MPI_File_get_type_extent(MPI_File fh, MPI_Datatype datatype, MPI_Aint *exten
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_view.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_view.html
index c188f72a..a644aaf6 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_view.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_get_view.html
@@ -9,8 +9,8 @@
 Returns the file view 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_File_get_view(MPI_File fh, MPI_Offset *disp, MPI_Datatype *etype,
-                      MPI_Datatype *filetype, char *datarep)
+int MPI_File_get_view(MPI_File fh, MPI_Offset * disp, MPI_Datatype * etype,
+                      MPI_Datatype * filetype, char *datarep)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -27,12 +27,12 @@ int MPI_File_get_view(MPI_File fh, MPI_Offset *disp, MPI_Datatype *etype,
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iread.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iread.html
index 9944c983..5ea8e0ef 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iread.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iread.html
@@ -9,7 +9,7 @@
 Nonblocking read using individual file pointer 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_File_iread(MPI_File fh, void *buf, int count, MPI_Datatype datatype, MPI_Request *request)
+int MPI_File_iread(MPI_File fh, void *buf, int count, MPI_Datatype datatype, MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -26,12 +26,12 @@ int MPI_File_iread(MPI_File fh, void *buf, int count, MPI_Datatype datatype, MPI
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iread_all.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iread_all.html
index 1eb2e2ac..c17f01e4 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iread_all.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iread_all.html
@@ -10,7 +10,7 @@ Nonblocking collective read using individual file pointer
 <H2>Synopsis</H2>
 <PRE>
 int MPI_File_iread_all(MPI_File fh, void *buf, int count,
-                       MPI_Datatype datatype, MPI_Request *request)
+                       MPI_Datatype datatype, MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -27,12 +27,12 @@ int MPI_File_iread_all(MPI_File fh, void *buf, int count,
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iread_at.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iread_at.html
index 4bb4a755..b9eecfb8 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iread_at.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iread_at.html
@@ -9,8 +9,8 @@
 Nonblocking read using explicit offset 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_File_iread_at(MPI_File fh, MPI_Offset offset, void *buf, int count, MPI_Datatype datatype, 
-                      MPIO_Request *request)
+int MPI_File_iread_at(MPI_File fh, MPI_Offset offset, void *buf, int count, MPI_Datatype datatype,
+                      MPIO_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -29,12 +29,12 @@ int MPI_File_iread_at(MPI_File fh, MPI_Offset offset, void *buf, int count, MPI_
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iread_at_all.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iread_at_all.html
index 01771426..ac7567bd 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iread_at_all.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iread_at_all.html
@@ -10,8 +10,7 @@ Nonblocking collective read using explicit offset
 <H2>Synopsis</H2>
 <PRE>
 int MPI_File_iread_at_all(MPI_File fh, MPI_Offset offset, void *buf,
-                          int count, MPI_Datatype datatype,
-                          MPI_Request *request)
+                          int count, MPI_Datatype datatype, MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -30,12 +29,12 @@ int MPI_File_iread_at_all(MPI_File fh, MPI_Offset offset, void *buf,
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iread_shared.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iread_shared.html
index b1615d5f..1d385ade 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iread_shared.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iread_shared.html
@@ -10,7 +10,7 @@ Nonblocking read using shared file pointer
 <H2>Synopsis</H2>
 <PRE>
 int MPI_File_iread_shared(MPI_File fh, void *buf, int count,
-                          MPI_Datatype datatype, MPI_Request *request)
+                          MPI_Datatype datatype, MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -27,12 +27,12 @@ int MPI_File_iread_shared(MPI_File fh, void *buf, int count,
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iwrite.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iwrite.html
index d217e33f..69640abe 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iwrite.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iwrite.html
@@ -14,7 +14,7 @@ Nonblocking write using individual file pointer
 #endif
 
 int MPI_File_iwrite(MPI_File fh, ROMIO_CONST void *buf, int count,
-                   MPI_Datatype datatype, MPI_Request *request)
+                    MPI_Datatype datatype, MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -31,12 +31,12 @@ int MPI_File_iwrite(MPI_File fh, ROMIO_CONST void *buf, int count,
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iwrite_all.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iwrite_all.html
index 566a35f1..f2d4f4cc 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iwrite_all.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iwrite_all.html
@@ -10,7 +10,7 @@ Nonblocking collective write using individual file pointer
 <H2>Synopsis</H2>
 <PRE>
 int MPI_File_iwrite_all(MPI_File fh, ROMIO_CONST void *buf, int count,
-                        MPI_Datatype datatype, MPI_Request *request)
+                        MPI_Datatype datatype, MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -27,12 +27,12 @@ int MPI_File_iwrite_all(MPI_File fh, ROMIO_CONST void *buf, int count,
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iwrite_at.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iwrite_at.html
index 8724df6c..2cfa73d1 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iwrite_at.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iwrite_at.html
@@ -14,8 +14,7 @@ Nonblocking write using explicit offset
 #endif
 
 int MPI_File_iwrite_at(MPI_File fh, MPI_Offset offset, ROMIO_CONST void *buf,
-                       int count, MPI_Datatype datatype, 
-                       MPIO_Request *request)
+                       int count, MPI_Datatype datatype, MPIO_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -34,12 +33,12 @@ int MPI_File_iwrite_at(MPI_File fh, MPI_Offset offset, ROMIO_CONST void *buf,
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iwrite_at_all.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iwrite_at_all.html
index e4b241b4..ad11f9aa 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iwrite_at_all.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iwrite_at_all.html
@@ -10,8 +10,7 @@ Nonblocking collective write using explicit offset
 <H2>Synopsis</H2>
 <PRE>
 int MPI_File_iwrite_at_all(MPI_File fh, MPI_Offset offset, ROMIO_CONST void *buf,
-                           int count, MPI_Datatype datatype,
-                           MPI_Request *request)
+                           int count, MPI_Datatype datatype, MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -30,12 +29,12 @@ int MPI_File_iwrite_at_all(MPI_File fh, MPI_Offset offset, ROMIO_CONST void *buf
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iwrite_shared.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iwrite_shared.html
index e7d73df4..78fdd794 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iwrite_shared.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_iwrite_shared.html
@@ -14,7 +14,7 @@ Nonblocking write using shared file pointer
 #endif
 
 int MPI_File_iwrite_shared(MPI_File fh, ROMIO_CONST void *buf, int count,
-                         MPI_Datatype datatype, MPIO_Request *request)
+                           MPI_Datatype datatype, MPIO_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -31,12 +31,12 @@ int MPI_File_iwrite_shared(MPI_File fh, ROMIO_CONST void *buf, int count,
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_open.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_open.html
index b02d6c69..0e6326ad 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_open.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_open.html
@@ -10,7 +10,7 @@ Opens a file
 <H2>Synopsis</H2>
 <PRE>
 int MPI_File_open(MPI_Comm comm, ROMIO_CONST char *filename, int amode,
-                  MPI_Info info, MPI_File *fh)
+                  MPI_Info info, MPI_File * fh)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>comm </B> <DD> communicator (handle)
@@ -27,12 +27,12 @@ int MPI_File_open(MPI_Comm comm, ROMIO_CONST char *filename, int amode,
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_preallocate.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_preallocate.html
index 36d7e0af..38bbdf75 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_preallocate.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_preallocate.html
@@ -18,12 +18,12 @@ int MPI_File_preallocate(MPI_File fh, MPI_Offset size)
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read.html
index ecca4201..c30b7be9 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read.html
@@ -9,8 +9,7 @@
 Read using individual file pointer 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_File_read(MPI_File fh, void *buf, int count,
-                  MPI_Datatype datatype, MPI_Status *status)
+int MPI_File_read(MPI_File fh, void *buf, int count, MPI_Datatype datatype, MPI_Status * status)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -27,12 +26,12 @@ int MPI_File_read(MPI_File fh, void *buf, int count,
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_all.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_all.html
index 5bab5d9c..d1394e6c 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_all.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_all.html
@@ -9,8 +9,7 @@
 Collective read using individual file pointer 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_File_read_all(MPI_File fh, void *buf, int count,
-                      MPI_Datatype datatype, MPI_Status *status)
+int MPI_File_read_all(MPI_File fh, void *buf, int count, MPI_Datatype datatype, MPI_Status * status)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -27,12 +26,12 @@ int MPI_File_read_all(MPI_File fh, void *buf, int count,
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_all_begin.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_all_begin.html
index e238f5f7..6c842d07 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_all_begin.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_all_begin.html
@@ -9,8 +9,7 @@
 Begin a split collective read using individual file pointer 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_File_read_all_begin(MPI_File fh, void *buf, int count,
-                            MPI_Datatype datatype)
+int MPI_File_read_all_begin(MPI_File fh, void *buf, int count, MPI_Datatype datatype)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -25,12 +24,12 @@ int MPI_File_read_all_begin(MPI_File fh, void *buf, int count,
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_all_end.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_all_end.html
index 18c8f2cf..0ecc1254 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_all_end.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_all_end.html
@@ -9,7 +9,7 @@
 Complete a split collective read using individual file pointer 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_File_read_all_end(MPI_File fh, void *buf, MPI_Status *status)
+int MPI_File_read_all_end(MPI_File fh, void *buf, MPI_Status * status)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -22,12 +22,12 @@ int MPI_File_read_all_end(MPI_File fh, void *buf, MPI_Status *status)
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_at.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_at.html
index df5f4719..5eed6119 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_at.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_at.html
@@ -10,7 +10,7 @@ Read using explicit offset
 <H2>Synopsis</H2>
 <PRE>
 int MPI_File_read_at(MPI_File fh, MPI_Offset offset, void *buf,
-                    int count, MPI_Datatype datatype, MPI_Status *status)
+                     int count, MPI_Datatype datatype, MPI_Status * status)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -29,12 +29,12 @@ int MPI_File_read_at(MPI_File fh, MPI_Offset offset, void *buf,
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_at_all.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_at_all.html
index 1f90f08d..5532651c 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_at_all.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_at_all.html
@@ -10,8 +10,7 @@ Collective read using explicit offset
 <H2>Synopsis</H2>
 <PRE>
 int MPI_File_read_at_all(MPI_File fh, MPI_Offset offset, void *buf,
-                         int count, MPI_Datatype datatype, 
-                         MPI_Status *status)
+                         int count, MPI_Datatype datatype, MPI_Status * status)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -30,12 +29,12 @@ int MPI_File_read_at_all(MPI_File fh, MPI_Offset offset, void *buf,
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_at_all_begin.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_at_all_begin.html
index 8f272d59..d6458e70 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_at_all_begin.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_at_all_begin.html
@@ -10,7 +10,7 @@ Begin a split collective read using explicit offset
 <H2>Synopsis</H2>
 <PRE>
 int MPI_File_read_at_all_begin(MPI_File fh, MPI_Offset offset, void *buf,
-                             int count, MPI_Datatype datatype)
+                               int count, MPI_Datatype datatype)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -27,12 +27,12 @@ int MPI_File_read_at_all_begin(MPI_File fh, MPI_Offset offset, void *buf,
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_at_all_end.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_at_all_end.html
index 1707a584..f122879e 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_at_all_end.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_at_all_end.html
@@ -9,7 +9,7 @@
 Complete a split collective read using explicit offset 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_File_read_at_all_end(MPI_File fh, void *buf, MPI_Status *status)
+int MPI_File_read_at_all_end(MPI_File fh, void *buf, MPI_Status * status)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -22,12 +22,12 @@ int MPI_File_read_at_all_end(MPI_File fh, void *buf, MPI_Status *status)
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_ordered.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_ordered.html
index a5267e01..d880c1a4 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_ordered.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_ordered.html
@@ -10,7 +10,7 @@ Collective read using shared file pointer
 <H2>Synopsis</H2>
 <PRE>
 int MPI_File_read_ordered(MPI_File fh, void *buf, int count,
-                          MPI_Datatype datatype, MPI_Status *status)
+                          MPI_Datatype datatype, MPI_Status * status)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -27,12 +27,12 @@ int MPI_File_read_ordered(MPI_File fh, void *buf, int count,
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_ordered_begin.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_ordered_begin.html
index 15fa6a2d..58102a30 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_ordered_begin.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_ordered_begin.html
@@ -9,8 +9,7 @@
 Begin a split collective read using shared file pointer 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_File_read_ordered_begin(MPI_File fh, void *buf, int count,
-                             MPI_Datatype datatype)
+int MPI_File_read_ordered_begin(MPI_File fh, void *buf, int count, MPI_Datatype datatype)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -25,12 +24,12 @@ int MPI_File_read_ordered_begin(MPI_File fh, void *buf, int count,
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_ordered_end.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_ordered_end.html
index de91d727..d199d85f 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_ordered_end.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_ordered_end.html
@@ -9,7 +9,7 @@
 Complete a split collective read using shared file pointer 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_File_read_ordered_end(MPI_File fh, void *buf, MPI_Status *status)
+int MPI_File_read_ordered_end(MPI_File fh, void *buf, MPI_Status * status)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -22,12 +22,12 @@ int MPI_File_read_ordered_end(MPI_File fh, void *buf, MPI_Status *status)
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_shared.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_shared.html
index d9b7279f..461a9c41 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_shared.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_read_shared.html
@@ -10,7 +10,7 @@ Read using shared file pointer
 <H2>Synopsis</H2>
 <PRE>
 int MPI_File_read_shared(MPI_File fh, void *buf, int count,
-                       MPI_Datatype datatype, MPI_Status *status)
+                         MPI_Datatype datatype, MPI_Status * status)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -27,12 +27,12 @@ int MPI_File_read_shared(MPI_File fh, void *buf, int count,
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_seek.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_seek.html
index 78f08fab..d659c2f8 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_seek.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_seek.html
@@ -20,12 +20,12 @@ int MPI_File_seek(MPI_File fh, MPI_Offset offset, int whence)
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_seek_shared.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_seek_shared.html
index f199295d..73162f31 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_seek_shared.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_seek_shared.html
@@ -20,12 +20,12 @@ int MPI_File_seek_shared(MPI_File fh, MPI_Offset offset, int whence)
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_set_atomicity.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_set_atomicity.html
index 3d464aa8..14e06d6f 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_set_atomicity.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_set_atomicity.html
@@ -18,12 +18,12 @@ int MPI_File_set_atomicity(MPI_File fh, int flag)
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_set_errhandler.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_set_errhandler.html
index 40035959..9166699f 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_set_errhandler.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_set_errhandler.html
@@ -13,9 +13,9 @@ int MPI_File_set_errhandler(MPI_File file, MPI_Errhandler errhandler)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>file </B><DD>MPI file (handle) 
+<DT><B>file </B><DD>MPI file (handle)
 
-<DT><B>errhandler </B><DD>new error handler for file (handle) 
+<DT><B>errhandler </B><DD>new error handler for file (handle)
 </DL>
 <P>
 <P>
@@ -28,33 +28,33 @@ with this routine.
 The MPI standard defined a thread-safe interface but this does not
 mean that all routines may be called without any thread locks.  For
 example, two threads must not attempt to change the contents of the
-same <tt>MPI_Info</tt> object concurrently.  The user is responsible in this
+same <TT>MPI_Info</TT> object concurrently.  The user is responsible in this
 case for using some mechanism, such as thread locks, to ensure that
 only one thread at a time makes use of this routine.
 <P>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_set_info.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_set_info.html
index fc0ca9ff..d8415f9c 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_set_info.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_set_info.html
@@ -18,12 +18,12 @@ int MPI_File_set_info(MPI_File fh, MPI_Info info)
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_set_size.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_set_size.html
index a8a1d0f3..8f477b23 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_set_size.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_set_size.html
@@ -18,12 +18,12 @@ int MPI_File_set_size(MPI_File fh, MPI_Offset size)
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_set_view.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_set_view.html
index e7de265e..4c40400e 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_set_view.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_set_view.html
@@ -10,7 +10,7 @@ Sets the file view
 <H2>Synopsis</H2>
 <PRE>
 int MPI_File_set_view(MPI_File fh, MPI_Offset disp, MPI_Datatype etype,
-                     MPI_Datatype filetype, ROMIO_CONST char *datarep, MPI_Info info)
+                      MPI_Datatype filetype, ROMIO_CONST char *datarep, MPI_Info info)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -27,12 +27,12 @@ int MPI_File_set_view(MPI_File fh, MPI_Offset disp, MPI_Datatype etype,
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_sync.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_sync.html
index 7348dcd6..893c66ae 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_sync.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_sync.html
@@ -16,12 +16,12 @@ int MPI_File_sync(MPI_File fh)
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write.html
index f7860306..174b452f 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write.html
@@ -10,7 +10,7 @@ Write using individual file pointer
 <H2>Synopsis</H2>
 <PRE>
 int MPI_File_write(MPI_File fh, ROMIO_CONST void *buf, int count,
-                   MPI_Datatype datatype, MPI_Status *status)
+                   MPI_Datatype datatype, MPI_Status * status)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -27,12 +27,12 @@ int MPI_File_write(MPI_File fh, ROMIO_CONST void *buf, int count,
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_all.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_all.html
index 638eaef7..19bd5cc4 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_all.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_all.html
@@ -10,7 +10,7 @@ Collective write using individual file pointer
 <H2>Synopsis</H2>
 <PRE>
 int MPI_File_write_all(MPI_File fh, ROMIO_CONST void *buf, int count,
-                       MPI_Datatype datatype, MPI_Status *status)
+                       MPI_Datatype datatype, MPI_Status * status)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -27,12 +27,12 @@ int MPI_File_write_all(MPI_File fh, ROMIO_CONST void *buf, int count,
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_all_begin.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_all_begin.html
index 3c9c553e..21c5fc8c 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_all_begin.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_all_begin.html
@@ -9,8 +9,7 @@
 Begin a split collective write using individual file pointer 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_File_write_all_begin(MPI_File fh, ROMIO_CONST void *buf, int count,
-                           MPI_Datatype datatype)
+int MPI_File_write_all_begin(MPI_File fh, ROMIO_CONST void *buf, int count, MPI_Datatype datatype)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -23,12 +22,12 @@ int MPI_File_write_all_begin(MPI_File fh, ROMIO_CONST void *buf, int count,
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_all_end.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_all_end.html
index e8aa7437..9b51551d 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_all_end.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_all_end.html
@@ -9,7 +9,7 @@
 Complete a split collective write using individual file pointer 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_File_write_all_end(MPI_File fh, ROMIO_CONST void *buf, MPI_Status *status)
+int MPI_File_write_all_end(MPI_File fh, ROMIO_CONST void *buf, MPI_Status * status)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -22,12 +22,12 @@ int MPI_File_write_all_end(MPI_File fh, ROMIO_CONST void *buf, MPI_Status *statu
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_at.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_at.html
index 82af6b2c..f251c370 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_at.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_at.html
@@ -10,7 +10,7 @@ Write using explicit offset
 <H2>Synopsis</H2>
 <PRE>
 int MPI_File_write_at(MPI_File fh, MPI_Offset offset, ROMIO_CONST void *buf,
-                      int count, MPI_Datatype datatype, MPI_Status *status)
+                      int count, MPI_Datatype datatype, MPI_Status * status)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -29,12 +29,12 @@ int MPI_File_write_at(MPI_File fh, MPI_Offset offset, ROMIO_CONST void *buf,
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_at_all.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_at_all.html
index 4c2774e4..79599cea 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_at_all.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_at_all.html
@@ -10,8 +10,7 @@ Collective write using explicit offset
 <H2>Synopsis</H2>
 <PRE>
 int MPI_File_write_at_all(MPI_File fh, MPI_Offset offset, ROMIO_CONST void *buf,
-                          int count, MPI_Datatype datatype, 
-                          MPI_Status *status)
+                          int count, MPI_Datatype datatype, MPI_Status * status)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -30,12 +29,12 @@ int MPI_File_write_at_all(MPI_File fh, MPI_Offset offset, ROMIO_CONST void *buf,
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_at_all_begin.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_at_all_begin.html
index 47e5506d..2f96874e 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_at_all_begin.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_at_all_begin.html
@@ -10,7 +10,7 @@ Begin a split collective write using explicit offset
 <H2>Synopsis</H2>
 <PRE>
 int MPI_File_write_at_all_begin(MPI_File fh, MPI_Offset offset, ROMIO_CONST void *buf,
-                             int count, MPI_Datatype datatype)
+                                int count, MPI_Datatype datatype)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -25,12 +25,12 @@ int MPI_File_write_at_all_begin(MPI_File fh, MPI_Offset offset, ROMIO_CONST void
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_at_all_end.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_at_all_end.html
index 02bb674f..bfeefdf7 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_at_all_end.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_at_all_end.html
@@ -9,7 +9,7 @@
 Complete a split collective write using explicit offset 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_File_write_at_all_end(MPI_File fh, ROMIO_CONST void *buf, MPI_Status *status)
+int MPI_File_write_at_all_end(MPI_File fh, ROMIO_CONST void *buf, MPI_Status * status)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -22,12 +22,12 @@ int MPI_File_write_at_all_end(MPI_File fh, ROMIO_CONST void *buf, MPI_Status *st
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_ordered.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_ordered.html
index dacfecd5..5b93cc73 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_ordered.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_ordered.html
@@ -10,7 +10,7 @@ Collective write using shared file pointer
 <H2>Synopsis</H2>
 <PRE>
 int MPI_File_write_ordered(MPI_File fh, ROMIO_CONST void *buf, int count,
-                         MPI_Datatype datatype, MPI_Status *status)
+                           MPI_Datatype datatype, MPI_Status * status)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -27,12 +27,12 @@ int MPI_File_write_ordered(MPI_File fh, ROMIO_CONST void *buf, int count,
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_ordered_begin.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_ordered_begin.html
index db4a019e..5346afdb 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_ordered_begin.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_ordered_begin.html
@@ -10,7 +10,7 @@ Begin a split collective write using shared file pointer
 <H2>Synopsis</H2>
 <PRE>
 int MPI_File_write_ordered_begin(MPI_File fh, ROMIO_CONST void *buf, int count,
-                              MPI_Datatype datatype)
+                                 MPI_Datatype datatype)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -25,12 +25,12 @@ int MPI_File_write_ordered_begin(MPI_File fh, ROMIO_CONST void *buf, int count,
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_ordered_end.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_ordered_end.html
index 440ce24b..f33ec424 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_ordered_end.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_ordered_end.html
@@ -9,7 +9,7 @@
 Complete a split collective write using shared file pointer 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_File_write_ordered_end(MPI_File fh, ROMIO_CONST void *buf, MPI_Status *status)
+int MPI_File_write_ordered_end(MPI_File fh, ROMIO_CONST void *buf, MPI_Status * status)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -22,12 +22,12 @@ int MPI_File_write_ordered_end(MPI_File fh, ROMIO_CONST void *buf, MPI_Status *s
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_shared.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_shared.html
index 9655a546..9240a5e6 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_shared.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_File_write_shared.html
@@ -10,7 +10,7 @@ Write using shared file pointer
 <H2>Synopsis</H2>
 <PRE>
 int MPI_File_write_shared(MPI_File fh, ROMIO_CONST void *buf, int count,
-                          MPI_Datatype datatype, MPI_Status *status)
+                          MPI_Datatype datatype, MPI_Status * status)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>fh </B> <DD> file handle (handle)
@@ -27,12 +27,12 @@ int MPI_File_write_shared(MPI_File fh, ROMIO_CONST void *buf, int count,
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Finalize.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Finalize.html
index 91760771..2d9d1134 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Finalize.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Finalize.html
@@ -9,40 +9,40 @@
 Terminates MPI execution environment 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Finalize( void )
+int MPI_Finalize(void)
 </PRE>
 <H2>Notes</H2>
 All processes must call this routine before exiting.  The number of
-processes running <em>after</em> this routine is called is undefined;
-it is best not to perform much more than a <tt>return rc</tt> after calling
-<tt>MPI_Finalize</tt>.
+processes running <EM>after</EM> this routine is called is undefined;
+it is best not to perform much more than a <TT>return rc</TT> after calling
+<TT>MPI_Finalize</TT>.
 <P>
 <H2>Thread and Signal Safety</H2>
-The MPI standard requires that <tt>MPI_Finalize</tt> be called <em>only</em> by the same
-thread that initialized MPI with either <tt>MPI_Init</tt> or <tt>MPI_Init_thread</tt>.
+The MPI standard requires that <TT>MPI_Finalize</TT> be called <EM>only</EM> by the same
+thread that initialized MPI with either <TT>MPI_Init</TT> or <TT>MPI_Init_thread</TT>.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Finalized.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Finalized.html
index d1864ce0..e9fb6d69 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Finalized.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Finalized.html
@@ -6,13 +6,13 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Finalized"><H1>MPI_Finalized</H1></A>
-Indicates whether <tt>MPI_Finalize</tt> has been called. 
+Indicates whether <TT>MPI_Finalize</TT> has been called. 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Finalized( int *flag )
+int MPI_Finalized(int *flag)
 </PRE>
 <H2>Output Parameters</H2>
-<DL><DT><B>flag </B> <DD> Flag is true if <tt>MPI_Finalize</tt> has been called and false otherwise. 
+<DL><DT><B>flag </B> <DD> Flag is true if <TT>MPI_Finalize</TT> has been called and false otherwise.
 (logical)
 </DL>
 <P>
@@ -23,27 +23,27 @@ This means that this routine may safely be used by multiple threads and
 from within a signal handler.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Free_mem.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Free_mem.html
index 729f0357..ddc607af 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Free_mem.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Free_mem.html
@@ -12,8 +12,8 @@ Free memory allocated with MPI_Alloc_mem
 int MPI_Free_mem(void *base)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>base </B> <DD> initial address of memory segment allocated by <tt>MPI_ALLOC_MEM</tt> 
-(choice) 
+<DL><DT><B>base </B> <DD> initial address of memory segment allocated by <TT>MPI_ALLOC_MEM
+</TT>(choice)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -21,31 +21,31 @@ int MPI_Free_mem(void *base)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Gather.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Gather.html
index 5c429bd3..dee3511f 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Gather.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Gather.html
@@ -10,30 +10,29 @@ Gathers together values from a group of processes
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Gather(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
-               void *recvbuf, int recvcount, MPI_Datatype recvtype,
-               int root, MPI_Comm comm)
+               void *recvbuf, int recvcount, MPI_Datatype recvtype, int root, MPI_Comm comm)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>sendbuf </B><DD>starting address of send buffer (choice) 
+<DT><B>sendbuf </B><DD>starting address of send buffer (choice)
 
-<DT><B>sendcount </B><DD>number of elements in send buffer (integer) 
+<DT><B>sendcount </B><DD>number of elements in send buffer (integer)
 
-<DT><B>sendtype </B><DD>data type of send buffer elements (handle) 
+<DT><B>sendtype </B><DD>data type of send buffer elements (handle)
 
-<DT><B>recvcount </B><DD>number of elements for any single receive (integer, 
-significant only at root) 
+<DT><B>recvcount </B><DD>number of elements for any single receive (integer,
+significant only at root)
 
-<DT><B>recvtype </B><DD>data type of recv buffer elements 
-(significant only at root) (handle) 
+<DT><B>recvtype </B><DD>data type of recv buffer elements
+(significant only at root) (handle)
 
-<DT><B>root </B><DD>rank of receiving process (integer) 
+<DT><B>root </B><DD>rank of receiving process (integer)
 
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>recvbuf </B> <DD> address of receive buffer (choice, significant only at <tt>root</tt>) 
+<DL><DT><B>recvbuf </B> <DD> address of receive buffer (choice, significant only at <TT>root</TT>)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -41,44 +40,44 @@ significant only at root)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_BUFFER </B> <DD> Invalid buffer pointer.  Usually a null buffer where
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Gatherv.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Gatherv.html
index 54fc4ce1..4586c752 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Gatherv.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Gatherv.html
@@ -15,31 +15,31 @@ int MPI_Gatherv(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>sendbuf </B><DD>starting address of send buffer (choice) 
+<DT><B>sendbuf </B><DD>starting address of send buffer (choice)
 
-<DT><B>sendcount </B><DD>number of elements in send buffer (integer) 
+<DT><B>sendcount </B><DD>number of elements in send buffer (integer)
 
-<DT><B>sendtype </B><DD>data type of send buffer elements (handle) 
+<DT><B>sendtype </B><DD>data type of send buffer elements (handle)
 
-<DT><B>recvcounts </B><DD>integer array (of length group size) 
+<DT><B>recvcounts </B><DD>integer array (of length group size)
 containing the number of elements that are received from each process
-(significant only at <tt>root</tt>) 
+(significant only at <TT>root</TT>)
 
-<DT><B>displs </B><DD>integer array (of length group size). Entry 
-<tt>i</tt>  specifies the displacement relative to recvbuf  at
-which to place the incoming data from process  <tt>i</tt>  (significant only
-at root) 
+<DT><B>displs </B><DD>integer array (of length group size). Entry
+<TT>i</TT>  specifies the displacement relative to recvbuf  at
+which to place the incoming data from process  <TT>i</TT>  (significant only
+at root)
 
-<DT><B>recvtype </B><DD>data type of recv buffer elements 
-(significant only at <tt>root</tt>) (handle) 
+<DT><B>recvtype </B><DD>data type of recv buffer elements
+(significant only at <TT>root</TT>) (handle)
 
-<DT><B>root </B><DD>rank of receiving process (integer) 
+<DT><B>root </B><DD>rank of receiving process (integer)
 
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>recvbuf </B> <DD> address of receive buffer (choice, significant only at <tt>root</tt>) 
+<DL><DT><B>recvbuf </B> <DD> address of receive buffer (choice, significant only at <TT>root</TT>)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -47,41 +47,41 @@ at root)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_BUFFER </B> <DD> Invalid buffer pointer.  Usually a null buffer where
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get.html
index 09df7b9e..17eb006f 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get.html
@@ -11,27 +11,26 @@ Get data from a memory window on a remote process
 <PRE>
 int MPI_Get(void *origin_addr, int origin_count, MPI_Datatype
             origin_datatype, int target_rank, MPI_Aint target_disp,
-            int target_count, MPI_Datatype target_datatype, MPI_Win
-            win)
+            int target_count, MPI_Datatype target_datatype, MPI_Win win)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
 <DT><B>origin_addr </B><DD>Address of the buffer in which to receive the data
 
-<DT><B>origin_count </B><DD>number of entries in origin buffer (nonnegative integer) 
+<DT><B>origin_count </B><DD>number of entries in origin buffer (nonnegative integer)
 
-<DT><B>origin_datatype </B><DD>datatype of each entry in origin buffer (handle) 
+<DT><B>origin_datatype </B><DD>datatype of each entry in origin buffer (handle)
 
-<DT><B>target_rank </B><DD>rank of target (nonnegative integer) 
+<DT><B>target_rank </B><DD>rank of target (nonnegative integer)
 
-<DT><B>target_disp </B><DD>displacement from window start to the beginning of the 
-target buffer (nonnegative integer) 
+<DT><B>target_disp </B><DD>displacement from window start to the beginning of the
+target buffer (nonnegative integer)
 
-<DT><B>target_count </B><DD>number of entries in target buffer (nonnegative integer) 
+<DT><B>target_count </B><DD>number of entries in target buffer (nonnegative integer)
 
-<DT><B>target_datatype </B><DD>datatype of each entry in target buffer (handle) 
+<DT><B>target_datatype </B><DD>datatype of each entry in target buffer (handle)
 
-<DT><B>win </B><DD>window object used for communication (handle) 
+<DT><B>win </B><DD>window object used for communication (handle)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -39,54 +38,54 @@ target buffer (nonnegative integer)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Rget
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get_accumulate.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get_accumulate.html
index b08b2800..54400a20 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get_accumulate.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get_accumulate.html
@@ -10,9 +10,9 @@ Perform an atomic, one-sided read-and-accumulate operation.
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Get_accumulate(const void *origin_addr, int origin_count,
-        MPI_Datatype origin_datatype, void *result_addr, int result_count,
-        MPI_Datatype result_datatype, int target_rank, MPI_Aint target_disp,
-        int target_count, MPI_Datatype target_datatype, MPI_Op op, MPI_Win win)
+                       MPI_Datatype origin_datatype, void *result_addr, int result_count,
+                       MPI_Datatype result_datatype, int target_rank, MPI_Aint target_disp,
+                       int target_count, MPI_Datatype target_datatype, MPI_Op op, MPI_Win win)
 </PRE>
 <P>
 Accumulate origin_count elements of type origin_datatype from the origin buffer
@@ -54,7 +54,7 @@ This operations is atomic with respect to other "accumulate" operations.
 <P>
 The get and accumulate steps are executed atomically for each basic element in
 the datatype (see MPI 3.0 Section 11.7 for details). The predefined operation
-<tt>MPI_REPLACE</tt> provides fetch-and-set behavior.
+<TT>MPI_REPLACE</TT> provides fetch-and-set behavior.
 <P>
 The origin and result buffers (origin_addr and result_addr) must be disjoint.
 Each datatype argument must be a predefined datatype or a derived datatype
@@ -64,61 +64,61 @@ operation op applies to elements of that predefined type. target_datatype must
 not specify overlapping entries, and the target buffer must fit in the target
 window or in attached memory in a dynamic window.
 <P>
-Any of the predefined operations for <tt>MPI_Reduce</tt>, as well as <tt>MPI_NO_OP</tt> or
-<tt>MPI_REPLACE</tt> can be specified as op. User-defined functions cannot be used. A
-new predefined operation, <tt>MPI_NO_OP</tt>, is defined. It corresponds to the
+Any of the predefined operations for <TT>MPI_Reduce</TT>, as well as <TT>MPI_NO_OP</TT> or
+<TT>MPI_REPLACE</TT> can be specified as op. User-defined functions cannot be used. A
+new predefined operation, <TT>MPI_NO_OP</TT>, is defined. It corresponds to the
 associative function f (a, b) = a; i.e., the current value in the target memory
 is returned in the result buffer at the origin and no operation is performed on
-the target buffer. <tt>MPI_NO_OP</tt> can be used only in <tt>MPI_Get_accumulate</tt>,
-<tt>MPI_Rget_accumulate</tt>, and <tt>MPI_Fetch_and_op</tt>. <tt>MPI_NO_OP</tt> cannot be used in
-<tt>MPI_Accumulate</tt>, <tt>MPI_Raccumulate</tt>, or collective reduction operations, such as
-<tt>MPI_Reduce</tt> and others.
+the target buffer. <TT>MPI_NO_OP</TT> can be used only in <TT>MPI_Get_accumulate</TT>,
+<TT>MPI_Rget_accumulate</TT>, and <TT>MPI_Fetch_and_op</TT>. <TT>MPI_NO_OP</TT> cannot be used in
+<TT>MPI_Accumulate</TT>, <TT>MPI_Raccumulate</TT>, or collective reduction operations, such as
+<TT>MPI_Reduce</TT> and others.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Rget_accumulate MPI_Fetch_and_op
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get_address.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get_address.html
index 6e4c225a..cfea051d 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get_address.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get_address.html
@@ -9,7 +9,7 @@
 Get the address of a location in memory 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Get_address(const void *location, MPI_Aint *address)
+int MPI_Get_address(const void *location, MPI_Aint * address)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>location </B> <DD> location in caller memory (choice)
@@ -22,11 +22,11 @@ int MPI_Get_address(const void *location, MPI_Aint *address)
 <H2>Notes</H2>
 This routine is provided for both the Fortran and C programmers.
 On many systems, the address returned by this routine will be the same
-as produced by the C <tt>&amp;</tt> operator, but this is not required in C and
+as produced by the C <TT>&amp;</TT> operator, but this is not required in C and
 may not be true of systems with word- rather than byte-oriented
 instructions or systems with segmented address spaces.
 <P>
-This routine should be used instead of <tt>MPI_Address</tt>.
+This routine should be used instead of <TT>MPI_Address</TT>.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
@@ -35,14 +35,14 @@ This means that this routine may safely be used by multiple threads and
 from within a signal handler.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 In Fortran, the integer type is always signed.  This can cause problems
 on systems where the address fits into a four byte unsigned integer but
@@ -57,22 +57,22 @@ addresses.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get_count.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get_count.html
index 93484461..9cd66394 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get_count.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get_count.html
@@ -9,53 +9,53 @@
 Gets the number of "top level" elements 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Get_count( const MPI_Status *status, MPI_Datatype datatype, int *count )
+int MPI_Get_count(const MPI_Status * status, MPI_Datatype datatype, int *count)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>status </B><DD>return status of receive operation (Status) 
+<DT><B>status </B><DD>return status of receive operation (Status)
 
-<DT><B>datatype </B><DD>datatype of each receive buffer element (handle) 
+<DT><B>datatype </B><DD>datatype of each receive buffer element (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>count </B> <DD> number of received elements (integer) 
+<DL><DT><B>count </B> <DD> number of received elements (integer)
 Notes:
 If the size of the datatype is zero, this routine will return a count of
-zero.  If the amount of data in <tt>status</tt> is not an exact multiple of the 
-size of <tt>datatype</tt> (so that <tt>count</tt> would not be integral), a <tt>count</tt> of
-<tt>MPI_UNDEFINED</tt> is returned instead.
+zero.  If the amount of data in <TT>status</TT> is not an exact multiple of the
+size of <TT>datatype</TT> (so that <TT>count</TT> would not be integral), a <TT>count</TT> of
+<TT>MPI_UNDEFINED</TT> is returned instead.
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get_elements.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get_elements.html
index e5a453a7..7691b8fd 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get_elements.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get_elements.html
@@ -9,7 +9,7 @@
 Returns the number of basic elements in a datatype 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Get_elements(const MPI_Status *status, MPI_Datatype datatype, int *count)
+int MPI_Get_elements(const MPI_Status * status, MPI_Datatype datatype, int *count)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -25,31 +25,31 @@ int MPI_Get_elements(const MPI_Status *status, MPI_Datatype datatype, int *count
 <H2>Notes</H2>
 <P>
 If the size of the datatype is zero and the amount of data returned as
-determined by <tt>status</tt> is also zero, this routine will return a count of
+determined by <TT>status</TT> is also zero, this routine will return a count of
 zero.  This is consistent with a clarification made by the MPI Forum.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get_elements_x.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get_elements_x.html
index 89c07d52..97166940 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get_elements_x.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get_elements_x.html
@@ -9,7 +9,7 @@
 Returns the number of basic elements in a datatype 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Get_elements_x(const MPI_Status *status, MPI_Datatype datatype, MPI_Count *count)
+int MPI_Get_elements_x(const MPI_Status * status, MPI_Datatype datatype, MPI_Count * count)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -27,31 +27,31 @@ int MPI_Get_elements_x(const MPI_Status *status, MPI_Datatype datatype, MPI_Coun
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get_library_version.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get_library_version.html
index 4fa02f61..4f002d68 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get_library_version.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get_library_version.html
@@ -29,27 +29,27 @@ This means that this routine may safely be used by multiple threads and
 from within a signal handler.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get_processor_name.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get_processor_name.html
index 159b9feb..2576811e 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get_processor_name.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get_processor_name.html
@@ -9,42 +9,42 @@
 Gets the name of the processor 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Get_processor_name( char *name, int *resultlen )
+int MPI_Get_processor_name(char *name, int *resultlen)
 </PRE>
 <H2>Output Parameters</H2>
 <DL>
 <DT><B>name </B><DD>A unique specifier for the actual (as opposed to virtual) node. This
-must be an array of size at least <tt>MPI_MAX_PROCESSOR_NAME</tt>.
+must be an array of size at least <TT>MPI_MAX_PROCESSOR_NAME</TT>.
 
-<DT><B>resultlen </B><DD>Length (in characters) of the name 
+<DT><B>resultlen </B><DD>Length (in characters) of the name
 </DL>
 <P>
 <H2>Notes</H2>
 The name returned should identify a particular piece of hardware;
 the exact format is implementation defined.  This name may or may not
-be the same as might be returned by <tt>gethostname</tt>, <tt>uname</tt>, or <tt>sysinfo</tt>.
+be the same as might be returned by <TT>gethostname</TT>, <TT>uname</TT>, or <TT>sysinfo</TT>.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 In Fortran, the character argument should be declared as a character string
-of <tt>MPI_MAX_PROCESSOR_NAME</tt> rather than an array of dimension
-<tt>MPI_MAX_PROCESSOR_NAME</tt>.  That is,
+of <TT>MPI_MAX_PROCESSOR_NAME</TT> rather than an array of dimension
+<TT>MPI_MAX_PROCESSOR_NAME</TT>.  That is,
 <PRE>
    character*(MPI_MAX_PROCESSOR_NAME) name
 </PRE>
@@ -59,23 +59,23 @@ The two
 <P>
 The sizes of MPI strings in Fortran are one less than the sizes of that
 string in C/C++ because the C/C++ versions provide room for the trailing
-null character required by C/C++.  For example, <tt>MPI_MAX_ERROR_STRING</tt> is
-<tt>mpif.h</tt> is one smaller than the same value in <tt>mpi.h</tt>.  See the MPI
+null character required by C/C++.  For example, <TT>MPI_MAX_ERROR_STRING</TT> is
+<TT>mpif.h</TT> is one smaller than the same value in <TT>mpi.h</TT>.  See the MPI
 standard, sections 2.6.2 and 4.12.9.
 <P>
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get_version.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get_version.html
index 57cc32d3..15820287 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get_version.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Get_version.html
@@ -9,7 +9,7 @@
 Return the version number of MPI 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Get_version( int *version, int *subversion )
+int MPI_Get_version(int *version, int *subversion)
 </PRE>
 <H2>Output Parameters</H2>
 <DL>
@@ -25,27 +25,27 @@ This means that this routine may safely be used by multiple threads and
 from within a signal handler.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Graph_create.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Graph_create.html
index 25e35226..ee096a46 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Graph_create.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Graph_create.html
@@ -10,23 +10,23 @@ Makes a new communicator to which topology information has been attached
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Graph_create(MPI_Comm comm_old, int nnodes, const int indx[],
-                     const int edges[], int reorder, MPI_Comm *comm_graph)
+                     const int edges[], int reorder, MPI_Comm * comm_graph)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>comm_old </B><DD>input communicator without topology (handle) 
+<DT><B>comm_old </B><DD>input communicator without topology (handle)
 
-<DT><B>nnodes </B><DD>number of nodes in graph (integer) 
+<DT><B>nnodes </B><DD>number of nodes in graph (integer)
 
-<DT><B>indx </B><DD>array of integers describing node degrees (see below) 
+<DT><B>indx </B><DD>array of integers describing node degrees (see below)
 
-<DT><B>edges </B><DD>array of integers describing graph edges (see below) 
+<DT><B>edges </B><DD>array of integers describing graph edges (see below)
 
-<DT><B>reorder </B><DD>ranking may be reordered (true) or not (false) (logical) 
+<DT><B>reorder </B><DD>ranking may be reordered (true) or not (false) (logical)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>comm_graph </B> <DD> communicator with graph topology added (handle) 
+<DL><DT><B>comm_graph </B> <DD> communicator with graph topology added (handle)
 </DL>
 <P>
 <H2>Notes</H2>
@@ -34,38 +34,38 @@ Each process must provide a description of the entire graph, not just the
 neigbors of the calling process.
 <P>
 <H2>Algorithm</H2>
-We ignore the <tt>reorder</tt> info currently.
+We ignore the <TT>reorder</TT> info currently.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -73,13 +73,13 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_TOPOLOGY </B> <DD> Invalid topology.  Either there is no topology 
 associated with this communicator, or it is not the correct type (e.g.,
-<tt>MPI_CART</tt> when expecting <tt>MPI_GRAPH</tt>).
+<TT>MPI_CART</TT> when expecting <TT>MPI_GRAPH</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <P>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Graph_get.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Graph_get.html
index 96b1c552..325aac7f 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Graph_get.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Graph_get.html
@@ -6,26 +6,25 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Graph_get"><H1>MPI_Graph_get</H1></A>
-Retrieves graph topology information associated with a  communicator 
+Retrieves graph topology information associated with a communicator 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Graph_get(MPI_Comm comm, int maxindex, int maxedges, 
-                  int indx[], int edges[])
+int MPI_Graph_get(MPI_Comm comm, int maxindex, int maxedges, int indx[], int edges[])
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>comm </B><DD>communicator with graph structure (handle) 
+<DT><B>comm </B><DD>communicator with graph structure (handle)
 
-<DT><B>maxindex </B><DD>length of vector <tt>indx</tt> in the calling program  (integer) 
+<DT><B>maxindex </B><DD>length of vector <TT>indx</TT> in the calling program  (integer)
 
-<DT><B>maxedges </B><DD>length of vector <tt>edges</tt> in the calling program  (integer) 
+<DT><B>maxedges </B><DD>length of vector <TT>edges</TT> in the calling program  (integer)
 </DL>
 <P>
 <H2>Output Parameters</H2>
 <DL>
-<DT><B>indx </B><DD>array of integers containing the graph structure (for details see the definition of <tt>MPI_GRAPH_CREATE</tt>) 
+<DT><B>indx </B><DD>array of integers containing the graph structure (for details see the definition of <TT>MPI_GRAPH_CREATE</TT>)
 
-<DT><B>edges </B><DD>array of integers containing the graph structure 
+<DT><B>edges </B><DD>array of integers containing the graph structure
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -35,27 +34,27 @@ This means that this routine may safely be used by multiple threads and
 from within a signal handler.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -63,12 +62,12 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_TOPOLOGY </B> <DD> Invalid topology.  Either there is no topology 
 associated with this communicator, or it is not the correct type (e.g.,
-<tt>MPI_CART</tt> when expecting <tt>MPI_GRAPH</tt>).
+<TT>MPI_CART</TT> when expecting <TT>MPI_GRAPH</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Graph_map.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Graph_map.html
index 5ad4e3b6..1503f75b 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Graph_map.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Graph_map.html
@@ -9,23 +9,22 @@
 Maps process to graph topology information 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Graph_map(MPI_Comm comm, int nnodes, const int indx[], const int edges[],
-                  int *newrank)
+int MPI_Graph_map(MPI_Comm comm, int nnodes, const int indx[], const int edges[], int *newrank)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>comm </B><DD>input communicator (handle) 
+<DT><B>comm </B><DD>input communicator (handle)
 
-<DT><B>nnodes </B><DD>number of graph nodes (integer) 
+<DT><B>nnodes </B><DD>number of graph nodes (integer)
 
-<DT><B>indx </B><DD>integer array specifying the graph structure, see <tt>MPI_GRAPH_CREATE</tt> 
-
-<DT><B>edges </B><DD>integer array specifying the graph structure 
+<DT><B>indx </B><DD>integer array specifying the graph structure, see <TT>MPI_GRAPH_CREATE
+</TT>
+<DT><B>edges </B><DD>integer array specifying the graph structure
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>newrank </B> <DD> reordered rank of the calling process; <tt>MPI_UNDEFINED</tt> if the 
-calling process does not belong to graph (integer) 
+<DL><DT><B>newrank </B> <DD> reordered rank of the calling process; <TT>MPI_UNDEFINED</TT> if the
+calling process does not belong to graph (integer)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -35,27 +34,27 @@ This means that this routine may safely be used by multiple threads and
 from within a signal handler.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -63,12 +62,12 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_TOPOLOGY </B> <DD> Invalid topology.  Either there is no topology 
 associated with this communicator, or it is not the correct type (e.g.,
-<tt>MPI_CART</tt> when expecting <tt>MPI_GRAPH</tt>).
+<TT>MPI_CART</TT> when expecting <TT>MPI_GRAPH</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Graph_neighbors.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Graph_neighbors.html
index 2c0fcc16..3beeea78 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Graph_neighbors.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Graph_neighbors.html
@@ -6,24 +6,23 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Graph_neighbors"><H1>MPI_Graph_neighbors</H1></A>
-Returns the neighbors of a node associated  with a graph topology 
+Returns the neighbors of a node associated with a graph topology 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Graph_neighbors(MPI_Comm comm, int rank, int maxneighbors, 
-                      int neighbors[])
+int MPI_Graph_neighbors(MPI_Comm comm, int rank, int maxneighbors, int neighbors[])
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>comm </B><DD>communicator with graph topology (handle) 
+<DT><B>comm </B><DD>communicator with graph topology (handle)
 
-<DT><B>rank </B><DD>rank of process in group of comm (integer) 
+<DT><B>rank </B><DD>rank of process in group of comm (integer)
 
-<DT><B>maxneighbors </B><DD>size of array neighbors (integer) 
+<DT><B>maxneighbors </B><DD>size of array neighbors (integer)
 </DL>
 <P>
 <H2>Output Parameters</H2>
 <DL><DT><B>neighbors </B> <DD> ranks of processes that are neighbors to specified process
-(array of integer) 
+(array of integer)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -33,27 +32,27 @@ This means that this routine may safely be used by multiple threads and
 from within a signal handler.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -61,16 +60,16 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_TOPOLOGY </B> <DD> Invalid topology.  Either there is no topology 
 associated with this communicator, or it is not the correct type (e.g.,
-<tt>MPI_CART</tt> when expecting <tt>MPI_GRAPH</tt>).
+<TT>MPI_CART</TT> when expecting <TT>MPI_GRAPH</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Graph_neighbors_count.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Graph_neighbors_count.html
index c2e9ca45..7759a067 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Graph_neighbors_count.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Graph_neighbors_count.html
@@ -13,13 +13,13 @@ int MPI_Graph_neighbors_count(MPI_Comm comm, int rank, int *nneighbors)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>comm </B><DD>communicator with graph topology (handle) 
+<DT><B>comm </B><DD>communicator with graph topology (handle)
 
-<DT><B>rank </B><DD>rank of process in group of <tt>comm</tt> (integer) 
+<DT><B>rank </B><DD>rank of process in group of <TT>comm</TT> (integer)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>nneighbors </B> <DD> number of neighbors of specified process (integer) 
+<DL><DT><B>nneighbors </B> <DD> number of neighbors of specified process (integer)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -29,27 +29,27 @@ This means that this routine may safely be used by multiple threads and
 from within a signal handler.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -57,16 +57,16 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_TOPOLOGY </B> <DD> Invalid topology.  Either there is no topology 
 associated with this communicator, or it is not the correct type (e.g.,
-<tt>MPI_CART</tt> when expecting <tt>MPI_GRAPH</tt>).
+<TT>MPI_CART</TT> when expecting <TT>MPI_GRAPH</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Graphdims_get.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Graphdims_get.html
index 3cb5cccc..ad648077 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Graphdims_get.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Graphdims_get.html
@@ -6,20 +6,20 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Graphdims_get"><H1>MPI_Graphdims_get</H1></A>
-Retrieves graph topology information associated with a  communicator 
+Retrieves graph topology information associated with a communicator 
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Graphdims_get(MPI_Comm comm, int *nnodes, int *nedges)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>comm </B> <DD> communicator for group with graph structure (handle) 
+<DL><DT><B>comm </B> <DD> communicator for group with graph structure (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
 <DL>
-<DT><B>nnodes </B><DD>number of nodes in graph (integer) 
+<DT><B>nnodes </B><DD>number of nodes in graph (integer)
 
-<DT><B>nedges </B><DD>number of edges in graph (integer) 
+<DT><B>nedges </B><DD>number of edges in graph (integer)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -29,27 +29,27 @@ This means that this routine may safely be used by multiple threads and
 from within a signal handler.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -57,12 +57,12 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_TOPOLOGY </B> <DD> Invalid topology.  Either there is no topology 
 associated with this communicator, or it is not the correct type (e.g.,
-<tt>MPI_CART</tt> when expecting <tt>MPI_GRAPH</tt>).
+<TT>MPI_CART</TT> when expecting <TT>MPI_GRAPH</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Grequest_complete.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Grequest_complete.html
index f86576a1..10cd1b22 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Grequest_complete.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Grequest_complete.html
@@ -9,7 +9,7 @@
 Notify MPI that a user-defined request is complete 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Grequest_complete( MPI_Request request )
+int MPI_Grequest_complete(MPI_Request request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>request </B> <DD> Generalized request to mark as complete
@@ -20,38 +20,38 @@ int MPI_Grequest_complete( MPI_Request request )
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Grequest_start
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Grequest_start.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Grequest_start.html
index 74584b2b..15f5a748 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Grequest_start.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Grequest_start.html
@@ -9,18 +9,18 @@
 Create and return a user-defined request 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Grequest_start( MPI_Grequest_query_function *query_fn, 
-                      MPI_Grequest_free_function *free_fn, 
-                      MPI_Grequest_cancel_function *cancel_fn, 
-                      void *extra_state, MPI_Request *request )
+int MPI_Grequest_start(MPI_Grequest_query_function * query_fn,
+                       MPI_Grequest_free_function * free_fn,
+                       MPI_Grequest_cancel_function * cancel_fn,
+                       void *extra_state, MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>query_fn </B><DD>callback function invoked when request status is queried (function)  
+<DT><B>query_fn </B><DD>callback function invoked when request status is queried (function)
 
-<DT><B>free_fn </B><DD>callback function invoked when request is freed (function) 
+<DT><B>free_fn </B><DD>callback function invoked when request is freed (function)
 
-<DT><B>cancel_fn </B><DD>callback function invoked when request is cancelled (function) 
+<DT><B>cancel_fn </B><DD>callback function invoked when request is cancelled (function)
 
 <DT><B>extra_state </B><DD>Extra state passed to the above functions.
 </DL>
@@ -33,21 +33,21 @@ int MPI_Grequest_start( MPI_Grequest_query_function *query_fn,
 The return values from the callback functions must be a valid MPI error code
 or class.  This value may either be the return value from any MPI routine
 (with one exception noted below) or any of the MPI error classes.
-For portable programs, <tt>MPI_ERR_OTHER</tt> may be used; to provide more
+For portable programs, <TT>MPI_ERR_OTHER</TT> may be used; to provide more
 specific information, create a new MPI error class or code with
-<tt>MPI_Add_error_class</tt> or <tt>MPI_Add_error_code</tt> and return that value.
+<TT>MPI_Add_error_class</TT> or <TT>MPI_Add_error_code</TT> and return that value.
 <P>
 The MPI standard is not clear on the return values from the callback routines.
 However, there are notes in the standard that imply that these are MPI error
 codes.  For example, pages 169 line 46 through page 170, line 1 require that
-the <tt>free_fn</tt> return an MPI error code that may be used in the MPI completion
-functions when they return <tt>MPI_ERR_IN_STATUS</tt>.
+the <TT>free_fn</TT> return an MPI error code that may be used in the MPI completion
+functions when they return <TT>MPI_ERR_IN_STATUS</TT>.
 <P>
-The one special case is the error value returned by <tt>MPI_Comm_dup</tt> when
+The one special case is the error value returned by <TT>MPI_Comm_dup</TT> when
 the attribute callback routine returns a failure.  The MPI standard is not
 clear on what values may be used to indicate an error return.  Further,
 the Intel MPI test suite made use of non-zero values to indicate failure,
-and expected these values to be returned by the <tt>MPI_Comm_dup</tt> when the
+and expected these values to be returned by the <TT>MPI_Comm_dup</TT> when the
 attribute routines encountered an error.  Such error values may not be valid
 MPI error codes or classes.  Because of this, it is the user's responsibility
 to either use valid MPI error codes in return from the attribute callbacks,
@@ -60,37 +60,37 @@ that MPI error classes are valid error codes).
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_compare.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_compare.html
index 67b37dc0..f8aff8b9 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_compare.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_compare.html
@@ -13,15 +13,15 @@ int MPI_Group_compare(MPI_Group group1, MPI_Group group2, int *result)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>group1 </B><DD>group1 (handle) 
+<DT><B>group1 </B><DD>group1 (handle)
 
-<DT><B>group2 </B><DD>group2 (handle) 
+<DT><B>group2 </B><DD>group2 (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>result </B> <DD> integer which is <tt>MPI_IDENT</tt> if the order and members of
-the two groups are the same, <tt>MPI_SIMILAR</tt> if only the members are the same,
-and <tt>MPI_UNEQUAL</tt> otherwise
+<DL><DT><B>result </B> <DD> integer which is <TT>MPI_IDENT</TT> if the order and members of
+the two groups are the same, <TT>MPI_SIMILAR</TT> if only the members are the same,
+and <TT>MPI_UNEQUAL</TT> otherwise
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -29,31 +29,31 @@ and <tt>MPI_UNEQUAL</tt> otherwise
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -62,6 +62,6 @@ possible.
 <DL><DT><B>MPI_ERR_GROUP </B> <DD> Null or invalid group passed to function.  
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_difference.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_difference.html
index 65d77aca..b9478ba9 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_difference.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_difference.html
@@ -9,52 +9,52 @@
 Makes a group from the difference of two groups 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Group_difference(MPI_Group group1, MPI_Group group2, MPI_Group *newgroup)
+int MPI_Group_difference(MPI_Group group1, MPI_Group group2, MPI_Group * newgroup)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>group1 </B><DD>first group (handle) 
+<DT><B>group1 </B><DD>first group (handle)
 
-<DT><B>group2 </B><DD>second group (handle) 
+<DT><B>group2 </B><DD>second group (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>newgroup </B> <DD> difference group (handle) 
+<DL><DT><B>newgroup </B> <DD> difference group (handle)
 </DL>
 <P>
 <H2>Notes</H2>
-The generated group containc the members of <tt>group1</tt> that are not in <tt>group2</tt>.
+The generated group containc the members of <TT>group1</TT> that are not in <TT>group2</TT>.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -66,7 +66,7 @@ possible.
 implementation is unable to acquire memory.  
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Group_free
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_excl.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_excl.html
index 8549a340..1449967e 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_excl.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_excl.html
@@ -9,20 +9,21 @@
 Produces a group by reordering an existing group and taking only unlisted members 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Group_excl(MPI_Group group, int n, const int ranks[], MPI_Group *newgroup)
+int MPI_Group_excl(MPI_Group group, int n, const int ranks[], MPI_Group * newgroup)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>group </B><DD>group (handle) 
+<DT><B>group </B><DD>group (handle)
 
-<DT><B>n </B><DD>number of elements in array <tt>ranks</tt> (integer) 
+<DT><B>n </B><DD>number of elements in array <TT>ranks</TT> (integer)
 
-<DT><B>ranks </B><DD>array of integer ranks in <tt>group</tt> not to appear in <tt>newgroup</tt> 
+<DT><B>ranks </B><DD>array of integer ranks in <TT>group</TT> not to appear in <TT>newgroup
+</TT>
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>newgroup </B> <DD> new group derived from above, preserving the order defined by 
-<tt>group</tt> (handle) 
+<DL><DT><B>newgroup </B> <DD> new group derived from above, preserving the order defined by
+<TT>group</TT> (handle)
 </DL>
 <P>
 <H2>Note</H2>
@@ -35,31 +36,31 @@ function is erroneous.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -71,14 +72,14 @@ possible.
 implementation is unable to acquire memory.  
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Group_free
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_free.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_free.html
index e38d6768..67793588 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_free.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_free.html
@@ -9,52 +9,52 @@
 Frees a group 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Group_free(MPI_Group *group)
+int MPI_Group_free(MPI_Group * group)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>group </B> <DD> group to free (handle) 
+<DL><DT><B>group </B> <DD> group to free (handle)
 </DL>
 <P>
 <H2>Notes</H2>
-On output, group is set to <tt>MPI_GROUP_NULL</tt>.
+On output, group is set to <TT>MPI_GROUP_NULL</TT>.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> This error class is associated with an error code that 
 indicates that an attempt was made to free one of the permanent groups.
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_incl.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_incl.html
index c650483f..5453cc21 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_incl.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_incl.html
@@ -9,21 +9,21 @@
 Produces a group by reordering an existing group and taking only listed members 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Group_incl(MPI_Group group, int n, const int ranks[], MPI_Group *newgroup)
+int MPI_Group_incl(MPI_Group group, int n, const int ranks[], MPI_Group * newgroup)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>group </B><DD>group (handle) 
+<DT><B>group </B><DD>group (handle)
 
-<DT><B>n </B><DD>number of elements in array <tt>ranks</tt> (and size of newgroup ) (integer) 
+<DT><B>n </B><DD>number of elements in array <TT>ranks</TT> (and size of newgroup) (integer)
 
-<DT><B>ranks </B><DD>ranks of processes in <tt>group</tt> to appear in <tt>newgroup</tt> (array of 
-integers) 
+<DT><B>ranks </B><DD>ranks of processes in <TT>group</TT> to appear in <TT>newgroup</TT> (array of
+integers)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>newgroup </B> <DD> new group derived from above, in the order defined by <tt>ranks</tt> 
-(handle) 
+<DL><DT><B>newgroup </B> <DD> new group derived from above, in the order defined by <TT>ranks
+</TT>(handle)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -31,31 +31,31 @@ integers)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -64,17 +64,17 @@ possible.
 <DL><DT><B>MPI_ERR_GROUP </B> <DD> Null or invalid group passed to function.  
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_INTERN </B> <DD> This error is returned when some part of the MPICH 
 implementation is unable to acquire memory.  
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Group_free
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_intersection.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_intersection.html
index 631d68b5..849a6ae5 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_intersection.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_intersection.html
@@ -9,53 +9,53 @@
 Produces a group as the intersection of two existing groups 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Group_intersection(MPI_Group group1, MPI_Group group2, MPI_Group *newgroup)
+int MPI_Group_intersection(MPI_Group group1, MPI_Group group2, MPI_Group * newgroup)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>group1 </B><DD>first group (handle) 
+<DT><B>group1 </B><DD>first group (handle)
 
-<DT><B>group2 </B><DD>second group (handle) 
+<DT><B>group2 </B><DD>second group (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>newgroup </B> <DD> intersection group (handle) 
+<DL><DT><B>newgroup </B> <DD> intersection group (handle)
 </DL>
 <P>
 <H2>Notes</H2>
-The output group contains those processes that are in both <tt>group1</tt> and
-<tt>group2</tt>.
+The output group contains those processes that are in both <TT>group1</TT> and
+<TT>group2</TT>.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -67,7 +67,7 @@ possible.
 implementation is unable to acquire memory.  
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Group_free
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_range_excl.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_range_excl.html
index 159f9a5c..ae507e1d 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_range_excl.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_range_excl.html
@@ -9,23 +9,22 @@
 Produces a group by excluding ranges of processes from an existing group 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Group_range_excl(MPI_Group group, int n, int ranges[][3], 
-                         MPI_Group *newgroup)
+int MPI_Group_range_excl(MPI_Group group, int n, int ranges[][3], MPI_Group * newgroup)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>group </B><DD>group (handle) 
+<DT><B>group </B><DD>group (handle)
 
-<DT><B>n </B><DD>number of elements in array <tt>ranks</tt> (integer) 
+<DT><B>n </B><DD>number of elements in array <TT>ranks</TT> (integer)
 
 <DT><B>ranges </B><DD>a one-dimensional array of integer triplets of the
 form (first rank, last rank, stride), indicating the ranks in
-<tt>group</tt>  of processes to be excluded from the output group <tt>newgroup</tt> .  
+<TT>group</TT>  of processes to be excluded from the output group <TT>newgroup</TT> .
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>newgroup </B> <DD> new group derived from above, preserving the 
-order in <tt>group</tt>  (handle) 
+<DL><DT><B>newgroup </B> <DD> new group derived from above, preserving the
+order in <TT>group</TT>  (handle)
 </DL>
 <P>
 <H2>Note</H2>
@@ -38,31 +37,31 @@ function is erroneous.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -75,13 +74,13 @@ implementation is unable to acquire memory.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Group_free
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_range_incl.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_range_incl.html
index 0a1f5799..b2bf5d5e 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_range_incl.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_range_incl.html
@@ -6,26 +6,25 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Group_range_incl"><H1>MPI_Group_range_incl</H1></A>
-Creates a new group from ranges of ranks in an  existing group 
+Creates a new group from ranges of ranks in an existing group 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Group_range_incl(MPI_Group group, int n, int ranges[][3], 
-                         MPI_Group *newgroup)
+int MPI_Group_range_incl(MPI_Group group, int n, int ranges[][3], MPI_Group * newgroup)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>group </B><DD>group (handle) 
+<DT><B>group </B><DD>group (handle)
 
-<DT><B>n </B><DD>number of triplets in array  <tt>ranges</tt> (integer) 
+<DT><B>n </B><DD>number of triplets in array  <TT>ranges</TT> (integer)
 
-<DT><B>ranges </B><DD>a one-dimensional array of integer triplets, of the 
+<DT><B>ranges </B><DD>a one-dimensional array of integer triplets, of the
 form (first rank, last rank, stride) indicating ranks in
-<tt>group</tt>  or processes to be included in <tt>newgroup</tt>.
+<TT>group</TT>  or processes to be included in <TT>newgroup</TT>.
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>newgroup </B> <DD> new group derived from above, in the 
-order defined by  <tt>ranges</tt> (handle)
+<DL><DT><B>newgroup </B> <DD> new group derived from above, in the
+order defined by  <TT>ranges</TT> (handle)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -33,31 +32,31 @@ order defined by  <tt>ranges</tt> (handle)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -69,14 +68,14 @@ possible.
 implementation is unable to acquire memory.  
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Group_free
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_rank.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_rank.html
index 374927ac..91871706 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_rank.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_rank.html
@@ -12,12 +12,12 @@ Returns the rank of this process in the given group
 int MPI_Group_rank(MPI_Group group, int *rank)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>group </B> <DD> group (handle) 
+<DL><DT><B>group </B> <DD> group (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>rank </B> <DD> rank of the calling process in group, or <tt>MPI_UNDEFINED</tt>  if the 
-process is not a member (integer) 
+<DL><DT><B>rank </B> <DD> rank of the calling process in group, or <TT>MPI_UNDEFINED</TT>  if the
+process is not a member (integer)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -27,27 +27,27 @@ This means that this routine may safely be used by multiple threads and
 from within a signal handler.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -56,6 +56,6 @@ possible.
 <DL><DT><B>MPI_ERR_GROUP </B> <DD> Null or invalid group passed to function.  
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_size.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_size.html
index fcecce57..4fe65e5e 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_size.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_size.html
@@ -13,11 +13,11 @@ int MPI_Group_size(MPI_Group group, int *size)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>group </B><DD>group (handle) 
+<DT><B>group </B><DD>group (handle)
 
 <P>
 <H2>Output Parameters</H2>
-<DT><B>size </B><DD>number of processes in the group (integer) 
+<DT><B>size </B><DD>number of processes in the group (integer)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -27,27 +27,27 @@ This means that this routine may safely be used by multiple threads and
 from within a signal handler.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -56,6 +56,6 @@ possible.
 <DL><DT><B>MPI_ERR_GROUP </B> <DD> Null or invalid group passed to function.  
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_translate_ranks.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_translate_ranks.html
index 16224689..dd0b4543 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_translate_ranks.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_translate_ranks.html
@@ -6,61 +6,61 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Group_translate_ranks"><H1>MPI_Group_translate_ranks</H1></A>
-Translates the ranks of processes in one group to  those in another group 
+Translates the ranks of processes in one group to those in another group 
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Group_translate_ranks(MPI_Group group1, int n, const int ranks1[],
-                            MPI_Group group2, int ranks2[])
+                              MPI_Group group2, int ranks2[])
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>group1 </B><DD>group1 (handle) 
+<DT><B>group1 </B><DD>group1 (handle)
 
-<DT><B>n </B><DD>number of ranks in  <tt>ranks1</tt> and <tt>ranks2</tt>  arrays (integer) 
+<DT><B>n </B><DD>number of ranks in  <TT>ranks1</TT> and <TT>ranks2</TT>  arrays (integer)
 
-<DT><B>ranks1 </B><DD>array of zero or more valid ranks in <tt>group1</tt> 
-
-<DT><B>group2 </B><DD>group2 (handle) 
+<DT><B>ranks1 </B><DD>array of zero or more valid ranks in <TT>group1
+</TT>
+<DT><B>group2 </B><DD>group2 (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>ranks2 </B> <DD> array of corresponding ranks in group2,  <tt>MPI_UNDEFINED</tt>  when no 
-correspondence exists. 
+<DL><DT><B>ranks2 </B> <DD> array of corresponding ranks in group2,  <TT>MPI_UNDEFINED</TT>  when no
+correspondence exists.
 </DL>
 <P>
 As a special case (see the MPI-2 errata), if the input rank is
-<tt>MPI_PROC_NULL</tt>, <tt>MPI_PROC_NULL</tt> is given as the output rank.
+<TT>MPI_PROC_NULL</TT>, <TT>MPI_PROC_NULL</TT> is given as the output rank.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_union.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_union.html
index 7714605e..21c28607 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_union.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Group_union.html
@@ -9,17 +9,17 @@
 Produces a group by combining two groups 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Group_union(MPI_Group group1, MPI_Group group2, MPI_Group *newgroup)
+int MPI_Group_union(MPI_Group group1, MPI_Group group2, MPI_Group * newgroup)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>group1 </B><DD>first group (handle) 
+<DT><B>group1 </B><DD>first group (handle)
 
-<DT><B>group2 </B><DD>second group (handle) 
+<DT><B>group2 </B><DD>second group (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>newgroup </B> <DD> union group (handle) 
+<DL><DT><B>newgroup </B> <DD> union group (handle)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -27,31 +27,31 @@ int MPI_Group_union(MPI_Group group1, MPI_Group group2, MPI_Group *newgroup)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -63,7 +63,7 @@ possible.
 implementation is unable to acquire memory.  
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Group_free
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Iallgather.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Iallgather.html
index d2232357..71059f01 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Iallgather.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Iallgather.html
@@ -11,7 +11,7 @@ Gathers data from all tasks and distribute the combined data to all tasks in a n
 <PRE>
 int MPI_Iallgather(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
                    void *recvbuf, int recvcount, MPI_Datatype recvtype,
-                   MPI_Comm comm, MPI_Request *request)
+                   MPI_Comm comm, MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -40,31 +40,31 @@ int MPI_Iallgather(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Iallgatherv.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Iallgatherv.html
index a1c757ab..5c5fc51d 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Iallgatherv.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Iallgatherv.html
@@ -11,7 +11,7 @@ Gathers data from all tasks and deliver the combined data to all tasks in a nonb
 <PRE>
 int MPI_Iallgatherv(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
                     const int recvcounts[], const int displs[], MPI_Datatype recvtype,
-                    MPI_Comm comm, MPI_Request *request)
+                    MPI_Comm comm, MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -42,31 +42,31 @@ int MPI_Iallgatherv(const void *sendbuf, int sendcount, MPI_Datatype sendtype, v
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Iallreduce.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Iallreduce.html
index b4cb4f51..ac95dbf4 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Iallreduce.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Iallreduce.html
@@ -10,8 +10,7 @@ Combines values from all processes and distributes the result back to all proces
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Iallreduce(const void *sendbuf, void *recvbuf, int count,
-                   MPI_Datatype datatype, MPI_Op op, MPI_Comm comm,
-                   MPI_Request *request)
+                   MPI_Datatype datatype, MPI_Op op, MPI_Comm comm, MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -38,31 +37,31 @@ int MPI_Iallreduce(const void *sendbuf, void *recvbuf, int count,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ialltoall.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ialltoall.html
index 69e6b579..32bdb656 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ialltoall.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ialltoall.html
@@ -11,7 +11,7 @@ Sends data from all to all processes in a nonblocking way
 <PRE>
 int MPI_Ialltoall(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
                   void *recvbuf, int recvcount, MPI_Datatype recvtype,
-                  MPI_Comm comm, MPI_Request *request)
+                  MPI_Comm comm, MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -40,31 +40,31 @@ int MPI_Ialltoall(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ialltoallv.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ialltoallv.html
index 1ae61a70..464cebe0 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ialltoallv.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ialltoallv.html
@@ -11,7 +11,7 @@ Sends data from all to all processes in a nonblocking way; each process may send
 <PRE>
 int MPI_Ialltoallv(const void *sendbuf, const int sendcounts[], const int sdispls[],
                    MPI_Datatype sendtype, void *recvbuf, const int recvcounts[],
-                   const int rdispls[], MPI_Datatype recvtype, MPI_Comm comm, MPI_Request *request)
+                   const int rdispls[], MPI_Datatype recvtype, MPI_Comm comm, MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -44,31 +44,31 @@ int MPI_Ialltoallv(const void *sendbuf, const int sendcounts[], const int sdispl
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ialltoallw.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ialltoallw.html
index ff27f397..53c83776 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ialltoallw.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ialltoallw.html
@@ -12,7 +12,7 @@ Nonblocking generalized all-to-all communication allowing different datatypes, c
 int MPI_Ialltoallw(const void *sendbuf, const int sendcounts[], const int sdispls[],
                    const MPI_Datatype sendtypes[], void *recvbuf, const int recvcounts[],
                    const int rdispls[], const MPI_Datatype recvtypes[], MPI_Comm comm,
-                   MPI_Request *request)
+                   MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -45,31 +45,31 @@ int MPI_Ialltoallw(const void *sendbuf, const int sendcounts[], const int sdispl
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ibarrier.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ibarrier.html
index b2294012..bb6f07ca 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ibarrier.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ibarrier.html
@@ -9,7 +9,7 @@
 Notifies the process that it has reached the barrier and returns immediately 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Ibarrier(MPI_Comm comm, MPI_Request *request)
+int MPI_Ibarrier(MPI_Comm comm, MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>comm </B> <DD> communicator (handle)
@@ -34,31 +34,31 @@ group have called MPI_Ibarrier.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ibcast.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ibcast.html
index c8d8875b..20b97754 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ibcast.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ibcast.html
@@ -9,7 +9,8 @@
 Broadcasts a message from the process with rank "root" to all other processes of the communicator in a nonblocking way 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Ibcast(void *buffer, int count, MPI_Datatype datatype, int root, MPI_Comm comm, MPI_Request *request)
+int MPI_Ibcast(void *buffer, int count, MPI_Datatype datatype, int root, MPI_Comm comm,
+               MPI_Request * request)
 </PRE>
 <H2>Input/Output Parameters</H2>
 <DL><DT><B>buffer </B> <DD> starting address of buffer (choice)
@@ -35,31 +36,31 @@ int MPI_Ibcast(void *buffer, int count, MPI_Datatype datatype, int root, MPI_Com
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ibsend.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ibsend.html
index 03afb77c..69f31424 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ibsend.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ibsend.html
@@ -10,25 +10,25 @@ Starts a nonblocking buffered send
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Ibsend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-               MPI_Comm comm, MPI_Request *request)
+               MPI_Comm comm, MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>buf </B><DD>initial address of send buffer (choice) 
+<DT><B>buf </B><DD>initial address of send buffer (choice)
 
-<DT><B>count </B><DD>number of elements in send buffer (integer) 
+<DT><B>count </B><DD>number of elements in send buffer (integer)
 
-<DT><B>datatype </B><DD>datatype of each send buffer element (handle) 
+<DT><B>datatype </B><DD>datatype of each send buffer element (handle)
 
-<DT><B>dest </B><DD>rank of destination (integer) 
+<DT><B>dest </B><DD>rank of destination (integer)
 
-<DT><B>tag </B><DD>message tag (integer) 
+<DT><B>tag </B><DD>message tag (integer)
 
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>request </B> <DD> communication request (handle) 
+<DL><DT><B>request </B> <DD> communication request (handle)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -36,54 +36,54 @@ int MPI_Ibsend(const void *buf, int count, MPI_Datatype datatype, int dest, int
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_TAG </B> <DD> Invalid tag argument.  Tags must be non-negative; tags
-in a receive (<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may
-also be <tt>MPI_ANY_TAG</tt>.  The largest tag value is available through the 
-the attribute <tt>MPI_TAG_UB</tt>.
+in a receive (<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may
+also be <TT>MPI_ANY_TAG</TT>.  The largest tag value is available through the 
+the attribute <TT>MPI_TAG_UB</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_BUFFER </B> <DD> Invalid buffer pointer.  Usually a null buffer where
 one is not valid.
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Iexscan.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Iexscan.html
index e2333527..71a4c97f 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Iexscan.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Iexscan.html
@@ -10,7 +10,7 @@ Computes the exclusive scan (partial reductions) of data on a collection of proc
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Iexscan(const void *sendbuf, void *recvbuf, int count, MPI_Datatype datatype,
-                MPI_Op op, MPI_Comm comm, MPI_Request *request)
+                MPI_Op op, MPI_Comm comm, MPI_Request * request)
 </PRE>
 <P>
 <H2>Input Parameters</H2>
@@ -38,31 +38,31 @@ int MPI_Iexscan(const void *sendbuf, void *recvbuf, int count, MPI_Datatype data
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Igather.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Igather.html
index f7045b07..05f52638 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Igather.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Igather.html
@@ -11,7 +11,7 @@ Gathers together values from a group of processes in a nonblocking way
 <PRE>
 int MPI_Igather(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
                 void *recvbuf, int recvcount, MPI_Datatype recvtype,
-                int root, MPI_Comm comm, MPI_Request *request)
+                int root, MPI_Comm comm, MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -21,7 +21,7 @@ int MPI_Igather(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
 
 <DT><B>sendtype </B><DD>data type of send buffer elements (handle)
 
-<DT><B>recvcount </B><DD>number of elements in receive buffer (significant only at root) (non-negative integer)
+<DT><B>recvcount </B><DD>number of elements for any single receive (non-negative integer, significant only at root)
 
 <DT><B>recvtype </B><DD>data type of receive buffer elements (significant only at root) (handle)
 
@@ -42,31 +42,31 @@ int MPI_Igather(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Igatherv.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Igatherv.html
index cf1de6f8..92a376db 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Igatherv.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Igatherv.html
@@ -11,7 +11,7 @@ Gathers into specified locations from all processes in a group in a nonblocking
 <PRE>
 int MPI_Igatherv(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
                  const int recvcounts[], const int displs[], MPI_Datatype recvtype, int root,
-                 MPI_Comm comm, MPI_Request *request)
+                 MPI_Comm comm, MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -44,31 +44,31 @@ int MPI_Igatherv(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Improbe.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Improbe.html
index 6cd5c5c7..7b829c45 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Improbe.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Improbe.html
@@ -9,7 +9,8 @@
 Nonblocking matched probe. 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Improbe(int source, int tag, MPI_Comm comm, int *flag, MPI_Message *message, MPI_Status *status)
+int MPI_Improbe(int source, int tag, MPI_Comm comm, int *flag, MPI_Message * message,
+                MPI_Status * status)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -34,31 +35,31 @@ int MPI_Improbe(int source, int tag, MPI_Comm comm, int *flag, MPI_Message *mess
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Imrecv.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Imrecv.html
index d86d86a2..b2ccb9a6 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Imrecv.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Imrecv.html
@@ -9,7 +9,8 @@
 Nonblocking receive of message matched by MPI_Mprobe or MPI_Improbe. 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Imrecv(void *buf, int count, MPI_Datatype datatype, MPI_Message *message, MPI_Request *request)
+int MPI_Imrecv(void *buf, int count, MPI_Datatype datatype, MPI_Message * message,
+               MPI_Request * request)
 </PRE>
 <H2>Input/Output Parameters</H2>
 <DL><DT><B>message </B> <DD> message (handle)
@@ -34,31 +35,31 @@ int MPI_Imrecv(void *buf, int count, MPI_Datatype datatype, MPI_Message *message
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ineighbor_allgather.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ineighbor_allgather.html
index 90d709f9..e7a5a196 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ineighbor_allgather.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ineighbor_allgather.html
@@ -9,7 +9,9 @@
 Nonblocking version of MPI_Neighbor_allgather. 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Ineighbor_allgather(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf, int recvcount, MPI_Datatype recvtype, MPI_Comm comm, MPI_Request *request)
+int MPI_Ineighbor_allgather(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
+                            void *recvbuf, int recvcount, MPI_Datatype recvtype, MPI_Comm comm,
+                            MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -38,31 +40,31 @@ int MPI_Ineighbor_allgather(const void *sendbuf, int sendcount, MPI_Datatype sen
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ineighbor_allgatherv.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ineighbor_allgatherv.html
index dd025095..e2126fda 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ineighbor_allgatherv.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ineighbor_allgatherv.html
@@ -9,7 +9,9 @@
 Nonblocking version of MPI_Neighbor_allgatherv. 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Ineighbor_allgatherv(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf, const int recvcounts[], const int displs[], MPI_Datatype recvtype, MPI_Comm comm, MPI_Request *request)
+int MPI_Ineighbor_allgatherv(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
+                             void *recvbuf, const int recvcounts[], const int displs[],
+                             MPI_Datatype recvtype, MPI_Comm comm, MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -40,31 +42,31 @@ int MPI_Ineighbor_allgatherv(const void *sendbuf, int sendcount, MPI_Datatype se
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ineighbor_alltoall.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ineighbor_alltoall.html
index 09730195..1246a357 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ineighbor_alltoall.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ineighbor_alltoall.html
@@ -9,7 +9,9 @@
 Nonblocking version of MPI_Neighbor_alltoall. 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Ineighbor_alltoall(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf, int recvcount, MPI_Datatype recvtype, MPI_Comm comm, MPI_Request *request)
+int MPI_Ineighbor_alltoall(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
+                           int recvcount, MPI_Datatype recvtype, MPI_Comm comm,
+                           MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -38,31 +40,31 @@ int MPI_Ineighbor_alltoall(const void *sendbuf, int sendcount, MPI_Datatype send
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ineighbor_alltoallv.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ineighbor_alltoallv.html
index 50e9fe1e..db99f917 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ineighbor_alltoallv.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ineighbor_alltoallv.html
@@ -9,7 +9,10 @@
 Nonblocking version of MPI_Neighbor_alltoallv. 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Ineighbor_alltoallv(const void *sendbuf, const int sendcounts[], const int sdispls[], MPI_Datatype sendtype, void *recvbuf, const int recvcounts[], const int rdispls[], MPI_Datatype recvtype, MPI_Comm comm, MPI_Request *request)
+int MPI_Ineighbor_alltoallv(const void *sendbuf, const int sendcounts[], const int sdispls[],
+                            MPI_Datatype sendtype, void *recvbuf, const int recvcounts[],
+                            const int rdispls[], MPI_Datatype recvtype, MPI_Comm comm,
+                            MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -42,31 +45,31 @@ int MPI_Ineighbor_alltoallv(const void *sendbuf, const int sendcounts[], const i
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ineighbor_alltoallw.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ineighbor_alltoallw.html
index 8344ac7f..6c4bd7a4 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ineighbor_alltoallw.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ineighbor_alltoallw.html
@@ -9,7 +9,10 @@
 Nonblocking version of MPI_Neighbor_alltoallw. 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Ineighbor_alltoallw(const void *sendbuf, const int sendcounts[], const MPI_Aint sdispls[], const MPI_Datatype sendtypes[], void *recvbuf, const int recvcounts[], const MPI_Aint rdispls[], const MPI_Datatype recvtypes[], MPI_Comm comm, MPI_Request *request)
+int MPI_Ineighbor_alltoallw(const void *sendbuf, const int sendcounts[], const MPI_Aint sdispls[],
+                            const MPI_Datatype sendtypes[], void *recvbuf, const int recvcounts[],
+                            const MPI_Aint rdispls[], const MPI_Datatype recvtypes[], MPI_Comm comm,
+                            MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -42,31 +45,31 @@ int MPI_Ineighbor_alltoallw(const void *sendbuf, const int sendcounts[], const M
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_create.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_create.html
index e913b136..82e850fb 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_create.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_create.html
@@ -9,7 +9,7 @@
 Creates a new info object 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Info_create( MPI_Info *info )
+int MPI_Info_create(MPI_Info * info)
 </PRE>
 <H2>Output Parameters</H2>
 <DL><DT><B>info </B> <DD> info object created (handle)
@@ -20,37 +20,37 @@ int MPI_Info_create( MPI_Info *info )
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_delete.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_delete.html
index 72733a9a..6a222aa7 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_delete.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_delete.html
@@ -9,7 +9,7 @@
 Deletes a (key,value) pair from info 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Info_delete( MPI_Info info, const char *key )
+int MPI_Info_delete(MPI_Info info, const char *key)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -27,32 +27,32 @@ not be used from within a signal handler.
 The MPI standard defined a thread-safe interface but this does not
 mean that all routines may be called without any thread locks.  For
 example, two threads must not attempt to change the contents of the
-same <tt>MPI_Info</tt> object concurrently.  The user is responsible in this
+same <TT>MPI_Info</TT> object concurrently.  The user is responsible in this
 case for using some mechanism, such as thread locks, to ensure that
 only one thread at a time makes use of this routine.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_dup.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_dup.html
index 70eaf129..00ba59b3 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_dup.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_dup.html
@@ -9,7 +9,7 @@
 Returns a duplicate of the info object 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Info_dup( MPI_Info info, MPI_Info *newinfo )
+int MPI_Info_dup(MPI_Info info, MPI_Info * newinfo)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>info </B> <DD> info object (handle)
@@ -23,44 +23,44 @@ int MPI_Info_dup( MPI_Info info, MPI_Info *newinfo )
 <H2>Thread and Interrupt Safety</H2>
 <P>
 This routine is thread and interrupt safe only if no MPI routine that
-updates or frees the same <tt>MPI_Info</tt> object may be called concurrently
+updates or frees the same <TT>MPI_Info</TT> object may be called concurrently
 with this routine.
 <P>
 The MPI standard defined a thread-safe interface but this does not
 mean that all routines may be called without any thread locks.  For
 example, two threads must not attempt to change the contents of the
-same <tt>MPI_Info</tt> object concurrently.  The user is responsible in this
+same <TT>MPI_Info</TT> object concurrently.  The user is responsible in this
 case for using some mechanism, such as thread locks, to ensure that
 only one thread at a time makes use of this routine.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_free.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_free.html
index 47b66c83..f799decc 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_free.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_free.html
@@ -9,7 +9,7 @@
 Frees an info object 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Info_free( MPI_Info *info )
+int MPI_Info_free(MPI_Info * info)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>info </B> <DD> info object to be freed (handle)
@@ -20,31 +20,31 @@ int MPI_Info_free( MPI_Info *info )
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -52,7 +52,7 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_INFO </B> <DD> Invalid Info 
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_get.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_get.html
index 8c6d180f..6a3704f1 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_get.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_get.html
@@ -13,8 +13,7 @@ Retrieves the value associated with a key
 #define FUNCNAME MPI_Info_get
 #undef FCNAME
 #define FCNAME MPL_QUOTE(FUNCNAME)
-int MPI_Info_get(MPI_Info info, const char *key, int valuelen, char *value,
-                int *flag)
+int MPI_Info_get(MPI_Info info, const char *key, int valuelen, char *value, int *flag)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -37,51 +36,51 @@ int MPI_Info_get(MPI_Info info, const char *key, int valuelen, char *value,
 <H2>Thread and Interrupt Safety</H2>
 <P>
 This routine is thread and interrupt safe only if no MPI routine that
-updates or frees the same <tt>MPI_Info</tt> object may be called concurrently
+updates or frees the same <TT>MPI_Info</TT> object may be called concurrently
 with this routine.
 <P>
 The MPI standard defined a thread-safe interface but this does not
 mean that all routines may be called without any thread locks.  For
 example, two threads must not attempt to change the contents of the
-same <tt>MPI_Info</tt> object concurrently.  The user is responsible in this
+same <TT>MPI_Info</TT> object concurrently.  The user is responsible in this
 case for using some mechanism, such as thread locks, to ensure that
 only one thread at a time makes use of this routine.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 <P>
 <DL><DT><B>MPI_ERR_INFO_KEY </B> <DD> Invalid or null key string for info.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_INFO_VALUE </B> <DD> Invalid or null value string for info
 </DL>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_get_nkeys.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_get_nkeys.html
index 51bc773c..ee9cf207 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_get_nkeys.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_get_nkeys.html
@@ -13,7 +13,7 @@ Returns the number of currently defined keys in info
 #define FUNCNAME MPI_Info_get_nkeys
 #undef FCNAME
 #define FCNAME MPL_QUOTE(FUNCNAME)
-int MPI_Info_get_nkeys( MPI_Info info, int *nkeys )
+int MPI_Info_get_nkeys(MPI_Info info, int *nkeys)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>info </B> <DD> info object (handle)
@@ -27,44 +27,44 @@ int MPI_Info_get_nkeys( MPI_Info info, int *nkeys )
 <H2>Thread and Interrupt Safety</H2>
 <P>
 This routine is thread and interrupt safe only if no MPI routine that
-updates or frees the same <tt>MPI_Info</tt> object may be called concurrently
+updates or frees the same <TT>MPI_Info</TT> object may be called concurrently
 with this routine.
 <P>
 The MPI standard defined a thread-safe interface but this does not
 mean that all routines may be called without any thread locks.  For
 example, two threads must not attempt to change the contents of the
-same <tt>MPI_Info</tt> object concurrently.  The user is responsible in this
+same <TT>MPI_Info</TT> object concurrently.  The user is responsible in this
 case for using some mechanism, such as thread locks, to ensure that
 only one thread at a time makes use of this routine.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_get_nthkey.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_get_nthkey.html
index 5cd4e670..cb7d55b6 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_get_nthkey.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_get_nthkey.html
@@ -13,7 +13,7 @@ Returns the nth defined key in info
 #define FUNCNAME MPI_Info_get_nthkey
 #undef FCNAME
 #define FCNAME MPL_QUOTE(FUNCNAME)
-int MPI_Info_get_nthkey( MPI_Info info, int n, char *key )
+int MPI_Info_get_nthkey(MPI_Info info, int n, char *key)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -23,54 +23,54 @@ int MPI_Info_get_nthkey( MPI_Info info, int n, char *key )
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>key </B> <DD> key (string).  The maximum number of characters is <tt>MPI_MAX_INFO_KEY</tt>.
+<DL><DT><B>key </B> <DD> key (string).  The maximum number of characters is <TT>MPI_MAX_INFO_KEY</TT>.
 </DL>
 <P>
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
 This routine is thread and interrupt safe only if no MPI routine that
-updates or frees the same <tt>MPI_Info</tt> object may be called concurrently
+updates or frees the same <TT>MPI_Info</TT> object may be called concurrently
 with this routine.
 <P>
 The MPI standard defined a thread-safe interface but this does not
 mean that all routines may be called without any thread locks.  For
 example, two threads must not attempt to change the contents of the
-same <tt>MPI_Info</tt> object concurrently.  The user is responsible in this
+same <TT>MPI_Info</TT> object concurrently.  The user is responsible in this
 case for using some mechanism, such as thread locks, to ensure that
 only one thread at a time makes use of this routine.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_get_valuelen.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_get_valuelen.html
index aa26dc1a..38a53cbc 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_get_valuelen.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_get_valuelen.html
@@ -6,14 +6,14 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Info_get_valuelen"><H1>MPI_Info_get_valuelen</H1></A>
-Retrieves the length of the value associated with  a key 
+Retrieves the length of the value associated with a key 
 <H2>Synopsis</H2>
 <PRE>
 #undef FUNCNAME
 #define FUNCNAME MPIRInfo_get_valuelen
 #undef FCNAME
 #define FCNAME MPL_QUOTE(FUNCNAME)
-int MPI_Info_get_valuelen( MPI_Info info, const char *key, int *valuelen, int *flag )
+int MPI_Info_get_valuelen(MPI_Info info, const char *key, int *valuelen, int *flag)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -33,38 +33,38 @@ int MPI_Info_get_valuelen( MPI_Info info, const char *key, int *valuelen, int *f
 <H2>Thread and Interrupt Safety</H2>
 <P>
 This routine is thread and interrupt safe only if no MPI routine that
-updates or frees the same <tt>MPI_Info</tt> object may be called concurrently
+updates or frees the same <TT>MPI_Info</TT> object may be called concurrently
 with this routine.
 <P>
 The MPI standard defined a thread-safe interface but this does not
 mean that all routines may be called without any thread locks.  For
 example, two threads must not attempt to change the contents of the
-same <tt>MPI_Info</tt> object concurrently.  The user is responsible in this
+same <TT>MPI_Info</TT> object concurrently.  The user is responsible in this
 case for using some mechanism, such as thread locks, to ensure that
 only one thread at a time makes use of this routine.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -73,7 +73,7 @@ possible.
 <P>
 <DL><DT><B>MPI_ERR_INFO_KEY </B> <DD> Invalid or null key string for info.
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_set.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_set.html
index ada01760..d48ef835 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_set.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Info_set.html
@@ -9,7 +9,7 @@
 Adds a (key,value) pair to info 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Info_set( MPI_Info info, const char *key, const char *value )
+int MPI_Info_set(MPI_Info info, const char *key, const char *value)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -29,32 +29,32 @@ not be used from within a signal handler.
 The MPI standard defined a thread-safe interface but this does not
 mean that all routines may be called without any thread locks.  For
 example, two threads must not attempt to change the contents of the
-same <tt>MPI_Info</tt> object concurrently.  The user is responsible in this
+same <TT>MPI_Info</TT> object concurrently.  The user is responsible in this
 case for using some mechanism, such as thread locks, to ensure that
 only one thread at a time makes use of this routine.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Init.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Init.html
index 119b15b7..519edd33 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Init.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Init.html
@@ -9,61 +9,61 @@
 Initialize the MPI execution environment 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Init( int *argc, char ***argv )
+int MPI_Init(int *argc, char ***argv)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>argc </B><DD>Pointer to the number of arguments 
+<DT><B>argc </B><DD>Pointer to the number of arguments
 
 <DT><B>argv </B><DD>Pointer to the argument vector
 </DL>
 <P>
 <H2>Thread and Signal Safety</H2>
 This routine must be called by one thread only.  That thread is called
-the <em>main thread</em> and must be the thread that calls <tt>MPI_Finalize</tt>.
+the <EM>main thread</EM> and must be the thread that calls <TT>MPI_Finalize</TT>.
 <P>
 <H2>Notes</H2>
-The MPI standard does not say what a program can do before an <tt>MPI_INIT</tt> or
-after an <tt>MPI_FINALIZE</tt>.  In the MPICH implementation, you should do
+The MPI standard does not say what a program can do before an <TT>MPI_INIT</TT> or
+after an <TT>MPI_FINALIZE</TT>.  In the MPICH implementation, you should do
 as little as possible.  In particular, avoid anything that changes the
 external state of the program, such as opening files, reading standard
 input or writing to standard output.
 <P>
 <H2>Notes for C</H2>
-As of MPI-2, <tt>MPI_Init</tt> will accept NULL as input parameters. Doing so
-will impact the values stored in <tt>MPI_INFO_ENV</tt>.
+As of MPI-2, <TT>MPI_Init</TT> will accept NULL as input parameters. Doing so
+will impact the values stored in <TT>MPI_INFO_ENV</TT>.
 <P>
 <H2>Notes for Fortran</H2>
-The Fortran binding for <tt>MPI_Init</tt> has only the error return
+The Fortran binding for <TT>MPI_Init</TT> has only the error return
 <PRE>
-    subroutine MPI_INIT( ierr )
+    subroutine MPI_INIT(ierr)
     integer ierr
 </PRE>
 
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_OTHER </B> <DD> This error class is associated with an error code that 
-indicates that an attempt was made to call <tt>MPI_INIT</tt> a second time.
-<tt>MPI_INIT</tt> may only be called once in a program.
+indicates that an attempt was made to call <TT>MPI_INIT</TT> a second time.
+<TT>MPI_INIT</TT> may only be called once in a program.
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Init_thread, MPI_Finalize
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Init_thread.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Init_thread.html
index c48eac77..97e34a8c 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Init_thread.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Init_thread.html
@@ -9,11 +9,11 @@
 Initialize the MPI execution environment 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Init_thread( int *argc, char ***argv, int required, int *provided )
+int MPI_Init_thread(int *argc, char ***argv, int required, int *provided)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>argc </B><DD>Pointer to the number of arguments 
+<DT><B>argc </B><DD>Pointer to the number of arguments
 
 <DT><B>argv </B><DD>Pointer to the argument vector
 
@@ -26,52 +26,52 @@ int MPI_Init_thread( int *argc, char ***argv, int required, int *provided )
 <P>
 <H2>Command line arguments</H2>
 MPI specifies no command-line arguments but does allow an MPI
-implementation to make use of them.  See <tt>MPI_INIT</tt> for a description of
-the command line arguments supported by <tt>MPI_INIT</tt> and <tt>MPI_INIT_THREAD</tt>.
+implementation to make use of them.  See <TT>MPI_INIT</TT> for a description of
+the command line arguments supported by <TT>MPI_INIT</TT> and <TT>MPI_INIT_THREAD</TT>.
 <P>
 <H2>Notes</H2>
 The valid values for the level of thread support are:
 <DL>
-<DT><B>MPI_THREAD_SINGLE </B><DD>Only one thread will execute. 
+<DT><B>MPI_THREAD_SINGLE </B><DD>Only one thread will execute.
 
-<DT><B>MPI_THREAD_FUNNELED </B><DD>The process may be multi-threaded, but only the main 
-thread will make MPI calls (all MPI calls are funneled to the 
-main thread). 
+<DT><B>MPI_THREAD_FUNNELED </B><DD>The process may be multi-threaded, but only the main
+thread will make MPI calls (all MPI calls are funneled to the
+main thread).
 
-<DT><B>MPI_THREAD_SERIALIZED </B><DD>The process may be multi-threaded, and multiple 
-threads may make MPI calls, but only one at a time: MPI calls are not 
-made concurrently from two distinct threads (all MPI calls are serialized). 
+<DT><B>MPI_THREAD_SERIALIZED </B><DD>The process may be multi-threaded, and multiple
+threads may make MPI calls, but only one at a time: MPI calls are not
+made concurrently from two distinct threads (all MPI calls are serialized).
 
-<DT><B>MPI_THREAD_MULTIPLE </B><DD>Multiple threads may call MPI, with no restrictions. 
+<DT><B>MPI_THREAD_MULTIPLE </B><DD>Multiple threads may call MPI, with no restrictions.
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-Note that the Fortran binding for this routine does not have the <tt>argc</tt> and
-<tt>argv</tt> arguments. (<tt>MPI_INIT_THREAD(required, provided, ierror)</tt>)
+Note that the Fortran binding for this routine does not have the <TT>argc</TT> and
+<TT>argv</TT> arguments. (<TT>MPI_INIT_THREAD(required, provided, ierror)</TT>)
 <P>
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Init, MPI_Finalize
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Initialized.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Initialized.html
index d2a935c2..2f72a27c 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Initialized.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Initialized.html
@@ -6,40 +6,40 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Initialized"><H1>MPI_Initialized</H1></A>
-Indicates whether <tt>MPI_Init</tt> has been called. 
+Indicates whether <TT>MPI_Init</TT> has been called. 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Initialized( int *flag )
+int MPI_Initialized(int *flag)
 </PRE>
 <H2>Output Parameters</H2>
-<DL><DT><B>flag </B> <DD> Flag is true if <tt>MPI_Init</tt> or <tt>MPI_Init_thread</tt> has been called and 
-false otherwise.  
+<DL><DT><B>flag </B> <DD> Flag is true if <TT>MPI_Init</TT> or <TT>MPI_Init_thread</TT> has been called and
+false otherwise.
 </DL>
 <P>
 <H2>Notes</H2>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Intercomm_create.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Intercomm_create.html
index fd0e99d0..b0b98fd1 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Intercomm_create.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Intercomm_create.html
@@ -9,9 +9,8 @@
 Creates an intercommuncator from two intracommunicators 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Intercomm_create(MPI_Comm local_comm, int local_leader, 
-                       MPI_Comm peer_comm, int remote_leader, int tag, 
-                       MPI_Comm *newintercomm)
+int MPI_Intercomm_create(MPI_Comm local_comm, int local_leader,
+                         MPI_Comm peer_comm, int remote_leader, int tag, MPI_Comm * newintercomm)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -19,17 +18,17 @@ int MPI_Intercomm_create(MPI_Comm local_comm, int local_leader,
 
 <DT><B>local_leader </B><DD>Rank in local_comm of leader (often 0)
 
-<DT><B>peer_comm </B><DD>Communicator used to communicate between a 
-designated process in the other communicator.  
-Significant only at the process in <tt>local_comm</tt> with
-rank <tt>local_leader</tt>.
+<DT><B>peer_comm </B><DD>Communicator used to communicate between a
+designated process in the other communicator.
+Significant only at the process in <TT>local_comm</TT> with
+rank <TT>local_leader</TT>.
 
 <DT><B>remote_leader </B><DD>Rank in peer_comm of remote leader (often 0)
 
 <DT><B>tag </B><DD>Message tag to use in constructing intercommunicator; if multiple
-<tt>MPI_Intercomm_creates</tt> are being made, they should use different tags (more
+<TT>MPI_Intercomm_creates</TT> are being made, they should use different tags (more
 precisely, ensure that the local and remote leaders are using different
-tags for each <tt>MPI_intercomm_create</tt>).
+tags for each <TT>MPI_intercomm_create</TT>).
 </DL>
 <P>
 <H2>Output Parameters</H2>
@@ -37,16 +36,16 @@ tags for each <tt>MPI_intercomm_create</tt>).
 </DL>
 <P>
 <H2>Notes</H2>
-<tt>peer_comm</tt> is significant only for the process designated the
-<tt>local_leader</tt> in the <tt>local_comm</tt>.
+<TT>peer_comm</TT> is significant only for the process designated the
+<TT>local_leader</TT> in the <TT>local_comm</TT>.
 <P>
 The MPI 1.1 Standard contains two mutually exclusive comments on the
 input intercommunicators.  One says that their repective groups must be
 disjoint; the other that the leaders can be the same process.  After
 some discussion by the MPI Forum, it has been decided that the groups must
-be disjoint.  Note that the <em>reason</em> given for this in the standard is
-<em>not</em> the reason for this choice; rather, the <em>other</em> operations on
-intercommunicators (like <tt>MPI_Intercomm_merge</tt>) do not make sense if the
+be disjoint.  Note that the <EM>reason</EM> given for this in the standard is
+<EM>not</EM> the reason for this choice; rather, the <EM>other</EM> operations on
+intercommunicators (like <TT>MPI_Intercomm_merge</TT>) do not make sense if the
 groups are not disjoint.
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -54,54 +53,54 @@ groups are not disjoint.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_TAG </B> <DD> Invalid tag argument.  Tags must be non-negative; tags
-in a receive (<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may
-also be <tt>MPI_ANY_TAG</tt>.  The largest tag value is available through the 
-the attribute <tt>MPI_TAG_UB</tt>.
+in a receive (<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may
+also be <TT>MPI_ANY_TAG</TT>.  The largest tag value is available through the 
+the attribute <TT>MPI_TAG_UB</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_INTERN </B> <DD> This error is returned when some part of the MPICH 
 implementation is unable to acquire memory.  
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <P>
-<H0>See Also</H0>
- MPI_Intercomm_merge, MPI_Comm_free, MPI_Comm_remote_group, 
-<br>MPI_Comm_remote_size
+<H2>See Also</H2>
+ MPI_Intercomm_merge, MPI_Comm_free, MPI_Comm_remote_group,
+<BR>MPI_Comm_remote_size
 <P>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Intercomm_merge.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Intercomm_merge.html
index b74f2579..91ee542b 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Intercomm_merge.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Intercomm_merge.html
@@ -9,7 +9,7 @@
 Creates an intracommuncator from an intercommunicator 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Intercomm_merge(MPI_Comm intercomm, int high, MPI_Comm *newintracomm)
+int MPI_Intercomm_merge(MPI_Comm intercomm, int high, MPI_Comm * newintracomm)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -17,7 +17,7 @@ int MPI_Intercomm_merge(MPI_Comm intercomm, int high, MPI_Comm *newintracomm)
 
 <DT><B>high </B><DD>Used to order the groups within comm (logical)
 when creating the new communicator.  This is a boolean value; the group
-that sets high true has its processes ordered <em>after</em> the group that sets 
+that sets high true has its processes ordered <EM>after</EM> the group that sets
 this value to false.  If all processes in the intercommunicator provide
 the same value, the choice of which group is ordered first is arbitrary.
 </DL>
@@ -27,7 +27,7 @@ the same value, the choice of which group is ordered first is arbitrary.
 </DL>
 <P>
 <H2>Notes</H2>
-While all processes may provide the same value for the <tt>high</tt> parameter,
+While all processes may provide the same value for the <TT>high</TT> parameter,
 this requires the MPI implementation to determine which group of
 processes should be ranked first.
 <P>
@@ -36,54 +36,54 @@ processes should be ranked first.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Algorithm</H2>
-<ol>
+<OL>
 <P>
-<li>Allocate contexts
-<li>Local and remote group leaders swap high values
-<li>Determine the high value.
-<li>Merge the two groups and make the intra-communicator
-</ol>
+<LI>Allocate contexts
+<LI>Local and remote group leaders swap high values
+<LI>Determine the high value.
+<LI>Merge the two groups and make the intra-communicator
+</OL>
 <P>
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_INTERN </B> <DD> This error is returned when some part of the MPICH 
 implementation is unable to acquire memory.  
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Intercomm_create, MPI_Comm_free
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Iprobe.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Iprobe.html
index 749d299d..789fdc5c 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Iprobe.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Iprobe.html
@@ -9,24 +9,23 @@
 Nonblocking test for a message 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Iprobe(int source, int tag, MPI_Comm comm, int *flag, 
-               MPI_Status *status)
+int MPI_Iprobe(int source, int tag, MPI_Comm comm, int *flag, MPI_Status * status)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>source </B><DD>source rank, or  <tt>MPI_ANY_SOURCE</tt> (integer) 
+<DT><B>source </B><DD>source rank, or  <TT>MPI_ANY_SOURCE</TT> (integer)
 
-<DT><B>tag </B><DD>tag value or  <tt>MPI_ANY_TAG</tt> (integer) 
+<DT><B>tag </B><DD>tag value or  <TT>MPI_ANY_TAG</TT> (integer)
 
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
 <DL>
-<DT><B>flag </B><DD>True if a message with the specified source, tag, and communicator 
-is available (logical) 
+<DT><B>flag </B><DD>True if a message with the specified source, tag, and communicator
+is available (logical)
 
-<DT><B>status </B><DD>status object (Status) 
+<DT><B>status </B><DD>status object (Status)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -34,47 +33,47 @@ is available (logical)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_TAG </B> <DD> Invalid tag argument.  Tags must be non-negative; tags
-in a receive (<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may
-also be <tt>MPI_ANY_TAG</tt>.  The largest tag value is available through the 
-the attribute <tt>MPI_TAG_UB</tt>.
+in a receive (<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may
+also be <TT>MPI_ANY_TAG</TT>.  The largest tag value is available through the 
+the attribute <TT>MPI_TAG_UB</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <P>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Irecv.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Irecv.html
index 8400c7f9..fd309efc 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Irecv.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Irecv.html
@@ -10,25 +10,25 @@ Begins a nonblocking receive
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Irecv(void *buf, int count, MPI_Datatype datatype, int source,
-              int tag, MPI_Comm comm, MPI_Request *request)
+              int tag, MPI_Comm comm, MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>buf </B><DD>initial address of receive buffer (choice) 
+<DT><B>buf </B><DD>initial address of receive buffer (choice)
 
-<DT><B>count </B><DD>number of elements in receive buffer (integer) 
+<DT><B>count </B><DD>number of elements in receive buffer (integer)
 
-<DT><B>datatype </B><DD>datatype of each receive buffer element (handle) 
+<DT><B>datatype </B><DD>datatype of each receive buffer element (handle)
 
-<DT><B>source </B><DD>rank of source (integer) 
+<DT><B>source </B><DD>rank of source (integer)
 
-<DT><B>tag </B><DD>message tag (integer) 
+<DT><B>tag </B><DD>message tag (integer)
 
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>request </B> <DD> communication request (handle) 
+<DL><DT><B>request </B> <DD> communication request (handle)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -36,54 +36,54 @@ int MPI_Irecv(void *buf, int count, MPI_Datatype datatype, int source,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_TAG </B> <DD> Invalid tag argument.  Tags must be non-negative; tags
-in a receive (<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may
-also be <tt>MPI_ANY_TAG</tt>.  The largest tag value is available through the 
-the attribute <tt>MPI_TAG_UB</tt>.
+in a receive (<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may
+also be <TT>MPI_ANY_TAG</TT>.  The largest tag value is available through the 
+the attribute <TT>MPI_TAG_UB</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_INTERN </B> <DD> This error is returned when some part of the MPICH 
 implementation is unable to acquire memory.  
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ireduce.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ireduce.html
index 28a68e94..f8dc50f6 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ireduce.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ireduce.html
@@ -10,7 +10,7 @@ Reduces values on all processes to a single value in a nonblocking way
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Ireduce(const void *sendbuf, void *recvbuf, int count, MPI_Datatype datatype,
-                MPI_Op op, int root, MPI_Comm comm, MPI_Request *request)
+                MPI_Op op, int root, MPI_Comm comm, MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -39,31 +39,31 @@ int MPI_Ireduce(const void *sendbuf, void *recvbuf, int count, MPI_Datatype data
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ireduce_scatter.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ireduce_scatter.html
index 04b29a5d..57836993 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ireduce_scatter.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ireduce_scatter.html
@@ -10,7 +10,7 @@ Combines values and scatters the results in a nonblocking way
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Ireduce_scatter(const void *sendbuf, void *recvbuf, const int recvcounts[],
-                        MPI_Datatype datatype, MPI_Op op, MPI_Comm comm, MPI_Request *request)
+                        MPI_Datatype datatype, MPI_Op op, MPI_Comm comm, MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -37,31 +37,31 @@ int MPI_Ireduce_scatter(const void *sendbuf, void *recvbuf, const int recvcounts
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ireduce_scatter_block.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ireduce_scatter_block.html
index 16d9ebb5..a6166e15 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ireduce_scatter_block.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ireduce_scatter_block.html
@@ -12,7 +12,7 @@ Combines values and scatters the results in a nonblocking way
 int MPI_Ireduce_scatter_block(const void *sendbuf, void *recvbuf,
                               int recvcount,
                               MPI_Datatype datatype, MPI_Op op, MPI_Comm comm,
-                              MPI_Request *request)
+                              MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -39,31 +39,31 @@ int MPI_Ireduce_scatter_block(const void *sendbuf, void *recvbuf,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Irsend.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Irsend.html
index a3abc55c..d3e66782 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Irsend.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Irsend.html
@@ -10,25 +10,25 @@ Starts a nonblocking ready send
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Irsend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-               MPI_Comm comm, MPI_Request *request)
+               MPI_Comm comm, MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>buf </B><DD>initial address of send buffer (choice) 
+<DT><B>buf </B><DD>initial address of send buffer (choice)
 
-<DT><B>count </B><DD>number of elements in send buffer (integer) 
+<DT><B>count </B><DD>number of elements in send buffer (integer)
 
-<DT><B>datatype </B><DD>datatype of each send buffer element (handle) 
+<DT><B>datatype </B><DD>datatype of each send buffer element (handle)
 
-<DT><B>dest </B><DD>rank of destination (integer) 
+<DT><B>dest </B><DD>rank of destination (integer)
 
-<DT><B>tag </B><DD>message tag (integer) 
+<DT><B>tag </B><DD>message tag (integer)
 
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>request </B> <DD> communication request (handle) 
+<DL><DT><B>request </B> <DD> communication request (handle)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -36,54 +36,54 @@ int MPI_Irsend(const void *buf, int count, MPI_Datatype datatype, int dest, int
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_TAG </B> <DD> Invalid tag argument.  Tags must be non-negative; tags
-in a receive (<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may
-also be <tt>MPI_ANY_TAG</tt>.  The largest tag value is available through the 
-the attribute <tt>MPI_TAG_UB</tt>.
+in a receive (<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may
+also be <TT>MPI_ANY_TAG</TT>.  The largest tag value is available through the 
+the attribute <TT>MPI_TAG_UB</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_INTERN </B> <DD> This error is returned when some part of the MPICH 
 implementation is unable to acquire memory.  
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Is_thread_main.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Is_thread_main.html
index 6670209b..93daf9bc 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Is_thread_main.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Is_thread_main.html
@@ -6,13 +6,13 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Is_thread_main"><H1>MPI_Is_thread_main</H1></A>
-Returns a flag indicating whether this thread called  <tt>MPI_Init</tt> or <tt>MPI_Init_thread</tt> 
+Returns a flag indicating whether this thread called <TT>MPI_Init</TT> or <TT>MPI_Init_thread</TT> 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Is_thread_main( int *flag )
+int MPI_Is_thread_main(int *flag)
 </PRE>
 <H2>Output Parameters</H2>
-<DL><DT><B>flag </B> <DD> Flag is true if <tt>MPI_Init</tt> or <tt>MPI_Init_thread</tt> has been called by 
+<DL><DT><B>flag </B> <DD> Flag is true if <TT>MPI_Init</TT> or <TT>MPI_Init_thread</TT> has been called by
 this thread and false otherwise.  (logical)
 </DL>
 <P>
@@ -23,27 +23,27 @@ This means that this routine may safely be used by multiple threads and
 from within a signal handler.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Iscan.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Iscan.html
index 8431d04c..5cf8aec5 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Iscan.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Iscan.html
@@ -10,7 +10,7 @@ Computes the scan (partial reductions) of data on a collection of processes in a
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Iscan(const void *sendbuf, void *recvbuf, int count, MPI_Datatype datatype,
-              MPI_Op op, MPI_Comm comm, MPI_Request *request)
+              MPI_Op op, MPI_Comm comm, MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -37,31 +37,31 @@ int MPI_Iscan(const void *sendbuf, void *recvbuf, int count, MPI_Datatype dataty
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Iscatter.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Iscatter.html
index cf5391ca..7a3bf481 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Iscatter.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Iscatter.html
@@ -11,7 +11,7 @@ Sends data from one process to all other processes in a communicator in a nonblo
 <PRE>
 int MPI_Iscatter(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
                  void *recvbuf, int recvcount, MPI_Datatype recvtype, int root,
-                 MPI_Comm comm, MPI_Request *request)
+                 MPI_Comm comm, MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -42,31 +42,31 @@ int MPI_Iscatter(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Iscatterv.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Iscatterv.html
index e87b2192..f0c02c06 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Iscatterv.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Iscatterv.html
@@ -11,7 +11,7 @@ Scatters a buffer in parts to all processes in a communicator in a nonblocking w
 <PRE>
 int MPI_Iscatterv(const void *sendbuf, const int sendcounts[], const int displs[],
                   MPI_Datatype sendtype, void *recvbuf, int recvcount, MPI_Datatype recvtype,
-                  int root, MPI_Comm comm, MPI_Request *request)
+                  int root, MPI_Comm comm, MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -44,31 +44,31 @@ int MPI_Iscatterv(const void *sendbuf, const int sendcounts[], const int displs[
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Isend.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Isend.html
index 8ec9e4bc..78942399 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Isend.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Isend.html
@@ -10,72 +10,72 @@ Begins a nonblocking send
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Isend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-              MPI_Comm comm, MPI_Request *request)
+              MPI_Comm comm, MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>buf </B><DD>initial address of send buffer (choice) 
+<DT><B>buf </B><DD>initial address of send buffer (choice)
 
-<DT><B>count </B><DD>number of elements in send buffer (integer) 
+<DT><B>count </B><DD>number of elements in send buffer (integer)
 
-<DT><B>datatype </B><DD>datatype of each send buffer element (handle) 
+<DT><B>datatype </B><DD>datatype of each send buffer element (handle)
 
-<DT><B>dest </B><DD>rank of destination (integer) 
+<DT><B>dest </B><DD>rank of destination (integer)
 
-<DT><B>tag </B><DD>message tag (integer) 
+<DT><B>tag </B><DD>message tag (integer)
 
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>request </B> <DD> communication request (handle) 
+<DL><DT><B>request </B> <DD> communication request (handle)
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_TAG </B> <DD> Invalid tag argument.  Tags must be non-negative; tags
-in a receive (<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may
-also be <tt>MPI_ANY_TAG</tt>.  The largest tag value is available through the 
-the attribute <tt>MPI_TAG_UB</tt>.
+in a receive (<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may
+also be <TT>MPI_ANY_TAG</TT>.  The largest tag value is available through the 
+the attribute <TT>MPI_TAG_UB</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_INTERN </B> <DD> This error is returned when some part of the MPICH 
 implementation is unable to acquire memory.  
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Issend.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Issend.html
index 26568513..f9e00edc 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Issend.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Issend.html
@@ -10,25 +10,25 @@ Starts a nonblocking synchronous send
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Issend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-               MPI_Comm comm, MPI_Request *request)
+               MPI_Comm comm, MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>buf </B><DD>initial address of send buffer (choice) 
+<DT><B>buf </B><DD>initial address of send buffer (choice)
 
-<DT><B>count </B><DD>number of elements in send buffer (integer) 
+<DT><B>count </B><DD>number of elements in send buffer (integer)
 
-<DT><B>datatype </B><DD>datatype of each send buffer element (handle) 
+<DT><B>datatype </B><DD>datatype of each send buffer element (handle)
 
-<DT><B>dest </B><DD>rank of destination (integer) 
+<DT><B>dest </B><DD>rank of destination (integer)
 
-<DT><B>tag </B><DD>message tag (integer) 
+<DT><B>tag </B><DD>message tag (integer)
 
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>request </B> <DD> communication request (handle) 
+<DL><DT><B>request </B> <DD> communication request (handle)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -36,54 +36,54 @@ int MPI_Issend(const void *buf, int count, MPI_Datatype datatype, int dest, int
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_TAG </B> <DD> Invalid tag argument.  Tags must be non-negative; tags
-in a receive (<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may
-also be <tt>MPI_ANY_TAG</tt>.  The largest tag value is available through the 
-the attribute <tt>MPI_TAG_UB</tt>.
+in a receive (<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may
+also be <TT>MPI_ANY_TAG</TT>.  The largest tag value is available through the 
+the attribute <TT>MPI_TAG_UB</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_INTERN </B> <DD> This error is returned when some part of the MPICH 
 implementation is unable to acquire memory.  
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Keyval_create.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Keyval_create.html
index 8e6e0178..41b1df77 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Keyval_create.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Keyval_create.html
@@ -9,29 +9,28 @@
 Greates a new attribute key 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Keyval_create(MPI_Copy_function *copy_fn, 
-                     MPI_Delete_function *delete_fn, 
-                     int *keyval, void *extra_state)
+int MPI_Keyval_create(MPI_Copy_function * copy_fn,
+                      MPI_Delete_function * delete_fn, int *keyval, void *extra_state)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>copy_fn </B><DD>Copy callback function for <tt>keyval</tt> 
-
-<DT><B>delete_fn </B><DD>Delete callback function for <tt>keyval</tt> 
-
-<DT><B>extra_state </B><DD>Extra state for callback functions 
+<DT><B>copy_fn </B><DD>Copy callback function for <TT>keyval
+</TT>
+<DT><B>delete_fn </B><DD>Delete callback function for <TT>keyval
+</TT>
+<DT><B>extra_state </B><DD>Extra state for callback functions
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>keyval </B> <DD> key value for future access (integer) 
+<DL><DT><B>keyval </B> <DD> key value for future access (integer)
 </DL>
 <P>
 <H2>Notes</H2>
 Key values are global (available for any and all communicators).
 <P>
 There are subtle differences between C and Fortran that require that the
-copy_fn be written in the same language that <tt>MPI_Keyval_create
-</tt>is called from.
+copy_fn be written in the same language that <TT>MPI_Keyval_create
+</TT>is called from.
 This should not be a problem for most users; only programmers using both
 Fortran and C in the same program need to be sure that they follow this rule.
 <P>
@@ -40,38 +39,38 @@ Fortran and C in the same program need to be sure that they follow this rule.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Deprecated Function</H2>
 The MPI-2 standard deprecated a number of routines because MPI-2 provides
 better versions.  This routine is one of those that was deprecated.  The
 routine may continue to be used, but new code should use the replacement
 routine.
-The replacement for this routine is <tt>MPI_Comm_create_keyval</tt>.
+The replacement for this routine is <TT>MPI_Comm_create_keyval</TT>.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -81,10 +80,10 @@ possible.
 implementation is unable to acquire memory.  
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Keyval_free, MPI_Comm_create_keyval
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Keyval_free.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Keyval_free.html
index 54b2a288..8dd0ba9d 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Keyval_free.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Keyval_free.html
@@ -12,7 +12,7 @@ Frees an attribute key for communicators
 int MPI_Keyval_free(int *keyval)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>keyval </B> <DD> Frees the integer key value (integer) 
+<DL><DT><B>keyval </B> <DD> Frees the integer key value (integer)
 </DL>
 <P>
 <H2>Note</H2>
@@ -23,51 +23,51 @@ The MPI-2 standard deprecated a number of routines because MPI-2 provides
 better versions.  This routine is one of those that was deprecated.  The
 routine may continue to be used, but new code should use the replacement
 routine.
-The replacement for this routine is <tt>MPI_Comm_free_keyval</tt>.
+The replacement for this routine is <TT>MPI_Comm_free_keyval</TT>.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> This error class is associated with an error code that 
 indicates that an attempt was made to free one of the permanent keys.
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Keyval_create, MPI_Comm_free_keyval
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Lookup_name.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Lookup_name.html
index f0951a25..3ea4f331 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Lookup_name.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Lookup_name.html
@@ -13,51 +13,51 @@ int MPI_Lookup_name(const char *service_name, MPI_Info info, char *port_name)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>service_name </B><DD>a service name (string) 
+<DT><B>service_name </B><DD>a service name (string)
 
-<DT><B>info </B><DD>implementation-specific information (handle) 
+<DT><B>info </B><DD>implementation-specific information (handle)
 </DL>
 <P>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>port_name </B> <DD> a port name (string) 
+<DL><DT><B>port_name </B> <DD> a port name (string)
 </DL>
 <P>
 <H2>Notes</H2>
-If the <tt>service_name</tt> is found, MPI copies the associated value into
-<tt>port_name</tt>.  The maximum size string that may be supplied by the system is
-<tt>MPI_MAX_PORT_NAME</tt>.
+If the <TT>service_name</TT> is found, MPI copies the associated value into
+<TT>port_name</TT>.  The maximum size string that may be supplied by the system is
+<TT>MPI_MAX_PORT_NAME</TT>.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -65,10 +65,10 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_INFO </B> <DD> Invalid Info 
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Mprobe.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Mprobe.html
index ee1d99a0..bf205a71 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Mprobe.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Mprobe.html
@@ -9,7 +9,7 @@
 Blocking matched probe. 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Mprobe(int source, int tag, MPI_Comm comm, MPI_Message *message, MPI_Status *status)
+int MPI_Mprobe(int source, int tag, MPI_Comm comm, MPI_Message * message, MPI_Status * status)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -32,31 +32,31 @@ int MPI_Mprobe(int source, int tag, MPI_Comm comm, MPI_Message *message, MPI_Sta
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Mrecv.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Mrecv.html
index 990fb995..a90bb78a 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Mrecv.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Mrecv.html
@@ -9,7 +9,8 @@
 Blocking receive of message matched by MPI_Mprobe or MPI_Improbe. 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Mrecv(void *buf, int count, MPI_Datatype datatype, MPI_Message *message, MPI_Status *status)
+int MPI_Mrecv(void *buf, int count, MPI_Datatype datatype, MPI_Message * message,
+              MPI_Status * status)
 </PRE>
 <H2>Input/Output Parameters</H2>
 <DL><DT><B>message </B> <DD> message (handle)
@@ -34,31 +35,31 @@ int MPI_Mrecv(void *buf, int count, MPI_Datatype datatype, MPI_Message *message,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Neighbor_allgather.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Neighbor_allgather.html
index 0f7cf9d7..0346930e 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Neighbor_allgather.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Neighbor_allgather.html
@@ -9,7 +9,8 @@
 In this function, each process i gathers data items from each process j if an edge (j,i) exists in the topology graph, and each process i sends the same data items to all processes j where an edge (i,j) exists. The send buffer is sent to each neighboring process and the l-th block in the receive buffer is received from the l-th neighbor. 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Neighbor_allgather(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf, int recvcount, MPI_Datatype recvtype, MPI_Comm comm)
+int MPI_Neighbor_allgather(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
+                           int recvcount, MPI_Datatype recvtype, MPI_Comm comm)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -35,31 +36,31 @@ int MPI_Neighbor_allgather(const void *sendbuf, int sendcount, MPI_Datatype send
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Neighbor_allgatherv.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Neighbor_allgatherv.html
index 6a8b5a49..86e1bc42 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Neighbor_allgatherv.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Neighbor_allgatherv.html
@@ -9,7 +9,9 @@
 The vector variant of MPI_Neighbor_allgather. 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Neighbor_allgatherv(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf, const int recvcounts[], const int displs[], MPI_Datatype recvtype, MPI_Comm comm)
+int MPI_Neighbor_allgatherv(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
+                            void *recvbuf, const int recvcounts[], const int displs[],
+                            MPI_Datatype recvtype, MPI_Comm comm)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -37,31 +39,31 @@ int MPI_Neighbor_allgatherv(const void *sendbuf, int sendcount, MPI_Datatype sen
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Neighbor_alltoall.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Neighbor_alltoall.html
index d00e2411..86f4b9e0 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Neighbor_alltoall.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Neighbor_alltoall.html
@@ -9,7 +9,8 @@
 In this function, each process i receives data items from each process j if an edge (j,i) exists in the topology graph or Cartesian topology.  Similarly, each process i sends data items to all processes j where an edge (i,j) exists. This call is more general than MPI_NEIGHBOR_ALLGATHER in that different data items can be sent to each neighbor. The k-th block in send buffer is sent to the k-th neighboring process and the l-th block in the receive buffer is received from the l-th neighbor. 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Neighbor_alltoall(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf, int recvcount, MPI_Datatype recvtype, MPI_Comm comm)
+int MPI_Neighbor_alltoall(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
+                          int recvcount, MPI_Datatype recvtype, MPI_Comm comm)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -35,31 +36,31 @@ int MPI_Neighbor_alltoall(const void *sendbuf, int sendcount, MPI_Datatype sendt
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Neighbor_alltoallv.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Neighbor_alltoallv.html
index cd64379d..12286184 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Neighbor_alltoallv.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Neighbor_alltoallv.html
@@ -9,7 +9,9 @@
 The vector variant of MPI_Neighbor_alltoall allows sending/receiving different numbers of elements to and from each neighbor. 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Neighbor_alltoallv(const void *sendbuf, const int sendcounts[], const int sdispls[], MPI_Datatype sendtype, void *recvbuf, const int recvcounts[], const int rdispls[], MPI_Datatype recvtype, MPI_Comm comm)
+int MPI_Neighbor_alltoallv(const void *sendbuf, const int sendcounts[], const int sdispls[],
+                           MPI_Datatype sendtype, void *recvbuf, const int recvcounts[],
+                           const int rdispls[], MPI_Datatype recvtype, MPI_Comm comm)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -39,31 +41,31 @@ int MPI_Neighbor_alltoallv(const void *sendbuf, const int sendcounts[], const in
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Neighbor_alltoallw.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Neighbor_alltoallw.html
index d9c07d6d..bfd8eefa 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Neighbor_alltoallw.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Neighbor_alltoallw.html
@@ -9,7 +9,9 @@
 Like MPI_Neighbor_alltoallv but it allows one to send and receive with different types to and from each neighbor. 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Neighbor_alltoallw(const void *sendbuf, const int sendcounts[], const MPI_Aint sdispls[], const MPI_Datatype sendtypes[], void *recvbuf, const int recvcounts[], const MPI_Aint rdispls[], const MPI_Datatype recvtypes[], MPI_Comm comm)
+int MPI_Neighbor_alltoallw(const void *sendbuf, const int sendcounts[], const MPI_Aint sdispls[],
+                           const MPI_Datatype sendtypes[], void *recvbuf, const int recvcounts[],
+                           const MPI_Aint rdispls[], const MPI_Datatype recvtypes[], MPI_Comm comm)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -39,31 +41,31 @@ int MPI_Neighbor_alltoallw(const void *sendbuf, const int sendcounts[], const MP
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Op_commute.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Op_commute.html
index b37e5c26..2d0c76be 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Op_commute.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Op_commute.html
@@ -16,7 +16,7 @@ int MPI_Op_commutative(MPI_Op op, int *commute)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>commute </B> <DD> Flag is true if <tt>op</tt> is a commutative operation. (logical)
+<DL><DT><B>commute </B> <DD> Flag is true if <TT>op</TT> is a commutative operation. (logical)
 </DL>
 <P>
 <H2>Null Handles</H2>
@@ -37,41 +37,41 @@ disallows freeing a null communicator.  The text from the standard is:
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Op_create
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Op_create.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Op_create.html
index 0e66486c..28fffd52 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Op_create.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Op_create.html
@@ -9,7 +9,7 @@
 Creates a user-defined combination function handle 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Op_create(MPI_User_function *user_fn, int commute, MPI_Op *op)
+int MPI_Op_create(MPI_User_function * user_fn, int commute, MPI_Op * op)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -19,19 +19,19 @@ int MPI_Op_create(MPI_User_function *user_fn, int commute, MPI_Op *op)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>op </B> <DD> operation (handle) 
+<DL><DT><B>op </B> <DD> operation (handle)
 </DL>
 <P>
 <H2>Notes on the user function</H2>
 The calling list for the user function type is
 <PRE>
- typedef void (MPI_User_function) ( void * a, 
-               void * b, int * len, MPI_Datatype * ); 
+ typedef void (MPI_User_function) (void * a,
+               void * b, int * len, MPI_Datatype *);
 </PRE>
 
-where the operation is <tt>b[i] = a[i] op b[i]</tt>, for <tt>i=0,...,len-1</tt>.  A pointer
+where the operation is <TT>b[i] = a[i] op b[i]</TT>, for <TT>i=0,...,len-1</TT>.  A pointer
 to the datatype given to the MPI collective computation routine (i.e.,
-<tt>MPI_Reduce</tt>, <tt>MPI_Allreduce</tt>, <tt>MPI_Scan</tt>, or <tt>MPI_Reduce_scatter</tt>) is also
+<TT>MPI_Reduce</TT>, <TT>MPI_Allreduce</TT>, <TT>MPI_Scan</TT>, or <TT>MPI_Reduce_scatter</TT>) is also
 passed to the user-specified routine.
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -39,25 +39,25 @@ passed to the user-specified routine.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Notes on collective operations</H2>
 <P>
-The reduction functions (<tt>MPI_Op</tt>) do not return an error value.  As a result,
-if the functions detect an error, all they can do is either call <tt>MPI_Abort
-</tt>or silently skip the problem.  Thus, if you change the error handler from
-<tt>MPI_ERRORS_ARE_FATAL</tt> to something else, for example, <tt>MPI_ERRORS_RETURN</tt>,
+The reduction functions (<TT>MPI_Op</TT>) do not return an error value.  As a result,
+if the functions detect an error, all they can do is either call <TT>MPI_Abort
+</TT>or silently skip the problem.  Thus, if you change the error handler from
+<TT>MPI_ERRORS_ARE_FATAL</TT> to something else, for example, <TT>MPI_ERRORS_RETURN</TT>,
 then no error may be indicated.
 <P>
 The reason for this is the performance problems in ensuring that
@@ -65,23 +65,23 @@ all collective routines return the same error value.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Op_free
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Op_free.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Op_free.html
index 5f9e9264..63a1b2de 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Op_free.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Op_free.html
@@ -9,14 +9,14 @@
 Frees a user-defined combination function handle 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Op_free(MPI_Op *op)
+int MPI_Op_free(MPI_Op * op)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>op </B> <DD> operation (handle) 
+<DL><DT><B>op </B> <DD> operation (handle)
 </DL>
 <P>
 <H2>Notes</H2>
-<tt>op</tt> is set to <tt>MPI_OP_NULL</tt> on exit.
+<TT>op</TT> is set to <TT>MPI_OP_NULL</TT> on exit.
 <P>
 <H2>Null Handles</H2>
 The MPI 1.1 specification, in the section on opaque objects, explicitly
@@ -36,45 +36,45 @@ disallows freeing a null communicator.  The text from the standard is:
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument; the error code associated with this
 error indicates an attempt to free an MPI permanent operation (e.g., 
-<tt>MPI_SUM</tt>).
+<TT>MPI_SUM</TT>).
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Op_create
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Open_port.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Open_port.html
index 99472a0b..43b2cfd2 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Open_port.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Open_port.html
@@ -6,33 +6,33 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Open_port"><H1>MPI_Open_port</H1></A>
-Establish an address that can be used to establish  connections between groups of MPI processes 
+Establish an address that can be used to establish connections between groups of MPI processes 
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Open_port(MPI_Info info, char *port_name)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>info </B> <DD> implementation-specific information on how to establish a 
-port for <tt>MPI_Comm_accept</tt> (handle) 
+<DL><DT><B>info </B> <DD> implementation-specific information on how to establish a
+port for <TT>MPI_Comm_accept</TT> (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>port_name </B> <DD> newly established port (string) 
+<DL><DT><B>port_name </B> <DD> newly established port (string)
 </DL>
 <P>
 <H2>Notes</H2>
-MPI copies a system-supplied port name into <tt>port_name</tt>. <tt>port_name</tt> identifies
+MPI copies a system-supplied port name into <TT>port_name</TT>. <TT>port_name</TT> identifies
 the newly opened port and can be used by a client to contact the server.
 The maximum size string that may be supplied by the system is
-<tt>MPI_MAX_PORT_NAME</tt>.
+<TT>MPI_MAX_PORT_NAME</TT>.
 <P>
 <H2>Reserved Info Key Values</H2>
 <DL>
-<DT><B>ip_port </B><DD>Value contains IP port number at which to establish a port. 
+<DT><B>ip_port </B><DD>Value contains IP port number at which to establish a port.
 
 <DT><B>ip_address </B><DD>Value contains IP address at which to establish a port.
 If the address is not a valid IP address of the host on which the
-<tt>MPI_OPEN_PORT</tt> call is made, the results are undefined. 
+<TT>MPI_OPEN_PORT</TT> call is made, the results are undefined.
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -40,31 +40,31 @@ If the address is not a valid IP address of the host on which the
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Pack.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Pack.html
index 4e9ebf33..0f2f4df9 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Pack.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Pack.html
@@ -11,11 +11,7 @@ Packs a datatype into contiguous memory
 <PRE>
 int MPI_Pack(const void *inbuf,
              int incount,
-             MPI_Datatype datatype,
-             void *outbuf,
-             int outsize,
-             int *position,
-             MPI_Comm comm)
+             MPI_Datatype datatype, void *outbuf, int outsize, int *position, MPI_Comm comm)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -49,36 +45,36 @@ message.
 <P>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Pack_external.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Pack_external.html
index 4e4567ec..96d00417 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Pack_external.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Pack_external.html
@@ -10,12 +10,9 @@ Packs a datatype into contiguous memory, using the external32 format
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Pack_external(const char datarep[],
-                     const void *inbuf,
-                     int incount,
-                     MPI_Datatype datatype,
-                     void *outbuf,
-                     MPI_Aint outsize,
-                     MPI_Aint *position)
+                      const void *inbuf,
+                      int incount,
+                      MPI_Datatype datatype, void *outbuf, MPI_Aint outsize, MPI_Aint * position)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -43,42 +40,42 @@ int MPI_Pack_external(const char datarep[],
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Pack_external_size.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Pack_external_size.html
index 80e51078..051df5e6 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Pack_external_size.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Pack_external_size.html
@@ -10,9 +10,7 @@ Returns the upper bound on the amount of space needed to pack a message using MP
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Pack_external_size(const char datarep[],
-                         int incount,
-                         MPI_Datatype datatype,
-                         MPI_Aint *size)
+                           int incount, MPI_Datatype datatype, MPI_Aint * size)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -32,41 +30,41 @@ int MPI_Pack_external_size(const char datarep[],
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Pack_size.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Pack_size.html
index ce7c386f..ac53376e 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Pack_size.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Pack_size.html
@@ -9,73 +9,70 @@
 Returns the upper bound on the amount of space needed to pack a message 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Pack_size(int incount,
-                 MPI_Datatype datatype,
-                 MPI_Comm comm,
-                 int *size)
+int MPI_Pack_size(int incount, MPI_Datatype datatype, MPI_Comm comm, int *size)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>incount </B><DD>count argument to packing call (integer) 
+<DT><B>incount </B><DD>count argument to packing call (integer)
 
-<DT><B>datatype </B><DD>datatype argument to packing call (handle) 
+<DT><B>datatype </B><DD>datatype argument to packing call (handle)
 
-<DT><B>comm </B><DD>communicator argument to packing call (handle) 
+<DT><B>comm </B><DD>communicator argument to packing call (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>size </B> <DD> upper bound on size of packed message, in bytes (integer) 
+<DL><DT><B>size </B> <DD> upper bound on size of packed message, in bytes (integer)
 </DL>
 <P>
 <H2>Notes</H2>
-The MPI standard document describes this in terms of <tt>MPI_Pack</tt>, but it
-applies to both <tt>MPI_Pack</tt> and <tt>MPI_Unpack</tt>.  That is, the value <tt>size</tt> is
-the maximum that is needed by either <tt>MPI_Pack</tt> or <tt>MPI_Unpack</tt>.
+The MPI standard document describes this in terms of <TT>MPI_Pack</TT>, but it
+applies to both <TT>MPI_Pack</TT> and <TT>MPI_Unpack</TT>.  That is, the value <TT>size</TT> is
+the maximum that is needed by either <TT>MPI_Pack</TT> or <TT>MPI_Unpack</TT>.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <P>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Pcontrol.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Pcontrol.html
index b638ff6b..1b2ecde3 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Pcontrol.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Pcontrol.html
@@ -13,40 +13,40 @@ int MPI_Pcontrol(const int level, ...)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>level </B><DD>Profiling level 
+<DT><B>level </B><DD>Profiling level
 
 <DT><B>... </B><DD>other arguments (see notes)
 </DL>
 <P>
 <H2>Notes</H2>
 This routine provides a common interface for profiling control.  The
-interpretation of <tt>level</tt> and any other arguments is left to the
+interpretation of <TT>level</TT> and any other arguments is left to the
 profiling library.  The intention is that a profiling library will
 provide a replacement for this routine and define the interpretation
 of the parameters.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Probe.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Probe.html
index 65b8e5c0..108fdb6e 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Probe.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Probe.html
@@ -9,19 +9,19 @@
 Blocking test for a message 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Probe(int source, int tag, MPI_Comm comm, MPI_Status *status)
+int MPI_Probe(int source, int tag, MPI_Comm comm, MPI_Status * status)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>source </B><DD>source rank, or <tt>MPI_ANY_SOURCE</tt> (integer) 
+<DT><B>source </B><DD>source rank, or <TT>MPI_ANY_SOURCE</TT> (integer)
 
-<DT><B>tag </B><DD>tag value or <tt>MPI_ANY_TAG</tt> (integer) 
+<DT><B>tag </B><DD>tag value or <TT>MPI_ANY_TAG</TT> (integer)
 
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>status </B> <DD> status object (Status) 
+<DL><DT><B>status </B> <DD> status object (Status)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -29,46 +29,46 @@ int MPI_Probe(int source, int tag, MPI_Comm comm, MPI_Status *status)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_TAG </B> <DD> Invalid tag argument.  Tags must be non-negative; tags
-in a receive (<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may
-also be <tt>MPI_ANY_TAG</tt>.  The largest tag value is available through the 
-the attribute <tt>MPI_TAG_UB</tt>.
+in a receive (<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may
+also be <TT>MPI_ANY_TAG</TT>.  The largest tag value is available through the 
+the attribute <TT>MPI_TAG_UB</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Publish_name.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Publish_name.html
index 12a430e0..d6306973 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Publish_name.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Publish_name.html
@@ -13,58 +13,58 @@ int MPI_Publish_name(const char *service_name, MPI_Info info, const char *port_n
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>service_name </B><DD>a service name to associate with the port (string) 
+<DT><B>service_name </B><DD>a service name to associate with the port (string)
 
-<DT><B>info </B><DD>implementation-specific information (handle) 
+<DT><B>info </B><DD>implementation-specific information (handle)
 
-<DT><B>port_name </B><DD>a port name (string) 
+<DT><B>port_name </B><DD>a port name (string)
 </DL>
 <P>
 <H2>Notes</H2>
-The maximum size string that may be supplied for <tt>port_name</tt> is
-<tt>MPI_MAX_PORT_NAME</tt>.
+The maximum size string that may be supplied for <TT>port_name</TT> is
+<TT>MPI_MAX_PORT_NAME</TT>.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_INFO </B> <DD> Invalid Info 
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Put.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Put.html
index 3f106a19..cc68055c 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Put.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Put.html
@@ -11,27 +11,26 @@ Put data into a memory window on a remote process
 <PRE>
 int MPI_Put(const void *origin_addr, int origin_count, MPI_Datatype
             origin_datatype, int target_rank, MPI_Aint target_disp,
-            int target_count, MPI_Datatype target_datatype, MPI_Win
-            win)
+            int target_count, MPI_Datatype target_datatype, MPI_Win win)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>origin_addr </B><DD>initial address of origin buffer (choice) 
+<DT><B>origin_addr </B><DD>initial address of origin buffer (choice)
 
-<DT><B>origin_count </B><DD>number of entries in origin buffer (nonnegative integer) 
+<DT><B>origin_count </B><DD>number of entries in origin buffer (nonnegative integer)
 
-<DT><B>origin_datatype </B><DD>datatype of each entry in origin buffer (handle) 
+<DT><B>origin_datatype </B><DD>datatype of each entry in origin buffer (handle)
 
-<DT><B>target_rank </B><DD>rank of target (nonnegative integer) 
+<DT><B>target_rank </B><DD>rank of target (nonnegative integer)
 
-<DT><B>target_disp </B><DD>displacement from start of window to target buffer (nonnegative integer) 
+<DT><B>target_disp </B><DD>displacement from start of window to target buffer (nonnegative integer)
 
-<DT><B>target_count </B><DD>number of entries in target buffer (nonnegative integer) 
+<DT><B>target_count </B><DD>number of entries in target buffer (nonnegative integer)
 
-<DT><B>target_datatype </B><DD>datatype of each entry in target buffer (handle) 
+<DT><B>target_datatype </B><DD>datatype of each entry in target buffer (handle)
 
 <P>
-<DT><B>win </B><DD>window object used for communication (handle) 
+<DT><B>win </B><DD>window object used for communication (handle)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -39,54 +38,54 @@ int MPI_Put(const void *origin_addr, int origin_count, MPI_Datatype
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Rput
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Query_thread.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Query_thread.html
index 1e47ae01..103da5da 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Query_thread.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Query_thread.html
@@ -6,33 +6,33 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Query_thread"><H1>MPI_Query_thread</H1></A>
-Return the level of thread support provided by the MPI  library 
+Return the level of thread support provided by the MPI library 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Query_thread( int *provided )
+int MPI_Query_thread(int *provided)
 </PRE>
 <H2>Output Parameters</H2>
 <DL><DT><B>provided </B> <DD> Level of thread support provided.  This is the same value
-that was returned in the <tt>provided</tt> argument in <tt>MPI_Init_thread</tt>.
+that was returned in the <TT>provided</TT> argument in <TT>MPI_Init_thread</TT>.
 </DL>
 <P>
 <H2>Notes</H2>
 The valid values for the level of thread support are:
 <DL>
-<DT><B>MPI_THREAD_SINGLE </B><DD>Only one thread will execute. 
+<DT><B>MPI_THREAD_SINGLE </B><DD>Only one thread will execute.
 
-<DT><B>MPI_THREAD_FUNNELED </B><DD>The process may be multi-threaded, but only the main 
-thread will make MPI calls (all MPI calls are funneled to the 
-main thread). 
+<DT><B>MPI_THREAD_FUNNELED </B><DD>The process may be multi-threaded, but only the main
+thread will make MPI calls (all MPI calls are funneled to the
+main thread).
 
-<DT><B>MPI_THREAD_SERIALIZED </B><DD>The process may be multi-threaded, and multiple 
-threads may make MPI calls, but only one at a time: MPI calls are not 
-made concurrently from two distinct threads (all MPI calls are serialized). 
+<DT><B>MPI_THREAD_SERIALIZED </B><DD>The process may be multi-threaded, and multiple
+threads may make MPI calls, but only one at a time: MPI calls are not
+made concurrently from two distinct threads (all MPI calls are serialized).
 
-<DT><B>MPI_THREAD_MULTIPLE </B><DD>Multiple threads may call MPI, with no restrictions. 
+<DT><B>MPI_THREAD_MULTIPLE </B><DD>Multiple threads may call MPI, with no restrictions.
 </DL>
 <P>
-If <tt>MPI_Init</tt> was called instead of <tt>MPI_Init_thread</tt>, the level of
+If <TT>MPI_Init</TT> was called instead of <TT>MPI_Init_thread</TT>, the level of
 thread support is defined by the implementation.  This routine allows
 you to find out the provided level.  It is also useful for library
 routines that discover that MPI has already been initialized and
@@ -45,27 +45,27 @@ This means that this routine may safely be used by multiple threads and
 from within a signal handler.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Raccumulate.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Raccumulate.html
index f956b4f7..06289d7e 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Raccumulate.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Raccumulate.html
@@ -10,16 +10,15 @@ Accumulate data into the target process using remote memory access and return a
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Raccumulate(const void *origin_addr, int origin_count, MPI_Datatype
-                   origin_datatype, int target_rank, MPI_Aint
-                   target_disp, int target_count, MPI_Datatype
-                   target_datatype, MPI_Op op, MPI_Win win,
-                   MPI_Request *request) 
+                    origin_datatype, int target_rank, MPI_Aint
+                    target_disp, int target_count, MPI_Datatype
+                    target_datatype, MPI_Op op, MPI_Win win, MPI_Request * request)
 </PRE>
 <P>
-<tt>MPI_Raccumulate</tt> is similar to <tt>MPI_Accumulate</tt>, except that it allocates a
+<TT>MPI_Raccumulate</TT> is similar to <TT>MPI_Accumulate</TT>, except that it allocates a
 communication request object and associates it with the request handle (the
 argument request) that can be used to wait or test for completion.  The
-completion of an <tt>MPI_Raccumulate</tt> operation indicates that the origin buffer is
+completion of an <TT>MPI_Raccumulate</TT> operation indicates that the origin buffer is
 free to be updated. It does not indicate that the operation has completed at
 the target window.
 <P>
@@ -51,53 +50,53 @@ buffer (nonnegative integer)
 <P>
 <H2>Notes</H2>
 The basic components of both the origin and target datatype must be the same
-predefined datatype (e.g., all <tt>MPI_INT</tt> or all <tt>MPI_DOUBLE_PRECISION</tt>).
+predefined datatype (e.g., all <TT>MPI_INT</TT> or all <TT>MPI_DOUBLE_PRECISION</TT>).
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Accumulate
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Recv.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Recv.html
index 5158f635..6512099f 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Recv.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Recv.html
@@ -10,88 +10,88 @@ Blocking receive for a message
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Recv(void *buf, int count, MPI_Datatype datatype, int source, int tag,
-             MPI_Comm comm, MPI_Status *status)
+             MPI_Comm comm, MPI_Status * status)
 </PRE>
 <H2>Output Parameters</H2>
 <DL>
-<DT><B>buf </B><DD>initial address of receive buffer (choice) 
+<DT><B>buf </B><DD>initial address of receive buffer (choice)
 
-<DT><B>status </B><DD>status object (Status) 
+<DT><B>status </B><DD>status object (Status)
 </DL>
 <P>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>count </B><DD>maximum number of elements in receive buffer (integer) 
+<DT><B>count </B><DD>maximum number of elements in receive buffer (integer)
 
-<DT><B>datatype </B><DD>datatype of each receive buffer element (handle) 
+<DT><B>datatype </B><DD>datatype of each receive buffer element (handle)
 
-<DT><B>source </B><DD>rank of source (integer) 
+<DT><B>source </B><DD>rank of source (integer)
 
-<DT><B>tag </B><DD>message tag (integer) 
+<DT><B>tag </B><DD>message tag (integer)
 
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Notes</H2>
-The <tt>count</tt> argument indicates the maximum length of a message; the actual
-length of the message can be determined with <tt>MPI_Get_count</tt>.
+The <TT>count</TT> argument indicates the maximum length of a message; the actual
+length of the message can be determined with <TT>MPI_Get_count</TT>.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
-The <tt>status</tt> argument must be declared as an array of size <tt>MPI_STATUS_SIZE</tt>,
-as in <tt>integer status(MPI_STATUS_SIZE)</tt>.
+The <TT>status</TT> argument must be declared as an array of size <TT>MPI_STATUS_SIZE</TT>,
+as in <TT>integer status(MPI_STATUS_SIZE)</TT>.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TAG </B> <DD> Invalid tag argument.  Tags must be non-negative; tags
-in a receive (<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may
-also be <tt>MPI_ANY_TAG</tt>.  The largest tag value is available through the 
-the attribute <tt>MPI_TAG_UB</tt>.
+in a receive (<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may
+also be <TT>MPI_ANY_TAG</TT>.  The largest tag value is available through the 
+the attribute <TT>MPI_TAG_UB</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <P>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Recv_init.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Recv_init.html
index 836a95ed..7597b861 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Recv_init.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Recv_init.html
@@ -9,26 +9,26 @@
 Create a persistent request for a receive 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Recv_init(void *buf, int count, MPI_Datatype datatype, int source, 
-                 int tag, MPI_Comm comm, MPI_Request *request)
+int MPI_Recv_init(void *buf, int count, MPI_Datatype datatype, int source,
+                  int tag, MPI_Comm comm, MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>buf </B><DD>initial address of receive buffer (choice) 
+<DT><B>buf </B><DD>initial address of receive buffer (choice)
 
-<DT><B>count </B><DD>number of elements received (integer) 
+<DT><B>count </B><DD>number of elements received (integer)
 
-<DT><B>datatype </B><DD>type of each element (handle) 
+<DT><B>datatype </B><DD>type of each element (handle)
 
-<DT><B>source </B><DD>rank of source or <tt>MPI_ANY_SOURCE</tt> (integer) 
+<DT><B>source </B><DD>rank of source or <TT>MPI_ANY_SOURCE</TT> (integer)
 
-<DT><B>tag </B><DD>message tag or <tt>MPI_ANY_TAG</tt> (integer) 
+<DT><B>tag </B><DD>message tag or <TT>MPI_ANY_TAG</TT> (integer)
 
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>request </B> <DD> communication request (handle) 
+<DL><DT><B>request </B> <DD> communication request (handle)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -36,31 +36,31 @@ int MPI_Recv_init(void *buf, int count, MPI_Datatype datatype, int source,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -70,26 +70,26 @@ possible.
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_TAG </B> <DD> Invalid tag argument.  Tags must be non-negative; tags
-in a receive (<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may
-also be <tt>MPI_ANY_TAG</tt>.  The largest tag value is available through the 
-the attribute <tt>MPI_TAG_UB</tt>.
+in a receive (<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may
+also be <TT>MPI_ANY_TAG</TT>.  The largest tag value is available through the 
+the attribute <TT>MPI_TAG_UB</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_INTERN </B> <DD> This error is returned when some part of the MPICH 
 implementation is unable to acquire memory.  
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Start, MPI_Startall, MPI_Request_free
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Reduce.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Reduce.html
index 340e2704..7baf6042 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Reduce.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Reduce.html
@@ -14,22 +14,22 @@ int MPI_Reduce(const void *sendbuf, void *recvbuf, int count, MPI_Datatype datat
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>sendbuf </B><DD>address of send buffer (choice) 
+<DT><B>sendbuf </B><DD>address of send buffer (choice)
 
-<DT><B>count </B><DD>number of elements in send buffer (integer) 
+<DT><B>count </B><DD>number of elements in send buffer (integer)
 
-<DT><B>datatype </B><DD>data type of elements of send buffer (handle) 
+<DT><B>datatype </B><DD>data type of elements of send buffer (handle)
 
-<DT><B>op </B><DD>reduce operation (handle) 
+<DT><B>op </B><DD>reduce operation (handle)
 
-<DT><B>root </B><DD>rank of root process (integer) 
+<DT><B>root </B><DD>rank of root process (integer)
 
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>recvbuf </B> <DD> address of receive buffer (choice, 
-significant only at <tt>root</tt>) 
+<DL><DT><B>recvbuf </B> <DD> address of receive buffer (choice,
+significant only at <TT>root</TT>)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -37,25 +37,25 @@ significant only at <tt>root</tt>)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Notes on collective operations</H2>
 <P>
-The reduction functions (<tt>MPI_Op</tt>) do not return an error value.  As a result,
-if the functions detect an error, all they can do is either call <tt>MPI_Abort
-</tt>or silently skip the problem.  Thus, if you change the error handler from
-<tt>MPI_ERRORS_ARE_FATAL</tt> to something else, for example, <tt>MPI_ERRORS_RETURN</tt>,
+The reduction functions (<TT>MPI_Op</TT>) do not return an error value.  As a result,
+if the functions detect an error, all they can do is either call <TT>MPI_Abort
+</TT>or silently skip the problem.  Thus, if you change the error handler from
+<TT>MPI_ERRORS_ARE_FATAL</TT> to something else, for example, <TT>MPI_ERRORS_RETURN</TT>,
 then no error may be indicated.
 <P>
 The reason for this is the performance problems in ensuring that
@@ -63,36 +63,36 @@ all collective routines return the same error value.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_BUFFER </B> <DD> Invalid buffer pointer.  Usually a null buffer where
 one is not valid.
 </DL>
 <DL><DT><B>MPI_ERR_BUFFER </B> <DD> This error class is associcated with an error code that
-indicates that two buffer arguments are <em>aliased</em>; that is, the 
+indicates that two buffer arguments are <EM>aliased</EM>; that is, the 
 describe overlapping storage (often the exact same storage).  This
 is prohibited in MPI (because it is prohibited by the Fortran 
 standard, and rather than have a separate case for C and Fortran, the
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Reduce_local.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Reduce_local.html
index 9317219f..8c68eb26 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Reduce_local.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Reduce_local.html
@@ -31,25 +31,25 @@ int MPI_Reduce_local(const void *inbuf, void *inoutbuf, int count, MPI_Datatype
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Notes on collective operations</H2>
 <P>
-The reduction functions (<tt>MPI_Op</tt>) do not return an error value.  As a result,
-if the functions detect an error, all they can do is either call <tt>MPI_Abort
-</tt>or silently skip the problem.  Thus, if you change the error handler from
-<tt>MPI_ERRORS_ARE_FATAL</tt> to something else, for example, <tt>MPI_ERRORS_RETURN</tt>,
+The reduction functions (<TT>MPI_Op</TT>) do not return an error value.  As a result,
+if the functions detect an error, all they can do is either call <TT>MPI_Abort
+</TT>or silently skip the problem.  Thus, if you change the error handler from
+<TT>MPI_ERRORS_ARE_FATAL</TT> to something else, for example, <TT>MPI_ERRORS_RETURN</TT>,
 then no error may be indicated.
 <P>
 The reason for this is the performance problems in ensuring that
@@ -57,16 +57,16 @@ all collective routines return the same error value.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -76,14 +76,14 @@ possible.
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_BUFFER </B> <DD> Invalid buffer pointer.  Usually a null buffer where
 one is not valid.
 </DL>
 <DL><DT><B>MPI_ERR_BUFFER </B> <DD> This error class is associcated with an error code that
-indicates that two buffer arguments are <em>aliased</em>; that is, the 
+indicates that two buffer arguments are <EM>aliased</EM>; that is, the 
 describe overlapping storage (often the exact same storage).  This
 is prohibited in MPI (because it is prohibited by the Fortran 
 standard, and rather than have a separate case for C and Fortran, the
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Reduce_scatter.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Reduce_scatter.html
index 45782ac0..a81956b6 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Reduce_scatter.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Reduce_scatter.html
@@ -10,25 +10,25 @@ Combines values and scatters the results
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Reduce_scatter(const void *sendbuf, void *recvbuf, const int recvcounts[],
-                      MPI_Datatype datatype, MPI_Op op, MPI_Comm comm)
+                       MPI_Datatype datatype, MPI_Op op, MPI_Comm comm)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>sendbuf </B><DD>starting address of send buffer (choice) 
+<DT><B>sendbuf </B><DD>starting address of send buffer (choice)
 
-<DT><B>recvcounts </B><DD>integer array specifying the 
+<DT><B>recvcounts </B><DD>integer array specifying the
 number of elements in result distributed to each process.
-Array must be identical on all calling processes. 
+Array must be identical on all calling processes.
 
-<DT><B>datatype </B><DD>data type of elements of input buffer (handle) 
+<DT><B>datatype </B><DD>data type of elements of input buffer (handle)
 
-<DT><B>op </B><DD>operation (handle) 
+<DT><B>op </B><DD>operation (handle)
 
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>recvbuf </B> <DD> starting address of receive buffer (choice) 
+<DL><DT><B>recvbuf </B> <DD> starting address of receive buffer (choice)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -36,25 +36,25 @@ Array must be identical on all calling processes.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Notes on collective operations</H2>
 <P>
-The reduction functions (<tt>MPI_Op</tt>) do not return an error value.  As a result,
-if the functions detect an error, all they can do is either call <tt>MPI_Abort
-</tt>or silently skip the problem.  Thus, if you change the error handler from
-<tt>MPI_ERRORS_ARE_FATAL</tt> to something else, for example, <tt>MPI_ERRORS_RETURN</tt>,
+The reduction functions (<TT>MPI_Op</TT>) do not return an error value.  As a result,
+if the functions detect an error, all they can do is either call <TT>MPI_Abort
+</TT>or silently skip the problem.  Thus, if you change the error handler from
+<TT>MPI_ERRORS_ARE_FATAL</TT> to something else, for example, <TT>MPI_ERRORS_RETURN</TT>,
 then no error may be indicated.
 <P>
 The reason for this is the performance problems in ensuring that
@@ -62,40 +62,40 @@ all collective routines return the same error value.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_BUFFER </B> <DD> Invalid buffer pointer.  Usually a null buffer where
 one is not valid.
 </DL>
-<DL><DT><B>MPI_ERR_OP </B> <DD> Invalid operation.  MPI operations (objects of type <tt>MPI_Op</tt>)
-must either be one of the predefined operations (e.g., <tt>MPI_SUM</tt>) or
-created with <tt>MPI_Op_create</tt>.
+<DL><DT><B>MPI_ERR_OP </B> <DD> Invalid operation.  MPI operations (objects of type <TT>MPI_Op</TT>)
+must either be one of the predefined operations (e.g., <TT>MPI_SUM</TT>) or
+created with <TT>MPI_Op_create</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_BUFFER </B> <DD> This error class is associcated with an error code that
-indicates that two buffer arguments are <em>aliased</em>; that is, the 
+indicates that two buffer arguments are <EM>aliased</EM>; that is, the 
 describe overlapping storage (often the exact same storage).  This
 is prohibited in MPI (because it is prohibited by the Fortran 
 standard, and rather than have a separate case for C and Fortran, the
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Reduce_scatter_block.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Reduce_scatter_block.html
index f4e098d6..eb7ed1ee 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Reduce_scatter_block.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Reduce_scatter_block.html
@@ -9,25 +9,24 @@
 Combines values and scatters the results 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Reduce_scatter_block(const void *sendbuf, void *recvbuf, 
-                             int recvcount, 
-                             MPI_Datatype datatype, MPI_Op op, MPI_Comm comm)
+int MPI_Reduce_scatter_block(const void *sendbuf, void *recvbuf,
+                             int recvcount, MPI_Datatype datatype, MPI_Op op, MPI_Comm comm)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>sendbuf </B><DD>starting address of send buffer (choice) 
+<DT><B>sendbuf </B><DD>starting address of send buffer (choice)
 
 <DT><B>recvcount </B><DD>element count per block (non-negative integer)
 
-<DT><B>datatype </B><DD>data type of elements of input buffer (handle) 
+<DT><B>datatype </B><DD>data type of elements of input buffer (handle)
 
-<DT><B>op </B><DD>operation (handle) 
+<DT><B>op </B><DD>operation (handle)
 
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>recvbuf </B> <DD> starting address of receive buffer (choice) 
+<DL><DT><B>recvbuf </B> <DD> starting address of receive buffer (choice)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -35,25 +34,25 @@ int MPI_Reduce_scatter_block(const void *sendbuf, void *recvbuf,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Notes on collective operations</H2>
 <P>
-The reduction functions (<tt>MPI_Op</tt>) do not return an error value.  As a result,
-if the functions detect an error, all they can do is either call <tt>MPI_Abort
-</tt>or silently skip the problem.  Thus, if you change the error handler from
-<tt>MPI_ERRORS_ARE_FATAL</tt> to something else, for example, <tt>MPI_ERRORS_RETURN</tt>,
+The reduction functions (<TT>MPI_Op</TT>) do not return an error value.  As a result,
+if the functions detect an error, all they can do is either call <TT>MPI_Abort
+</TT>or silently skip the problem.  Thus, if you change the error handler from
+<TT>MPI_ERRORS_ARE_FATAL</TT> to something else, for example, <TT>MPI_ERRORS_RETURN</TT>,
 then no error may be indicated.
 <P>
 The reason for this is the performance problems in ensuring that
@@ -61,40 +60,40 @@ all collective routines return the same error value.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_BUFFER </B> <DD> Invalid buffer pointer.  Usually a null buffer where
 one is not valid.
 </DL>
-<DL><DT><B>MPI_ERR_OP </B> <DD> Invalid operation.  MPI operations (objects of type <tt>MPI_Op</tt>)
-must either be one of the predefined operations (e.g., <tt>MPI_SUM</tt>) or
-created with <tt>MPI_Op_create</tt>.
+<DL><DT><B>MPI_ERR_OP </B> <DD> Invalid operation.  MPI operations (objects of type <TT>MPI_Op</TT>)
+must either be one of the predefined operations (e.g., <TT>MPI_SUM</TT>) or
+created with <TT>MPI_Op_create</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_BUFFER </B> <DD> This error class is associcated with an error code that
-indicates that two buffer arguments are <em>aliased</em>; that is, the 
+indicates that two buffer arguments are <EM>aliased</EM>; that is, the 
 describe overlapping storage (often the exact same storage).  This
 is prohibited in MPI (because it is prohibited by the Fortran 
 standard, and rather than have a separate case for C and Fortran, the
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Register_datarep.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Register_datarep.html
index bafce011..ad46d18e 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Register_datarep.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Register_datarep.html
@@ -6,14 +6,13 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Register_datarep"><H1>MPI_Register_datarep</H1></A>
-Register functions for user-defined data  representations 
+Register functions for user-defined data representations 
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Register_datarep(ROMIO_CONST char *datarep,
-                       MPI_Datarep_conversion_function *read_conversion_fn,
-                       MPI_Datarep_conversion_function *write_conversion_fn,
-                       MPI_Datarep_extent_function *dtype_file_extent_fn,
-                       void *extra_state)
+                         MPI_Datarep_conversion_function * read_conversion_fn,
+                         MPI_Datarep_conversion_function * write_conversion_fn,
+                         MPI_Datarep_extent_function * dtype_file_extent_fn, void *extra_state)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -36,17 +35,17 @@ three functions
 This function allows the user to provide routines to convert data from
 an external representation, used within a file, and the native representation,
 used within the CPU.  There is one predefined data representation,
-<tt>external32</tt>.  Please consult the MPI-2 standard for details on this
+<TT>external32</TT>.  Please consult the MPI-2 standard for details on this
 function.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Request_free.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Request_free.html
index e4774089..def31657 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Request_free.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Request_free.html
@@ -9,22 +9,22 @@
 Frees a communication request object 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Request_free(MPI_Request *request)
+int MPI_Request_free(MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>request </B> <DD> communication request (handle) 
+<DL><DT><B>request </B> <DD> communication request (handle)
 </DL>
 <P>
 <H2>Notes</H2>
 <P>
 This routine is normally used to free inactive persistent requests created with
-either <tt>MPI_Recv_init</tt> or <tt>MPI_Send_init</tt> and friends.  It <em>is</em> also
+either <TT>MPI_Recv_init</TT> or <TT>MPI_Send_init</TT> and friends.  It <EM>is</EM> also
 permissible to free an active request.  However, once freed, the request can no
-longer be used in a wait or test routine (e.g., <tt>MPI_Wait</tt>) to determine
+longer be used in a wait or test routine (e.g., <TT>MPI_Wait</TT>) to determine
 completion.
 <P>
 This routine may also be used to free a non-persistent requests such as those
-created with <tt>MPI_Irecv</tt> or <tt>MPI_Isend</tt> and friends.  Like active persistent
+created with <TT>MPI_Irecv</TT> or <TT>MPI_Isend</TT> and friends.  Like active persistent
 requests, once freed, the request can no longer be used with test/wait routines
 to determine completion.
 <P>
@@ -33,46 +33,46 @@ to determine completion.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
-<DL><DT><B>MPI_ERR_REQUEST </B> <DD> Invalid <tt>MPI_Request</tt>.  Either null or, in the case of a
-<tt>MPI_Start</tt> or <tt>MPI_Startall</tt>, not a persistent request.
+<DL><DT><B>MPI_ERR_REQUEST </B> <DD> Invalid <TT>MPI_Request</TT>.  Either null or, in the case of a
+<TT>MPI_Start</TT> or <TT>MPI_Startall</TT>, not a persistent request.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
 also: MPI_Isend, MPI_Irecv, MPI_Issend, MPI_Ibsend, MPI_Irsend,
-<br>MPI_Recv_init, MPI_Send_init, MPI_Ssend_init, MPI_Rsend_init, MPI_Wait,
+<BR>MPI_Recv_init, MPI_Send_init, MPI_Ssend_init, MPI_Rsend_init, MPI_Wait,
 MPI_Test, MPI_Waitall, MPI_Waitany, MPI_Waitsome, MPI_Testall, MPI_Testany,
 MPI_Testsome
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Request_get_status.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Request_get_status.html
index f241921f..e9be696a 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Request_get_status.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Request_get_status.html
@@ -9,54 +9,54 @@
 Nondestructive test for the completion of a Request 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Request_get_status(MPI_Request request, int *flag, MPI_Status *status)
+int MPI_Request_get_status(MPI_Request request, int *flag, MPI_Status * status)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>request </B> <DD> request (handle).  May be <tt>MPI_REQUEST_NULL</tt>.
+<DL><DT><B>request </B> <DD> request (handle).  May be <TT>MPI_REQUEST_NULL</TT>.
 </DL>
 <P>
 <H2>Output Parameters</H2>
 <DL>
 <DT><B>flag </B><DD>true if operation has completed (logical)
 
-<DT><B>status </B><DD>status object (Status).  May be <tt>MPI_STATUS_IGNORE</tt>.
+<DT><B>status </B><DD>status object (Status).  May be <TT>MPI_STATUS_IGNORE</TT>.
 </DL>
 <P>
 <H2>Notes</H2>
-Unlike <tt>MPI_Test</tt>, <tt>MPI_Request_get_status</tt> does not deallocate or
+Unlike <TT>MPI_Test</TT>, <TT>MPI_Request_get_status</TT> does not deallocate or
 deactivate the request.  A call to one of the test/wait routines or
-<tt>MPI_Request_free</tt> should be made to release the request object.
+<TT>MPI_Request_free</TT> should be made to release the request object.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Rget.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Rget.html
index 5f8e5e8e..cff6f099 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Rget.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Rget.html
@@ -10,15 +10,14 @@ Get data from a memory window on a remote process
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Rget(void *origin_addr, int origin_count, MPI_Datatype
-            origin_datatype, int target_rank, MPI_Aint target_disp,
-            int target_count, MPI_Datatype target_datatype, MPI_Win
-            win, MPI_Request *request)
+             origin_datatype, int target_rank, MPI_Aint target_disp,
+             int target_count, MPI_Datatype target_datatype, MPI_Win win, MPI_Request * request)
 </PRE>
 <P>
-<tt>MPI_Rget</tt> is similar to <tt>MPI_Get</tt>, except that it allocates a communication
+<TT>MPI_Rget</TT> is similar to <TT>MPI_Get</TT>, except that it allocates a communication
 request object and associates it with the request handle (the argument request)
-that can be used to wait or test for completion. The completion of an <tt>MPI_Rget
-</tt>operation indicates that the data is available in the origin buffer. If
+that can be used to wait or test for completion. The completion of an <TT>MPI_Rget
+</TT>operation indicates that the data is available in the origin buffer. If
 origin_addr points to memory attached to a window, then the data becomes
 available in the private copy of this window.
 <P>
@@ -51,54 +50,54 @@ target buffer (nonnegative integer)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Get
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Rget_accumulate.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Rget_accumulate.html
index b8197500..121ac217 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Rget_accumulate.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Rget_accumulate.html
@@ -10,16 +10,16 @@ Perform an atomic, one-sided read-and-accumulate operation and return a request
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Rget_accumulate(const void *origin_addr, int origin_count,
-        MPI_Datatype origin_datatype, void *result_addr, int result_count,
-        MPI_Datatype result_datatype, int target_rank, MPI_Aint target_disp,
-        int target_count, MPI_Datatype target_datatype, MPI_Op op, MPI_Win win,
-        MPI_Request *request)
+                        MPI_Datatype origin_datatype, void *result_addr, int result_count,
+                        MPI_Datatype result_datatype, int target_rank, MPI_Aint target_disp,
+                        int target_count, MPI_Datatype target_datatype, MPI_Op op, MPI_Win win,
+                        MPI_Request * request)
 </PRE>
 <P>
-<tt>MPI_Rget_accumulate</tt> is similar to <tt>MPI_Get_accumulate</tt>, except that it allocates
+<TT>MPI_Rget_accumulate</TT> is similar to <TT>MPI_Get_accumulate</TT>, except that it allocates
 a communication request object and associates it with the request handle (the
 argument request) that can be used to wait or test for completion. The
-completion of an <tt>MPI_Rget_accumulate</tt> operation indicates that the data is
+completion of an <TT>MPI_Rget_accumulate</TT> operation indicates that the data is
 available in the result buffer and the origin buffer is free to be updated. It
 does not indicate that the operation has been completed at the target window.
 <P>
@@ -60,56 +60,56 @@ This operations is atomic with respect to other "accumulate" operations.
 <P>
 The get and accumulate steps are executed atomically for each basic element in
 the datatype (see MPI 3.0 Section 11.7 for details). The predefined operation
-<tt>MPI_REPLACE</tt> provides fetch-and-set behavior.
+<TT>MPI_REPLACE</TT> provides fetch-and-set behavior.
 <P>
 The basic components of both the origin and target datatype must be the same
-predefined datatype (e.g., all <tt>MPI_INT</tt> or all <tt>MPI_DOUBLE_PRECISION</tt>).
+predefined datatype (e.g., all <TT>MPI_INT</TT> or all <TT>MPI_DOUBLE_PRECISION</TT>).
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Get_accumulate MPI_Fetch_and_op
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Rput.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Rput.html
index 3ddad9b0..174caddc 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Rput.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Rput.html
@@ -10,18 +10,17 @@ Put data into a memory window on a remote process and return a request handle fo
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Rput(const void *origin_addr, int origin_count, MPI_Datatype
-            origin_datatype, int target_rank, MPI_Aint target_disp,
-            int target_count, MPI_Datatype target_datatype, MPI_Win
-            win, MPI_Request *request)
+             origin_datatype, int target_rank, MPI_Aint target_disp,
+             int target_count, MPI_Datatype target_datatype, MPI_Win win, MPI_Request * request)
 </PRE>
 <P>
-<tt>MPI_Rput</tt> is similar to <tt>MPI_Put</tt>, except that it allocates a
+<TT>MPI_Rput</TT> is similar to <TT>MPI_Put</TT>, except that it allocates a
 communication request object and associates it with the request handle (the
-argument request). The completion of an <tt>MPI_Rput</tt> operation (i.e., after the
+argument request). The completion of an <TT>MPI_Rput</TT> operation (i.e., after the
 corresponding test or wait) indicates that the sender is now free to update
 the locations in the origin buffer. It does not indicate that the data is
 available at the target window. If remote completion is required,
-<tt>MPI_Win_flush</tt>, <tt>MPI_Win_flush_all</tt>, <tt>MPI_Win_unlock</tt>, or <tt>MPI_Win_unlock_all</tt> can be
+<TT>MPI_Win_flush</TT>, <TT>MPI_Win_flush_all</TT>, <TT>MPI_Win_unlock</TT>, or <TT>MPI_Win_unlock_all</TT> can be
 used.
 <P>
 <H2>Input Parameters</H2>
@@ -52,54 +51,54 @@ used.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Put
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Rsend.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Rsend.html
index a841b982..780f5ee5 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Rsend.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Rsend.html
@@ -6,25 +6,24 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Rsend"><H1>MPI_Rsend</H1></A>
-Blocking ready send  
+Blocking ready send 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Rsend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-              MPI_Comm comm)
+int MPI_Rsend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag, MPI_Comm comm)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>buf </B><DD>initial address of send buffer (choice) 
+<DT><B>buf </B><DD>initial address of send buffer (choice)
 
-<DT><B>count </B><DD>number of elements in send buffer (nonnegative integer) 
+<DT><B>count </B><DD>number of elements in send buffer (nonnegative integer)
 
-<DT><B>datatype </B><DD>datatype of each send buffer element (handle) 
+<DT><B>datatype </B><DD>datatype of each send buffer element (handle)
 
-<DT><B>dest </B><DD>rank of destination (integer) 
+<DT><B>dest </B><DD>rank of destination (integer)
 
-<DT><B>tag </B><DD>message tag (integer) 
+<DT><B>tag </B><DD>message tag (integer)
 
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -32,54 +31,54 @@ int MPI_Rsend(const void *buf, int count, MPI_Datatype datatype, int dest, int t
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_TAG </B> <DD> Invalid tag argument.  Tags must be non-negative; tags
-in a receive (<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may
-also be <tt>MPI_ANY_TAG</tt>.  The largest tag value is available through the 
-the attribute <tt>MPI_TAG_UB</tt>.
+in a receive (<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may
+also be <TT>MPI_ANY_TAG</TT>.  The largest tag value is available through the 
+the attribute <TT>MPI_TAG_UB</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <P>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Rsend_init.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Rsend_init.html
index 27fdcca4..e600d9ae 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Rsend_init.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Rsend_init.html
@@ -10,25 +10,25 @@ Creates a persistent request for a ready send
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Rsend_init(const void *buf, int count, MPI_Datatype datatype, int dest,
-                  int tag, MPI_Comm comm, MPI_Request *request)
+                   int tag, MPI_Comm comm, MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>buf </B><DD>initial address of send buffer (choice) 
+<DT><B>buf </B><DD>initial address of send buffer (choice)
 
-<DT><B>count </B><DD>number of elements sent (integer) 
+<DT><B>count </B><DD>number of elements sent (integer)
 
-<DT><B>datatype </B><DD>type of each element (handle) 
+<DT><B>datatype </B><DD>type of each element (handle)
 
-<DT><B>dest </B><DD>rank of destination (integer) 
+<DT><B>dest </B><DD>rank of destination (integer)
 
-<DT><B>tag </B><DD>message tag (integer) 
+<DT><B>tag </B><DD>message tag (integer)
 
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>request </B> <DD> communication request (handle) 
+<DL><DT><B>request </B> <DD> communication request (handle)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -36,31 +36,31 @@ int MPI_Rsend_init(const void *buf, int count, MPI_Datatype datatype, int dest,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -70,26 +70,26 @@ possible.
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_TAG </B> <DD> Invalid tag argument.  Tags must be non-negative; tags
-in a receive (<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may
-also be <tt>MPI_ANY_TAG</tt>.  The largest tag value is available through the 
-the attribute <tt>MPI_TAG_UB</tt>.
+in a receive (<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may
+also be <TT>MPI_ANY_TAG</TT>.  The largest tag value is available through the 
+the attribute <TT>MPI_TAG_UB</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_INTERN </B> <DD> This error is returned when some part of the MPICH 
 implementation is unable to acquire memory.  
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Start, MPI_Request_free, MPI_Send_init
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Scan.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Scan.html
index 3b8443e3..9c7cf1ea 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Scan.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Scan.html
@@ -14,19 +14,19 @@ int MPI_Scan(const void *sendbuf, void *recvbuf, int count, MPI_Datatype datatyp
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>sendbuf </B><DD>starting address of send buffer (choice) 
+<DT><B>sendbuf </B><DD>starting address of send buffer (choice)
 
-<DT><B>count </B><DD>number of elements in input buffer (integer) 
+<DT><B>count </B><DD>number of elements in input buffer (integer)
 
-<DT><B>datatype </B><DD>data type of elements of input buffer (handle) 
+<DT><B>datatype </B><DD>data type of elements of input buffer (handle)
 
-<DT><B>op </B><DD>operation (handle) 
+<DT><B>op </B><DD>operation (handle)
 
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>recvbuf </B> <DD> starting address of receive buffer (choice) 
+<DL><DT><B>recvbuf </B> <DD> starting address of receive buffer (choice)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -34,25 +34,25 @@ int MPI_Scan(const void *sendbuf, void *recvbuf, int count, MPI_Datatype datatyp
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Notes on collective operations</H2>
 <P>
-The reduction functions (<tt>MPI_Op</tt>) do not return an error value.  As a result,
-if the functions detect an error, all they can do is either call <tt>MPI_Abort
-</tt>or silently skip the problem.  Thus, if you change the error handler from
-<tt>MPI_ERRORS_ARE_FATAL</tt> to something else, for example, <tt>MPI_ERRORS_RETURN</tt>,
+The reduction functions (<TT>MPI_Op</TT>) do not return an error value.  As a result,
+if the functions detect an error, all they can do is either call <TT>MPI_Abort
+</TT>or silently skip the problem.  Thus, if you change the error handler from
+<TT>MPI_ERRORS_ARE_FATAL</TT> to something else, for example, <TT>MPI_ERRORS_RETURN</TT>,
 then no error may be indicated.
 <P>
 The reason for this is the performance problems in ensuring that
@@ -60,36 +60,36 @@ all collective routines return the same error value.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_BUFFER </B> <DD> Invalid buffer pointer.  Usually a null buffer where
 one is not valid.
 </DL>
 <DL><DT><B>MPI_ERR_BUFFER </B> <DD> This error class is associcated with an error code that
-indicates that two buffer arguments are <em>aliased</em>; that is, the 
+indicates that two buffer arguments are <EM>aliased</EM>; that is, the 
 describe overlapping storage (often the exact same storage).  This
 is prohibited in MPI (because it is prohibited by the Fortran 
 standard, and rather than have a separate case for C and Fortran, the
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Scatter.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Scatter.html
index 25294ab6..f4b0d3ec 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Scatter.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Scatter.html
@@ -6,35 +6,34 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Scatter"><H1>MPI_Scatter</H1></A>
-Sends data from one process to all other processes in a  communicator 
+Sends data from one process to all other processes in a communicator 
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Scatter(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
-               void *recvbuf, int recvcount, MPI_Datatype recvtype, int root,
-               MPI_Comm comm)
+                void *recvbuf, int recvcount, MPI_Datatype recvtype, int root, MPI_Comm comm)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>sendbuf </B><DD>address of send buffer (choice, significant 
-only at <tt>root</tt>) 
+<DT><B>sendbuf </B><DD>address of send buffer (choice, significant
+only at <TT>root</TT>)
 
-<DT><B>sendcount </B><DD>number of elements sent to each process 
-(integer, significant only at <tt>root</tt>) 
+<DT><B>sendcount </B><DD>number of elements sent to each process
+(integer, significant only at <TT>root</TT>)
 
-<DT><B>sendtype </B><DD>data type of send buffer elements (significant only at <tt>root</tt>) 
-(handle) 
+<DT><B>sendtype </B><DD>data type of send buffer elements (significant only at <TT>root</TT>)
+(handle)
 
-<DT><B>recvcount </B><DD>number of elements in receive buffer (integer) 
+<DT><B>recvcount </B><DD>number of elements in receive buffer (integer)
 
-<DT><B>recvtype </B><DD>data type of receive buffer elements (handle) 
+<DT><B>recvtype </B><DD>data type of receive buffer elements (handle)
 
-<DT><B>root </B><DD>rank of sending process (integer) 
+<DT><B>root </B><DD>rank of sending process (integer)
 
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>recvbuf </B> <DD> address of receive buffer (choice) 
+<DL><DT><B>recvbuf </B> <DD> address of receive buffer (choice)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -42,44 +41,44 @@ only at <tt>root</tt>)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_BUFFER </B> <DD> Invalid buffer pointer.  Usually a null buffer where
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Scatterv.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Scatterv.html
index c80ee30f..f673ab86 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Scatterv.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Scatterv.html
@@ -11,33 +11,32 @@ Scatters a buffer in parts to all processes in a communicator
 <PRE>
 int MPI_Scatterv(const void *sendbuf, const int *sendcounts, const int *displs,
                  MPI_Datatype sendtype, void *recvbuf, int recvcount,
-                 MPI_Datatype recvtype,
-                 int root, MPI_Comm comm)
+                 MPI_Datatype recvtype, int root, MPI_Comm comm)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>sendbuf </B><DD>address of send buffer (choice, significant only at <tt>root</tt>) 
+<DT><B>sendbuf </B><DD>address of send buffer (choice, significant only at <TT>root</TT>)
 
-<DT><B>sendcounts </B><DD>integer array (of length group size) 
-specifying the number of elements to send to each processor  
+<DT><B>sendcounts </B><DD>integer array (of length group size)
+specifying the number of elements to send to each processor
 
-<DT><B>displs </B><DD>integer array (of length group size). Entry 
-<tt>i</tt>  specifies the displacement (relative to sendbuf  from
-which to take the outgoing data to process  <tt>i</tt> 
+<DT><B>displs </B><DD>integer array (of length group size). Entry
+<TT>i</TT>  specifies the displacement (relative to sendbuf  from
+which to take the outgoing data to process  <TT>i
+</TT>
+<DT><B>sendtype </B><DD>data type of send buffer elements (handle)
 
-<DT><B>sendtype </B><DD>data type of send buffer elements (handle) 
+<DT><B>recvcount </B><DD>number of elements in receive buffer (integer)
 
-<DT><B>recvcount </B><DD>number of elements in receive buffer (integer) 
+<DT><B>recvtype </B><DD>data type of receive buffer elements (handle)
 
-<DT><B>recvtype </B><DD>data type of receive buffer elements (handle) 
+<DT><B>root </B><DD>rank of sending process (integer)
 
-<DT><B>root </B><DD>rank of sending process (integer) 
-
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>recvbuf </B> <DD> address of receive buffer (choice) 
+<DL><DT><B>recvbuf </B> <DD> address of receive buffer (choice)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -45,44 +44,44 @@ which to take the outgoing data to process  <tt>i</tt>
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_BUFFER </B> <DD> Invalid buffer pointer.  Usually a null buffer where
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Send.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Send.html
index 973883aa..9aca15a5 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Send.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Send.html
@@ -9,22 +9,21 @@
 Performs a blocking send 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Send(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-             MPI_Comm comm)
+int MPI_Send(const void *buf, int count, MPI_Datatype datatype, int dest, int tag, MPI_Comm comm)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>buf </B><DD>initial address of send buffer (choice) 
+<DT><B>buf </B><DD>initial address of send buffer (choice)
 
-<DT><B>count </B><DD>number of elements in send buffer (nonnegative integer) 
+<DT><B>count </B><DD>number of elements in send buffer (nonnegative integer)
 
-<DT><B>datatype </B><DD>datatype of each send buffer element (handle) 
+<DT><B>datatype </B><DD>datatype of each send buffer element (handle)
 
-<DT><B>dest </B><DD>rank of destination (integer) 
+<DT><B>dest </B><DD>rank of destination (integer)
 
-<DT><B>tag </B><DD>message tag (integer) 
+<DT><B>tag </B><DD>message tag (integer)
 
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Notes</H2>
@@ -36,57 +35,57 @@ process.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_TAG </B> <DD> Invalid tag argument.  Tags must be non-negative; tags
-in a receive (<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may
-also be <tt>MPI_ANY_TAG</tt>.  The largest tag value is available through the 
-the attribute <tt>MPI_TAG_UB</tt>.
+in a receive (<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may
+also be <TT>MPI_ANY_TAG</TT>.  The largest tag value is available through the 
+the attribute <TT>MPI_TAG_UB</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Isend, MPI_Bsend
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Send_init.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Send_init.html
index 3cf42a20..36595a5c 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Send_init.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Send_init.html
@@ -10,25 +10,25 @@ Create a persistent request for a standard send
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Send_init(const void *buf, int count, MPI_Datatype datatype, int dest,
-                 int tag, MPI_Comm comm, MPI_Request *request)
+                  int tag, MPI_Comm comm, MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>buf </B><DD>initial address of send buffer (choice) 
+<DT><B>buf </B><DD>initial address of send buffer (choice)
 
-<DT><B>count </B><DD>number of elements sent (integer) 
+<DT><B>count </B><DD>number of elements sent (integer)
 
-<DT><B>datatype </B><DD>type of each element (handle) 
+<DT><B>datatype </B><DD>type of each element (handle)
 
-<DT><B>dest </B><DD>rank of destination (integer) 
+<DT><B>dest </B><DD>rank of destination (integer)
 
-<DT><B>tag </B><DD>message tag (integer) 
+<DT><B>tag </B><DD>message tag (integer)
 
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>request </B> <DD> communication request (handle) 
+<DL><DT><B>request </B> <DD> communication request (handle)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -36,31 +36,31 @@ int MPI_Send_init(const void *buf, int count, MPI_Datatype datatype, int dest,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -70,26 +70,26 @@ possible.
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_TAG </B> <DD> Invalid tag argument.  Tags must be non-negative; tags
-in a receive (<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may
-also be <tt>MPI_ANY_TAG</tt>.  The largest tag value is available through the 
-the attribute <tt>MPI_TAG_UB</tt>.
+in a receive (<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may
+also be <TT>MPI_ANY_TAG</TT>.  The largest tag value is available through the 
+the attribute <TT>MPI_TAG_UB</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_INTERN </B> <DD> This error is returned when some part of the MPICH 
 implementation is unable to acquire memory.  
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Start, MPI_Startall, MPI_Request_free
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Sendrecv.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Sendrecv.html
index 210ac18e..71c9a1ea 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Sendrecv.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Sendrecv.html
@@ -10,37 +10,36 @@ Sends and receives a message
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Sendrecv(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
-                int dest, int sendtag,
-                void *recvbuf, int recvcount, MPI_Datatype recvtype,
-                int source, int recvtag,
-                MPI_Comm comm, MPI_Status *status)
+                 int dest, int sendtag,
+                 void *recvbuf, int recvcount, MPI_Datatype recvtype,
+                 int source, int recvtag, MPI_Comm comm, MPI_Status * status)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>sendbuf </B><DD>initial address of send buffer (choice) 
+<DT><B>sendbuf </B><DD>initial address of send buffer (choice)
 
-<DT><B>sendcount </B><DD>number of elements in send buffer (integer) 
+<DT><B>sendcount </B><DD>number of elements in send buffer (integer)
 
-<DT><B>sendtype </B><DD>type of elements in send buffer (handle) 
+<DT><B>sendtype </B><DD>type of elements in send buffer (handle)
 
-<DT><B>dest </B><DD>rank of destination (integer) 
+<DT><B>dest </B><DD>rank of destination (integer)
 
-<DT><B>sendtag </B><DD>send tag (integer) 
+<DT><B>sendtag </B><DD>send tag (integer)
 
-<DT><B>recvcount </B><DD>number of elements in receive buffer (integer) 
+<DT><B>recvcount </B><DD>number of elements in receive buffer (integer)
 
-<DT><B>recvtype </B><DD>type of elements in receive buffer (handle) 
+<DT><B>recvtype </B><DD>type of elements in receive buffer (handle)
 
-<DT><B>source </B><DD>rank of source (integer) 
+<DT><B>source </B><DD>rank of source (integer)
 
-<DT><B>recvtag </B><DD>receive tag (integer) 
+<DT><B>recvtag </B><DD>receive tag (integer)
 
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
 <DL>
-<DT><B>recvbuf </B><DD>initial address of receive buffer (choice) 
+<DT><B>recvbuf </B><DD>initial address of receive buffer (choice)
 
 <DT><B>status </B><DD>status object (Status).  This refers to the receive operation.
 </DL>
@@ -50,57 +49,57 @@ int MPI_Sendrecv(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
-The <tt>status</tt> argument must be declared as an array of size <tt>MPI_STATUS_SIZE</tt>,
-as in <tt>integer status(MPI_STATUS_SIZE)</tt>.
+The <TT>status</TT> argument must be declared as an array of size <TT>MPI_STATUS_SIZE</TT>,
+as in <TT>integer status(MPI_STATUS_SIZE)</TT>.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_TAG </B> <DD> Invalid tag argument.  Tags must be non-negative; tags
-in a receive (<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may
-also be <tt>MPI_ANY_TAG</tt>.  The largest tag value is available through the 
-the attribute <tt>MPI_TAG_UB</tt>.
+in a receive (<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may
+also be <TT>MPI_ANY_TAG</TT>.  The largest tag value is available through the 
+the attribute <TT>MPI_TAG_UB</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <P>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Sendrecv_replace.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Sendrecv_replace.html
index 0ad62a9f..810cb50c 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Sendrecv_replace.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Sendrecv_replace.html
@@ -9,32 +9,32 @@
 Sends and receives using a single buffer 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Sendrecv_replace(void *buf, int count, MPI_Datatype datatype, 
-                       int dest, int sendtag, int source, int recvtag,
-                       MPI_Comm comm, MPI_Status *status)
+int MPI_Sendrecv_replace(void *buf, int count, MPI_Datatype datatype,
+                         int dest, int sendtag, int source, int recvtag,
+                         MPI_Comm comm, MPI_Status * status)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>count </B><DD>number of elements in send and receive buffer (integer) 
+<DT><B>count </B><DD>number of elements in send and receive buffer (integer)
 
-<DT><B>datatype </B><DD>type of elements in send and receive buffer (handle) 
+<DT><B>datatype </B><DD>type of elements in send and receive buffer (handle)
 
-<DT><B>dest </B><DD>rank of destination (integer) 
+<DT><B>dest </B><DD>rank of destination (integer)
 
-<DT><B>sendtag </B><DD>send message tag (integer) 
+<DT><B>sendtag </B><DD>send message tag (integer)
 
-<DT><B>source </B><DD>rank of source (integer) 
+<DT><B>source </B><DD>rank of source (integer)
 
-<DT><B>recvtag </B><DD>receive message tag (integer) 
+<DT><B>recvtag </B><DD>receive message tag (integer)
 
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
 <DL>
-<DT><B>buf </B><DD>initial address of send and receive buffer (choice) 
+<DT><B>buf </B><DD>initial address of send and receive buffer (choice)
 
-<DT><B>status </B><DD>status object (Status) 
+<DT><B>status </B><DD>status object (Status)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -42,57 +42,57 @@ int MPI_Sendrecv_replace(void *buf, int count, MPI_Datatype datatype,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
-The <tt>status</tt> argument must be declared as an array of size <tt>MPI_STATUS_SIZE</tt>,
-as in <tt>integer status(MPI_STATUS_SIZE)</tt>.
+The <TT>status</TT> argument must be declared as an array of size <TT>MPI_STATUS_SIZE</TT>,
+as in <TT>integer status(MPI_STATUS_SIZE)</TT>.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_TAG </B> <DD> Invalid tag argument.  Tags must be non-negative; tags
-in a receive (<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may
-also be <tt>MPI_ANY_TAG</tt>.  The largest tag value is available through the 
-the attribute <tt>MPI_TAG_UB</tt>.
+in a receive (<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may
+also be <TT>MPI_ANY_TAG</TT>.  The largest tag value is available through the 
+the attribute <TT>MPI_TAG_UB</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_TRUNCATE </B> <DD> Message truncated on receive.  The buffer size specified
 was too small for the received message.  This is a recoverable error in
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ssend.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ssend.html
index 19aa7dfb..670cadb2 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ssend.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ssend.html
@@ -9,22 +9,21 @@
 Blocking synchronous send 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Ssend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-              MPI_Comm comm)
+int MPI_Ssend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag, MPI_Comm comm)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>buf </B><DD>initial address of send buffer (choice) 
+<DT><B>buf </B><DD>initial address of send buffer (choice)
 
-<DT><B>count </B><DD>number of elements in send buffer (nonnegative integer) 
+<DT><B>count </B><DD>number of elements in send buffer (nonnegative integer)
 
-<DT><B>datatype </B><DD>datatype of each send buffer element (handle) 
+<DT><B>datatype </B><DD>datatype of each send buffer element (handle)
 
-<DT><B>dest </B><DD>rank of destination (integer) 
+<DT><B>dest </B><DD>rank of destination (integer)
 
-<DT><B>tag </B><DD>message tag (integer) 
+<DT><B>tag </B><DD>message tag (integer)
 
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -32,53 +31,53 @@ int MPI_Ssend(const void *buf, int count, MPI_Datatype datatype, int dest, int t
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_TAG </B> <DD> Invalid tag argument.  Tags must be non-negative; tags
-in a receive (<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may
-also be <tt>MPI_ANY_TAG</tt>.  The largest tag value is available through the 
-the attribute <tt>MPI_TAG_UB</tt>.
+in a receive (<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may
+also be <TT>MPI_ANY_TAG</TT>.  The largest tag value is available through the 
+the attribute <TT>MPI_TAG_UB</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ssend_init.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ssend_init.html
index 8ec438dc..d7ad3fec 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ssend_init.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Ssend_init.html
@@ -10,25 +10,25 @@ Creates a persistent request for a synchronous send
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Ssend_init(const void *buf, int count, MPI_Datatype datatype, int dest,
-                  int tag, MPI_Comm comm, MPI_Request *request)
+                   int tag, MPI_Comm comm, MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>buf </B><DD>initial address of send buffer (choice) 
+<DT><B>buf </B><DD>initial address of send buffer (choice)
 
-<DT><B>count </B><DD>number of elements sent (integer) 
+<DT><B>count </B><DD>number of elements sent (integer)
 
-<DT><B>datatype </B><DD>type of each element (handle) 
+<DT><B>datatype </B><DD>type of each element (handle)
 
-<DT><B>dest </B><DD>rank of destination (integer) 
+<DT><B>dest </B><DD>rank of destination (integer)
 
-<DT><B>tag </B><DD>message tag (integer) 
+<DT><B>tag </B><DD>message tag (integer)
 
-<DT><B>comm </B><DD>communicator (handle) 
+<DT><B>comm </B><DD>communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>request </B> <DD> communication request (handle) 
+<DL><DT><B>request </B> <DD> communication request (handle)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -36,53 +36,53 @@ int MPI_Ssend_init(const void *buf, int count, MPI_Datatype datatype, int dest,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_TAG </B> <DD> Invalid tag argument.  Tags must be non-negative; tags
-in a receive (<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may
-also be <tt>MPI_ANY_TAG</tt>.  The largest tag value is available through the 
-the attribute <tt>MPI_TAG_UB</tt>.
+in a receive (<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may
+also be <TT>MPI_ANY_TAG</TT>.  The largest tag value is available through the 
+the attribute <TT>MPI_TAG_UB</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Start.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Start.html
index 4874be4f..19f72fe7 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Start.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Start.html
@@ -9,10 +9,10 @@
 Initiates a communication with a persistent request handle 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Start(MPI_Request *request)
+int MPI_Start(MPI_Request * request)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>request </B> <DD> communication request (handle) 
+<DL><DT><B>request </B> <DD> communication request (handle)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -20,38 +20,38 @@ int MPI_Start(MPI_Request *request)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
-<DL><DT><B>MPI_ERR_REQUEST </B> <DD> Invalid <tt>MPI_Request</tt>.  Either null or, in the case of a
-<tt>MPI_Start</tt> or <tt>MPI_Startall</tt>, not a persistent request.
+<DL><DT><B>MPI_ERR_REQUEST </B> <DD> Invalid <TT>MPI_Request</TT>.  Either null or, in the case of a
+<TT>MPI_Start</TT> or <TT>MPI_Startall</TT>, not a persistent request.
 </DL>
 <P>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Startall.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Startall.html
index 170d738a..3dd8040c 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Startall.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Startall.html
@@ -6,65 +6,65 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Startall"><H1>MPI_Startall</H1></A>
-Starts a collection of persistent requests  
+Starts a collection of persistent requests 
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Startall(int count, MPI_Request array_of_requests[])
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>count </B><DD>list length (integer) 
+<DT><B>count </B><DD>list length (integer)
 
-<DT><B>array_of_requests </B><DD>array of requests (array of handle) 
+<DT><B>array_of_requests </B><DD>array of requests (array of handle)
 </DL>
 <P>
 <H2>Notes</H2>
 <P>
-Unlike <tt>MPI_Waitall</tt>, <tt>MPI_Startall</tt> does not provide a mechanism for
+Unlike <TT>MPI_Waitall</TT>, <TT>MPI_Startall</TT> does not provide a mechanism for
 returning multiple errors nor pinpointing the request(s) involved.
-Furthermore, the behavior of <tt>MPI_Startall</tt> after an error occurs is not
+Furthermore, the behavior of <TT>MPI_Startall</TT> after an error occurs is not
 defined by the MPI standard.  If well-defined error reporting and behavior
-are required, multiple calls to <tt>MPI_Start</tt> should be used instead.
+are required, multiple calls to <TT>MPI_Start</TT> should be used instead.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
-<DL><DT><B>MPI_ERR_REQUEST </B> <DD> Invalid <tt>MPI_Request</tt>.  Either null or, in the case of a
-<tt>MPI_Start</tt> or <tt>MPI_Startall</tt>, not a persistent request.
+<DL><DT><B>MPI_ERR_REQUEST </B> <DD> Invalid <TT>MPI_Request</TT>.  Either null or, in the case of a
+<TT>MPI_Start</TT> or <TT>MPI_Startall</TT>, not a persistent request.
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Status_set_cancelled.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Status_set_cancelled.html
index e364e65f..08854c71 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Status_set_cancelled.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Status_set_cancelled.html
@@ -6,10 +6,10 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Status_set_cancelled"><H1>MPI_Status_set_cancelled</H1></A>
-Sets the cancelled state associated with a  Status object 
+Sets the cancelled state associated with a Status object 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Status_set_cancelled(MPI_Status *status, int flag)
+int MPI_Status_set_cancelled(MPI_Status * status, int flag)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -23,37 +23,37 @@ int MPI_Status_set_cancelled(MPI_Status *status, int flag)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Status_set_elements.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Status_set_elements.html
index 801d5f8e..811222a8 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Status_set_elements.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Status_set_elements.html
@@ -9,16 +9,15 @@
 Set the number of elements in a status 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Status_set_elements(MPI_Status *status, MPI_Datatype datatype, 
-                          int count)
+int MPI_Status_set_elements(MPI_Status * status, MPI_Datatype datatype, int count)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>status </B><DD>status to associate count with (Status) 
+<DT><B>status </B><DD>status to associate count with (Status)
 
-<DT><B>datatype </B><DD>datatype associated with count (handle) 
+<DT><B>datatype </B><DD>datatype associated with count (handle)
 
-<DT><B>count </B><DD>number of elements to associate with status (integer) 
+<DT><B>count </B><DD>number of elements to associate with status (integer)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -26,41 +25,41 @@ int MPI_Status_set_elements(MPI_Status *status, MPI_Datatype datatype,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Status_set_elements_x.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Status_set_elements_x.html
index 4a2bcef8..f23e5eb5 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Status_set_elements_x.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Status_set_elements_x.html
@@ -9,7 +9,7 @@
 Set the number of elements in a status 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Status_set_elements_x(MPI_Status *status, MPI_Datatype datatype, MPI_Count count)
+int MPI_Status_set_elements_x(MPI_Status * status, MPI_Datatype datatype, MPI_Count count)
 </PRE>
 <H2>Input/Output Parameters</H2>
 <DL><DT><B>status </B> <DD> status with which to associate count (Status)
@@ -27,31 +27,31 @@ int MPI_Status_set_elements_x(MPI_Status *status, MPI_Datatype datatype, MPI_Cou
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_category_changed.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_category_changed.html
index 973c18af..18306121 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_category_changed.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_category_changed.html
@@ -25,21 +25,21 @@ from the second call is higher, then some categories have been added or expanded
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_category_get_categories.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_category_get_categories.html
index f1daa4de..997ec79a 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_category_get_categories.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_category_get_categories.html
@@ -27,21 +27,21 @@ int MPI_T_category_get_categories(int cat_index, int len, int indices[])
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_category_get_cvars.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_category_get_cvars.html
index ece44bb8..9f85f85e 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_category_get_cvars.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_category_get_cvars.html
@@ -27,21 +27,21 @@ int MPI_T_category_get_cvars(int cat_index, int len, int indices[])
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_category_get_index.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_category_get_index.html
index dbc49b10..df5cd19f 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_category_get_index.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_category_get_index.html
@@ -24,21 +24,21 @@ int MPI_T_category_get_index(const char *name, int *cat_index)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_category_get_info.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_category_get_info.html
index d32ecad2..da3396f0 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_category_get_info.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_category_get_info.html
@@ -10,7 +10,7 @@ Get the information about a category
 <H2>Synopsis</H2>
 <PRE>
 int MPI_T_category_get_info(int cat_index, char *name, int *name_len, char *desc,
-        int *desc_len, int *num_cvars, int *num_pvars, int *num_categories)
+                            int *desc_len, int *num_cvars, int *num_pvars, int *num_categories)
 </PRE>
 <H2>Input/Output Parameters</H2>
 <DL>
@@ -41,21 +41,21 @@ int MPI_T_category_get_info(int cat_index, char *name, int *name_len, char *desc
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_category_get_num.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_category_get_num.html
index db47f9e5..4a9f4c6f 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_category_get_num.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_category_get_num.html
@@ -20,21 +20,21 @@ int MPI_T_category_get_num(int *num_cat)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_category_get_pvars.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_category_get_pvars.html
index 289fd2a0..af0e7c6e 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_category_get_pvars.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_category_get_pvars.html
@@ -27,21 +27,21 @@ int MPI_T_category_get_pvars(int cat_index, int len, int indices[])
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_cvar_get_index.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_cvar_get_index.html
index ea0f3512..c496cb09 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_cvar_get_index.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_cvar_get_index.html
@@ -24,21 +24,21 @@ int MPI_T_cvar_get_index(const char *name, int *cvar_index)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_cvar_get_info.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_cvar_get_info.html
index 5546a11e..02011a22 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_cvar_get_info.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_cvar_get_info.html
@@ -10,8 +10,8 @@ Get the information about a control variable
 <H2>Synopsis</H2>
 <PRE>
 int MPI_T_cvar_get_info(int cvar_index, char *name, int *name_len,
-    int *verbosity, MPI_Datatype *datatype, MPI_T_enum *enumtype,
-    char *desc, int *desc_len, int *binding, int *scope)
+                        int *verbosity, MPI_Datatype * datatype, MPI_T_enum * enumtype,
+                        char *desc, int *desc_len, int *binding, int *scope)
 </PRE>
 <H2>Input/Output Parameters</H2>
 <DL>
@@ -46,21 +46,21 @@ int MPI_T_cvar_get_info(int cvar_index, char *name, int *name_len,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_cvar_get_num.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_cvar_get_num.html
index 1df60967..4ba66d24 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_cvar_get_num.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_cvar_get_num.html
@@ -20,21 +20,21 @@ int MPI_T_cvar_get_num(int *num_cvar)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_cvar_handle_alloc.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_cvar_handle_alloc.html
index b6bfffd5..1067154e 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_cvar_handle_alloc.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_cvar_handle_alloc.html
@@ -9,7 +9,8 @@
 Allocate a handle for a control variable 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_T_cvar_handle_alloc(int cvar_index, void *obj_handle, MPI_T_cvar_handle *handle, int *count)
+int MPI_T_cvar_handle_alloc(int cvar_index, void *obj_handle, MPI_T_cvar_handle * handle,
+                            int *count)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -30,21 +31,21 @@ int MPI_T_cvar_handle_alloc(int cvar_index, void *obj_handle, MPI_T_cvar_handle
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_cvar_handle_free.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_cvar_handle_free.html
index f310524d..ec2bd988 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_cvar_handle_free.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_cvar_handle_free.html
@@ -9,7 +9,7 @@
 Free an existing handle for a control variable 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_T_cvar_handle_free(MPI_T_cvar_handle *handle)
+int MPI_T_cvar_handle_free(MPI_T_cvar_handle * handle)
 </PRE>
 <H2>Input/Output Parameters</H2>
 <DL><DT><B>handle </B> <DD> handle to be freed (handle)
@@ -20,21 +20,21 @@ int MPI_T_cvar_handle_free(MPI_T_cvar_handle *handle)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_cvar_read.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_cvar_read.html
index 0706190d..9ca481f4 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_cvar_read.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_cvar_read.html
@@ -24,21 +24,21 @@ int MPI_T_cvar_read(MPI_T_cvar_handle handle, void *buf)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_cvar_write.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_cvar_write.html
index 20b53b33..6aedb23e 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_cvar_write.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_cvar_write.html
@@ -23,21 +23,21 @@ int MPI_T_cvar_write(MPI_T_cvar_handle handle, const void *buf)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_enum_get_info.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_enum_get_info.html
index f7f8b5e9..a6c94974 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_enum_get_info.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_enum_get_info.html
@@ -31,21 +31,21 @@ int MPI_T_enum_get_info(MPI_T_enum enumtype, int *num, char *name, int *name_len
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_enum_get_item.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_enum_get_item.html
index 4f23f910..76a20a75 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_enum_get_item.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_enum_get_item.html
@@ -33,21 +33,21 @@ int MPI_T_enum_get_item(MPI_T_enum enumtype, int index, int *value, char *name,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_finalize.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_finalize.html
index a8bb52e5..0306baa0 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_finalize.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_finalize.html
@@ -31,21 +31,21 @@ have called MPI_T_init_thread() and MPI_T_finalize() an equal number of times.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -54,7 +54,7 @@ possible.
 <DL><DT><B>MPI_T_ERR_NOT_INITIALIZED </B> <DD> The MPI tool information interface is not initialized.
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
 MPI_T_init_thread
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_init_thread.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_init_thread.html
index a1360fcd..b2aac0cb 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_init_thread.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_init_thread.html
@@ -40,28 +40,28 @@ made concurrently from two distinct threads (all MPI_T calls are serialized).
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
 MPI_T_finalize
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_get_index.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_get_index.html
index 7064f5ac..5c28b6d7 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_get_index.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_get_index.html
@@ -26,21 +26,21 @@ int MPI_T_pvar_get_index(const char *name, int var_class, int *pvar_index)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_get_info.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_get_info.html
index 088d5120..6cb56357 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_get_info.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_get_info.html
@@ -10,8 +10,8 @@ Get the inforamtion about a performance variable
 <H2>Synopsis</H2>
 <PRE>
 int MPI_T_pvar_get_info(int pvar_index, char *name, int *name_len, int *verbosity,
-    int *var_class, MPI_Datatype *datatype, MPI_T_enum *enumtype, char *desc,
-    int *desc_len, int *binding, int *readonly, int *continuous, int *atomic)
+                        int *var_class, MPI_Datatype * datatype, MPI_T_enum * enumtype, char *desc,
+                        int *desc_len, int *binding, int *readonly, int *continuous, int *atomic)
 </PRE>
 <H2>Input/Output Parameters</H2>
 <DL>
@@ -52,21 +52,21 @@ int MPI_T_pvar_get_info(int pvar_index, char *name, int *name_len, int *verbosit
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_get_num.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_get_num.html
index f2265991..12f329e4 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_get_num.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_get_num.html
@@ -20,21 +20,21 @@ int MPI_T_pvar_get_num(int *num_pvar)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_handle_alloc.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_handle_alloc.html
index da298bba..1bc31e01 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_handle_alloc.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_handle_alloc.html
@@ -10,7 +10,7 @@ Allocate a handle for a performance variable
 <H2>Synopsis</H2>
 <PRE>
 int MPI_T_pvar_handle_alloc(MPI_T_pvar_session session, int pvar_index,
-                            void *obj_handle, MPI_T_pvar_handle *handle, int *count)
+                            void *obj_handle, MPI_T_pvar_handle * handle, int *count)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -33,21 +33,21 @@ int MPI_T_pvar_handle_alloc(MPI_T_pvar_session session, int pvar_index,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_handle_free.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_handle_free.html
index b6c3f10d..e20cab1e 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_handle_free.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_handle_free.html
@@ -9,7 +9,7 @@
 Free an existing handle for a performance variable 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_T_pvar_handle_free(MPI_T_pvar_session session, MPI_T_pvar_handle *handle)
+int MPI_T_pvar_handle_free(MPI_T_pvar_session session, MPI_T_pvar_handle * handle)
 </PRE>
 <H2>Input/Output Parameters</H2>
 <DL>
@@ -23,21 +23,21 @@ int MPI_T_pvar_handle_free(MPI_T_pvar_session session, MPI_T_pvar_handle *handle
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_read.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_read.html
index 53953e06..9322f2ea 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_read.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_read.html
@@ -38,21 +38,21 @@ MPI_T_pvar_read().
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_readreset.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_readreset.html
index 264d0d89..7fdcfe8f 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_readreset.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_readreset.html
@@ -27,21 +27,21 @@ int MPI_T_pvar_readreset(MPI_T_pvar_session session, MPI_T_pvar_handle handle, v
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_reset.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_reset.html
index 3e13030b..6059d884 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_reset.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_reset.html
@@ -33,21 +33,21 @@ variables are ignored when MPI_T_PVAR_ALL_HANDLES is specified.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_session_create.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_session_create.html
index 6e432ce2..aa0633e2 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_session_create.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_session_create.html
@@ -9,7 +9,7 @@
 Create a new session for accessing performance variables 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_T_pvar_session_create(MPI_T_pvar_session *session)
+int MPI_T_pvar_session_create(MPI_T_pvar_session * session)
 </PRE>
 <H2>Output Parameters</H2>
 <DL><DT><B>session </B> <DD> identifier of performance session (handle)
@@ -20,21 +20,21 @@ int MPI_T_pvar_session_create(MPI_T_pvar_session *session)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_session_free.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_session_free.html
index 06cbe96b..e53a8410 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_session_free.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_session_free.html
@@ -9,7 +9,7 @@
 Free an existing performance variable session 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_T_pvar_session_free(MPI_T_pvar_session *session)
+int MPI_T_pvar_session_free(MPI_T_pvar_session * session)
 </PRE>
 <H2>Input/Output Parameters</H2>
 <DL><DT><B>session </B> <DD> identifier of performance experiment session (handle)
@@ -25,21 +25,21 @@ return, MPI sets the session identifier to MPI_T_PVAR_SESSION_NULL.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_start.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_start.html
index 43d2665a..b311e5b3 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_start.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_start.html
@@ -31,21 +31,21 @@ MPI_T_PVAR_ALL_HANDLES is specified.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_stop.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_stop.html
index 9778a99b..77f5e644 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_stop.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_stop.html
@@ -34,21 +34,21 @@ MPI_T_PVAR_ALL_HANDLES is specified.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_write.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_write.html
index c396f9e1..96ab9fd5 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_write.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_T_pvar_write.html
@@ -36,21 +36,21 @@ MPI_T_pvar_write().
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Test.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Test.html
index b5df58e5..61babaf8 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Test.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Test.html
@@ -9,17 +9,17 @@
 Tests for the completion of a request 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Test(MPI_Request *request, int *flag, MPI_Status *status)
+int MPI_Test(MPI_Request * request, int *flag, MPI_Status * status)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>request </B> <DD> MPI request (handle) 
+<DL><DT><B>request </B> <DD> MPI request (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
 <DL>
-<DT><B>flag </B><DD>true if operation completed (logical) 
+<DT><B>flag </B><DD>true if operation completed (logical)
 
-<DT><B>status </B><DD>status object (Status).  May be <tt>MPI_STATUS_IGNORE</tt>.
+<DT><B>status </B><DD>status object (Status).  May be <TT>MPI_STATUS_IGNORE</TT>.
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -27,61 +27,61 @@ int MPI_Test(MPI_Request *request, int *flag, MPI_Status *status)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes on the MPI_Status argument</H2>
 <P>
-The <tt>MPI_ERROR</tt> field of the status return is only set if
-the return from the MPI routine is <tt>MPI_ERR_IN_STATUS</tt>.  That error class
+The <TT>MPI_ERROR</TT> field of the status return is only set if
+the return from the MPI routine is <TT>MPI_ERR_IN_STATUS</TT>.  That error class
 is only returned by the routines that take an array of status arguments
-(<tt>MPI_Testall</tt>, <tt>MPI_Testsome</tt>, <tt>MPI_Waitall</tt>, and <tt>MPI_Waitsome</tt>).  In
-all other cases, the value of the <tt>MPI_ERROR</tt> field in the status is
+(<TT>MPI_Testall</TT>, <TT>MPI_Testsome</TT>, <TT>MPI_Waitall</TT>, and <TT>MPI_Waitsome</TT>).  In
+all other cases, the value of the <TT>MPI_ERROR</TT> field in the status is
 unchanged.  See section 3.2.5 in the MPI-1.1 specification for the
 exact text.
 <P>
-For send operations, the only use of status is for <tt>MPI_Test_cancelled</tt> or
+For send operations, the only use of status is for <TT>MPI_Test_cancelled</TT> or
 in the case that there is an error in one of the four routines that
-may return the error class <tt>MPI_ERR_IN_STATUS</tt>, in which case the
-<tt>MPI_ERROR</tt> field of status will be set.  In that case, the value
-will be set to <tt>MPI_SUCCESS</tt> for any send or receive operation that completed
-successfully, or <tt>MPI_ERR_PENDING</tt> for any operation which has neither
+may return the error class <TT>MPI_ERR_IN_STATUS</TT>, in which case the
+<TT>MPI_ERROR</TT> field of status will be set.  In that case, the value
+will be set to <TT>MPI_SUCCESS</TT> for any send or receive operation that completed
+successfully, or <TT>MPI_ERR_PENDING</TT> for any operation which has neither
 failed nor completed.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
-The <tt>status</tt> argument must be declared as an array of size <tt>MPI_STATUS_SIZE</tt>,
-as in <tt>integer status(MPI_STATUS_SIZE)</tt>.
+The <TT>status</TT> argument must be declared as an array of size <TT>MPI_STATUS_SIZE</TT>,
+as in <TT>integer status(MPI_STATUS_SIZE)</TT>.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
-<DL><DT><B>MPI_ERR_REQUEST </B> <DD> Invalid <tt>MPI_Request</tt>.  Either null or, in the case of a
-<tt>MPI_Start</tt> or <tt>MPI_Startall</tt>, not a persistent request.
+<DL><DT><B>MPI_ERR_REQUEST </B> <DD> Invalid <TT>MPI_Request</TT>.  Either null or, in the case of a
+<TT>MPI_Start</TT> or <TT>MPI_Startall</TT>, not a persistent request.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Test_cancelled.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Test_cancelled.html
index 027c28fd..4e04daaf 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Test_cancelled.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Test_cancelled.html
@@ -9,14 +9,14 @@
 Tests to see if a request was cancelled 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Test_cancelled(const MPI_Status *status, int *flag)
+int MPI_Test_cancelled(const MPI_Status * status, int *flag)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>status </B> <DD> status object (Status) 
+<DL><DT><B>status </B> <DD> status object (Status)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>flag </B> <DD> true if the request was cancelled, false otherwise (logical) 
+<DL><DT><B>flag </B> <DD> true if the request was cancelled, false otherwise (logical)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -24,37 +24,37 @@ int MPI_Test_cancelled(const MPI_Status *status, int *flag)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Testall.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Testall.html
index 81bb467b..a7f72ec1 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Testall.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Testall.html
@@ -9,38 +9,38 @@
 Tests for the completion of all previously initiated requests 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Testall(int count, MPI_Request array_of_requests[], int *flag, 
-               MPI_Status array_of_statuses[])
+int MPI_Testall(int count, MPI_Request array_of_requests[], int *flag,
+                MPI_Status array_of_statuses[])
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>count </B><DD>lists length (integer) 
+<DT><B>count </B><DD>lists length (integer)
 
-<DT><B>array_of_requests </B><DD>array of requests (array of handles) 
+<DT><B>array_of_requests </B><DD>array of requests (array of handles)
 </DL>
 <P>
 <H2>Output Parameters</H2>
 <DL>
-<DT><B>flag </B><DD>True if all requests have completed; false otherwise (logical) 
+<DT><B>flag </B><DD>True if all requests have completed; false otherwise (logical)
 
 <DT><B>array_of_statuses </B><DD>array of status objects (array of Status).  May be
-<tt>MPI_STATUSES_IGNORE</tt>.
+<TT>MPI_STATUSES_IGNORE</TT>.
 </DL>
 <P>
 <H2>Notes</H2>
-<tt>flag</tt> is true only if all requests have completed.  Otherwise, flag is
-false and neither the <tt>array_of_requests</tt> nor the <tt>array_of_statuses</tt> is
+<TT>flag</TT> is true only if all requests have completed.  Otherwise, flag is
+false and neither the <TT>array_of_requests</TT> nor the <TT>array_of_statuses</TT> is
 modified.
 <P>
-If one or more of the requests completes with an error, <tt>MPI_ERR_IN_STATUS</tt> is
-returned.  An error value will be present is elements of <tt>array_of_status
-</tt>associated with the requests.  Likewise, the <tt>MPI_ERROR</tt> field in the status
+If one or more of the requests completes with an error, <TT>MPI_ERR_IN_STATUS</TT> is
+returned.  An error value will be present is elements of <TT>array_of_status
+</TT>associated with the requests.  Likewise, the <TT>MPI_ERROR</TT> field in the status
 elements associated with requests that have successfully completed will be
-<tt>MPI_SUCCESS</tt>.  Finally, those requests that have not completed will have a
-value of <tt>MPI_ERR_PENDING</tt>.
+<TT>MPI_SUCCESS</TT>.  Finally, those requests that have not completed will have a
+value of <TT>MPI_ERR_PENDING</TT>.
 <P>
 While it is possible to list a request handle more than once in the
-<tt>array_of_requests</tt>, such an action is considered erroneous and may cause the
+<TT>array_of_requests</TT>, such an action is considered erroneous and may cause the
 program to unexecpectedly terminate or produce incorrect results.
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -48,77 +48,77 @@ program to unexecpectedly terminate or produce incorrect results.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes on the MPI_Status argument</H2>
 <P>
-The <tt>MPI_ERROR</tt> field of the status return is only set if
-the return from the MPI routine is <tt>MPI_ERR_IN_STATUS</tt>.  That error class
+The <TT>MPI_ERROR</TT> field of the status return is only set if
+the return from the MPI routine is <TT>MPI_ERR_IN_STATUS</TT>.  That error class
 is only returned by the routines that take an array of status arguments
-(<tt>MPI_Testall</tt>, <tt>MPI_Testsome</tt>, <tt>MPI_Waitall</tt>, and <tt>MPI_Waitsome</tt>).  In
-all other cases, the value of the <tt>MPI_ERROR</tt> field in the status is
+(<TT>MPI_Testall</TT>, <TT>MPI_Testsome</TT>, <TT>MPI_Waitall</TT>, and <TT>MPI_Waitsome</TT>).  In
+all other cases, the value of the <TT>MPI_ERROR</TT> field in the status is
 unchanged.  See section 3.2.5 in the MPI-1.1 specification for the
 exact text.
 <P>
-For send operations, the only use of status is for <tt>MPI_Test_cancelled</tt> or
+For send operations, the only use of status is for <TT>MPI_Test_cancelled</TT> or
 in the case that there is an error in one of the four routines that
-may return the error class <tt>MPI_ERR_IN_STATUS</tt>, in which case the
-<tt>MPI_ERROR</tt> field of status will be set.  In that case, the value
-will be set to <tt>MPI_SUCCESS</tt> for any send or receive operation that completed
-successfully, or <tt>MPI_ERR_PENDING</tt> for any operation which has neither
+may return the error class <TT>MPI_ERR_IN_STATUS</TT>, in which case the
+<TT>MPI_ERROR</TT> field of status will be set.  In that case, the value
+will be set to <TT>MPI_SUCCESS</TT> for any send or receive operation that completed
+successfully, or <TT>MPI_ERR_PENDING</TT> for any operation which has neither
 failed nor completed.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
-<DL><DT><B>MPI_ERR_IN_STATUS </B> <DD> The actual error value is in the <tt>MPI_Status</tt> argument.
+<DL><DT><B>MPI_ERR_IN_STATUS </B> <DD> The actual error value is in the <TT>MPI_Status</TT> argument.
 This error class is returned only from the multiple-completion routines
-(<tt>MPI_Testall</tt>, <tt>MPI_Testany</tt>, <tt>MPI_Testsome</tt>, <tt>MPI_Waitall</tt>, <tt>MPI_Waitany</tt>,
-and <tt>MPI_Waitsome</tt>).  The field <tt>MPI_ERROR</tt> in the status argument
-contains the error value or <tt>MPI_SUCCESS</tt> (no error and complete) or
-<tt>MPI_ERR_PENDING</tt> to indicate that the request has not completed.
+(<TT>MPI_Testall</TT>, <TT>MPI_Testany</TT>, <TT>MPI_Testsome</TT>, <TT>MPI_Waitall</TT>, <TT>MPI_Waitany</TT>,
+and <TT>MPI_Waitsome</TT>).  The field <TT>MPI_ERROR</TT> in the status argument
+contains the error value or <TT>MPI_SUCCESS</TT> (no error and complete) or
+<TT>MPI_ERR_PENDING</TT> to indicate that the request has not completed.
 </DL>
 The MPI Standard does not specify what the result of the multiple
 completion routines is when an error occurs.  For example, in an
-<tt>MPI_WAITALL</tt>, does the routine wait for all requests to either fail or
+<TT>MPI_WAITALL</TT>, does the routine wait for all requests to either fail or
 complete, or does it return immediately (with the MPI definition of
 immediately, which means independent of actions of other MPI processes)?
 MPICH has chosen to make the return immediate (alternately, local in MPI
-terms), and to use the error class <tt>MPI_ERR_PENDING</tt> (introduced in MPI 1.1)
+terms), and to use the error class <TT>MPI_ERR_PENDING</TT> (introduced in MPI 1.1)
 to indicate which requests have not completed.  In most cases, only
 one request with an error will be detected in each call to an MPI routine
 that tests multiple requests.  The requests that have not been processed
 (because an error occured in one of the requests) will have their
-<tt>MPI_ERROR</tt> field marked with <tt>MPI_ERR_PENDING</tt>.
-<DL><DT><B>MPI_ERR_REQUEST </B> <DD> Invalid <tt>MPI_Request</tt>.  Either null or, in the case of a
-<tt>MPI_Start</tt> or <tt>MPI_Startall</tt>, not a persistent request.
+<TT>MPI_ERROR</TT> field marked with <TT>MPI_ERR_PENDING</TT>.
+<DL><DT><B>MPI_ERR_REQUEST </B> <DD> Invalid <TT>MPI_Request</TT>.  Either null or, in the case of a
+<TT>MPI_Start</TT> or <TT>MPI_Startall</TT>, not a persistent request.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Testany.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Testany.html
index 143a6f87..3dd78294 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Testany.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Testany.html
@@ -6,33 +6,33 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Testany"><H1>MPI_Testany</H1></A>
-Tests for completion of any previdously initiated  requests 
+Tests for completion of any previdously initiated requests 
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Testany(int count, MPI_Request array_of_requests[], int *indx,
-               int *flag, MPI_Status *status)
+                int *flag, MPI_Status * status)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>count </B><DD>list length (integer) 
+<DT><B>count </B><DD>list length (integer)
 
-<DT><B>array_of_requests </B><DD>array of requests (array of handles) 
+<DT><B>array_of_requests </B><DD>array of requests (array of handles)
 </DL>
 <P>
 <H2>Output Parameters</H2>
 <DL>
-<DT><B>indx </B><DD>index of operation that completed, or <tt>MPI_UNDEFINED</tt>  if none
-completed (integer) 
+<DT><B>indx </B><DD>index of operation that completed, or <TT>MPI_UNDEFINED</TT>  if none
+completed (integer)
 
-<DT><B>flag </B><DD>true if one of the operations is complete (logical) 
+<DT><B>flag </B><DD>true if one of the operations is complete (logical)
 
-<DT><B>status </B><DD>status object (Status).  May be <tt>MPI_STATUS_IGNORE</tt>.
+<DT><B>status </B><DD>status object (Status).  May be <TT>MPI_STATUS_IGNORE</TT>.
 </DL>
 <P>
 <H2>Notes</H2>
 <P>
 While it is possible to list a request handle more than once in the
-<tt>array_of_requests</tt>, such an action is considered erroneous and may cause the
+<TT>array_of_requests</TT>, such an action is considered erroneous and may cause the
 program to unexecpectedly terminate or produce incorrect results.
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -40,49 +40,49 @@ program to unexecpectedly terminate or produce incorrect results.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes on the MPI_Status argument</H2>
 <P>
-The <tt>MPI_ERROR</tt> field of the status return is only set if
-the return from the MPI routine is <tt>MPI_ERR_IN_STATUS</tt>.  That error class
+The <TT>MPI_ERROR</TT> field of the status return is only set if
+the return from the MPI routine is <TT>MPI_ERR_IN_STATUS</TT>.  That error class
 is only returned by the routines that take an array of status arguments
-(<tt>MPI_Testall</tt>, <tt>MPI_Testsome</tt>, <tt>MPI_Waitall</tt>, and <tt>MPI_Waitsome</tt>).  In
-all other cases, the value of the <tt>MPI_ERROR</tt> field in the status is
+(<TT>MPI_Testall</TT>, <TT>MPI_Testsome</TT>, <TT>MPI_Waitall</TT>, and <TT>MPI_Waitsome</TT>).  In
+all other cases, the value of the <TT>MPI_ERROR</TT> field in the status is
 unchanged.  See section 3.2.5 in the MPI-1.1 specification for the
 exact text.
 <P>
-For send operations, the only use of status is for <tt>MPI_Test_cancelled</tt> or
+For send operations, the only use of status is for <TT>MPI_Test_cancelled</TT> or
 in the case that there is an error in one of the four routines that
-may return the error class <tt>MPI_ERR_IN_STATUS</tt>, in which case the
-<tt>MPI_ERROR</tt> field of status will be set.  In that case, the value
-will be set to <tt>MPI_SUCCESS</tt> for any send or receive operation that completed
-successfully, or <tt>MPI_ERR_PENDING</tt> for any operation which has neither
+may return the error class <TT>MPI_ERR_IN_STATUS</TT>, in which case the
+<TT>MPI_ERROR</TT> field of status will be set.  In that case, the value
+will be set to <TT>MPI_SUCCESS</TT> for any send or receive operation that completed
+successfully, or <TT>MPI_ERR_PENDING</TT> for any operation which has neither
 failed nor completed.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Testsome.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Testsome.html
index 6f4ad28e..37a93eca 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Testsome.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Testsome.html
@@ -9,31 +9,31 @@
 Tests for some given requests to complete 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Testsome(int incount, MPI_Request array_of_requests[], int *outcount, 
-                int array_of_indices[], MPI_Status array_of_statuses[])
+int MPI_Testsome(int incount, MPI_Request array_of_requests[], int *outcount,
+                 int array_of_indices[], MPI_Status array_of_statuses[])
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>incount </B><DD>length of array_of_requests (integer) 
+<DT><B>incount </B><DD>length of array_of_requests (integer)
 
-<DT><B>array_of_requests </B><DD>array of requests (array of handles) 
+<DT><B>array_of_requests </B><DD>array of requests (array of handles)
 </DL>
 <P>
 <H2>Output Parameters</H2>
 <DL>
-<DT><B>outcount </B><DD>number of completed requests (integer) 
+<DT><B>outcount </B><DD>number of completed requests (integer)
 
-<DT><B>array_of_indices </B><DD>array of indices of operations that 
-completed (array of integers) 
+<DT><B>array_of_indices </B><DD>array of indices of operations that
+completed (array of integers)
 
-<DT><B>array_of_statuses </B><DD>array of status objects for 
-operations that completed (array of Status).  May be <tt>MPI_STATUSES_IGNORE</tt>.
+<DT><B>array_of_statuses </B><DD>array of status objects for
+operations that completed (array of Status).  May be <TT>MPI_STATUSES_IGNORE</TT>.
 </DL>
 <P>
 <H2>Notes</H2>
 <P>
 While it is possible to list a request handle more than once in the
-<tt>array_of_requests</tt>, such an action is considered erroneous and may cause the
+<TT>array_of_requests</TT>, such an action is considered erroneous and may cause the
 program to unexecpectedly terminate or produce incorrect results.
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -41,72 +41,72 @@ program to unexecpectedly terminate or produce incorrect results.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes on the MPI_Status argument</H2>
 <P>
-The <tt>MPI_ERROR</tt> field of the status return is only set if
-the return from the MPI routine is <tt>MPI_ERR_IN_STATUS</tt>.  That error class
+The <TT>MPI_ERROR</TT> field of the status return is only set if
+the return from the MPI routine is <TT>MPI_ERR_IN_STATUS</TT>.  That error class
 is only returned by the routines that take an array of status arguments
-(<tt>MPI_Testall</tt>, <tt>MPI_Testsome</tt>, <tt>MPI_Waitall</tt>, and <tt>MPI_Waitsome</tt>).  In
-all other cases, the value of the <tt>MPI_ERROR</tt> field in the status is
+(<TT>MPI_Testall</TT>, <TT>MPI_Testsome</TT>, <TT>MPI_Waitall</TT>, and <TT>MPI_Waitsome</TT>).  In
+all other cases, the value of the <TT>MPI_ERROR</TT> field in the status is
 unchanged.  See section 3.2.5 in the MPI-1.1 specification for the
 exact text.
 <P>
-For send operations, the only use of status is for <tt>MPI_Test_cancelled</tt> or
+For send operations, the only use of status is for <TT>MPI_Test_cancelled</TT> or
 in the case that there is an error in one of the four routines that
-may return the error class <tt>MPI_ERR_IN_STATUS</tt>, in which case the
-<tt>MPI_ERROR</tt> field of status will be set.  In that case, the value
-will be set to <tt>MPI_SUCCESS</tt> for any send or receive operation that completed
-successfully, or <tt>MPI_ERR_PENDING</tt> for any operation which has neither
+may return the error class <TT>MPI_ERR_IN_STATUS</TT>, in which case the
+<TT>MPI_ERROR</TT> field of status will be set.  In that case, the value
+will be set to <TT>MPI_SUCCESS</TT> for any send or receive operation that completed
+successfully, or <TT>MPI_ERR_PENDING</TT> for any operation which has neither
 failed nor completed.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
-<DL><DT><B>MPI_ERR_IN_STATUS </B> <DD> The actual error value is in the <tt>MPI_Status</tt> argument.
+<DL><DT><B>MPI_ERR_IN_STATUS </B> <DD> The actual error value is in the <TT>MPI_Status</TT> argument.
 This error class is returned only from the multiple-completion routines
-(<tt>MPI_Testall</tt>, <tt>MPI_Testany</tt>, <tt>MPI_Testsome</tt>, <tt>MPI_Waitall</tt>, <tt>MPI_Waitany</tt>,
-and <tt>MPI_Waitsome</tt>).  The field <tt>MPI_ERROR</tt> in the status argument
-contains the error value or <tt>MPI_SUCCESS</tt> (no error and complete) or
-<tt>MPI_ERR_PENDING</tt> to indicate that the request has not completed.
+(<TT>MPI_Testall</TT>, <TT>MPI_Testany</TT>, <TT>MPI_Testsome</TT>, <TT>MPI_Waitall</TT>, <TT>MPI_Waitany</TT>,
+and <TT>MPI_Waitsome</TT>).  The field <TT>MPI_ERROR</TT> in the status argument
+contains the error value or <TT>MPI_SUCCESS</TT> (no error and complete) or
+<TT>MPI_ERR_PENDING</TT> to indicate that the request has not completed.
 </DL>
 The MPI Standard does not specify what the result of the multiple
 completion routines is when an error occurs.  For example, in an
-<tt>MPI_WAITALL</tt>, does the routine wait for all requests to either fail or
+<TT>MPI_WAITALL</TT>, does the routine wait for all requests to either fail or
 complete, or does it return immediately (with the MPI definition of
 immediately, which means independent of actions of other MPI processes)?
 MPICH has chosen to make the return immediate (alternately, local in MPI
-terms), and to use the error class <tt>MPI_ERR_PENDING</tt> (introduced in MPI 1.1)
+terms), and to use the error class <TT>MPI_ERR_PENDING</TT> (introduced in MPI 1.1)
 to indicate which requests have not completed.  In most cases, only
 one request with an error will be detected in each call to an MPI routine
 that tests multiple requests.  The requests that have not been processed
 (because an error occured in one of the requests) will have their
-<tt>MPI_ERROR</tt> field marked with <tt>MPI_ERR_PENDING</tt>.
+<TT>MPI_ERROR</TT> field marked with <TT>MPI_ERR_PENDING</TT>.
 <P>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Topo_test.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Topo_test.html
index d372b81a..4ce1ec02 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Topo_test.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Topo_test.html
@@ -6,18 +6,18 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Topo_test"><H1>MPI_Topo_test</H1></A>
-Determines the type of topology (if any) associated with a  communicator 
+Determines the type of topology (if any) associated with a communicator 
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Topo_test(MPI_Comm comm, int *status)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>comm </B> <DD> communicator (handle) 
+<DL><DT><B>comm </B> <DD> communicator (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>status </B> <DD> topology type of communicator <tt>comm</tt> (integer).  If the
-communicator has no associated topology, returns <tt>MPI_UNDEFINED</tt>.
+<DL><DT><B>status </B> <DD> topology type of communicator <TT>comm</TT> (integer).  If the
+communicator has no associated topology, returns <TT>MPI_UNDEFINED</TT>.
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -27,40 +27,40 @@ This means that this routine may safely be used by multiple threads and
 from within a signal handler.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Graph_create, MPI_Cart_create
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_commit.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_commit.html
index 484e8f5f..02565c01 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_commit.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_commit.html
@@ -9,10 +9,10 @@
 Commits the datatype 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Type_commit(MPI_Datatype *datatype)
+int MPI_Type_commit(MPI_Datatype * datatype)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>datatype </B> <DD> datatype (handle) 
+<DL><DT><B>datatype </B> <DD> datatype (handle)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -20,38 +20,38 @@ int MPI_Type_commit(MPI_Datatype *datatype)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_contiguous.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_contiguous.html
index 227f7a43..dbfdddb0 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_contiguous.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_contiguous.html
@@ -9,19 +9,17 @@
 Creates a contiguous datatype 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Type_contiguous(int count,
-                      MPI_Datatype oldtype,
-                      MPI_Datatype *newtype)
+int MPI_Type_contiguous(int count, MPI_Datatype oldtype, MPI_Datatype * newtype)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>count </B><DD>replication count (nonnegative integer) 
+<DT><B>count </B><DD>replication count (nonnegative integer)
 
-<DT><B>oldtype </B><DD>old datatype (handle) 
+<DT><B>oldtype </B><DD>old datatype (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>newtype </B> <DD> new datatype (handle) 
+<DL><DT><B>newtype </B> <DD> new datatype (handle)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -29,38 +27,38 @@ int MPI_Type_contiguous(int count,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_darray.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_darray.html
index 5eb28768..14f07ce7 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_darray.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_darray.html
@@ -10,15 +10,13 @@ Create a datatype representing a distributed array
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Type_create_darray(int size,
-                         int rank,
-                         int ndims,
-                         const int array_of_gsizes[],
-                         const int array_of_distribs[],
-                         const int array_of_dargs[],
-                         const int array_of_psizes[],
-                         int order,
-                         MPI_Datatype oldtype,
-                         MPI_Datatype *newtype)
+                           int rank,
+                           int ndims,
+                           const int array_of_gsizes[],
+                           const int array_of_distribs[],
+                           const int array_of_dargs[],
+                           const int array_of_psizes[],
+                           int order, MPI_Datatype oldtype, MPI_Datatype * newtype)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -50,41 +48,41 @@ int MPI_Type_create_darray(int size,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_hindexed.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_hindexed.html
index 31538f73..8b1c559e 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_hindexed.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_hindexed.html
@@ -10,10 +10,9 @@ Create a datatype for an indexed datatype with displacements in bytes
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Type_create_hindexed(int count,
-                           const int array_of_blocklengths[],
-                           const MPI_Aint array_of_displacements[],
-                           MPI_Datatype oldtype,
-                           MPI_Datatype *newtype)
+                             const int array_of_blocklengths[],
+                             const MPI_Aint array_of_displacements[],
+                             MPI_Datatype oldtype, MPI_Datatype * newtype)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -36,41 +35,41 @@ array_of_displacements and array_of_blocklengths (integer)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_hindexed_block.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_hindexed_block.html
index c7b8bc27..8e2643a5 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_hindexed_block.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_hindexed_block.html
@@ -10,9 +10,9 @@ Create an hindexed datatype with constant-sized blocks
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Type_create_hindexed_block(int count,
-                                    int blocklength,
-                                    const MPI_Aint array_of_displacements[],
-                                    MPI_Datatype oldtype, MPI_Datatype * newtype)
+                                   int blocklength,
+                                   const MPI_Aint array_of_displacements[],
+                                   MPI_Datatype oldtype, MPI_Datatype * newtype)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -34,41 +34,41 @@ int MPI_Type_create_hindexed_block(int count,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_hvector.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_hvector.html
index e9c7d778..3ad00f9e 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_hvector.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_hvector.html
@@ -10,10 +10,8 @@ Create a datatype with a constant stride given in bytes
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Type_create_hvector(int count,
-                          int blocklength,
-                          MPI_Aint stride,
-                          MPI_Datatype oldtype,
-                          MPI_Datatype *newtype)
+                            int blocklength,
+                            MPI_Aint stride, MPI_Datatype oldtype, MPI_Datatype * newtype)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -35,41 +33,41 @@ int MPI_Type_create_hvector(int count,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_indexed_block.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_indexed_block.html
index 32772e3a..31547561 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_indexed_block.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_indexed_block.html
@@ -10,24 +10,23 @@ Create an indexed datatype with constant-sized blocks
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Type_create_indexed_block(int count,
-                               int blocklength,
-                               const int array_of_displacements[],
-                               MPI_Datatype oldtype,
-                               MPI_Datatype *newtype)
+                                  int blocklength,
+                                  const int array_of_displacements[],
+                                  MPI_Datatype oldtype, MPI_Datatype * newtype)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>count </B><DD>length of array of displacements (integer) 
+<DT><B>count </B><DD>length of array of displacements (integer)
 
-<DT><B>blocklength </B><DD>size of block (integer) 
+<DT><B>blocklength </B><DD>size of block (integer)
 
-<DT><B>array_of_displacements </B><DD>array of displacements (array of integer) 
+<DT><B>array_of_displacements </B><DD>array of displacements (array of integer)
 
-<DT><B>oldtype </B><DD>old datatype (handle) 
+<DT><B>oldtype </B><DD>old datatype (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>newtype </B> <DD> new datatype (handle) 
+<DL><DT><B>newtype </B> <DD> new datatype (handle)
 </DL>
 <P>
 <H2>Notes</H2>
@@ -44,7 +43,7 @@ is to do something like the following
 </PRE>
 
 expecting this to send "a(1),a(11),..." because the indices have values
-"1,11,...".   Because these are <em>displacements</em> from the beginning of "a",
+"1,11,...".   Because these are <EM>displacements</EM> from the beginning of "a",
 it actually sends "a(1+1),a(1+11),...".
 <P>
 If you wish to consider the displacements as indices into a Fortran array,
@@ -59,41 +58,41 @@ consider declaring the Fortran array with a zero origin
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_keyval.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_keyval.html
index 76f25ae8..fcabeae1 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_keyval.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_keyval.html
@@ -9,21 +9,21 @@
 Create an attribute keyval for MPI datatypes 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Type_create_keyval(MPI_Type_copy_attr_function *type_copy_attr_fn, 
-                         MPI_Type_delete_attr_function *type_delete_attr_fn,
-                         int *type_keyval, void *extra_state)
+int MPI_Type_create_keyval(MPI_Type_copy_attr_function * type_copy_attr_fn,
+                           MPI_Type_delete_attr_function * type_delete_attr_fn,
+                           int *type_keyval, void *extra_state)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>type_copy_attr_fn </B><DD>copy callback function for type_keyval (function) 
+<DT><B>type_copy_attr_fn </B><DD>copy callback function for type_keyval (function)
 
-<DT><B>type_delete_attr_fn </B><DD>delete callback function for type_keyval (function) 
+<DT><B>type_delete_attr_fn </B><DD>delete callback function for type_keyval (function)
 
-<DT><B>extra_state </B><DD>extra state for callback functions 
+<DT><B>extra_state </B><DD>extra state for callback functions
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>type_keyval </B> <DD> key value for future access (integer) 
+<DL><DT><B>type_keyval </B> <DD> key value for future access (integer)
 </DL>
 <P>
 <H2>Notes</H2>
@@ -40,9 +40,9 @@ Default copy and delete functions are available.  These are
 <P>
 <H2>Return value from attribute callbacks</H2>
 The MPI-2 versions of the attribute callbacks should return either
-<tt>MPI_SUCCESS</tt> on success or a valid MPI error code or class on failure.
+<TT>MPI_SUCCESS</TT> on success or a valid MPI error code or class on failure.
 The MPI standard is ambiguous on this point, but as MPI-2 provides
-the routines <tt>MPI_Add_error_class</tt> and <tt>MPI_Add_error_code</tt> that allow the
+the routines <TT>MPI_Add_error_class</TT> and <TT>MPI_Add_error_code</TT> that allow the
 user to define and use MPI error codes and classes.
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -50,37 +50,37 @@ user to define and use MPI error codes and classes.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_resized.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_resized.html
index b35a0029..37ec2234 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_resized.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_resized.html
@@ -10,9 +10,7 @@ Create a datatype with a new lower bound and extent from an existing datatype
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Type_create_resized(MPI_Datatype oldtype,
-                          MPI_Aint lb,
-                          MPI_Aint extent,
-                          MPI_Datatype *newtype)
+                            MPI_Aint lb, MPI_Aint extent, MPI_Datatype * newtype)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -32,38 +30,38 @@ int MPI_Type_create_resized(MPI_Datatype oldtype,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_struct.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_struct.html
index 58b3f5ca..0fc0495a 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_struct.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_struct.html
@@ -10,10 +10,9 @@ Create an MPI datatype from a general set of datatypes, displacements, and block
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Type_create_struct(int count,
-                         const int array_of_blocklengths[],
-                         const MPI_Aint array_of_displacements[],
-                         const MPI_Datatype array_of_types[],
-                         MPI_Datatype *newtype)
+                           const int array_of_blocklengths[],
+                           const MPI_Aint array_of_displacements[],
+                           const MPI_Datatype array_of_types[], MPI_Datatype * newtype)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -37,41 +36,41 @@ datatype objects)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_subarray.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_subarray.html
index 13ce182b..532a181a 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_subarray.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_create_subarray.html
@@ -10,12 +10,10 @@ Create a datatype for a subarray of a regular, multidimensional array
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Type_create_subarray(int ndims,
-                           const int array_of_sizes[],
-                           const int array_of_subsizes[],
-                           const int array_of_starts[],
-                           int order,
-                           MPI_Datatype oldtype,
-                           MPI_Datatype *newtype)
+                             const int array_of_sizes[],
+                             const int array_of_subsizes[],
+                             const int array_of_starts[],
+                             int order, MPI_Datatype oldtype, MPI_Datatype * newtype)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -44,41 +42,41 @@ the subarray (array of positive integers)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_delete_attr.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_delete_attr.html
index 6c653f9f..b3188cee 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_delete_attr.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_delete_attr.html
@@ -6,7 +6,7 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Type_delete_attr"><H1>MPI_Type_delete_attr</H1></A>
-Deletes an attribute value associated with a key on  a datatype 
+Deletes an attribute value associated with a key on a datatype 
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Type_delete_attr(MPI_Datatype datatype, int type_keyval)
@@ -15,7 +15,7 @@ int MPI_Type_delete_attr(MPI_Datatype datatype, int type_keyval)
 <DL>
 <DT><B>datatype </B><DD>MPI datatype to which attribute is attached (handle)
 
-<DT><B>type_keyval </B><DD>The key value of the deleted attribute (integer) 
+<DT><B>type_keyval </B><DD>The key value of the deleted attribute (integer)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -23,37 +23,37 @@ int MPI_Type_delete_attr(MPI_Datatype datatype, int type_keyval)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 <DL><DT><B>MPI_ERR_KEYVAL </B> <DD> Invalid keyval
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_dup.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_dup.html
index 286b703e..85925be3 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_dup.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_dup.html
@@ -9,14 +9,18 @@
 Duplicate a datatype 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Type_dup(MPI_Datatype oldtype, MPI_Datatype *newtype)
+#undef FUNCNAME
+#define FUNCNAME MPI_Type_dup
+#undef FCNAME
+#define FCNAME MPL_QUOTE(FUNCNAME)
+int MPI_Type_dup(MPI_Datatype oldtype, MPI_Datatype * newtype)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>oldtype </B> <DD> datatype (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>newtype </B> <DD> copy of type (handle) 
+<DL><DT><B>newtype </B> <DD> copy of type (handle)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -24,38 +28,38 @@ int MPI_Type_dup(MPI_Datatype oldtype, MPI_Datatype *newtype)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_extent.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_extent.html
index cb3ad0b9..ad0797fd 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_extent.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_extent.html
@@ -9,7 +9,7 @@
 Returns the extent of a datatype 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Type_extent(MPI_Datatype datatype, MPI_Aint *extent)
+int MPI_Type_extent(MPI_Datatype datatype, MPI_Aint * extent)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>datatype </B> <DD> datatype (handle)
@@ -30,37 +30,37 @@ The MPI-2 standard deprecated a number of routines because MPI-2 provides
 better versions.  This routine is one of those that was deprecated.  The
 routine may continue to be used, but new code should use the replacement
 routine.
-The replacement for this routine is <tt>MPI_Type_get_extent</tt>.
+The replacement for this routine is <TT>MPI_Type_get_extent</TT>.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_free.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_free.html
index b7a0b877..6431f2d1 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_free.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_free.html
@@ -9,20 +9,20 @@
 Frees the datatype 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Type_free(MPI_Datatype *datatype)
+int MPI_Type_free(MPI_Datatype * datatype)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>datatype </B> <DD> datatype that is freed (handle) 
+<DL><DT><B>datatype </B> <DD> datatype that is freed (handle)
 </DL>
 <P>
 <H2>Predefined types</H2>
 <P>
 The MPI standard states that (in Opaque Objects)
-<blockquote>
+<BLOCKQUOTE>
 <P>
 MPI provides certain predefined opaque objects and predefined, static handles
 to these objects. Such objects may not be destroyed.
-</blockquote>
+</BLOCKQUOTE>
 <P>
 <P>
 Thus, it is an error to free a predefined datatype.  The same section makes
@@ -33,41 +33,41 @@ it clear that it is an error to free a null datatype.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_free_keyval.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_free_keyval.html
index 41e5330f..d6d85226 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_free_keyval.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_free_keyval.html
@@ -20,37 +20,37 @@ int MPI_Type_free_keyval(int *type_keyval)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 <DL><DT><B>MPI_ERR_KEYVAL </B> <DD> Invalid keyval
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_get_attr.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_get_attr.html
index 0d6de9ab..aab32c65 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_get_attr.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_get_attr.html
@@ -9,30 +9,29 @@
 Retrieves attribute value by key 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Type_get_attr(MPI_Datatype datatype, int type_keyval, void *attribute_val,
-                     int *flag)
+int MPI_Type_get_attr(MPI_Datatype datatype, int type_keyval, void *attribute_val, int *flag)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
 <DT><B>datatype </B><DD>datatype to which the attribute is attached (handle)
 
-<DT><B>type_keyval </B><DD>key value (integer) 
+<DT><B>type_keyval </B><DD>key value (integer)
 </DL>
 <P>
 <H2>Output Parameters</H2>
 <DL>
-<DT><B>attribute_val </B><DD>attribute value, unless flag = false 
+<DT><B>attribute_val </B><DD>attribute value, unless flag = false
 
-<DT><B>flag </B><DD>false if no attribute is associated with the key (logical) 
+<DT><B>flag </B><DD>false if no attribute is associated with the key (logical)
 </DL>
 <P>
 <H2>Notes</H2>
 Attributes must be extracted from the same language as they were inserted
-in with <tt>MPI_Type_set_attr</tt>.  The notes for C and Fortran below explain
+in with <TT>MPI_Type_set_attr</TT>.  The notes for C and Fortran below explain
 why.
 <P>
 <H2>Notes for C</H2>
-Even though the <tt>attr_value</tt> argument is declared as <tt>void *</tt>, it is
+Even though the <TT>attr_value</TT> argument is declared as <TT>void *</TT>, it is
 really the address of a void pointer.  See the rationale in the
 standard for more details.
 <P>
@@ -41,31 +40,31 @@ standard for more details.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -74,6 +73,6 @@ possible.
 <DL><DT><B>MPI_ERR_KEYVAL </B> <DD> Invalid keyval
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_get_contents.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_get_contents.html
index bdb99c86..44cb205a 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_get_contents.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_get_contents.html
@@ -10,12 +10,11 @@ get type contents
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Type_get_contents(MPI_Datatype datatype,
-                        int max_integers,
-                        int max_addresses,
-                        int max_datatypes,
-                        int array_of_integers[],
-                        MPI_Aint array_of_addresses[],
-                        MPI_Datatype array_of_datatypes[])
+                          int max_integers,
+                          int max_addresses,
+                          int max_datatypes,
+                          int array_of_integers[],
+                          MPI_Aint array_of_addresses[], MPI_Datatype array_of_datatypes[])
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -40,27 +39,27 @@ int MPI_Type_get_contents(MPI_Datatype datatype,
 <H2>Notes</H2>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_get_envelope.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_get_envelope.html
index 3310e6a2..43d01384 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_get_envelope.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_get_envelope.html
@@ -10,10 +10,7 @@ get type envelope
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Type_get_envelope(MPI_Datatype datatype,
-                        int *num_integers,
-                        int *num_addresses,
-                        int *num_datatypes,
-                        int *combiner)
+                          int *num_integers, int *num_addresses, int *num_datatypes, int *combiner)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>datatype </B> <DD> datatype to access (handle)
@@ -33,27 +30,27 @@ int MPI_Type_get_envelope(MPI_Datatype datatype,
 <H2>Notes</H2>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_get_extent.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_get_extent.html
index 7dedf0b3..c7076bc4 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_get_extent.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_get_extent.html
@@ -9,7 +9,7 @@
 Get the lower bound and extent for a Datatype 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Type_get_extent(MPI_Datatype datatype, MPI_Aint *lb, MPI_Aint *extent)
+int MPI_Type_get_extent(MPI_Datatype datatype, MPI_Aint * lb, MPI_Aint * extent)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>datatype </B> <DD> datatype to get information on (handle)
@@ -29,37 +29,37 @@ This means that this routine may safely be used by multiple threads and
 from within a signal handler.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_get_extent_x.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_get_extent_x.html
index 811795ce..2e8ec6eb 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_get_extent_x.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_get_extent_x.html
@@ -9,7 +9,7 @@
 Get the lower bound and extent as MPI_Count values for a Datatype 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Type_get_extent_x(MPI_Datatype datatype, MPI_Count *lb, MPI_Count *extent)
+int MPI_Type_get_extent_x(MPI_Datatype datatype, MPI_Count * lb, MPI_Count * extent)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>datatype </B> <DD> datatype (handle)
@@ -27,31 +27,31 @@ int MPI_Type_get_extent_x(MPI_Datatype datatype, MPI_Count *lb, MPI_Count *exten
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_get_name.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_get_name.html
index a21c4897..05bf0f85 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_get_name.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_get_name.html
@@ -33,7 +33,7 @@ with this routine.
 The MPI standard defined a thread-safe interface but this does not
 mean that all routines may be called without any thread locks.  For
 example, two threads must not attempt to change the contents of the
-same <tt>MPI_Info</tt> object concurrently.  The user is responsible in this
+same <TT>MPI_Info</TT> object concurrently.  The user is responsible in this
 case for using some mechanism, such as thread locks, to ensure that
 only one thread at a time makes use of this routine.
 <P>
@@ -52,37 +52,37 @@ disallows freeing a null communicator.  The text from the standard is:
 
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_get_true_extent.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_get_true_extent.html
index fec9a99a..03924893 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_get_true_extent.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_get_true_extent.html
@@ -9,8 +9,7 @@
 Get the true lower bound and extent for a datatype 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Type_get_true_extent(MPI_Datatype datatype, MPI_Aint *true_lb,
-                           MPI_Aint *true_extent)
+int MPI_Type_get_true_extent(MPI_Datatype datatype, MPI_Aint * true_lb, MPI_Aint * true_extent)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>datatype </B> <DD> datatype to get information on (handle)
@@ -30,37 +29,37 @@ This means that this routine may safely be used by multiple threads and
 from within a signal handler.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_get_true_extent_x.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_get_true_extent_x.html
index 48d5d330..164c70c5 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_get_true_extent_x.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_get_true_extent_x.html
@@ -9,7 +9,7 @@
 Get the true lower bound and extent as MPI_Count values for a datatype 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Type_get_true_extent_x(MPI_Datatype datatype, MPI_Count *true_lb, MPI_Count *true_extent)
+int MPI_Type_get_true_extent_x(MPI_Datatype datatype, MPI_Count * true_lb, MPI_Count * true_extent)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>datatype </B> <DD> datatype (handle)
@@ -27,31 +27,31 @@ int MPI_Type_get_true_extent_x(MPI_Datatype datatype, MPI_Count *true_lb, MPI_Co
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_hindexed.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_hindexed.html
index 0a5b4a7f..058de804 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_hindexed.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_hindexed.html
@@ -10,10 +10,9 @@ Creates an indexed datatype with offsets in bytes
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Type_hindexed(int count,
-                     int *array_of_blocklengths,
-                     MPI_Aint *array_of_displacements,
-                     MPI_Datatype oldtype,
-                     MPI_Datatype *newtype)
+                      int *array_of_blocklengths,
+                      MPI_Aint * array_of_displacements,
+                      MPI_Datatype oldtype, MPI_Datatype * newtype)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -27,7 +26,7 @@ int MPI_Type_hindexed(int count,
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>newtype </B> <DD> new datatype (handle) 
+<DL><DT><B>newtype </B> <DD> new datatype (handle)
 </DL>
 <P>
 <H2>Deprecated Function</H2>
@@ -35,25 +34,25 @@ The MPI-2 standard deprecated a number of routines because MPI-2 provides
 better versions.  This routine is one of those that was deprecated.  The
 routine may continue to be used, but new code should use the replacement
 routine.
-This routine is replaced by <tt>MPI_Type_create_hindexed</tt>.
+This routine is replaced by <TT>MPI_Type_create_hindexed</TT>.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 The array_of_displacements are displacements, and are based on a zero origin.  A common error
 is to do something like to following
@@ -69,7 +68,7 @@ is to do something like to following
 </PRE>
 
 expecting this to send "a(1),a(11),..." because the array_of_displacements have values
-"1,11,...".   Because these are <em>displacements</em> from the beginning of "a",
+"1,11,...".   Because these are <EM>displacements</EM> from the beginning of "a",
 it actually sends "a(1+1),a(1+11),...".
 <P>
 If you wish to consider the displacements as array_of_displacements into a Fortran array,
@@ -81,23 +80,23 @@ consider declaring the Fortran array with a zero origin
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
@@ -107,6 +106,6 @@ non-negative; a count of zero is often valid.
 implementation is unable to acquire memory.  
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_hvector.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_hvector.html
index 3493b256..f5a99661 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_hvector.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_hvector.html
@@ -10,21 +10,18 @@ type_hvector
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Type_hvector(int count,
-                    int blocklength,
-                    MPI_Aint stride,
-                    MPI_Datatype oldtype,
-                    MPI_Datatype *newtype)
+                     int blocklength, MPI_Aint stride, MPI_Datatype oldtype, MPI_Datatype * newtype)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>count </B><DD>number of blocks (nonnegative integer) 
+<DT><B>count </B><DD>number of blocks (nonnegative integer)
 
-<DT><B>blocklength </B><DD>number of elements in each block 
+<DT><B>blocklength </B><DD>number of elements in each block
 (nonnegative integer)
 
-<DT><B>stride </B><DD>number of bytes between start of each block (integer) 
+<DT><B>stride </B><DD>number of bytes between start of each block (integer)
 
-<DT><B>oldtype </B><DD>old datatype (handle) 
+<DT><B>oldtype </B><DD>old datatype (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
@@ -34,27 +31,27 @@ int MPI_Type_hvector(int count,
 <H2>Notes</H2>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_indexed.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_indexed.html
index 3a78da84..a54e504a 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_indexed.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_indexed.html
@@ -10,10 +10,9 @@ Creates an indexed datatype
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Type_indexed(int count,
-                    const int *array_of_blocklengths,
-                    const int *array_of_displacements,
-                    MPI_Datatype oldtype,
-                    MPI_Datatype *newtype)
+                     const int *array_of_blocklengths,
+                     const int *array_of_displacements,
+                     MPI_Datatype oldtype, MPI_Datatype * newtype)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -28,7 +27,7 @@ integers)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>newtype </B> <DD> new datatype (handle) 
+<DL><DT><B>newtype </B> <DD> new datatype (handle)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -36,18 +35,18 @@ integers)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 The array_of_displacements are displacements, and are based on a zero origin.  A common error
 is to do something like to following
@@ -63,7 +62,7 @@ is to do something like to following
 </PRE>
 
 expecting this to send "a(1),a(11),..." because the array_of_displacements have values
-"1,11,...".   Because these are <em>displacements</em> from the beginning of "a",
+"1,11,...".   Because these are <EM>displacements</EM> from the beginning of "a",
 it actually sends "a(1+1),a(1+11),...".
 <P>
 If you wish to consider the displacements as array_of_displacements into a Fortran array,
@@ -75,16 +74,16 @@ consider declaring the Fortran array with a zero origin
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -92,11 +91,11 @@ possible.
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_INTERN </B> <DD> This error is returned when some part of the MPICH 
 implementation is unable to acquire memory.  
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_lb.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_lb.html
index 47330d72..a1b8af68 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_lb.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_lb.html
@@ -9,7 +9,7 @@
 Returns the lower-bound of a datatype 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Type_lb(MPI_Datatype datatype, MPI_Aint *displacement)
+int MPI_Type_lb(MPI_Datatype datatype, MPI_Aint * displacement)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>datatype </B> <DD> datatype (handle)
@@ -25,7 +25,7 @@ The MPI-2 standard deprecated a number of routines because MPI-2 provides
 better versions.  This routine is one of those that was deprecated.  The
 routine may continue to be used, but new code should use the replacement
 routine.
-The replacement for this routine is <tt>MPI_Type_Get_extent</tt>.
+The replacement for this routine is <TT>MPI_Type_Get_extent</TT>.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
@@ -34,37 +34,37 @@ This means that this routine may safely be used by multiple threads and
 from within a signal handler.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_match_size.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_match_size.html
index b9aa6639..02c25e7e 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_match_size.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_match_size.html
@@ -9,13 +9,13 @@
 Find an MPI datatype matching a specified size 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Type_match_size(int typeclass, int size, MPI_Datatype *datatype)
+int MPI_Type_match_size(int typeclass, int size, MPI_Datatype * datatype)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>typeclass </B><DD>generic type specifier (integer) 
+<DT><B>typeclass </B><DD>generic type specifier (integer)
 
-<DT><B>size </B><DD>size, in bytes, of representation (integer) 
+<DT><B>size </B><DD>size, in bytes, of representation (integer)
 </DL>
 <P>
 <H2>Output Parameters</H2>
@@ -23,47 +23,47 @@ int MPI_Type_match_size(int typeclass, int size, MPI_Datatype *datatype)
 </DL>
 <P>
 <H2>Notes</H2>
-<tt>typeclass</tt> is one of <tt>MPI_TYPECLASS_REAL</tt>, <tt>MPI_TYPECLASS_INTEGER</tt> and
-<tt>MPI_TYPECLASS_COMPLEX</tt>, corresponding to the desired typeclass.
+<TT>typeclass</TT> is one of <TT>MPI_TYPECLASS_REAL</TT>, <TT>MPI_TYPECLASS_INTEGER</TT> and
+<TT>MPI_TYPECLASS_COMPLEX</TT>, corresponding to the desired typeclass.
 The function returns an MPI datatype matching a local variable of type
-<tt>( typeclass, size )</tt>.
+<TT>(typeclass, size)</TT>.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_set_attr.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_set_attr.html
index d8c0ca74..093723ae 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_set_attr.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_set_attr.html
@@ -15,48 +15,48 @@ int MPI_Type_set_attr(MPI_Datatype datatype, int type_keyval, void *attribute_va
 <DL>
 <DT><B>datatype </B><DD>MPI Datatype to which attribute will be attached (handle)
 
-<DT><B>type_keyval </B><DD>key value, as returned by  <tt>MPI_Type_create_keyval</tt> (integer)
+<DT><B>type_keyval </B><DD>key value, as returned by  <TT>MPI_Type_create_keyval</TT> (integer)
 
-<DT><B>attribute_val </B><DD>attribute value 
+<DT><B>attribute_val </B><DD>attribute value
 </DL>
 <P>
 <H2>Notes</H2>
 <P>
 The type of the attribute value depends on whether C or Fortran is being used.
-In C, an attribute value is a pointer (<tt>void *</tt>); in Fortran, it is an
+In C, an attribute value is a pointer (<TT>void *</TT>); in Fortran, it is an
 address-sized integer.
 <P>
 If an attribute is already present, the delete function (specified when the
 corresponding keyval was created) will be called.
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_KEYVAL </B> <DD> Invalid keyval
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_set_name.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_set_name.html
index 77cd2291..b41f94ec 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_set_name.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_set_name.html
@@ -15,44 +15,44 @@ int MPI_Type_set_name(MPI_Datatype datatype, const char *type_name)
 <DL>
 <DT><B>datatype </B><DD>datatype whose identifier is to be set (handle)
 
-<DT><B>type_name </B><DD>the character string which is remembered as the name (string) 
+<DT><B>type_name </B><DD>the character string which is remembered as the name (string)
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_size.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_size.html
index f2e02e64..acea1b7f 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_size.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_size.html
@@ -12,11 +12,11 @@ Return the number of bytes occupied by entries in the datatype
 int MPI_Type_size(MPI_Datatype datatype, int *size)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>datatype </B> <DD> datatype (handle) 
+<DL><DT><B>datatype </B> <DD> datatype (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>size </B> <DD> datatype size (integer) 
+<DL><DT><B>size </B> <DD> datatype size (integer)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -26,37 +26,37 @@ This means that this routine may safely be used by multiple threads and
 from within a signal handler.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_size_x.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_size_x.html
index a29056f3..3b44fbda 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_size_x.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_size_x.html
@@ -9,7 +9,7 @@
 Return the number of bytes occupied by entries in the datatype 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Type_size_x(MPI_Datatype datatype, MPI_Count *size)
+int MPI_Type_size_x(MPI_Datatype datatype, MPI_Count * size)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>datatype </B> <DD> datatype (handle)
@@ -24,31 +24,31 @@ int MPI_Type_size_x(MPI_Datatype datatype, MPI_Count *size)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_struct.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_struct.html
index 670b4346..41a39dcd 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_struct.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_struct.html
@@ -10,27 +10,26 @@ Creates a struct datatype
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Type_struct(int count,
-                   int *array_of_blocklengths,
-                   MPI_Aint *array_of_displacements,
-                   MPI_Datatype *array_of_types,
-                   MPI_Datatype *newtype)
+                    int *array_of_blocklengths,
+                    MPI_Aint * array_of_displacements,
+                    MPI_Datatype * array_of_types, MPI_Datatype * newtype)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>count </B><DD>number of blocks (integer) -- also number of 
+<DT><B>count </B><DD>number of blocks (integer) -- also number of
 entries in arrays array_of_types ,
-array_of_displacements  and array_of_blocklengths  
+array_of_displacements  and array_of_blocklengths
 
 <DT><B>array_of_blocklengths </B><DD>number of elements in each block (array)
 
 <DT><B>array_of_displacements </B><DD>byte displacement of each block (array)
 
 <DT><B>array_of_types </B><DD>type of elements in each block (array
-of handles to datatype objects) 
+of handles to datatype objects)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>newtype </B> <DD> new datatype (handle) 
+<DL><DT><B>newtype </B> <DD> new datatype (handle)
 </DL>
 <P>
 <H2>Deprecated Function</H2>
@@ -38,11 +37,11 @@ The MPI-2 standard deprecated a number of routines because MPI-2 provides
 better versions.  This routine is one of those that was deprecated.  The
 routine may continue to be used, but new code should use the replacement
 routine.
-The replacement for this routine is <tt>MPI_Type_create_struct
-</tt>
+The replacement for this routine is <TT>MPI_Type_create_struct
+</TT>
 <P>
 <H2>Notes</H2>
-If an upperbound is set explicitly by using the MPI datatype <tt>MPI_UB</tt>, the
+If an upperbound is set explicitly by using the MPI datatype <TT>MPI_UB</TT>, the
 corresponding index must be positive.
 <P>
 The MPI standard originally made vague statements about padding and alignment;
@@ -52,16 +51,16 @@ be sent with a count greater than one.  For example,
     struct { int a; char b; } foo;
 </PRE>
 
-may have <tt>sizeof(foo) &gt; sizeof(int) + sizeof(char)</tt>; for example,
-<tt>sizeof(foo) == 2*sizeof(int)</tt>.  The initial version of the MPI standard
-defined the extent of a datatype as including an <em>epsilon</em> that would have
+may have <TT>sizeof(foo) &gt; sizeof(int) + sizeof(char)</TT>; for example,
+<TT>sizeof(foo) == 2*sizeof(int)</TT>.  The initial version of the MPI standard
+defined the extent of a datatype as including an <EM>epsilon</EM> that would have
 allowed an implementation to make the extent an MPI datatype
-for this structure equal to <tt>2*sizeof(int)</tt>.
+for this structure equal to <TT>2*sizeof(int)</TT>.
 However, since different systems might define different paddings, there was
 much discussion by the MPI Forum about what was the correct value of
 epsilon, and one suggestion was to define epsilon as zero.
 This would have been the best thing to do in MPI 1.0, particularly since
-the <tt>MPI_UB</tt> type allows the user to easily set the end of the structure.
+the <TT>MPI_UB</TT> type allows the user to easily set the end of the structure.
 Unfortunately, this change did not make it into the final document.
 Currently, this routine does not add any padding, since the amount of
 padding needed is determined by the compiler that the user is using to
@@ -70,14 +69,14 @@ A later version of MPICH may provide for some natural choices of padding
 (e.g., multiple of the size of the largest basic member), but users are
 advised to never depend on this, even with vendor MPI implementations.
 Instead, if you define a structure datatype and wish to send or receive
-multiple items, you should explicitly include an <tt>MPI_UB</tt> entry as the
+multiple items, you should explicitly include an <TT>MPI_UB</TT> entry as the
 last member of the structure.  For example, the following code can be used
 for the structure foo
 <PRE>
     blen[0] = 1; array_of_displacements[0] = 0; oldtypes[0] = MPI_INT;
     blen[1] = 1; array_of_displacements[1] = &amp;foo.b - &amp;foo; oldtypes[1] = MPI_CHAR;
     blen[2] = 1; array_of_displacements[2] = sizeof(foo); oldtypes[2] = MPI_UB;
-    MPI_Type_struct( 3, blen, array_of_displacements, oldtypes, &amp;newtype );
+    MPI_Type_struct(3, blen, array_of_displacements, oldtypes, &amp;newtype);
 </PRE>
 
 <P>
@@ -86,38 +85,38 @@ for the structure foo
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_ub.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_ub.html
index 0f39f0dc..f5b17016 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_ub.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_ub.html
@@ -9,7 +9,7 @@
 Returns the upper bound of a datatype 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Type_ub(MPI_Datatype datatype, MPI_Aint *displacement)
+int MPI_Type_ub(MPI_Datatype datatype, MPI_Aint * displacement)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>datatype </B> <DD> datatype (handle)
@@ -25,8 +25,8 @@ The MPI-2 standard deprecated a number of routines because MPI-2 provides
 better versions.  This routine is one of those that was deprecated.  The
 routine may continue to be used, but new code should use the replacement
 routine.
-The replacement for this routine is <tt>MPI_Type_get_extent
-</tt>
+The replacement for this routine is <TT>MPI_Type_get_extent
+</TT>
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
@@ -35,37 +35,37 @@ This means that this routine may safely be used by multiple threads and
 from within a signal handler.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_vector.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_vector.html
index c078a03a..dcf5b1db 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_vector.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Type_vector.html
@@ -10,16 +10,13 @@ Creates a vector (strided) datatype
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Type_vector(int count,
-                   int blocklength,
-                   int stride, 
-                   MPI_Datatype oldtype,
-                   MPI_Datatype *newtype)
+                    int blocklength, int stride, MPI_Datatype oldtype, MPI_Datatype * newtype)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>count </B><DD>number of blocks (nonnegative integer) 
+<DT><B>count </B><DD>number of blocks (nonnegative integer)
 
-<DT><B>blocklength </B><DD>number of elements in each block 
+<DT><B>blocklength </B><DD>number of elements in each block
 (nonnegative integer)
 
 <DT><B>stride </B><DD>number of elements between start of each block (integer)
@@ -36,40 +33,40 @@ int MPI_Type_vector(int count,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Unpack.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Unpack.html
index a4979edf..2efc413b 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Unpack.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Unpack.html
@@ -10,8 +10,7 @@ Unpack a buffer according to a datatype into contiguous memory
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Unpack(const void *inbuf, int insize, int *position,
-               void *outbuf, int outcount, MPI_Datatype datatype,
-               MPI_Comm comm)
+               void *outbuf, int outcount, MPI_Datatype datatype, MPI_Comm comm)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -40,51 +39,51 @@ int MPI_Unpack(const void *inbuf, int insize, int *position,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Pack, MPI_Pack_size
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Unpack_external.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Unpack_external.html
index 50ae030d..a9dba98c 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Unpack_external.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Unpack_external.html
@@ -10,12 +10,9 @@ Unpack a buffer (packed with MPI_Pack_external) according to a datatype into con
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Unpack_external(const char datarep[],
-                      const void *inbuf,
-                      MPI_Aint insize,
-                      MPI_Aint *position,
-                      void *outbuf,
-                      int outcount,
-                      MPI_Datatype datatype)
+                        const void *inbuf,
+                        MPI_Aint insize,
+                        MPI_Aint * position, void *outbuf, int outcount, MPI_Datatype datatype)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
@@ -43,41 +40,41 @@ int MPI_Unpack_external(const char datarep[],
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DT><B>MPI_SUCCESS </B><DD>No error; MPI routine completed successfully.
 
 <DT><B>MPI_ERR_TYPE </B><DD>Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 
 <DT><B>MPI_ERR_ARG </B><DD>Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Unpublish_name.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Unpublish_name.html
index 915e3da4..4a3c1919 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Unpublish_name.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Unpublish_name.html
@@ -6,18 +6,18 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Unpublish_name"><H1>MPI_Unpublish_name</H1></A>
-Unpublish a service name published with  MPI_Publish_name 
+Unpublish a service name published with MPI_Publish_name 
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Unpublish_name(const char *service_name, MPI_Info info, const char *port_name)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>service_name </B><DD>a service name (string) 
+<DT><B>service_name </B><DD>a service name (string)
 
-<DT><B>info </B><DD>implementation-specific information (handle) 
+<DT><B>info </B><DD>implementation-specific information (handle)
 
-<DT><B>port_name </B><DD>a port name (string) 
+<DT><B>port_name </B><DD>a port name (string)
 </DL>
 <P>
 <P>
@@ -30,33 +30,33 @@ with this routine.
 The MPI standard defined a thread-safe interface but this does not
 mean that all routines may be called without any thread locks.  For
 example, two threads must not attempt to change the contents of the
-same <tt>MPI_Info</tt> object concurrently.  The user is responsible in this
+same <TT>MPI_Info</TT> object concurrently.  The user is responsible in this
 case for using some mechanism, such as thread locks, to ensure that
 only one thread at a time makes use of this routine.
 <P>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -65,9 +65,9 @@ possible.
 <DL><DT><B>MPI_ERR_INFO </B> <DD> Invalid Info 
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Wait.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Wait.html
index 0b6a71d7..434c1568 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Wait.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Wait.html
@@ -9,32 +9,32 @@
 Waits for an MPI request to complete 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Wait(MPI_Request *request, MPI_Status *status)
+int MPI_Wait(MPI_Request * request, MPI_Status * status)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>request </B> <DD> request (handle) 
+<DL><DT><B>request </B> <DD> request (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>status </B> <DD> status object (Status).  May be <tt>MPI_STATUS_IGNORE</tt>.
+<DL><DT><B>status </B> <DD> status object (Status).  May be <TT>MPI_STATUS_IGNORE</TT>.
 </DL>
 <P>
 <H2>Notes on the MPI_Status argument</H2>
 <P>
-The <tt>MPI_ERROR</tt> field of the status return is only set if
-the return from the MPI routine is <tt>MPI_ERR_IN_STATUS</tt>.  That error class
+The <TT>MPI_ERROR</TT> field of the status return is only set if
+the return from the MPI routine is <TT>MPI_ERR_IN_STATUS</TT>.  That error class
 is only returned by the routines that take an array of status arguments
-(<tt>MPI_Testall</tt>, <tt>MPI_Testsome</tt>, <tt>MPI_Waitall</tt>, and <tt>MPI_Waitsome</tt>).  In
-all other cases, the value of the <tt>MPI_ERROR</tt> field in the status is
+(<TT>MPI_Testall</TT>, <TT>MPI_Testsome</TT>, <TT>MPI_Waitall</TT>, and <TT>MPI_Waitsome</TT>).  In
+all other cases, the value of the <TT>MPI_ERROR</TT> field in the status is
 unchanged.  See section 3.2.5 in the MPI-1.1 specification for the
 exact text.
 <P>
-For send operations, the only use of status is for <tt>MPI_Test_cancelled</tt> or
+For send operations, the only use of status is for <TT>MPI_Test_cancelled</TT> or
 in the case that there is an error in one of the four routines that
-may return the error class <tt>MPI_ERR_IN_STATUS</tt>, in which case the
-<tt>MPI_ERROR</tt> field of status will be set.  In that case, the value
-will be set to <tt>MPI_SUCCESS</tt> for any send or receive operation that completed
-successfully, or <tt>MPI_ERR_PENDING</tt> for any operation which has neither
+may return the error class <TT>MPI_ERR_IN_STATUS</TT>, in which case the
+<TT>MPI_ERROR</TT> field of status will be set.  In that case, the value
+will be set to <TT>MPI_SUCCESS</TT> for any send or receive operation that completed
+successfully, or <TT>MPI_ERR_PENDING</TT> for any operation which has neither
 failed nor completed.
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -42,43 +42,43 @@ failed nor completed.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
-The <tt>status</tt> argument must be declared as an array of size <tt>MPI_STATUS_SIZE</tt>,
-as in <tt>integer status(MPI_STATUS_SIZE)</tt>.
+The <TT>status</TT> argument must be declared as an array of size <TT>MPI_STATUS_SIZE</TT>,
+as in <TT>integer status(MPI_STATUS_SIZE)</TT>.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
-<DL><DT><B>MPI_ERR_REQUEST </B> <DD> Invalid <tt>MPI_Request</tt>.  Either null or, in the case of a
-<tt>MPI_Start</tt> or <tt>MPI_Startall</tt>, not a persistent request.
+<DL><DT><B>MPI_ERR_REQUEST </B> <DD> Invalid <TT>MPI_Request</TT>.  Either null or, in the case of a
+<TT>MPI_Start</TT> or <TT>MPI_Startall</TT>, not a persistent request.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Waitall.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Waitall.html
index 7b43d1a1..386fcf9c 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Waitall.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Waitall.html
@@ -9,29 +9,28 @@
 Waits for all given MPI Requests to complete 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Waitall(int count, MPI_Request array_of_requests[], 
-               MPI_Status array_of_statuses[])
+int MPI_Waitall(int count, MPI_Request array_of_requests[], MPI_Status array_of_statuses[])
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>count </B><DD>list length (integer) 
+<DT><B>count </B><DD>list length (integer)
 
 <DT><B>array_of_requests </B><DD>array of request handles (array of handles)
 </DL>
 <P>
 <H2>Output Parameters</H2>
 <DL><DT><B>array_of_statuses </B> <DD> array of status objects (array of Statuses).  May be
-<tt>MPI_STATUSES_IGNORE</tt>.
+<TT>MPI_STATUSES_IGNORE</TT>.
 </DL>
 <P>
 <H2>Notes</H2>
 <P>
-If one or more of the requests completes with an error, <tt>MPI_ERR_IN_STATUS</tt> is
-returned.  An error value will be present is elements of <tt>array_of_status
-</tt>associated with the requests.  Likewise, the <tt>MPI_ERROR</tt> field in the status
+If one or more of the requests completes with an error, <TT>MPI_ERR_IN_STATUS</TT> is
+returned.  An error value will be present is elements of <TT>array_of_status
+</TT>associated with the requests.  Likewise, the <TT>MPI_ERROR</TT> field in the status
 elements associated with requests that have successfully completed will be
-<tt>MPI_SUCCESS</tt>.  Finally, those requests that have not completed will have a
-value of <tt>MPI_ERR_PENDING</tt>.
+<TT>MPI_SUCCESS</TT>.  Finally, those requests that have not completed will have a
+value of <TT>MPI_ERR_PENDING</TT>.
 <P>
 While it is possible to list a request handle more than once in the
 array_of_requests, such an action is considered erroneous and may cause the
@@ -39,20 +38,20 @@ program to unexecpectedly terminate or produce incorrect results.
 <P>
 <H2>Notes on the MPI_Status argument</H2>
 <P>
-The <tt>MPI_ERROR</tt> field of the status return is only set if
-the return from the MPI routine is <tt>MPI_ERR_IN_STATUS</tt>.  That error class
+The <TT>MPI_ERROR</TT> field of the status return is only set if
+the return from the MPI routine is <TT>MPI_ERR_IN_STATUS</TT>.  That error class
 is only returned by the routines that take an array of status arguments
-(<tt>MPI_Testall</tt>, <tt>MPI_Testsome</tt>, <tt>MPI_Waitall</tt>, and <tt>MPI_Waitsome</tt>).  In
-all other cases, the value of the <tt>MPI_ERROR</tt> field in the status is
+(<TT>MPI_Testall</TT>, <TT>MPI_Testsome</TT>, <TT>MPI_Waitall</TT>, and <TT>MPI_Waitsome</TT>).  In
+all other cases, the value of the <TT>MPI_ERROR</TT> field in the status is
 unchanged.  See section 3.2.5 in the MPI-1.1 specification for the
 exact text.
 <P>
-For send operations, the only use of status is for <tt>MPI_Test_cancelled</tt> or
+For send operations, the only use of status is for <TT>MPI_Test_cancelled</TT> or
 in the case that there is an error in one of the four routines that
-may return the error class <tt>MPI_ERR_IN_STATUS</tt>, in which case the
-<tt>MPI_ERROR</tt> field of status will be set.  In that case, the value
-will be set to <tt>MPI_SUCCESS</tt> for any send or receive operation that completed
-successfully, or <tt>MPI_ERR_PENDING</tt> for any operation which has neither
+may return the error class <TT>MPI_ERR_IN_STATUS</TT>, in which case the
+<TT>MPI_ERROR</TT> field of status will be set.  In that case, the value
+will be set to <TT>MPI_SUCCESS</TT> for any send or receive operation that completed
+successfully, or <TT>MPI_ERR_PENDING</TT> for any operation which has neither
 failed nor completed.
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -60,59 +59,59 @@ failed nor completed.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
-<DL><DT><B>MPI_ERR_REQUEST </B> <DD> Invalid <tt>MPI_Request</tt>.  Either null or, in the case of a
-<tt>MPI_Start</tt> or <tt>MPI_Startall</tt>, not a persistent request.
+<DL><DT><B>MPI_ERR_REQUEST </B> <DD> Invalid <TT>MPI_Request</TT>.  Either null or, in the case of a
+<TT>MPI_Start</TT> or <TT>MPI_Startall</TT>, not a persistent request.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
-<DL><DT><B>MPI_ERR_IN_STATUS </B> <DD> The actual error value is in the <tt>MPI_Status</tt> argument.
+<DL><DT><B>MPI_ERR_IN_STATUS </B> <DD> The actual error value is in the <TT>MPI_Status</TT> argument.
 This error class is returned only from the multiple-completion routines
-(<tt>MPI_Testall</tt>, <tt>MPI_Testany</tt>, <tt>MPI_Testsome</tt>, <tt>MPI_Waitall</tt>, <tt>MPI_Waitany</tt>,
-and <tt>MPI_Waitsome</tt>).  The field <tt>MPI_ERROR</tt> in the status argument
-contains the error value or <tt>MPI_SUCCESS</tt> (no error and complete) or
-<tt>MPI_ERR_PENDING</tt> to indicate that the request has not completed.
+(<TT>MPI_Testall</TT>, <TT>MPI_Testany</TT>, <TT>MPI_Testsome</TT>, <TT>MPI_Waitall</TT>, <TT>MPI_Waitany</TT>,
+and <TT>MPI_Waitsome</TT>).  The field <TT>MPI_ERROR</TT> in the status argument
+contains the error value or <TT>MPI_SUCCESS</TT> (no error and complete) or
+<TT>MPI_ERR_PENDING</TT> to indicate that the request has not completed.
 </DL>
 The MPI Standard does not specify what the result of the multiple
 completion routines is when an error occurs.  For example, in an
-<tt>MPI_WAITALL</tt>, does the routine wait for all requests to either fail or
+<TT>MPI_WAITALL</TT>, does the routine wait for all requests to either fail or
 complete, or does it return immediately (with the MPI definition of
 immediately, which means independent of actions of other MPI processes)?
 MPICH has chosen to make the return immediate (alternately, local in MPI
-terms), and to use the error class <tt>MPI_ERR_PENDING</tt> (introduced in MPI 1.1)
+terms), and to use the error class <TT>MPI_ERR_PENDING</TT> (introduced in MPI 1.1)
 to indicate which requests have not completed.  In most cases, only
 one request with an error will be detected in each call to an MPI routine
 that tests multiple requests.  The requests that have not been processed
 (because an error occured in one of the requests) will have their
-<tt>MPI_ERROR</tt> field marked with <tt>MPI_ERR_PENDING</tt>.
+<TT>MPI_ERROR</TT> field marked with <TT>MPI_ERR_PENDING</TT>.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Waitany.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Waitany.html
index f3a915ba..cbce99bf 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Waitany.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Waitany.html
@@ -9,27 +9,26 @@
 Waits for any specified MPI Request to complete 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Waitany(int count, MPI_Request array_of_requests[], int *indx,
-               MPI_Status *status)
+int MPI_Waitany(int count, MPI_Request array_of_requests[], int *indx, MPI_Status * status)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>count </B><DD>list length (integer) 
+<DT><B>count </B><DD>list length (integer)
 
-<DT><B>array_of_requests </B><DD>array of requests (array of handles) 
+<DT><B>array_of_requests </B><DD>array of requests (array of handles)
 </DL>
 <P>
 <H2>Output Parameters</H2>
 <DL>
 <DT><B>indx </B><DD>index of handle for operation that completed (integer).  In the
-range <tt>0</tt> to <tt>count-1</tt>.  In Fortran, the range is <tt>1</tt> to <tt>count</tt>.
+range <TT>0</TT> to <TT>count-1</TT>.  In Fortran, the range is <TT>1</TT> to <TT>count</TT>.
 
-<DT><B>status </B><DD>status object (Status).  May be <tt>MPI_STATUS_IGNORE</tt>.
+<DT><B>status </B><DD>status object (Status).  May be <TT>MPI_STATUS_IGNORE</TT>.
 </DL>
 <P>
 <H2>Notes</H2>
-If all of the requests are <tt>MPI_REQUEST_NULL</tt>, then <tt>indx</tt> is returned as
-<tt>MPI_UNDEFINED</tt>, and <tt>status</tt> is returned as an empty status.
+If all of the requests are <TT>MPI_REQUEST_NULL</TT>, then <TT>indx</TT> is returned as
+<TT>MPI_UNDEFINED</TT>, and <TT>status</TT> is returned as an empty status.
 <P>
 While it is possible to list a request handle more than once in the
 array_of_requests, such an action is considered erroneous and may cause the
@@ -37,20 +36,20 @@ program to unexecpectedly terminate or produce incorrect results.
 <P>
 <H2>Notes on the MPI_Status argument</H2>
 <P>
-The <tt>MPI_ERROR</tt> field of the status return is only set if
-the return from the MPI routine is <tt>MPI_ERR_IN_STATUS</tt>.  That error class
+The <TT>MPI_ERROR</TT> field of the status return is only set if
+the return from the MPI routine is <TT>MPI_ERR_IN_STATUS</TT>.  That error class
 is only returned by the routines that take an array of status arguments
-(<tt>MPI_Testall</tt>, <tt>MPI_Testsome</tt>, <tt>MPI_Waitall</tt>, and <tt>MPI_Waitsome</tt>).  In
-all other cases, the value of the <tt>MPI_ERROR</tt> field in the status is
+(<TT>MPI_Testall</TT>, <TT>MPI_Testsome</TT>, <TT>MPI_Waitall</TT>, and <TT>MPI_Waitsome</TT>).  In
+all other cases, the value of the <TT>MPI_ERROR</TT> field in the status is
 unchanged.  See section 3.2.5 in the MPI-1.1 specification for the
 exact text.
 <P>
-For send operations, the only use of status is for <tt>MPI_Test_cancelled</tt> or
+For send operations, the only use of status is for <TT>MPI_Test_cancelled</TT> or
 in the case that there is an error in one of the four routines that
-may return the error class <tt>MPI_ERR_IN_STATUS</tt>, in which case the
-<tt>MPI_ERROR</tt> field of status will be set.  In that case, the value
-will be set to <tt>MPI_SUCCESS</tt> for any send or receive operation that completed
-successfully, or <tt>MPI_ERR_PENDING</tt> for any operation which has neither
+may return the error class <TT>MPI_ERR_IN_STATUS</TT>, in which case the
+<TT>MPI_ERROR</TT> field of status will be set.  In that case, the value
+will be set to <TT>MPI_SUCCESS</TT> for any send or receive operation that completed
+successfully, or <TT>MPI_ERR_PENDING</TT> for any operation which has neither
 failed nor completed.
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -58,40 +57,40 @@ failed nor completed.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
-<DL><DT><B>MPI_ERR_REQUEST </B> <DD> Invalid <tt>MPI_Request</tt>.  Either null or, in the case of a
-<tt>MPI_Start</tt> or <tt>MPI_Startall</tt>, not a persistent request.
+<DL><DT><B>MPI_ERR_REQUEST </B> <DD> Invalid <TT>MPI_Request</TT>.  Either null or, in the case of a
+<TT>MPI_Start</TT> or <TT>MPI_Startall</TT>, not a persistent request.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Waitsome.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Waitsome.html
index 15509134..94efce11 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Waitsome.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Waitsome.html
@@ -9,65 +9,64 @@
 Waits for some given MPI Requests to complete 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Waitsome(int incount, MPI_Request array_of_requests[], 
-                int *outcount, int array_of_indices[],
-                MPI_Status array_of_statuses[])
+int MPI_Waitsome(int incount, MPI_Request array_of_requests[],
+                 int *outcount, int array_of_indices[], MPI_Status array_of_statuses[])
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>incount </B><DD>length of array_of_requests (integer) 
+<DT><B>incount </B><DD>length of array_of_requests (integer)
 
-<DT><B>array_of_requests </B><DD>array of requests (array of handles) 
+<DT><B>array_of_requests </B><DD>array of requests (array of handles)
 </DL>
 <P>
 <H2>Output Parameters</H2>
 <DL>
-<DT><B>outcount </B><DD>number of completed requests (integer) 
+<DT><B>outcount </B><DD>number of completed requests (integer)
 
-<DT><B>array_of_indices </B><DD>array of indices of operations that 
-completed (array of integers) 
+<DT><B>array_of_indices </B><DD>array of indices of operations that
+completed (array of integers)
 
-<DT><B>array_of_statuses </B><DD>array of status objects for 
-operations that completed (array of Status).  May be <tt>MPI_STATUSES_IGNORE</tt>.
+<DT><B>array_of_statuses </B><DD>array of status objects for
+operations that completed (array of Status).  May be <TT>MPI_STATUSES_IGNORE</TT>.
 </DL>
 <P>
 <H2>Notes</H2>
-The array of indicies are in the range <tt>0</tt> to <tt>incount - 1</tt> for C and
-in the range <tt>1</tt> to <tt>incount</tt> for Fortran.
+The array of indicies are in the range <TT>0</TT> to <TT>incount - 1</TT> for C and
+in the range <TT>1</TT> to <TT>incount</TT> for Fortran.
 <P>
 Null requests are ignored; if all requests are null, then the routine
-returns with <tt>outcount</tt> set to <tt>MPI_UNDEFINED</tt>.
+returns with <TT>outcount</TT> set to <TT>MPI_UNDEFINED</TT>.
 <P>
 While it is possible to list a request handle more than once in the
 array_of_requests, such an action is considered erroneous and may cause the
 program to unexecpectedly terminate or produce incorrect results.
 <P>
-<tt>MPI_Waitsome</tt> provides an interface much like the Unix <tt>select</tt> or <tt>poll
-</tt>calls and, in a high qualilty implementation, indicates all of the requests
-that have completed when <tt>MPI_Waitsome</tt> is called.
-However, <tt>MPI_Waitsome</tt> only guarantees that at least one
-request has completed; there is no guarantee that <em>all</em> completed requests
-will be returned, or that the entries in <tt>array_of_indices</tt> will be in
-increasing order. Also, requests that are completed while <tt>MPI_Waitsome</tt> is
+<TT>MPI_Waitsome</TT> provides an interface much like the Unix <TT>select</TT> or <TT>poll
+</TT>calls and, in a high qualilty implementation, indicates all of the requests
+that have completed when <TT>MPI_Waitsome</TT> is called.
+However, <TT>MPI_Waitsome</TT> only guarantees that at least one
+request has completed; there is no guarantee that <EM>all</EM> completed requests
+will be returned, or that the entries in <TT>array_of_indices</TT> will be in
+increasing order. Also, requests that are completed while <TT>MPI_Waitsome</TT> is
 executing may or may not be returned, depending on the timing of the
 completion of the message.
 <P>
 <H2>Notes on the MPI_Status argument</H2>
 <P>
-The <tt>MPI_ERROR</tt> field of the status return is only set if
-the return from the MPI routine is <tt>MPI_ERR_IN_STATUS</tt>.  That error class
+The <TT>MPI_ERROR</TT> field of the status return is only set if
+the return from the MPI routine is <TT>MPI_ERR_IN_STATUS</TT>.  That error class
 is only returned by the routines that take an array of status arguments
-(<tt>MPI_Testall</tt>, <tt>MPI_Testsome</tt>, <tt>MPI_Waitall</tt>, and <tt>MPI_Waitsome</tt>).  In
-all other cases, the value of the <tt>MPI_ERROR</tt> field in the status is
+(<TT>MPI_Testall</TT>, <TT>MPI_Testsome</TT>, <TT>MPI_Waitall</TT>, and <TT>MPI_Waitsome</TT>).  In
+all other cases, the value of the <TT>MPI_ERROR</TT> field in the status is
 unchanged.  See section 3.2.5 in the MPI-1.1 specification for the
 exact text.
 <P>
-For send operations, the only use of status is for <tt>MPI_Test_cancelled</tt> or
+For send operations, the only use of status is for <TT>MPI_Test_cancelled</TT> or
 in the case that there is an error in one of the four routines that
-may return the error class <tt>MPI_ERR_IN_STATUS</tt>, in which case the
-<tt>MPI_ERROR</tt> field of status will be set.  In that case, the value
-will be set to <tt>MPI_SUCCESS</tt> for any send or receive operation that completed
-successfully, or <tt>MPI_ERR_PENDING</tt> for any operation which has neither
+may return the error class <TT>MPI_ERR_IN_STATUS</TT>, in which case the
+<TT>MPI_ERROR</TT> field of status will be set.  In that case, the value
+will be set to <TT>MPI_SUCCESS</TT> for any send or receive operation that completed
+successfully, or <TT>MPI_ERR_PENDING</TT> for any operation which has neither
 failed nor completed.
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -75,59 +74,59 @@ failed nor completed.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
-<DL><DT><B>MPI_ERR_REQUEST </B> <DD> Invalid <tt>MPI_Request</tt>.  Either null or, in the case of a
-<tt>MPI_Start</tt> or <tt>MPI_Startall</tt>, not a persistent request.
+<DL><DT><B>MPI_ERR_REQUEST </B> <DD> Invalid <TT>MPI_Request</TT>.  Either null or, in the case of a
+<TT>MPI_Start</TT> or <TT>MPI_Startall</TT>, not a persistent request.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
-<DL><DT><B>MPI_ERR_IN_STATUS </B> <DD> The actual error value is in the <tt>MPI_Status</tt> argument.
+<DL><DT><B>MPI_ERR_IN_STATUS </B> <DD> The actual error value is in the <TT>MPI_Status</TT> argument.
 This error class is returned only from the multiple-completion routines
-(<tt>MPI_Testall</tt>, <tt>MPI_Testany</tt>, <tt>MPI_Testsome</tt>, <tt>MPI_Waitall</tt>, <tt>MPI_Waitany</tt>,
-and <tt>MPI_Waitsome</tt>).  The field <tt>MPI_ERROR</tt> in the status argument
-contains the error value or <tt>MPI_SUCCESS</tt> (no error and complete) or
-<tt>MPI_ERR_PENDING</tt> to indicate that the request has not completed.
+(<TT>MPI_Testall</TT>, <TT>MPI_Testany</TT>, <TT>MPI_Testsome</TT>, <TT>MPI_Waitall</TT>, <TT>MPI_Waitany</TT>,
+and <TT>MPI_Waitsome</TT>).  The field <TT>MPI_ERROR</TT> in the status argument
+contains the error value or <TT>MPI_SUCCESS</TT> (no error and complete) or
+<TT>MPI_ERR_PENDING</TT> to indicate that the request has not completed.
 </DL>
 The MPI Standard does not specify what the result of the multiple
 completion routines is when an error occurs.  For example, in an
-<tt>MPI_WAITALL</tt>, does the routine wait for all requests to either fail or
+<TT>MPI_WAITALL</TT>, does the routine wait for all requests to either fail or
 complete, or does it return immediately (with the MPI definition of
 immediately, which means independent of actions of other MPI processes)?
 MPICH has chosen to make the return immediate (alternately, local in MPI
-terms), and to use the error class <tt>MPI_ERR_PENDING</tt> (introduced in MPI 1.1)
+terms), and to use the error class <TT>MPI_ERR_PENDING</TT> (introduced in MPI 1.1)
 to indicate which requests have not completed.  In most cases, only
 one request with an error will be detected in each call to an MPI routine
 that tests multiple requests.  The requests that have not been processed
 (because an error occured in one of the requests) will have their
-<tt>MPI_ERROR</tt> field marked with <tt>MPI_ERR_PENDING</tt>.
+<TT>MPI_ERROR</TT> field marked with <TT>MPI_ERR_PENDING</TT>.
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_allocate.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_allocate.html
index 6ca780db..9722c8f6 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_allocate.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_allocate.html
@@ -9,8 +9,8 @@
 Create and allocate an MPI Window object for one-sided communication. 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Win_allocate(MPI_Aint size, int disp_unit, MPI_Info info, 
-                  MPI_Comm comm, void *baseptr, MPI_Win *win)
+int MPI_Win_allocate(MPI_Aint size, int disp_unit, MPI_Info info,
+                     MPI_Comm comm, void *baseptr, MPI_Win * win)
 </PRE>
 <P>
 This is a collective call executed by all processes in the group of comm. On
@@ -18,7 +18,7 @@ each process, it allocates memory of at least size bytes, returns a pointer to
 it, and returns a window object that can be used by all processes in comm to
 perform RMA operations. The returned memory consists of size bytes local to
 each process, starting at address baseptr and is associated with the window as
-if the user called <tt>MPI_Win_create</tt> on existing memory. The size argument may be
+if the user called <TT>MPI_Win_create</TT> on existing memory. The size argument may be
 different at each process and size = 0 is valid; however, a library might
 allocate and expose more memory in order to create a fast, globally symmetric
 allocation.
@@ -45,50 +45,50 @@ allocation.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_INFO </B> <DD> Invalid Info 
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 <DL><DT><B>MPI_ERR_SIZE </B> <DD> 
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
 MPI_Win_allocate_shared MPI_Win_create MPI_Win_create_dynamic MPI_Win_free
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_allocate_shared.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_allocate_shared.html
index 784e4d80..fa47322a 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_allocate_shared.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_allocate_shared.html
@@ -10,7 +10,7 @@ Create an MPI Window object for one-sided communication and shared memory access
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Win_allocate_shared(MPI_Aint size, int disp_unit, MPI_Info info, MPI_Comm comm,
-                             void *baseptr, MPI_Win *win)
+                            void *baseptr, MPI_Win * win)
 </PRE>
 This is a collective call executed by all processes in the group of comm. On
 each process i, it allocates memory of at least size bytes that is shared among
@@ -18,7 +18,7 @@ all processes in comm, and returns a pointer to the locally allocated segment
 in baseptr that can be used for load/store accesses on the calling process. The
 locally allocated memory can be the target of load/store accesses by remote
 processes; the base pointers for other processes can be queried using the
-function <tt>MPI_Win_shared_query</tt>.
+function <TT>MPI_Win_shared_query</TT>.
 <P>
 The call also returns a window object that can be used by all processes in comm
 to perform RMA operations. The size argument may be different at each process
@@ -54,50 +54,50 @@ to calculate remote address offsets with local information only.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_INFO </B> <DD> Invalid Info 
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 <DL><DT><B>MPI_ERR_SIZE </B> <DD> 
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Win_allocate MPI_Win_create MPI_Win_create_dynamic MPI_Win_free MPI_Win_shared_query
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_attach.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_attach.html
index 58036e23..98405324 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_attach.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_attach.html
@@ -16,7 +16,7 @@ Attaches a local memory region beginning at base for remote access within the
 given window. The memory region specified must not contain any part that is
 already attached to the window win, that is, attaching overlapping memory
 concurrently within the same window is erroneous. The argument win must be a
-window that was created with <tt>MPI_Win_create_dynamic</tt>. Multiple (but
+window that was created with <TT>MPI_Win_create_dynamic</TT>. Multiple (but
 non-overlapping) memory regions may be attached to the same window.
 <P>
 <H2>Input Parameters</H2>
@@ -33,54 +33,54 @@ non-overlapping) memory regions may be attached to the same window.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Win_create_dynamic MPI_Win_detach
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_call_errhandler.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_call_errhandler.html
index 9128b848..35e07340 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_call_errhandler.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_call_errhandler.html
@@ -6,16 +6,16 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Win_call_errhandler"><H1>MPI_Win_call_errhandler</H1></A>
-Call the error handler installed on a  window object 
+Call the error handler installed on a window object 
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Win_call_errhandler(MPI_Win win, int errorcode)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>win </B><DD>window with error handler (handle) 
+<DT><B>win </B><DD>window with error handler (handle)
 
-<DT><B>errorcode </B><DD>error code (integer) 
+<DT><B>errorcode </B><DD>error code (integer)
 </DL>
 <P>
 <H2>Note</H2>
@@ -32,33 +32,33 @@ with this routine.
 The MPI standard defined a thread-safe interface but this does not
 mean that all routines may be called without any thread locks.  For
 example, two threads must not attempt to change the contents of the
-same <tt>MPI_Info</tt> object concurrently.  The user is responsible in this
+same <TT>MPI_Info</TT> object concurrently.  The user is responsible in this
 case for using some mechanism, such as thread locks, to ensure that
 only one thread at a time makes use of this routine.
 <P>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_complete.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_complete.html
index 89d2e3e9..ca9b7752 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_complete.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_complete.html
@@ -12,7 +12,7 @@ Completes an RMA operations begun after an MPI_Win_start.
 int MPI_Win_complete(MPI_Win win)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>win </B> <DD> window object (handle) 
+<DL><DT><B>win </B> <DD> window object (handle)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -20,31 +20,31 @@ int MPI_Win_complete(MPI_Win win)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -52,7 +52,7 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_create.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_create.html
index 8ce604ec..cd7ddd25 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_create.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_create.html
@@ -9,8 +9,8 @@
 Create an MPI Window object for one-sided communication 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Win_create(void *base, MPI_Aint size, int disp_unit, MPI_Info info, 
-                  MPI_Comm comm, MPI_Win *win)
+int MPI_Win_create(void *base, MPI_Aint size, int disp_unit, MPI_Info info,
+                   MPI_Comm comm, MPI_Win * win)
 </PRE>
 <P>
 This is a collective call executed by all processes in the group of comm. It
@@ -50,7 +50,7 @@ The info argument provides optimization hints to the runtime about the expected
 usage pattern of the window. The following info keys are predefined.
 <P>
 <DL><DT><B>no_locks </B> <DD> If set to true, then the implementation may assume that passive
-target synchronization (i.e., <tt>MPI_Win_lock</tt>, <tt>MPI_Win_lock_all</tt>) will not be used on
+target synchronization (i.e., <TT>MPI_Win_lock</TT>, <TT>MPI_Win_lock_all</TT>) will not be used on
 the given window. This implies that this window is not used for 3-party
 communication, and RMA can be implemented with no (less) asynchronous agent
 activity at this process.
@@ -66,7 +66,7 @@ following read/write ordering rules, where e.g. "raw" means read-after-write:
 concurrent accumulate calls to the same target address will use the same
 operation. If set to same_op_no_op, then the implementation will assume that
 all concurrent accumulate calls to the same target address will use the same
-operation or <tt>MPI_NO_OP</tt>. This can eliminate the need to protect access for
+operation or <TT>MPI_NO_OP</TT>. This can eliminate the need to protect access for
 certain operation types where the hardware can guarantee atomicity. The default
 is same_op_no_op.
 </DL>
@@ -76,50 +76,50 @@ is same_op_no_op.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_INFO </B> <DD> Invalid Info 
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 <DL><DT><B>MPI_ERR_SIZE </B> <DD> 
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Win_allocate MPI_Win_allocate_shared MPI_Win_create_dynamic MPI_Win_free
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_create_dynamic.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_create_dynamic.html
index cf0d1047..dcb018db 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_create_dynamic.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_create_dynamic.html
@@ -9,7 +9,7 @@
 Create an MPI Window object for one-sided communication.  This window allows memory to be dynamically exposed and un-exposed for RMA operations. 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Win_create_dynamic(MPI_Info info, MPI_Comm comm, MPI_Win *win)
+int MPI_Win_create_dynamic(MPI_Info info, MPI_Comm comm, MPI_Win * win)
 </PRE>
 <P>
 This is a collective call executed by all processes in the group of comm. It
@@ -18,13 +18,13 @@ attached as described below. This routine returns a window object that can be
 used by these processes to perform RMA operations on attached memory. Because
 this window has special properties, it will sometimes be referred to as a
 dynamic window.  The info argument can be used to specify hints similar to the
-info argument for <tt>MPI_Win_create</tt>.
+info argument for <TT>MPI_Win_create</TT>.
 <P>
-In the case of a window created with <tt>MPI_Win_create_dynamic</tt>, the target_disp
+In the case of a window created with <TT>MPI_Win_create_dynamic</TT>, the target_disp
 for all RMA functions is the address at the target; i.e., the effective
-window_base is <tt>MPI_BOTTOM</tt> and the disp_unit is one. For dynamic windows, the
+window_base is <TT>MPI_BOTTOM</TT> and the disp_unit is one. For dynamic windows, the
 target_disp argument to RMA communication operations is not restricted to
-non-negative values. Users should use <tt>MPI_Get_address</tt> at the target process to
+non-negative values. Users should use <TT>MPI_Get_address</TT> at the target process to
 determine the address of a target memory location and communicate this address
 to the origin process.
 <P>
@@ -42,13 +42,13 @@ to the origin process.
 <H2>Notes</H2>
 <P>
 Users are cautioned that displacement arithmetic can overflow in variables of
-type <tt>MPI_Aint</tt> and result in unexpected values on some platforms. This issue may
+type <TT>MPI_Aint</TT> and result in unexpected values on some platforms. This issue may
 be addressed in a future version of MPI.
 <P>
 Memory in this window may not be used as the target of one-sided accesses in
-this window until it is attached using the function <tt>MPI_Win_attach</tt>. That is, in
-addition to using <tt>MPI_Win_create_dynamic</tt> to create an MPI window, the user must
-use <tt>MPI_Win_attach</tt> before any local memory may be the target of an MPI RMA
+this window until it is attached using the function <TT>MPI_Win_attach</TT>. That is, in
+addition to using <TT>MPI_Win_create_dynamic</TT> to create an MPI window, the user must
+use <TT>MPI_Win_attach</TT> before any local memory may be the target of an MPI RMA
 operation. Only memory that is currently accessible may be attached.
 <P>
 <P>
@@ -57,50 +57,50 @@ operation. Only memory that is currently accessible may be attached.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COMM </B> <DD> Invalid communicator.  A common error is to use a null
-communicator in a call (not even allowed in <tt>MPI_Comm_rank</tt>).
+communicator in a call (not even allowed in <TT>MPI_Comm_rank</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_INFO </B> <DD> Invalid Info 
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 <DL><DT><B>MPI_ERR_SIZE </B> <DD> 
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Win_attach MPI_Win_detach MPI_Win_allocate MPI_Win_allocate_shared MPI_Win_create MPI_Win_free
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_create_errhandler.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_create_errhandler.html
index 40c65fe8..ef46516f 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_create_errhandler.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_create_errhandler.html
@@ -9,15 +9,15 @@
 Create an error handler for use with MPI window objects 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Win_create_errhandler(MPI_Win_errhandler_function *win_errhandler_fn,
-                            MPI_Errhandler *errhandler)
+int MPI_Win_create_errhandler(MPI_Win_errhandler_function * win_errhandler_fn,
+                              MPI_Errhandler * errhandler)
 </PRE>
 <H2>Input Parameters</H2>
 <DL><DT><B>win_errhandler_fn </B> <DD> user defined error handling procedure (function)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>errhandler </B> <DD> MPI error handler (handle) 
+<DL><DT><B>errhandler </B> <DD> MPI error handler (handle)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -25,37 +25,37 @@ int MPI_Win_create_errhandler(MPI_Win_errhandler_function *win_errhandler_fn,
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_create_keyval.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_create_keyval.html
index 68008a32..5732c70d 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_create_keyval.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_create_keyval.html
@@ -9,21 +9,21 @@
 Create an attribute keyval for MPI window objects 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Win_create_keyval(MPI_Win_copy_attr_function *win_copy_attr_fn, 
-                        MPI_Win_delete_attr_function *win_delete_attr_fn, 
-                        int *win_keyval, void *extra_state)
+int MPI_Win_create_keyval(MPI_Win_copy_attr_function * win_copy_attr_fn,
+                          MPI_Win_delete_attr_function * win_delete_attr_fn,
+                          int *win_keyval, void *extra_state)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>win_copy_attr_fn </B><DD>copy callback function for win_keyval (function) 
+<DT><B>win_copy_attr_fn </B><DD>copy callback function for win_keyval (function)
 
-<DT><B>win_delete_attr_fn </B><DD>delete callback function for win_keyval (function) 
+<DT><B>win_delete_attr_fn </B><DD>delete callback function for win_keyval (function)
 
-<DT><B>extra_state </B><DD>extra state for callback functions 
+<DT><B>extra_state </B><DD>extra state for callback functions
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>win_keyval </B> <DD> key value for future access (integer) 
+<DL><DT><B>win_keyval </B> <DD> key value for future access (integer)
 </DL>
 <P>
 <H2>Notes</H2>
@@ -39,9 +39,9 @@ Default copy and delete functions are available.  These are
 <P>
 <H2>Return value from attribute callbacks</H2>
 The MPI-2 versions of the attribute callbacks should return either
-<tt>MPI_SUCCESS</tt> on success or a valid MPI error code or class on failure.
+<TT>MPI_SUCCESS</TT> on success or a valid MPI error code or class on failure.
 The MPI standard is ambiguous on this point, but as MPI-2 provides
-the routines <tt>MPI_Add_error_class</tt> and <tt>MPI_Add_error_code</tt> that allow the
+the routines <TT>MPI_Add_error_class</TT> and <TT>MPI_Add_error_code</TT> that allow the
 user to define and use MPI error codes and classes.
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -49,40 +49,40 @@ user to define and use MPI error codes and classes.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_delete_attr.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_delete_attr.html
index 57b2c84c..bd59293e 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_delete_attr.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_delete_attr.html
@@ -6,16 +6,16 @@
 </HEAD>
 <BODY BGCOLOR="FFFFFF">
 <A NAME="MPI_Win_delete_attr"><H1>MPI_Win_delete_attr</H1></A>
-Deletes an attribute value associated with a key on  a datatype 
+Deletes an attribute value associated with a key on a datatype 
 <H2>Synopsis</H2>
 <PRE>
 int MPI_Win_delete_attr(MPI_Win win, int win_keyval)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>win </B><DD>window from which the attribute is deleted (handle) 
+<DT><B>win </B><DD>window from which the attribute is deleted (handle)
 
-<DT><B>win_keyval </B><DD>key value (integer) 
+<DT><B>win_keyval </B><DD>key value (integer)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -23,31 +23,31 @@ int MPI_Win_delete_attr(MPI_Win win, int win_keyval)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -57,7 +57,7 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_KEYVAL </B> <DD> Invalid keyval
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_detach.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_detach.html
index 6cc50f8e..a6648c52 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_detach.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_detach.html
@@ -14,7 +14,7 @@ int MPI_Win_detach(MPI_Win win, const void *base)
 <P>
 Detaches a previously attached memory region beginning at base. The arguments
 base and win must match the arguments passed to a previous call to
-<tt>MPI_Win_attach</tt>.
+<TT>MPI_Win_attach</TT>.
 <P>
 <H2>Input Parameters</H2>
 <DL>
@@ -31,54 +31,54 @@ Memory also becomes detached when the associated dynamic memory window is freed.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_COUNT </B> <DD> Invalid count argument.  Count arguments must be 
 non-negative; a count of zero is often valid.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_TYPE </B> <DD> Invalid datatype argument.  Additionally, this error can
-occur if an uncommitted MPI_Datatype (see <tt>MPI_Type_commit</tt>) is used
+occur if an uncommitted MPI_Datatype (see <TT>MPI_Type_commit</TT>) is used
 in a communication call.
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Win_create_dynamic MPI_Win_attach
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_fence.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_fence.html
index 1052363a..7e248da2 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_fence.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_fence.html
@@ -13,31 +13,31 @@ int MPI_Win_fence(int assert, MPI_Win win)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>assert </B><DD>program assertion (integer) 
+<DT><B>assert </B><DD>program assertion (integer)
 
-<DT><B>win </B><DD>window object (handle) 
+<DT><B>win </B><DD>window object (handle)
 </DL>
 <P>
 <H2>Notes</H2>
-The <tt>assert</tt> argument is used to indicate special conditions for the
-fence that an implementation may use to optimize the <tt>MPI_Win_fence
-</tt>operation.  The value zero is always correct.  Other assertion values
-may be or'ed together.  Assertions that are valid for <tt>MPI_Win_fence</tt> are:
+The <TT>assert</TT> argument is used to indicate special conditions for the
+fence that an implementation may use to optimize the <TT>MPI_Win_fence
+</TT>operation.  The value zero is always correct.  Other assertion values
+may be or'ed together.  Assertions that are valid for <TT>MPI_Win_fence</TT> are:
 <P>
 <DL>
-<DT><B>MPI_MODE_NOSTORE </B><DD>the local window was not updated by local stores 
-(or local get or receive calls) since last synchronization. 
+<DT><B>MPI_MODE_NOSTORE </B><DD>the local window was not updated by local stores
+(or local get or receive calls) since last synchronization.
 
-<DT><B>MPI_MODE_NOPUT </B><DD>the local window will not be updated by put or accumulate 
-calls after the fence call, until the ensuing (fence) synchronization. 
+<DT><B>MPI_MODE_NOPUT </B><DD>the local window will not be updated by put or accumulate
+calls after the fence call, until the ensuing (fence) synchronization.
 
-<DT><B>MPI_MODE_NOPRECEDE </B><DD>the fence does not complete any sequence of locally 
-issued RMA calls. If this assertion is given by any process in the window 
-group, then it must be given by all processes in the group. 
+<DT><B>MPI_MODE_NOPRECEDE </B><DD>the fence does not complete any sequence of locally
+issued RMA calls. If this assertion is given by any process in the window
+group, then it must be given by all processes in the group.
 
-<DT><B>MPI_MODE_NOSUCCEED </B><DD>the fence does not start any sequence of locally 
-issued RMA calls. If the assertion is given by any process in the window 
-group, then it must be given by all processes in the group. 
+<DT><B>MPI_MODE_NOSUCCEED </B><DD>the fence does not start any sequence of locally
+issued RMA calls. If the assertion is given by any process in the window
+group, then it must be given by all processes in the group.
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -45,37 +45,37 @@ group, then it must be given by all processes in the group.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_flush.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_flush.html
index 19da36cb..022bc752 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_flush.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_flush.html
@@ -12,7 +12,7 @@ Complete all outstanding RMA operations at the given target.
 int MPI_Win_flush(int rank, MPI_Win win)
 </PRE>
 <P>
-<tt>MPI_Win_flush</tt> completes all outstanding RMA operations initiated by the calling
+<TT>MPI_Win_flush</TT> completes all outstanding RMA operations initiated by the calling
 process to the target rank on the specified window. The operations are
 completed both at the origin and at the target.
 <P>
@@ -28,31 +28,31 @@ completed both at the origin and at the target.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -60,15 +60,15 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Win_flush_all MPI_Win_flush_local MPI_Win_flush_local_all MPI_Win_lock MPI_Win_lock_all
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_flush_all.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_flush_all.html
index d91d9e73..0ddbf5e6 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_flush_all.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_flush_all.html
@@ -25,31 +25,31 @@ both at the origin and at the target when this call returns.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -57,15 +57,15 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Win_flush MPI_Win_flush_local MPI_Win_flush_local_all MPI_Win_lock MPI_Win_lock_all
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_flush_local.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_flush_local.html
index 3dabd4f1..a5fe82c5 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_flush_local.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_flush_local.html
@@ -29,31 +29,31 @@ buffers provided to put, get, or accumulate operations.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -61,15 +61,15 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Win_flush MPI_Win_flush_all MPI_Win_flush_local_all MPI_Win_lock MPI_Win_lock_all
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_flush_local_all.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_flush_local_all.html
index 192aaedb..b0a2fc6e 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_flush_local_all.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_flush_local_all.html
@@ -13,7 +13,7 @@ int MPI_Win_flush_local_all(MPI_Win win)
 </PRE>
 <P>
 All RMA operations issued to any target prior to this call in this window will
-have completed at the origin when <tt>MPI_Win_flush_local_all</tt> returns.
+have completed at the origin when <TT>MPI_Win_flush_local_all</TT> returns.
 <P>
 <H2>Input Parameters</H2>
 <DL><DT><B>win </B> <DD> window object (handle)
@@ -24,31 +24,31 @@ have completed at the origin when <tt>MPI_Win_flush_local_all</tt> returns.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -56,15 +56,15 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Win_flush MPI_Win_flush_all MPI_Win_flush_local MPI_Win_lock MPI_Win_lock_all
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_free.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_free.html
index ce9f5875..50c163e6 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_free.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_free.html
@@ -9,45 +9,45 @@
 Free an MPI RMA window 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Win_free(MPI_Win *win)
+int MPI_Win_free(MPI_Win * win)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>win </B> <DD> window object (handle) 
+<DL><DT><B>win </B> <DD> window object (handle)
 </DL>
 <P>
 <H2>Notes</H2>
-If successfully freed, <tt>win</tt> is set to <tt>MPI_WIN_NULL</tt>.
+If successfully freed, <TT>win</TT> is set to <TT>MPI_WIN_NULL</TT>.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -55,7 +55,7 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_free_keyval.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_free_keyval.html
index 045d976d..a99c1322 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_free_keyval.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_free_keyval.html
@@ -12,7 +12,7 @@ Frees an attribute key for MPI RMA windows
 int MPI_Win_free_keyval(int *win_keyval)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>win_keyval </B> <DD> key value (integer) 
+<DL><DT><B>win_keyval </B> <DD> key value (integer)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -20,31 +20,31 @@ int MPI_Win_free_keyval(int *win_keyval)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -52,7 +52,7 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 <DL><DT><B>MPI_ERR_KEYVAL </B> <DD> Invalid keyval
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_get_attr.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_get_attr.html
index 1882ae81..0b0401cf 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_get_attr.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_get_attr.html
@@ -9,32 +9,31 @@
 Get attribute cached on an MPI window object 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Win_get_attr(MPI_Win win, int win_keyval, void *attribute_val, 
-                    int *flag)
+int MPI_Win_get_attr(MPI_Win win, int win_keyval, void *attribute_val, int *flag)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>win </B><DD>window to which the attribute is attached (handle) 
+<DT><B>win </B><DD>window to which the attribute is attached (handle)
 
-<DT><B>win_keyval </B><DD>key value (integer) 
+<DT><B>win_keyval </B><DD>key value (integer)
 </DL>
 <P>
 <H2>Output Parameters</H2>
 <DL>
-<DT><B>attribute_val </B><DD>attribute value, unless flag is false 
+<DT><B>attribute_val </B><DD>attribute value, unless flag is false
 
-<DT><B>flag </B><DD>false if no attribute is associated with the key (logical) 
+<DT><B>flag </B><DD>false if no attribute is associated with the key (logical)
 </DL>
 <P>
 <H2>Notes</H2>
 The following attributes are predefined for all MPI Window objects:
 <P>
 <DL>
-<DT><B>MPI_WIN_BASE </B><DD>window base address. 
+<DT><B>MPI_WIN_BASE </B><DD>window base address.
 
-<DT><B>MPI_WIN_SIZE </B><DD>window size, in bytes. 
+<DT><B>MPI_WIN_SIZE </B><DD>window size, in bytes.
 
-<DT><B>MPI_WIN_DISP_UNIT </B><DD>displacement unit associated with the window. 
+<DT><B>MPI_WIN_DISP_UNIT </B><DD>displacement unit associated with the window.
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -42,31 +41,31 @@ The following attributes are predefined for all MPI Window objects:
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -76,7 +75,7 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_KEYVAL </B> <DD> Invalid keyval
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_get_errhandler.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_get_errhandler.html
index 052d024c..68d41be1 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_get_errhandler.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_get_errhandler.html
@@ -9,14 +9,14 @@
 Get the error handler for the MPI RMA window 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Win_get_errhandler(MPI_Win win, MPI_Errhandler *errhandler)
+int MPI_Win_get_errhandler(MPI_Win win, MPI_Errhandler * errhandler)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>win </B> <DD> window (handle) 
+<DL><DT><B>win </B> <DD> window (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>errhandler </B> <DD> error handler currently associated with window (handle) 
+<DL><DT><B>errhandler </B> <DD> error handler currently associated with window (handle)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -24,31 +24,31 @@ int MPI_Win_get_errhandler(MPI_Win win, MPI_Errhandler *errhandler)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -56,7 +56,7 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_get_group.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_get_group.html
index a017af8b..28528920 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_get_group.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_get_group.html
@@ -9,52 +9,52 @@
 Get the MPI Group of the window object 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Win_get_group(MPI_Win win, MPI_Group *group)
+int MPI_Win_get_group(MPI_Win win, MPI_Group * group)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>win </B> <DD> window object (handle) 
+<DL><DT><B>win </B> <DD> window object (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>group </B> <DD> group of processes which share access to the window (handle) 
+<DL><DT><B>group </B> <DD> group of processes which share access to the window (handle)
 </DL>
 <P>
 <H2>Notes</H2>
 The group is a duplicate of the group from the communicator used to
-create the MPI window, and should be freed with <tt>MPI_Group_free</tt> when
+create the MPI window, and should be freed with <TT>MPI_Group_free</TT> when
 it is no longer needed.  This group can be used to form the group of
-neighbors for the routines <tt>MPI_Win_post</tt> and <tt>MPI_Win_start</tt>.
+neighbors for the routines <TT>MPI_Win_post</TT> and <TT>MPI_Win_start</TT>.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -63,9 +63,9 @@ possible.
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_get_info.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_get_info.html
index 746e8165..251cfb1c 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_get_info.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_get_info.html
@@ -9,13 +9,13 @@
 Returns a new info object containing the hints of the window associated with win. 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Win_get_info(MPI_Win win, MPI_Info *info_used)
+int MPI_Win_get_info(MPI_Win win, MPI_Info * info_used)
 </PRE>
 <P>
 The current setting of all hints actually used by the system related to this
 window is returned in info_used. If no such hints exist, a handle to a newly
 created info object is returned that contains no key/value pair. The user is
-responsible for freeing info_used via <tt>MPI_Info_free</tt>.
+responsible for freeing info_used via <TT>MPI_Info_free</TT>.
 <P>
 <H2>Input Parameters</H2>
 <DL><DT><B>win </B> <DD> window object (handle)
@@ -38,47 +38,47 @@ set.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
 </DL>
 <DL><DT><B>MPI_ERR_INFO </B> <DD> Invalid Info 
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Win_set_info
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_get_name.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_get_name.html
index 185a224b..7eb28e54 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_get_name.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_get_name.html
@@ -12,15 +12,15 @@ Get the print name associated with the MPI RMA window
 int MPI_Win_get_name(MPI_Win win, char *win_name, int *resultlen)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>win </B> <DD> window whose name is to be returned (handle) 
+<DL><DT><B>win </B> <DD> window whose name is to be returned (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
 <DL>
-<DT><B>win_name </B><DD>the name previously stored on the window, or a empty string if 
-no such name exists (string) 
+<DT><B>win_name </B><DD>the name previously stored on the window, or a empty string if
+no such name exists (string)
 
-<DT><B>resultlen </B><DD>length of returned name (integer) 
+<DT><B>resultlen </B><DD>length of returned name (integer)
 </DL>
 <P>
 <P>
@@ -33,33 +33,33 @@ with this routine.
 The MPI standard defined a thread-safe interface but this does not
 mean that all routines may be called without any thread locks.  For
 example, two threads must not attempt to change the contents of the
-same <tt>MPI_Info</tt> object concurrently.  The user is responsible in this
+same <TT>MPI_Info</TT> object concurrently.  The user is responsible in this
 case for using some mechanism, such as thread locks, to ensure that
 only one thread at a time makes use of this routine.
 <P>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -67,10 +67,10 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_lock.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_lock.html
index 1df2343c..7fc01d34 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_lock.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_lock.html
@@ -13,15 +13,15 @@ int MPI_Win_lock(int lock_type, int rank, int assert, MPI_Win win)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>lock_type </B><DD>Indicates whether other processes may access the target 
-window at the same time (if <tt>MPI_LOCK_SHARED</tt>) or not (<tt>MPI_LOCK_EXCLUSIVE</tt>)
+<DT><B>lock_type </B><DD>Indicates whether other processes may access the target
+window at the same time (if <TT>MPI_LOCK_SHARED</TT>) or not (<TT>MPI_LOCK_EXCLUSIVE</TT>)
 
-<DT><B>rank </B><DD>rank of locked window (nonnegative integer) 
+<DT><B>rank </B><DD>rank of locked window (nonnegative integer)
 
 <DT><B>assert </B><DD>Used to optimize this call; zero may be used as a default.
-See notes. (integer) 
+See notes. (integer)
 
-<DT><B>win </B><DD>window object (handle) 
+<DT><B>win </B><DD>window object (handle)
 </DL>
 <P>
 <H2>Notes</H2>
@@ -32,19 +32,19 @@ process.
 <P>
 Implementations may restrict the use of RMA communication that is
 synchronized
-by lock calls to windows in memory allocated by <tt>MPI_Alloc_mem</tt>. Locks can
+by lock calls to windows in memory allocated by <TT>MPI_Alloc_mem</TT>. Locks can
 be used portably only in such memory.
 <P>
-The <tt>assert</tt> argument is used to indicate special conditions for the
-fence that an implementation may use to optimize the <tt>MPI_Win_lock
-</tt>operation.  The value zero is always correct.  Other assertion values
-may be or'ed together.  Assertions that are valid for <tt>MPI_Win_lock</tt> are:
+The <TT>assert</TT> argument is used to indicate special conditions for the
+fence that an implementation may use to optimize the <TT>MPI_Win_lock
+</TT>operation.  The value zero is always correct.  Other assertion values
+may be or'ed together.  Assertions that are valid for <TT>MPI_Win_lock</TT> are:
 <P>
-<DL><DT><B>MPI_MODE_NOCHECK </B> <DD> no other process holds, or will attempt to acquire a 
-conflicting lock, while the caller holds the window lock. This is useful 
-when mutual exclusion is achieved by other means, but the coherence 
-operations that may be attached to the lock and unlock calls are still 
-required. 
+<DL><DT><B>MPI_MODE_NOCHECK </B> <DD> no other process holds, or will attempt to acquire a
+conflicting lock, while the caller holds the window lock. This is useful
+when mutual exclusion is achieved by other means, but the coherence
+operations that may be attached to the lock and unlock calls are still
+required.
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -52,31 +52,31 @@ required.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -84,11 +84,11 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_lock_all.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_lock_all.html
index 5571f407..ef44acd4 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_lock_all.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_lock_all.html
@@ -13,9 +13,9 @@ int MPI_Win_lock_all(int assert, MPI_Win win)
 </PRE>
 <P>
 Starts an RMA access epoch to all processes in win, with a lock type of
-<tt>MPI_Lock_shared</tt>. During the epoch, the calling process can access the window
+<TT>MPI_Lock_shared</TT>. During the epoch, the calling process can access the window
 memory on all processes in win by using RMA operations. A window locked with
-<tt>MPI_Win_lock_all</tt> must be unlocked with <tt>MPI_Win_unlock_all</tt>. This routine is not
+<TT>MPI_Win_lock_all</TT> must be unlocked with <TT>MPI_Win_unlock_all</TT>. This routine is not
 collective -- the ALL refers to a lock on all members of the group of the
 window.
 <P>
@@ -31,52 +31,52 @@ See notes. (integer)
 <P>
 This call is not collective.
 <P>
-The <tt>assert</tt> argument is used to indicate special conditions for the fence that
-an implementation may use to optimize the <tt>MPI_Win_lock_all</tt> operation.  The
+The <TT>assert</TT> argument is used to indicate special conditions for the fence that
+an implementation may use to optimize the <TT>MPI_Win_lock_all</TT> operation.  The
 value zero is always correct.  Other assertion values may be or'ed together.
-Assertions that are valid for <tt>MPI_Win_lock_all</tt> are:
+Assertions that are valid for <TT>MPI_Win_lock_all</TT> are:
 <P>
-<DL><DT><B><tt>MPI_MODE_NOCHECK</tt> </B> <DD> No other process holds, or will attempt to acquire a
+<DL><DT><B><TT>MPI_MODE_NOCHECK</TT> </B> <DD> No other process holds, or will attempt to acquire a
 conflicting lock, while the caller holds the window lock. This is useful
 when mutual exclusion is achieved by other means, but the coherence
 operations that may be attached to the lock and unlock calls are still
 required.
 </DL>
 <P>
-There may be additional overheads associated with using <tt>MPI_Win_lock</tt> and
-<tt>MPI_Win_lock_all</tt> concurrently on the same window. These overheads could be
-avoided by specifying the assertion <tt>MPI_MODE_NOCHECK</tt> when possible
+There may be additional overheads associated with using <TT>MPI_Win_lock</TT> and
+<TT>MPI_Win_lock_all</TT> concurrently on the same window. These overheads could be
+avoided by specifying the assertion <TT>MPI_MODE_NOCHECK</TT> when possible
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -84,15 +84,15 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Win_unlock_all
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_post.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_post.html
index 21160c84..1af2eb3a 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_post.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_post.html
@@ -13,57 +13,57 @@ int MPI_Win_post(MPI_Group group, int assert, MPI_Win win)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>group </B><DD>group of origin processes (handle) 
+<DT><B>group </B><DD>group of origin processes (handle)
 
 <DT><B>assert </B><DD>Used to optimize this call; zero may be used as a default.
-See notes. (integer) 
+See notes. (integer)
 
-<DT><B>win </B><DD>window object (handle) 
+<DT><B>win </B><DD>window object (handle)
 </DL>
 <P>
 <H2>Notes</H2>
-The <tt>assert</tt> argument is used to indicate special conditions for the
-fence that an implementation may use to optimize the <tt>MPI_Win_post
-</tt>operation.  The value zero is always correct.  Other assertion values
-may be or'ed together.  Assertions that are valid for <tt>MPI_Win_post</tt> are:
+The <TT>assert</TT> argument is used to indicate special conditions for the
+fence that an implementation may use to optimize the <TT>MPI_Win_post
+</TT>operation.  The value zero is always correct.  Other assertion values
+may be or'ed together.  Assertions that are valid for <TT>MPI_Win_post</TT> are:
 <P>
 <DL>
-<DT><B>MPI_MODE_NOCHECK </B><DD>the matching calls to <tt>MPI_WIN_START</tt> have not yet 
-occurred on any origin processes when the call to <tt>MPI_WIN_POST</tt> is made. 
-The nocheck option can be specified by a post call if and only if it is 
-specified by each matching start call. 
+<DT><B>MPI_MODE_NOCHECK </B><DD>the matching calls to <TT>MPI_WIN_START</TT> have not yet
+occurred on any origin processes when the call to <TT>MPI_WIN_POST</TT> is made.
+The nocheck option can be specified by a post call if and only if it is
+specified by each matching start call.
 
-<DT><B>MPI_MODE_NOSTORE </B><DD>the local window was not updated by local stores (or 
-local get or receive calls) since last synchronization. This may avoid 
-the need for cache synchronization at the post call. 
+<DT><B>MPI_MODE_NOSTORE </B><DD>the local window was not updated by local stores (or
+local get or receive calls) since last synchronization. This may avoid
+the need for cache synchronization at the post call.
 
-<DT><B>MPI_MODE_NOPUT </B><DD>the local window will not be updated by put or accumulate 
-calls after the post call, until the ensuing (wait) synchronization. This 
-may avoid the need for cache synchronization at the wait call. 
+<DT><B>MPI_MODE_NOPUT </B><DD>the local window will not be updated by put or accumulate
+calls after the post call, until the ensuing (wait) synchronization. This
+may avoid the need for cache synchronization at the wait call.
 </DL>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_set_attr.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_set_attr.html
index f8b6e510..7acf4cfa 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_set_attr.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_set_attr.html
@@ -13,17 +13,17 @@ int MPI_Win_set_attr(MPI_Win win, int win_keyval, void *attribute_val)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>win </B><DD>MPI window object to which attribute will be attached (handle) 
+<DT><B>win </B><DD>MPI window object to which attribute will be attached (handle)
 
-<DT><B>win_keyval </B><DD>key value, as returned by  <tt>MPI_Win_create_keyval</tt> (integer)
+<DT><B>win_keyval </B><DD>key value, as returned by  <TT>MPI_Win_create_keyval</TT> (integer)
 
-<DT><B>attribute_val </B><DD>attribute value 
+<DT><B>attribute_val </B><DD>attribute value
 </DL>
 <P>
 <H2>Notes</H2>
 <P>
 The type of the attribute value depends on whether C or Fortran is being used.
-In C, an attribute value is a pointer (<tt>void *</tt>); in Fortran, it is an
+In C, an attribute value is a pointer (<TT>void *</TT>); in Fortran, it is an
 address-sized integer.
 <P>
 If an attribute is already present, the delete function (specified when the
@@ -34,31 +34,31 @@ corresponding keyval was created) will be called.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_set_errhandler.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_set_errhandler.html
index e38c9af9..b69ef690 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_set_errhandler.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_set_errhandler.html
@@ -13,9 +13,9 @@ int MPI_Win_set_errhandler(MPI_Win win, MPI_Errhandler errhandler)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>win </B><DD>window (handle) 
+<DT><B>win </B><DD>window (handle)
 
-<DT><B>errhandler </B><DD>new error handler for window (handle) 
+<DT><B>errhandler </B><DD>new error handler for window (handle)
 </DL>
 <P>
 <P>
@@ -28,33 +28,33 @@ with this routine.
 The MPI standard defined a thread-safe interface but this does not
 mean that all routines may be called without any thread locks.  For
 example, two threads must not attempt to change the contents of the
-same <tt>MPI_Info</tt> object concurrently.  The user is responsible in this
+same <TT>MPI_Info</TT> object concurrently.  The user is responsible in this
 case for using some mechanism, such as thread locks, to ensure that
 only one thread at a time makes use of this routine.
 <P>
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_set_info.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_set_info.html
index dfcc8be2..0ab8cd83 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_set_info.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_set_info.html
@@ -36,47 +36,47 @@ call.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
 </DL>
 <DL><DT><B>MPI_ERR_INFO </B> <DD> Invalid Info 
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Win_get_info
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_set_name.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_set_name.html
index 67941a11..a86ea77c 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_set_name.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_set_name.html
@@ -13,9 +13,9 @@ int MPI_Win_set_name(MPI_Win win, const char *win_name)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>win </B><DD>window whose identifier is to be set (handle) 
+<DT><B>win </B><DD>window whose identifier is to be set (handle)
 
-<DT><B>win_name </B><DD>the character string which is remembered as the name (string) 
+<DT><B>win_name </B><DD>the character string which is remembered as the name (string)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -23,31 +23,31 @@ int MPI_Win_set_name(MPI_Win win, const char *win_name)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -55,10 +55,10 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_shared_query.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_shared_query.html
index fa51a01b..054bfdc3 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_shared_query.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_shared_query.html
@@ -9,22 +9,22 @@
 Query the size and base pointer for a patch of a shared memory window. 
 <H2>Synopsis</H2>
 <PRE>
-int MPI_Win_shared_query(MPI_Win win, int rank, MPI_Aint *size, int *disp_unit, void *baseptr)
+int MPI_Win_shared_query(MPI_Win win, int rank, MPI_Aint * size, int *disp_unit, void *baseptr)
 </PRE>
 <P>
 This function queries the process-local address for remote memory segments
-created with <tt>MPI_Win_allocate_shared</tt>. This function can return different
+created with <TT>MPI_Win_allocate_shared</TT>. This function can return different
 process-local addresses for the same physical memory on different processes.
 <P>
 The returned memory can be used for load/store accesses subject to the
 constraints defined in MPI 3.0, Section 11.7. This function can only be called
-with windows of type <tt>MPI_Win_flavor_shared</tt>. If the passed window is not of
-flavor <tt>MPI_Win_flavor_shared</tt>, the error <tt>MPI_ERR_RMA_FLAVOR</tt> is raised. When rank
-is <tt>MPI_PROC_NULL</tt>, the pointer, disp_unit, and size returned are the pointer,
+with windows of type <TT>MPI_Win_flavor_shared</TT>. If the passed window is not of
+flavor <TT>MPI_Win_flavor_shared</TT>, the error <TT>MPI_ERR_RMA_FLAVOR</TT> is raised. When rank
+is <TT>MPI_PROC_NULL</TT>, the pointer, disp_unit, and size returned are the pointer,
 disp_unit, and size of the memory segment belonging the lowest rank that
 specified size &gt; 0. If all processes in the group attached to the window
 specified size = 0, then the call returns size = 0 and a baseptr as if
-<tt>MPI_Alloc_mem</tt> was called with size = 0.
+<TT>MPI_Alloc_mem</TT> was called with size = 0.
 <P>
 <H2>Input Parameters</H2>
 <DL>
@@ -48,47 +48,47 @@ segment belonging to the target rank.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
 <DL><DT><B>MPI_SUCCESS </B> <DD> No error; MPI routine completed successfully.
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Win_allocate_shared
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_start.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_start.html
index 2e4bef41..777da4c2 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_start.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_start.html
@@ -13,27 +13,27 @@ int MPI_Win_start(MPI_Group group, int assert, MPI_Win win)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>group </B><DD>group of target processes (handle) 
+<DT><B>group </B><DD>group of target processes (handle)
 
 <DT><B>assert </B><DD>Used to optimize this call; zero may be used as a default.
-See notes. (integer) 
+See notes. (integer)
 
-<DT><B>win </B><DD>window object (handle) 
+<DT><B>win </B><DD>window object (handle)
 </DL>
 <P>
 <H2>Notes</H2>
-The <tt>assert</tt> argument is used to indicate special conditions for the
-fence that an implementation may use to optimize the <tt>MPI_Win_start
-</tt>operation.  The value zero is always correct.  Other assertion values
-may be or'ed together.  Assertions tha are valid for <tt>MPI_Win_start</tt> are:
+The <TT>assert</TT> argument is used to indicate special conditions for the
+fence that an implementation may use to optimize the <TT>MPI_Win_start
+</TT>operation.  The value zero is always correct.  Other assertion values
+may be or'ed together.  Assertions tha are valid for <TT>MPI_Win_start</TT> are:
 <P>
-<DL><DT><B>MPI_MODE_NOCHECK </B> <DD> the matching calls to <tt>MPI_WIN_POST</tt> have already 
-completed on all target processes when the call to <tt>MPI_WIN_START</tt> is made. 
-The nocheck option can be specified in a start call if and only if it is 
-specified in each matching post call. This is similar to the optimization 
-of ready-send that may save a handshake when the handshake is implicit in 
-the code. (However, ready-send is matched by a regular receive, whereas 
-both start and post must specify the nocheck option.) 
+<DL><DT><B>MPI_MODE_NOCHECK </B> <DD> the matching calls to <TT>MPI_WIN_POST</TT> have already
+completed on all target processes when the call to <TT>MPI_WIN_START</TT> is made.
+The nocheck option can be specified in a start call if and only if it is
+specified in each matching post call. This is similar to the optimization
+of ready-send that may save a handshake when the handshake is implicit in
+the code. (However, ready-send is matched by a regular receive, whereas
+both start and post must specify the nocheck option.)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -41,31 +41,31 @@ both start and post must specify the nocheck option.)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -73,7 +73,7 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_sync.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_sync.html
index f755f046..6a9ff2e7 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_sync.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_sync.html
@@ -12,9 +12,9 @@ Synchronize public and private copies of the given window.
 int MPI_Win_sync(MPI_Win win)
 </PRE>
 <P>
-The call <tt>MPI_Win_sync</tt> synchronizes the private and public window copies of win.
-For the purposes of synchronizing the private and public window, <tt>MPI_Win_sync
-</tt>has the effect of ending and reopening an access and exposure epoch on the
+The call <TT>MPI_Win_sync</TT> synchronizes the private and public window copies of win.
+For the purposes of synchronizing the private and public window, <TT>MPI_Win_sync
+</TT>has the effect of ending and reopening an access and exposure epoch on the
 window (note that it does not actually end an epoch or complete any pending MPI
 RMA operations).
 <P>
@@ -27,31 +27,31 @@ RMA operations).
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -59,15 +59,15 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Win_flush MPI_Win_flush_all MPI_Win_flush_local MPI_Win_flush_local_all
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_test.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_test.html
index 8ab8812c..70edfde7 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_test.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_test.html
@@ -12,46 +12,46 @@ Test whether an RMA exposure epoch has completed
 int MPI_Win_test(MPI_Win win, int *flag)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>win </B> <DD> window object (handle) 
+<DL><DT><B>win </B> <DD> window object (handle)
 </DL>
 <P>
 <H2>Output Parameters</H2>
-<DL><DT><B>flag </B> <DD> success flag (logical) 
+<DL><DT><B>flag </B> <DD> success flag (logical)
 </DL>
 <P>
 <H2>Notes</H2>
-This is the nonblocking version of <tt>MPI_Win_wait</tt>.
+This is the nonblocking version of <TT>MPI_Win_wait</TT>.
 <P>
 <H2>Thread and Interrupt Safety</H2>
 <P>
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -59,14 +59,14 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 <DL><DT><B>MPI_ERR_ARG </B> <DD> Invalid argument.  Some argument is invalid and is not
-identified by a specific error class (e.g., <tt>MPI_ERR_RANK</tt>).
+identified by a specific error class (e.g., <TT>MPI_ERR_RANK</TT>).
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Win_wait, MPI_Win_post
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_unlock.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_unlock.html
index e4fbfce0..caeb67ad 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_unlock.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_unlock.html
@@ -13,9 +13,9 @@ int MPI_Win_unlock(int rank, MPI_Win win)
 </PRE>
 <H2>Input Parameters</H2>
 <DL>
-<DT><B>rank </B><DD>rank of window (nonnegative integer) 
+<DT><B>rank </B><DD>rank of window (nonnegative integer)
 
-<DT><B>win </B><DD>window object (handle) 
+<DT><B>win </B><DD>window object (handle)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -23,31 +23,31 @@ int MPI_Win_unlock(int rank, MPI_Win win)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -55,15 +55,15 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Win_lock
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_unlock_all.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_unlock_all.html
index 1cb8813d..fd2a9997 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_unlock_all.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_unlock_all.html
@@ -13,7 +13,7 @@ int MPI_Win_unlock_all(MPI_Win win)
 </PRE>
 <P>
 Completes a shared RMA access epoch started by a call to
-<tt>MPI_Win_lock_all</tt>. RMA operations issued during this epoch will
+<TT>MPI_Win_lock_all</TT>. RMA operations issued during this epoch will
 have completed both at the origin and at the target when the call returns.
 <P>
 <H2>Input Parameters</H2>
@@ -28,31 +28,31 @@ This call is not collective.
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -60,15 +60,15 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_RANK </B> <DD> Invalid source or destination rank.  Ranks must be between
 zero and the size of the communicator minus one; ranks in a receive
-(<tt>MPI_Recv</tt>, <tt>MPI_Irecv</tt>, <tt>MPI_Sendrecv</tt>, etc.) may also be <tt>MPI_ANY_SOURCE</tt>.
+(<TT>MPI_Recv</TT>, <TT>MPI_Irecv</TT>, <TT>MPI_Sendrecv</TT>, etc.) may also be <TT>MPI_ANY_SOURCE</TT>.
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
  MPI_Win_lock_all
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_wait.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_wait.html
index 3ac38a3e..8d1904f0 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_wait.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Win_wait.html
@@ -12,7 +12,7 @@ Completes an RMA exposure epoch begun with MPI_Win_post
 int MPI_Win_wait(MPI_Win win)
 </PRE>
 <H2>Input Parameters</H2>
-<DL><DT><B>win </B> <DD> window object (handle) 
+<DL><DT><B>win </B> <DD> window object (handle)
 </DL>
 <P>
 <H2>Thread and Interrupt Safety</H2>
@@ -20,31 +20,31 @@ int MPI_Win_wait(MPI_Win win)
 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 <tt>malloc
-</tt>or other non-MPICH runtime routines that are themselves not interrupt-safe.
+this is due to the use of memory allocation routines such as <TT>malloc
+</TT>or other non-MPICH runtime routines that are themselves not interrupt-safe.
 <P>
 <H2>Notes for Fortran</H2>
-All MPI routines in Fortran (except for <tt>MPI_WTIME</tt> and <tt>MPI_WTICK</tt>) have
-an additional argument <tt>ierr</tt> at the end of the argument list.  <tt>ierr
-</tt>is an integer and has the same meaning as the return value of the routine
+All MPI routines in Fortran (except for <TT>MPI_WTIME</TT> and <TT>MPI_WTICK</TT>) have
+an additional argument <TT>ierr</TT> at the end of the argument list.  <TT>ierr
+</TT>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
-<tt>call</tt> statement.
+<TT>call</TT> statement.
 <P>
-All MPI objects (e.g., <tt>MPI_Datatype</tt>, <tt>MPI_Comm</tt>) are of type <tt>INTEGER
-</tt>in Fortran.
+All MPI objects (e.g., <TT>MPI_Datatype</TT>, <TT>MPI_Comm</TT>) are of type <TT>INTEGER
+</TT>in Fortran.
 <P>
 <H2>Errors</H2>
 <P>
-All MPI routines (except <tt>MPI_Wtime</tt> and <tt>MPI_Wtick</tt>) return an error value;
+All MPI routines (except <TT>MPI_Wtime</TT> and <TT>MPI_Wtick</TT>) 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 <tt>MPI_Comm_set_errhandler</tt> (for communicators),
-<tt>MPI_File_set_errhandler</tt> (for files), and <tt>MPI_Win_set_errhandler</tt> (for
-RMA windows).  The MPI-1 routine <tt>MPI_Errhandler_set</tt> may be used but
+may be changed with <TT>MPI_Comm_set_errhandler</TT> (for communicators),
+<TT>MPI_File_set_errhandler</TT> (for files), and <TT>MPI_Win_set_errhandler</TT> (for
+RMA windows).  The MPI-1 routine <TT>MPI_Errhandler_set</TT> may be used but
 its use is deprecated.  The predefined error handler
-<tt>MPI_ERRORS_RETURN</tt> may be used to cause error values to be returned.
-Note that MPI does <em>not</em> guarentee that an MPI program can continue past
+<TT>MPI_ERRORS_RETURN</TT> may be used to cause error values to be returned.
+Note that MPI does <EM>not</EM> guarentee that an MPI program can continue past
 an error; however, MPI implementations will attempt to continue whenever
 possible.
 <P>
@@ -52,7 +52,7 @@ possible.
 </DL>
 <DL><DT><B>MPI_ERR_WIN </B> <DD> Invalid MPI window object
 </DL>
-<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <tt>MPI_Error_string</tt> to get more information
+<DL><DT><B>MPI_ERR_OTHER </B> <DD> Other error; use <TT>MPI_Error_string</TT> to get more information
 about this error code. 
 </DL>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Wtick.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Wtick.html
index 284e9083..1bf3876a 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Wtick.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Wtick.html
@@ -9,15 +9,15 @@
 Returns the resolution of MPI_Wtime 
 <H2>Synopsis</H2>
 <PRE>
-double MPI_Wtick( void )
+double MPI_Wtick(void)
 </PRE>
 <H2>Return value</H2>
 Time in seconds of resolution of MPI_Wtime
 <P>
 <H2>Notes for Fortran</H2>
-This is a function, declared as <tt>DOUBLE PRECISION MPI_WTICK()</tt> in Fortran.
+This is a function, declared as <TT>DOUBLE PRECISION MPI_WTICK()</TT> in Fortran.
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
 also: MPI_Wtime, MPI_Comm_get_attr, MPI_Attr_get
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Wtime.html b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Wtime.html
index 12066c22..0da7ae06 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Wtime.html
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/MPI_Wtime.html
@@ -9,21 +9,21 @@
 Returns an elapsed time on the calling processor 
 <H2>Synopsis</H2>
 <PRE>
-double MPI_Wtime( void )
+double MPI_Wtime(void)
 </PRE>
 <H2>Return value</H2>
 Time in seconds since an arbitrary time in the past.
 <P>
 <H2>Notes</H2>
 This is intended to be a high-resolution, elapsed (or wall) clock.
-See <tt>MPI_WTICK</tt> to determine the resolution of <tt>MPI_WTIME</tt>.
-If the attribute <tt>MPI_WTIME_IS_GLOBAL</tt> is defined and true, then the
-value is synchronized across all processes in <tt>MPI_COMM_WORLD</tt>.
+See <TT>MPI_WTICK</TT> to determine the resolution of <TT>MPI_WTIME</TT>.
+If the attribute <TT>MPI_WTIME_IS_GLOBAL</TT> is defined and true, then the
+value is synchronized across all processes in <TT>MPI_COMM_WORLD</TT>.
 <P>
 <H2>Notes for Fortran</H2>
-This is a function, declared as <tt>DOUBLE PRECISION MPI_WTIME()</tt> in Fortran.
+This is a function, declared as <TT>DOUBLE PRECISION MPI_WTIME()</TT> in Fortran.
 <P>
-<H0>See Also</H0>
+<H2>See Also</H2>
 also: MPI_Wtick, MPI_Comm_get_attr, MPI_Attr_get
-<br>
+<BR>
 </BODY></HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/index.htm b/linx64/mpi/mpich/share/doc/mpich/www3/index.htm
index 48ccd264..1679df39 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/index.htm
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/index.htm
@@ -1,539 +1,551 @@
-<HTML>
-<HEAD>
-<TITLE>Web pages for MPI Routines and Constants</TITLE>
-<!-- This file generated by createhtmlindex on  -->
-</HEAD>
-<BODY BGCOLOR="FFFFFF">
-<H1>Web pages for MPI Routines and Constants</H1>
-<TABLE>
-<TR><TD><A HREF="Constants.html">Constants</A></TD>
-<TD><A HREF="MPI_File_set_atomicity.html">MPI_File_set_atomicity</A></TD>
-<TD><A HREF="MPI_Rput.html">MPI_Rput</A></TD>
-</TR>
-<TR><TD><A HREF="MPIX_Comm_agree.html">MPIX_Comm_agree</A></TD>
-<TD><A HREF="MPI_File_set_errhandler.html">MPI_File_set_errhandler</A></TD>
-<TD><A HREF="MPI_Rsend.html">MPI_Rsend</A></TD>
-</TR>
-<TR><TD><A HREF="MPIX_Comm_failure_ack.html">MPIX_Comm_failure_ack</A></TD>
-<TD><A HREF="MPI_File_set_info.html">MPI_File_set_info</A></TD>
-<TD><A HREF="MPI_Rsend_init.html">MPI_Rsend_init</A></TD>
-</TR>
-<TR><TD><A HREF="MPIX_Comm_failure_get_acked.html">MPIX_Comm_failure_get_acked</A></TD>
-<TD><A HREF="MPI_File_set_size.html">MPI_File_set_size</A></TD>
-<TD><A HREF="MPI_Scan.html">MPI_Scan</A></TD>
-</TR>
-<TR><TD><A HREF="MPIX_Comm_revoke.html">MPIX_Comm_revoke</A></TD>
-<TD><A HREF="MPI_File_set_view.html">MPI_File_set_view</A></TD>
-<TD><A HREF="MPI_Scatter.html">MPI_Scatter</A></TD>
-</TR>
-<TR><TD><A HREF="MPIX_Comm_shrink.html">MPIX_Comm_shrink</A></TD>
-<TD><A HREF="MPI_File_sync.html">MPI_File_sync</A></TD>
-<TD><A HREF="MPI_Scatterv.html">MPI_Scatterv</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Abort.html">MPI_Abort</A></TD>
-<TD><A HREF="MPI_File_write.html">MPI_File_write</A></TD>
-<TD><A HREF="MPI_Send.html">MPI_Send</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Accumulate.html">MPI_Accumulate</A></TD>
-<TD><A HREF="MPI_File_write_all.html">MPI_File_write_all</A></TD>
-<TD><A HREF="MPI_Send_init.html">MPI_Send_init</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Add_error_class.html">MPI_Add_error_class</A></TD>
-<TD><A HREF="MPI_File_write_all_begin.html">MPI_File_write_all_begin</A></TD>
-<TD><A HREF="MPI_Sendrecv.html">MPI_Sendrecv</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Add_error_code.html">MPI_Add_error_code</A></TD>
-<TD><A HREF="MPI_File_write_all_end.html">MPI_File_write_all_end</A></TD>
-<TD><A HREF="MPI_Sendrecv_replace.html">MPI_Sendrecv_replace</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Add_error_string.html">MPI_Add_error_string</A></TD>
-<TD><A HREF="MPI_File_write_at.html">MPI_File_write_at</A></TD>
-<TD><A HREF="MPI_Ssend.html">MPI_Ssend</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Address.html">MPI_Address</A></TD>
-<TD><A HREF="MPI_File_write_at_all.html">MPI_File_write_at_all</A></TD>
-<TD><A HREF="MPI_Ssend_init.html">MPI_Ssend_init</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Aint_add.html">MPI_Aint_add</A></TD>
-<TD><A HREF="MPI_File_write_at_all_begin.html">MPI_File_write_at_all_begin</A></TD>
-<TD><A HREF="MPI_Start.html">MPI_Start</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Aint_diff.html">MPI_Aint_diff</A></TD>
-<TD><A HREF="MPI_File_write_at_all_end.html">MPI_File_write_at_all_end</A></TD>
-<TD><A HREF="MPI_Startall.html">MPI_Startall</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Allgather.html">MPI_Allgather</A></TD>
-<TD><A HREF="MPI_File_write_ordered.html">MPI_File_write_ordered</A></TD>
-<TD><A HREF="MPI_Status_set_cancelled.html">MPI_Status_set_cancelled</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Allgatherv.html">MPI_Allgatherv</A></TD>
-<TD><A HREF="MPI_File_write_ordered_begin.html">MPI_File_write_ordered_begin</A></TD>
-<TD><A HREF="MPI_Status_set_elements.html">MPI_Status_set_elements</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Alloc_mem.html">MPI_Alloc_mem</A></TD>
-<TD><A HREF="MPI_File_write_ordered_end.html">MPI_File_write_ordered_end</A></TD>
-<TD><A HREF="MPI_Status_set_elements_x.html">MPI_Status_set_elements_x</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Allreduce.html">MPI_Allreduce</A></TD>
-<TD><A HREF="MPI_File_write_shared.html">MPI_File_write_shared</A></TD>
-<TD><A HREF="MPI_T_category_changed.html">MPI_T_category_changed</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Alltoall.html">MPI_Alltoall</A></TD>
-<TD><A HREF="MPI_Finalize.html">MPI_Finalize</A></TD>
-<TD><A HREF="MPI_T_category_get_categories.html">MPI_T_category_get_categories</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Alltoallv.html">MPI_Alltoallv</A></TD>
-<TD><A HREF="MPI_Finalized.html">MPI_Finalized</A></TD>
-<TD><A HREF="MPI_T_category_get_cvars.html">MPI_T_category_get_cvars</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Alltoallw.html">MPI_Alltoallw</A></TD>
-<TD><A HREF="MPI_Free_mem.html">MPI_Free_mem</A></TD>
-<TD><A HREF="MPI_T_category_get_info.html">MPI_T_category_get_info</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Attr_delete.html">MPI_Attr_delete</A></TD>
-<TD><A HREF="MPI_Gather.html">MPI_Gather</A></TD>
-<TD><A HREF="MPI_T_category_get_num.html">MPI_T_category_get_num</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Attr_get.html">MPI_Attr_get</A></TD>
-<TD><A HREF="MPI_Gatherv.html">MPI_Gatherv</A></TD>
-<TD><A HREF="MPI_T_category_get_pvars.html">MPI_T_category_get_pvars</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Attr_put.html">MPI_Attr_put</A></TD>
-<TD><A HREF="MPI_Get.html">MPI_Get</A></TD>
-<TD><A HREF="MPI_T_cvar_get_info.html">MPI_T_cvar_get_info</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Barrier.html">MPI_Barrier</A></TD>
-<TD><A HREF="MPI_Get_accumulate.html">MPI_Get_accumulate</A></TD>
-<TD><A HREF="MPI_T_cvar_get_num.html">MPI_T_cvar_get_num</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Bcast.html">MPI_Bcast</A></TD>
-<TD><A HREF="MPI_Get_address.html">MPI_Get_address</A></TD>
-<TD><A HREF="MPI_T_cvar_handle_alloc.html">MPI_T_cvar_handle_alloc</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Bsend.html">MPI_Bsend</A></TD>
-<TD><A HREF="MPI_Get_count.html">MPI_Get_count</A></TD>
-<TD><A HREF="MPI_T_cvar_handle_free.html">MPI_T_cvar_handle_free</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Bsend_init.html">MPI_Bsend_init</A></TD>
-<TD><A HREF="MPI_Get_elements.html">MPI_Get_elements</A></TD>
-<TD><A HREF="MPI_T_cvar_read.html">MPI_T_cvar_read</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Buffer_attach.html">MPI_Buffer_attach</A></TD>
-<TD><A HREF="MPI_Get_elements_x.html">MPI_Get_elements_x</A></TD>
-<TD><A HREF="MPI_T_cvar_write.html">MPI_T_cvar_write</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Buffer_detach.html">MPI_Buffer_detach</A></TD>
-<TD><A HREF="MPI_Get_library_version.html">MPI_Get_library_version</A></TD>
-<TD><A HREF="MPI_T_enum_get_info.html">MPI_T_enum_get_info</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Cancel.html">MPI_Cancel</A></TD>
-<TD><A HREF="MPI_Get_processor_name.html">MPI_Get_processor_name</A></TD>
-<TD><A HREF="MPI_T_enum_get_item.html">MPI_T_enum_get_item</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Cart_coords.html">MPI_Cart_coords</A></TD>
-<TD><A HREF="MPI_Get_version.html">MPI_Get_version</A></TD>
-<TD><A HREF="MPI_T_finalize.html">MPI_T_finalize</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Cart_create.html">MPI_Cart_create</A></TD>
-<TD><A HREF="MPI_Graph_create.html">MPI_Graph_create</A></TD>
-<TD><A HREF="MPI_T_init_thread.html">MPI_T_init_thread</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Cart_get.html">MPI_Cart_get</A></TD>
-<TD><A HREF="MPI_Graph_get.html">MPI_Graph_get</A></TD>
-<TD><A HREF="MPI_T_pvar_get_info.html">MPI_T_pvar_get_info</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Cart_map.html">MPI_Cart_map</A></TD>
-<TD><A HREF="MPI_Graph_map.html">MPI_Graph_map</A></TD>
-<TD><A HREF="MPI_T_pvar_get_num.html">MPI_T_pvar_get_num</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Cart_rank.html">MPI_Cart_rank</A></TD>
-<TD><A HREF="MPI_Graph_neighbors.html">MPI_Graph_neighbors</A></TD>
-<TD><A HREF="MPI_T_pvar_handle_alloc.html">MPI_T_pvar_handle_alloc</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Cart_shift.html">MPI_Cart_shift</A></TD>
-<TD><A HREF="MPI_Graph_neighbors_count.html">MPI_Graph_neighbors_count</A></TD>
-<TD><A HREF="MPI_T_pvar_handle_free.html">MPI_T_pvar_handle_free</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Cart_sub.html">MPI_Cart_sub</A></TD>
-<TD><A HREF="MPI_Graphdims_get.html">MPI_Graphdims_get</A></TD>
-<TD><A HREF="MPI_T_pvar_read.html">MPI_T_pvar_read</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Cartdim_get.html">MPI_Cartdim_get</A></TD>
-<TD><A HREF="MPI_Grequest_complete.html">MPI_Grequest_complete</A></TD>
-<TD><A HREF="MPI_T_pvar_readreset.html">MPI_T_pvar_readreset</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Close_port.html">MPI_Close_port</A></TD>
-<TD><A HREF="MPI_Grequest_start.html">MPI_Grequest_start</A></TD>
-<TD><A HREF="MPI_T_pvar_reset.html">MPI_T_pvar_reset</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_accept.html">MPI_Comm_accept</A></TD>
-<TD><A HREF="MPI_Group_compare.html">MPI_Group_compare</A></TD>
-<TD><A HREF="MPI_T_pvar_session_create.html">MPI_T_pvar_session_create</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_call_errhandler.html">MPI_Comm_call_errhandler</A></TD>
-<TD><A HREF="MPI_Group_difference.html">MPI_Group_difference</A></TD>
-<TD><A HREF="MPI_T_pvar_session_free.html">MPI_T_pvar_session_free</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_compare.html">MPI_Comm_compare</A></TD>
-<TD><A HREF="MPI_Group_excl.html">MPI_Group_excl</A></TD>
-<TD><A HREF="MPI_T_pvar_start.html">MPI_T_pvar_start</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_connect.html">MPI_Comm_connect</A></TD>
-<TD><A HREF="MPI_Group_free.html">MPI_Group_free</A></TD>
-<TD><A HREF="MPI_T_pvar_stop.html">MPI_T_pvar_stop</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_create.html">MPI_Comm_create</A></TD>
-<TD><A HREF="MPI_Group_incl.html">MPI_Group_incl</A></TD>
-<TD><A HREF="MPI_T_pvar_write.html">MPI_T_pvar_write</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_create_errhandler.html">MPI_Comm_create_errhandler</A></TD>
-<TD><A HREF="MPI_Group_intersection.html">MPI_Group_intersection</A></TD>
-<TD><A HREF="MPI_Test.html">MPI_Test</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_create_group.html">MPI_Comm_create_group</A></TD>
-<TD><A HREF="MPI_Group_range_excl.html">MPI_Group_range_excl</A></TD>
-<TD><A HREF="MPI_Test_cancelled.html">MPI_Test_cancelled</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_create_keyval.html">MPI_Comm_create_keyval</A></TD>
-<TD><A HREF="MPI_Group_range_incl.html">MPI_Group_range_incl</A></TD>
-<TD><A HREF="MPI_Testall.html">MPI_Testall</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_delete_attr.html">MPI_Comm_delete_attr</A></TD>
-<TD><A HREF="MPI_Group_rank.html">MPI_Group_rank</A></TD>
-<TD><A HREF="MPI_Testany.html">MPI_Testany</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_disconnect.html">MPI_Comm_disconnect</A></TD>
-<TD><A HREF="MPI_Group_size.html">MPI_Group_size</A></TD>
-<TD><A HREF="MPI_Testsome.html">MPI_Testsome</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_dup.html">MPI_Comm_dup</A></TD>
-<TD><A HREF="MPI_Group_translate_ranks.html">MPI_Group_translate_ranks</A></TD>
-<TD><A HREF="MPI_Topo_test.html">MPI_Topo_test</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_dup_with_info.html">MPI_Comm_dup_with_info</A></TD>
-<TD><A HREF="MPI_Group_union.html">MPI_Group_union</A></TD>
-<TD><A HREF="MPI_Type_commit.html">MPI_Type_commit</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_free.html">MPI_Comm_free</A></TD>
-<TD><A HREF="MPI_Iallgather.html">MPI_Iallgather</A></TD>
-<TD><A HREF="MPI_Type_contiguous.html">MPI_Type_contiguous</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_free_keyval.html">MPI_Comm_free_keyval</A></TD>
-<TD><A HREF="MPI_Iallgatherv.html">MPI_Iallgatherv</A></TD>
-<TD><A HREF="MPI_Type_create_darray.html">MPI_Type_create_darray</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_get_attr.html">MPI_Comm_get_attr</A></TD>
-<TD><A HREF="MPI_Iallreduce.html">MPI_Iallreduce</A></TD>
-<TD><A HREF="MPI_Type_create_hindexed.html">MPI_Type_create_hindexed</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_get_errhandler.html">MPI_Comm_get_errhandler</A></TD>
-<TD><A HREF="MPI_Ialltoall.html">MPI_Ialltoall</A></TD>
-<TD><A HREF="MPI_Type_create_hindexed_block.html">MPI_Type_create_hindexed_block</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_get_info.html">MPI_Comm_get_info</A></TD>
-<TD><A HREF="MPI_Ialltoallv.html">MPI_Ialltoallv</A></TD>
-<TD><A HREF="MPI_Type_create_hvector.html">MPI_Type_create_hvector</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_get_name.html">MPI_Comm_get_name</A></TD>
-<TD><A HREF="MPI_Ialltoallw.html">MPI_Ialltoallw</A></TD>
-<TD><A HREF="MPI_Type_create_indexed_block.html">MPI_Type_create_indexed_block</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_get_parent.html">MPI_Comm_get_parent</A></TD>
-<TD><A HREF="MPI_Ibarrier.html">MPI_Ibarrier</A></TD>
-<TD><A HREF="MPI_Type_create_keyval.html">MPI_Type_create_keyval</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_group.html">MPI_Comm_group</A></TD>
-<TD><A HREF="MPI_Ibcast.html">MPI_Ibcast</A></TD>
-<TD><A HREF="MPI_Type_create_resized.html">MPI_Type_create_resized</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_idup.html">MPI_Comm_idup</A></TD>
-<TD><A HREF="MPI_Ibsend.html">MPI_Ibsend</A></TD>
-<TD><A HREF="MPI_Type_create_struct.html">MPI_Type_create_struct</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_join.html">MPI_Comm_join</A></TD>
-<TD><A HREF="MPI_Iexscan.html">MPI_Iexscan</A></TD>
-<TD><A HREF="MPI_Type_create_subarray.html">MPI_Type_create_subarray</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_rank.html">MPI_Comm_rank</A></TD>
-<TD><A HREF="MPI_Igather.html">MPI_Igather</A></TD>
-<TD><A HREF="MPI_Type_delete_attr.html">MPI_Type_delete_attr</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_remote_group.html">MPI_Comm_remote_group</A></TD>
-<TD><A HREF="MPI_Igatherv.html">MPI_Igatherv</A></TD>
-<TD><A HREF="MPI_Type_dup.html">MPI_Type_dup</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_remote_size.html">MPI_Comm_remote_size</A></TD>
-<TD><A HREF="MPI_Improbe.html">MPI_Improbe</A></TD>
-<TD><A HREF="MPI_Type_extent.html">MPI_Type_extent</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_set_attr.html">MPI_Comm_set_attr</A></TD>
-<TD><A HREF="MPI_Imrecv.html">MPI_Imrecv</A></TD>
-<TD><A HREF="MPI_Type_free.html">MPI_Type_free</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_set_errhandler.html">MPI_Comm_set_errhandler</A></TD>
-<TD><A HREF="MPI_Ineighbor_allgather.html">MPI_Ineighbor_allgather</A></TD>
-<TD><A HREF="MPI_Type_free_keyval.html">MPI_Type_free_keyval</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_set_info.html">MPI_Comm_set_info</A></TD>
-<TD><A HREF="MPI_Ineighbor_allgatherv.html">MPI_Ineighbor_allgatherv</A></TD>
-<TD><A HREF="MPI_Type_get_attr.html">MPI_Type_get_attr</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_set_name.html">MPI_Comm_set_name</A></TD>
-<TD><A HREF="MPI_Ineighbor_alltoall.html">MPI_Ineighbor_alltoall</A></TD>
-<TD><A HREF="MPI_Type_get_contents.html">MPI_Type_get_contents</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_size.html">MPI_Comm_size</A></TD>
-<TD><A HREF="MPI_Ineighbor_alltoallv.html">MPI_Ineighbor_alltoallv</A></TD>
-<TD><A HREF="MPI_Type_get_envelope.html">MPI_Type_get_envelope</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_spawn.html">MPI_Comm_spawn</A></TD>
-<TD><A HREF="MPI_Ineighbor_alltoallw.html">MPI_Ineighbor_alltoallw</A></TD>
-<TD><A HREF="MPI_Type_get_extent.html">MPI_Type_get_extent</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_spawn_multiple.html">MPI_Comm_spawn_multiple</A></TD>
-<TD><A HREF="MPI_Info_create.html">MPI_Info_create</A></TD>
-<TD><A HREF="MPI_Type_get_extent_x.html">MPI_Type_get_extent_x</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_split.html">MPI_Comm_split</A></TD>
-<TD><A HREF="MPI_Info_delete.html">MPI_Info_delete</A></TD>
-<TD><A HREF="MPI_Type_get_name.html">MPI_Type_get_name</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_split_type.html">MPI_Comm_split_type</A></TD>
-<TD><A HREF="MPI_Info_dup.html">MPI_Info_dup</A></TD>
-<TD><A HREF="MPI_Type_get_true_extent.html">MPI_Type_get_true_extent</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Comm_test_inter.html">MPI_Comm_test_inter</A></TD>
-<TD><A HREF="MPI_Info_free.html">MPI_Info_free</A></TD>
-<TD><A HREF="MPI_Type_get_true_extent_x.html">MPI_Type_get_true_extent_x</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Compare_and_swap.html">MPI_Compare_and_swap</A></TD>
-<TD><A HREF="MPI_Info_get.html">MPI_Info_get</A></TD>
-<TD><A HREF="MPI_Type_hindexed.html">MPI_Type_hindexed</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Dims_create.html">MPI_Dims_create</A></TD>
-<TD><A HREF="MPI_Info_get_nkeys.html">MPI_Info_get_nkeys</A></TD>
-<TD><A HREF="MPI_Type_hvector.html">MPI_Type_hvector</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Dist_graph_create.html">MPI_Dist_graph_create</A></TD>
-<TD><A HREF="MPI_Info_get_nthkey.html">MPI_Info_get_nthkey</A></TD>
-<TD><A HREF="MPI_Type_indexed.html">MPI_Type_indexed</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Dist_graph_create_adjacent.html">MPI_Dist_graph_create_adjacent</A></TD>
-<TD><A HREF="MPI_Info_get_valuelen.html">MPI_Info_get_valuelen</A></TD>
-<TD><A HREF="MPI_Type_lb.html">MPI_Type_lb</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Dist_graph_neighbors.html">MPI_Dist_graph_neighbors</A></TD>
-<TD><A HREF="MPI_Info_set.html">MPI_Info_set</A></TD>
-<TD><A HREF="MPI_Type_match_size.html">MPI_Type_match_size</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Dist_graph_neighbors_count.html">MPI_Dist_graph_neighbors_count</A></TD>
-<TD><A HREF="MPI_Init.html">MPI_Init</A></TD>
-<TD><A HREF="MPI_Type_set_attr.html">MPI_Type_set_attr</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Errhandler_create.html">MPI_Errhandler_create</A></TD>
-<TD><A HREF="MPI_Init_thread.html">MPI_Init_thread</A></TD>
-<TD><A HREF="MPI_Type_set_name.html">MPI_Type_set_name</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Errhandler_free.html">MPI_Errhandler_free</A></TD>
-<TD><A HREF="MPI_Initialized.html">MPI_Initialized</A></TD>
-<TD><A HREF="MPI_Type_size.html">MPI_Type_size</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Errhandler_get.html">MPI_Errhandler_get</A></TD>
-<TD><A HREF="MPI_Intercomm_create.html">MPI_Intercomm_create</A></TD>
-<TD><A HREF="MPI_Type_size_x.html">MPI_Type_size_x</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Errhandler_set.html">MPI_Errhandler_set</A></TD>
-<TD><A HREF="MPI_Intercomm_merge.html">MPI_Intercomm_merge</A></TD>
-<TD><A HREF="MPI_Type_struct.html">MPI_Type_struct</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Error_class.html">MPI_Error_class</A></TD>
-<TD><A HREF="MPI_Iprobe.html">MPI_Iprobe</A></TD>
-<TD><A HREF="MPI_Type_ub.html">MPI_Type_ub</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Error_string.html">MPI_Error_string</A></TD>
-<TD><A HREF="MPI_Irecv.html">MPI_Irecv</A></TD>
-<TD><A HREF="MPI_Type_vector.html">MPI_Type_vector</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Exscan.html">MPI_Exscan</A></TD>
-<TD><A HREF="MPI_Ireduce.html">MPI_Ireduce</A></TD>
-<TD><A HREF="MPI_Unpack.html">MPI_Unpack</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_Fetch_and_op.html">MPI_Fetch_and_op</A></TD>
-<TD><A HREF="MPI_Ireduce_scatter.html">MPI_Ireduce_scatter</A></TD>
-<TD><A HREF="MPI_Unpack_external.html">MPI_Unpack_external</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_c2f.html">MPI_File_c2f</A></TD>
-<TD><A HREF="MPI_Ireduce_scatter_block.html">MPI_Ireduce_scatter_block</A></TD>
-<TD><A HREF="MPI_Unpublish_name.html">MPI_Unpublish_name</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_call_errhandler.html">MPI_File_call_errhandler</A></TD>
-<TD><A HREF="MPI_Irsend.html">MPI_Irsend</A></TD>
-<TD><A HREF="MPI_Wait.html">MPI_Wait</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_close.html">MPI_File_close</A></TD>
-<TD><A HREF="MPI_Is_thread_main.html">MPI_Is_thread_main</A></TD>
-<TD><A HREF="MPI_Waitall.html">MPI_Waitall</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_create_errhandler.html">MPI_File_create_errhandler</A></TD>
-<TD><A HREF="MPI_Iscan.html">MPI_Iscan</A></TD>
-<TD><A HREF="MPI_Waitany.html">MPI_Waitany</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_delete.html">MPI_File_delete</A></TD>
-<TD><A HREF="MPI_Iscatter.html">MPI_Iscatter</A></TD>
-<TD><A HREF="MPI_Waitsome.html">MPI_Waitsome</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_f2c.html">MPI_File_f2c</A></TD>
-<TD><A HREF="MPI_Iscatterv.html">MPI_Iscatterv</A></TD>
-<TD><A HREF="MPI_Win_allocate.html">MPI_Win_allocate</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_get_amode.html">MPI_File_get_amode</A></TD>
-<TD><A HREF="MPI_Isend.html">MPI_Isend</A></TD>
-<TD><A HREF="MPI_Win_allocate_shared.html">MPI_Win_allocate_shared</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_get_atomicity.html">MPI_File_get_atomicity</A></TD>
-<TD><A HREF="MPI_Issend.html">MPI_Issend</A></TD>
-<TD><A HREF="MPI_Win_attach.html">MPI_Win_attach</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_get_byte_offset.html">MPI_File_get_byte_offset</A></TD>
-<TD><A HREF="MPI_Keyval_create.html">MPI_Keyval_create</A></TD>
-<TD><A HREF="MPI_Win_call_errhandler.html">MPI_Win_call_errhandler</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_get_errhandler.html">MPI_File_get_errhandler</A></TD>
-<TD><A HREF="MPI_Keyval_free.html">MPI_Keyval_free</A></TD>
-<TD><A HREF="MPI_Win_complete.html">MPI_Win_complete</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_get_group.html">MPI_File_get_group</A></TD>
-<TD><A HREF="MPI_Lookup_name.html">MPI_Lookup_name</A></TD>
-<TD><A HREF="MPI_Win_create.html">MPI_Win_create</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_get_info.html">MPI_File_get_info</A></TD>
-<TD><A HREF="MPI_Mprobe.html">MPI_Mprobe</A></TD>
-<TD><A HREF="MPI_Win_create_dynamic.html">MPI_Win_create_dynamic</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_get_position.html">MPI_File_get_position</A></TD>
-<TD><A HREF="MPI_Mrecv.html">MPI_Mrecv</A></TD>
-<TD><A HREF="MPI_Win_create_errhandler.html">MPI_Win_create_errhandler</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_get_position_shared.html">MPI_File_get_position_shared</A></TD>
-<TD><A HREF="MPI_Neighbor_allgather.html">MPI_Neighbor_allgather</A></TD>
-<TD><A HREF="MPI_Win_create_keyval.html">MPI_Win_create_keyval</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_get_size.html">MPI_File_get_size</A></TD>
-<TD><A HREF="MPI_Neighbor_allgatherv.html">MPI_Neighbor_allgatherv</A></TD>
-<TD><A HREF="MPI_Win_delete_attr.html">MPI_Win_delete_attr</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_get_type_extent.html">MPI_File_get_type_extent</A></TD>
-<TD><A HREF="MPI_Neighbor_alltoall.html">MPI_Neighbor_alltoall</A></TD>
-<TD><A HREF="MPI_Win_detach.html">MPI_Win_detach</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_get_view.html">MPI_File_get_view</A></TD>
-<TD><A HREF="MPI_Neighbor_alltoallv.html">MPI_Neighbor_alltoallv</A></TD>
-<TD><A HREF="MPI_Win_fence.html">MPI_Win_fence</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_iread.html">MPI_File_iread</A></TD>
-<TD><A HREF="MPI_Neighbor_alltoallw.html">MPI_Neighbor_alltoallw</A></TD>
-<TD><A HREF="MPI_Win_flush.html">MPI_Win_flush</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_iread_all.html">MPI_File_iread_all</A></TD>
-<TD><A HREF="MPI_Op_commute.html">MPI_Op_commute</A></TD>
-<TD><A HREF="MPI_Win_flush_all.html">MPI_Win_flush_all</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_iread_at.html">MPI_File_iread_at</A></TD>
-<TD><A HREF="MPI_Op_create.html">MPI_Op_create</A></TD>
-<TD><A HREF="MPI_Win_flush_local.html">MPI_Win_flush_local</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_iread_at_all.html">MPI_File_iread_at_all</A></TD>
-<TD><A HREF="MPI_Op_free.html">MPI_Op_free</A></TD>
-<TD><A HREF="MPI_Win_flush_local_all.html">MPI_Win_flush_local_all</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_iread_shared.html">MPI_File_iread_shared</A></TD>
-<TD><A HREF="MPI_Open_port.html">MPI_Open_port</A></TD>
-<TD><A HREF="MPI_Win_free.html">MPI_Win_free</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_iwrite.html">MPI_File_iwrite</A></TD>
-<TD><A HREF="MPI_Pack.html">MPI_Pack</A></TD>
-<TD><A HREF="MPI_Win_free_keyval.html">MPI_Win_free_keyval</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_iwrite_all.html">MPI_File_iwrite_all</A></TD>
-<TD><A HREF="MPI_Pack_external.html">MPI_Pack_external</A></TD>
-<TD><A HREF="MPI_Win_get_attr.html">MPI_Win_get_attr</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_iwrite_at.html">MPI_File_iwrite_at</A></TD>
-<TD><A HREF="MPI_Pack_external_size.html">MPI_Pack_external_size</A></TD>
-<TD><A HREF="MPI_Win_get_errhandler.html">MPI_Win_get_errhandler</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_iwrite_at_all.html">MPI_File_iwrite_at_all</A></TD>
-<TD><A HREF="MPI_Pack_size.html">MPI_Pack_size</A></TD>
-<TD><A HREF="MPI_Win_get_group.html">MPI_Win_get_group</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_iwrite_shared.html">MPI_File_iwrite_shared</A></TD>
-<TD><A HREF="MPI_Pcontrol.html">MPI_Pcontrol</A></TD>
-<TD><A HREF="MPI_Win_get_info.html">MPI_Win_get_info</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_open.html">MPI_File_open</A></TD>
-<TD><A HREF="MPI_Probe.html">MPI_Probe</A></TD>
-<TD><A HREF="MPI_Win_get_name.html">MPI_Win_get_name</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_preallocate.html">MPI_File_preallocate</A></TD>
-<TD><A HREF="MPI_Publish_name.html">MPI_Publish_name</A></TD>
-<TD><A HREF="MPI_Win_lock.html">MPI_Win_lock</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_read.html">MPI_File_read</A></TD>
-<TD><A HREF="MPI_Put.html">MPI_Put</A></TD>
-<TD><A HREF="MPI_Win_lock_all.html">MPI_Win_lock_all</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_read_all.html">MPI_File_read_all</A></TD>
-<TD><A HREF="MPI_Query_thread.html">MPI_Query_thread</A></TD>
-<TD><A HREF="MPI_Win_post.html">MPI_Win_post</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_read_all_begin.html">MPI_File_read_all_begin</A></TD>
-<TD><A HREF="MPI_Raccumulate.html">MPI_Raccumulate</A></TD>
-<TD><A HREF="MPI_Win_set_attr.html">MPI_Win_set_attr</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_read_all_end.html">MPI_File_read_all_end</A></TD>
-<TD><A HREF="MPI_Recv.html">MPI_Recv</A></TD>
-<TD><A HREF="MPI_Win_set_errhandler.html">MPI_Win_set_errhandler</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_read_at.html">MPI_File_read_at</A></TD>
-<TD><A HREF="MPI_Recv_init.html">MPI_Recv_init</A></TD>
-<TD><A HREF="MPI_Win_set_info.html">MPI_Win_set_info</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_read_at_all.html">MPI_File_read_at_all</A></TD>
-<TD><A HREF="MPI_Reduce.html">MPI_Reduce</A></TD>
-<TD><A HREF="MPI_Win_set_name.html">MPI_Win_set_name</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_read_at_all_begin.html">MPI_File_read_at_all_begin</A></TD>
-<TD><A HREF="MPI_Reduce_local.html">MPI_Reduce_local</A></TD>
-<TD><A HREF="MPI_Win_shared_query.html">MPI_Win_shared_query</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_read_at_all_end.html">MPI_File_read_at_all_end</A></TD>
-<TD><A HREF="MPI_Reduce_scatter.html">MPI_Reduce_scatter</A></TD>
-<TD><A HREF="MPI_Win_start.html">MPI_Win_start</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_read_ordered.html">MPI_File_read_ordered</A></TD>
-<TD><A HREF="MPI_Reduce_scatter_block.html">MPI_Reduce_scatter_block</A></TD>
-<TD><A HREF="MPI_Win_sync.html">MPI_Win_sync</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_read_ordered_begin.html">MPI_File_read_ordered_begin</A></TD>
-<TD><A HREF="MPI_Register_datarep.html">MPI_Register_datarep</A></TD>
-<TD><A HREF="MPI_Win_test.html">MPI_Win_test</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_read_ordered_end.html">MPI_File_read_ordered_end</A></TD>
-<TD><A HREF="MPI_Request_free.html">MPI_Request_free</A></TD>
-<TD><A HREF="MPI_Win_unlock.html">MPI_Win_unlock</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_read_shared.html">MPI_File_read_shared</A></TD>
-<TD><A HREF="MPI_Request_get_status.html">MPI_Request_get_status</A></TD>
-<TD><A HREF="MPI_Win_unlock_all.html">MPI_Win_unlock_all</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_seek.html">MPI_File_seek</A></TD>
-<TD><A HREF="MPI_Rget.html">MPI_Rget</A></TD>
-<TD><A HREF="MPI_Win_wait.html">MPI_Win_wait</A></TD>
-</TR>
-<TR><TD><A HREF="MPI_File_seek_shared.html">MPI_File_seek_shared</A></TD>
-<TD><A HREF="MPI_Rget_accumulate.html">MPI_Rget_accumulate</A></TD>
-<TD><A HREF="MPI_Wtick.html">MPI_Wtick</A></TD>
-</TR>
-</TABLE>
-</BODY>
-</HTML>
+<HTML>
+<HEAD>
+<TITLE>Web pages for MPI Routines and Constants</TITLE>
+<!-- This file generated by createhtmlindex on  -->
+</HEAD>
+<BODY BGCOLOR="FFFFFF">
+<H1>Web pages for MPI Routines and Constants</H1>
+<TABLE>
+<TR><TD><A HREF="Constants.html">Constants</A></TD>
+<TD><A HREF="MPI_File_read_ordered_end.html">MPI_File_read_ordered_end</A></TD>
+<TD><A HREF="MPI_Rget_accumulate.html">MPI_Rget_accumulate</A></TD>
+</TR>
+<TR><TD><A HREF="MPIR_Type_commit.html">MPIR_Type_commit</A></TD>
+<TD><A HREF="MPI_File_read_shared.html">MPI_File_read_shared</A></TD>
+<TD><A HREF="MPI_Rput.html">MPI_Rput</A></TD>
+</TR>
+<TR><TD><A HREF="MPIR_Type_contiguous.html">MPIR_Type_contiguous</A></TD>
+<TD><A HREF="MPI_File_seek.html">MPI_File_seek</A></TD>
+<TD><A HREF="MPI_Rsend.html">MPI_Rsend</A></TD>
+</TR>
+<TR><TD><A HREF="MPIR_Type_dup.html">MPIR_Type_dup</A></TD>
+<TD><A HREF="MPI_File_seek_shared.html">MPI_File_seek_shared</A></TD>
+<TD><A HREF="MPI_Rsend_init.html">MPI_Rsend_init</A></TD>
+</TR>
+<TR><TD><A HREF="MPIR_Type_get_contents.html">MPIR_Type_get_contents</A></TD>
+<TD><A HREF="MPI_File_set_atomicity.html">MPI_File_set_atomicity</A></TD>
+<TD><A HREF="MPI_Scan.html">MPI_Scan</A></TD>
+</TR>
+<TR><TD><A HREF="MPIR_Type_indexed.html">MPIR_Type_indexed</A></TD>
+<TD><A HREF="MPI_File_set_errhandler.html">MPI_File_set_errhandler</A></TD>
+<TD><A HREF="MPI_Scatter.html">MPI_Scatter</A></TD>
+</TR>
+<TR><TD><A HREF="MPIR_Type_struct.html">MPIR_Type_struct</A></TD>
+<TD><A HREF="MPI_File_set_info.html">MPI_File_set_info</A></TD>
+<TD><A HREF="MPI_Scatterv.html">MPI_Scatterv</A></TD>
+</TR>
+<TR><TD><A HREF="MPIR_Type_vector.html">MPIR_Type_vector</A></TD>
+<TD><A HREF="MPI_File_set_size.html">MPI_File_set_size</A></TD>
+<TD><A HREF="MPI_Send.html">MPI_Send</A></TD>
+</TR>
+<TR><TD><A HREF="MPIX_Comm_agree.html">MPIX_Comm_agree</A></TD>
+<TD><A HREF="MPI_File_set_view.html">MPI_File_set_view</A></TD>
+<TD><A HREF="MPI_Send_init.html">MPI_Send_init</A></TD>
+</TR>
+<TR><TD><A HREF="MPIX_Comm_failure_ack.html">MPIX_Comm_failure_ack</A></TD>
+<TD><A HREF="MPI_File_sync.html">MPI_File_sync</A></TD>
+<TD><A HREF="MPI_Sendrecv.html">MPI_Sendrecv</A></TD>
+</TR>
+<TR><TD><A HREF="MPIX_Comm_failure_get_acked.html">MPIX_Comm_failure_get_acked</A></TD>
+<TD><A HREF="MPI_File_write.html">MPI_File_write</A></TD>
+<TD><A HREF="MPI_Sendrecv_replace.html">MPI_Sendrecv_replace</A></TD>
+</TR>
+<TR><TD><A HREF="MPIX_Comm_revoke.html">MPIX_Comm_revoke</A></TD>
+<TD><A HREF="MPI_File_write_all.html">MPI_File_write_all</A></TD>
+<TD><A HREF="MPI_Ssend.html">MPI_Ssend</A></TD>
+</TR>
+<TR><TD><A HREF="MPIX_Comm_shrink.html">MPIX_Comm_shrink</A></TD>
+<TD><A HREF="MPI_File_write_all_begin.html">MPI_File_write_all_begin</A></TD>
+<TD><A HREF="MPI_Ssend_init.html">MPI_Ssend_init</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Abort.html">MPI_Abort</A></TD>
+<TD><A HREF="MPI_File_write_all_end.html">MPI_File_write_all_end</A></TD>
+<TD><A HREF="MPI_Start.html">MPI_Start</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Accumulate.html">MPI_Accumulate</A></TD>
+<TD><A HREF="MPI_File_write_at.html">MPI_File_write_at</A></TD>
+<TD><A HREF="MPI_Startall.html">MPI_Startall</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Add_error_class.html">MPI_Add_error_class</A></TD>
+<TD><A HREF="MPI_File_write_at_all.html">MPI_File_write_at_all</A></TD>
+<TD><A HREF="MPI_Status_set_cancelled.html">MPI_Status_set_cancelled</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Add_error_code.html">MPI_Add_error_code</A></TD>
+<TD><A HREF="MPI_File_write_at_all_begin.html">MPI_File_write_at_all_begin</A></TD>
+<TD><A HREF="MPI_Status_set_elements.html">MPI_Status_set_elements</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Add_error_string.html">MPI_Add_error_string</A></TD>
+<TD><A HREF="MPI_File_write_at_all_end.html">MPI_File_write_at_all_end</A></TD>
+<TD><A HREF="MPI_Status_set_elements_x.html">MPI_Status_set_elements_x</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Address.html">MPI_Address</A></TD>
+<TD><A HREF="MPI_File_write_ordered.html">MPI_File_write_ordered</A></TD>
+<TD><A HREF="MPI_T_category_changed.html">MPI_T_category_changed</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Aint_add.html">MPI_Aint_add</A></TD>
+<TD><A HREF="MPI_File_write_ordered_begin.html">MPI_File_write_ordered_begin</A></TD>
+<TD><A HREF="MPI_T_category_get_categories.html">MPI_T_category_get_categories</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Aint_diff.html">MPI_Aint_diff</A></TD>
+<TD><A HREF="MPI_File_write_ordered_end.html">MPI_File_write_ordered_end</A></TD>
+<TD><A HREF="MPI_T_category_get_cvars.html">MPI_T_category_get_cvars</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Allgather.html">MPI_Allgather</A></TD>
+<TD><A HREF="MPI_File_write_shared.html">MPI_File_write_shared</A></TD>
+<TD><A HREF="MPI_T_category_get_info.html">MPI_T_category_get_info</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Allgatherv.html">MPI_Allgatherv</A></TD>
+<TD><A HREF="MPI_Finalize.html">MPI_Finalize</A></TD>
+<TD><A HREF="MPI_T_category_get_num.html">MPI_T_category_get_num</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Alloc_mem.html">MPI_Alloc_mem</A></TD>
+<TD><A HREF="MPI_Finalized.html">MPI_Finalized</A></TD>
+<TD><A HREF="MPI_T_category_get_pvars.html">MPI_T_category_get_pvars</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Allreduce.html">MPI_Allreduce</A></TD>
+<TD><A HREF="MPI_Free_mem.html">MPI_Free_mem</A></TD>
+<TD><A HREF="MPI_T_cvar_get_info.html">MPI_T_cvar_get_info</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Alltoall.html">MPI_Alltoall</A></TD>
+<TD><A HREF="MPI_Gather.html">MPI_Gather</A></TD>
+<TD><A HREF="MPI_T_cvar_get_num.html">MPI_T_cvar_get_num</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Alltoallv.html">MPI_Alltoallv</A></TD>
+<TD><A HREF="MPI_Gatherv.html">MPI_Gatherv</A></TD>
+<TD><A HREF="MPI_T_cvar_handle_alloc.html">MPI_T_cvar_handle_alloc</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Alltoallw.html">MPI_Alltoallw</A></TD>
+<TD><A HREF="MPI_Get.html">MPI_Get</A></TD>
+<TD><A HREF="MPI_T_cvar_handle_free.html">MPI_T_cvar_handle_free</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Attr_delete.html">MPI_Attr_delete</A></TD>
+<TD><A HREF="MPI_Get_accumulate.html">MPI_Get_accumulate</A></TD>
+<TD><A HREF="MPI_T_cvar_read.html">MPI_T_cvar_read</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Attr_get.html">MPI_Attr_get</A></TD>
+<TD><A HREF="MPI_Get_address.html">MPI_Get_address</A></TD>
+<TD><A HREF="MPI_T_cvar_write.html">MPI_T_cvar_write</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Attr_put.html">MPI_Attr_put</A></TD>
+<TD><A HREF="MPI_Get_count.html">MPI_Get_count</A></TD>
+<TD><A HREF="MPI_T_enum_get_info.html">MPI_T_enum_get_info</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Barrier.html">MPI_Barrier</A></TD>
+<TD><A HREF="MPI_Get_elements.html">MPI_Get_elements</A></TD>
+<TD><A HREF="MPI_T_enum_get_item.html">MPI_T_enum_get_item</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Bcast.html">MPI_Bcast</A></TD>
+<TD><A HREF="MPI_Get_elements_x.html">MPI_Get_elements_x</A></TD>
+<TD><A HREF="MPI_T_finalize.html">MPI_T_finalize</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Bsend.html">MPI_Bsend</A></TD>
+<TD><A HREF="MPI_Get_library_version.html">MPI_Get_library_version</A></TD>
+<TD><A HREF="MPI_T_init_thread.html">MPI_T_init_thread</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Bsend_init.html">MPI_Bsend_init</A></TD>
+<TD><A HREF="MPI_Get_processor_name.html">MPI_Get_processor_name</A></TD>
+<TD><A HREF="MPI_T_pvar_get_info.html">MPI_T_pvar_get_info</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Buffer_attach.html">MPI_Buffer_attach</A></TD>
+<TD><A HREF="MPI_Get_version.html">MPI_Get_version</A></TD>
+<TD><A HREF="MPI_T_pvar_get_num.html">MPI_T_pvar_get_num</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Buffer_detach.html">MPI_Buffer_detach</A></TD>
+<TD><A HREF="MPI_Graph_create.html">MPI_Graph_create</A></TD>
+<TD><A HREF="MPI_T_pvar_handle_alloc.html">MPI_T_pvar_handle_alloc</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Cancel.html">MPI_Cancel</A></TD>
+<TD><A HREF="MPI_Graph_get.html">MPI_Graph_get</A></TD>
+<TD><A HREF="MPI_T_pvar_handle_free.html">MPI_T_pvar_handle_free</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Cart_coords.html">MPI_Cart_coords</A></TD>
+<TD><A HREF="MPI_Graph_map.html">MPI_Graph_map</A></TD>
+<TD><A HREF="MPI_T_pvar_read.html">MPI_T_pvar_read</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Cart_create.html">MPI_Cart_create</A></TD>
+<TD><A HREF="MPI_Graph_neighbors.html">MPI_Graph_neighbors</A></TD>
+<TD><A HREF="MPI_T_pvar_readreset.html">MPI_T_pvar_readreset</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Cart_get.html">MPI_Cart_get</A></TD>
+<TD><A HREF="MPI_Graph_neighbors_count.html">MPI_Graph_neighbors_count</A></TD>
+<TD><A HREF="MPI_T_pvar_reset.html">MPI_T_pvar_reset</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Cart_map.html">MPI_Cart_map</A></TD>
+<TD><A HREF="MPI_Graphdims_get.html">MPI_Graphdims_get</A></TD>
+<TD><A HREF="MPI_T_pvar_session_create.html">MPI_T_pvar_session_create</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Cart_rank.html">MPI_Cart_rank</A></TD>
+<TD><A HREF="MPI_Grequest_complete.html">MPI_Grequest_complete</A></TD>
+<TD><A HREF="MPI_T_pvar_session_free.html">MPI_T_pvar_session_free</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Cart_shift.html">MPI_Cart_shift</A></TD>
+<TD><A HREF="MPI_Grequest_start.html">MPI_Grequest_start</A></TD>
+<TD><A HREF="MPI_T_pvar_start.html">MPI_T_pvar_start</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Cart_sub.html">MPI_Cart_sub</A></TD>
+<TD><A HREF="MPI_Group_compare.html">MPI_Group_compare</A></TD>
+<TD><A HREF="MPI_T_pvar_stop.html">MPI_T_pvar_stop</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Cartdim_get.html">MPI_Cartdim_get</A></TD>
+<TD><A HREF="MPI_Group_difference.html">MPI_Group_difference</A></TD>
+<TD><A HREF="MPI_T_pvar_write.html">MPI_T_pvar_write</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Close_port.html">MPI_Close_port</A></TD>
+<TD><A HREF="MPI_Group_excl.html">MPI_Group_excl</A></TD>
+<TD><A HREF="MPI_Test.html">MPI_Test</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_accept.html">MPI_Comm_accept</A></TD>
+<TD><A HREF="MPI_Group_free.html">MPI_Group_free</A></TD>
+<TD><A HREF="MPI_Test_cancelled.html">MPI_Test_cancelled</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_call_errhandler.html">MPI_Comm_call_errhandler</A></TD>
+<TD><A HREF="MPI_Group_incl.html">MPI_Group_incl</A></TD>
+<TD><A HREF="MPI_Testall.html">MPI_Testall</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_compare.html">MPI_Comm_compare</A></TD>
+<TD><A HREF="MPI_Group_intersection.html">MPI_Group_intersection</A></TD>
+<TD><A HREF="MPI_Testany.html">MPI_Testany</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_connect.html">MPI_Comm_connect</A></TD>
+<TD><A HREF="MPI_Group_range_excl.html">MPI_Group_range_excl</A></TD>
+<TD><A HREF="MPI_Testsome.html">MPI_Testsome</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_create.html">MPI_Comm_create</A></TD>
+<TD><A HREF="MPI_Group_range_incl.html">MPI_Group_range_incl</A></TD>
+<TD><A HREF="MPI_Topo_test.html">MPI_Topo_test</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_create_errhandler.html">MPI_Comm_create_errhandler</A></TD>
+<TD><A HREF="MPI_Group_rank.html">MPI_Group_rank</A></TD>
+<TD><A HREF="MPI_Type_commit.html">MPI_Type_commit</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_create_group.html">MPI_Comm_create_group</A></TD>
+<TD><A HREF="MPI_Group_size.html">MPI_Group_size</A></TD>
+<TD><A HREF="MPI_Type_contiguous.html">MPI_Type_contiguous</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_create_keyval.html">MPI_Comm_create_keyval</A></TD>
+<TD><A HREF="MPI_Group_translate_ranks.html">MPI_Group_translate_ranks</A></TD>
+<TD><A HREF="MPI_Type_create_darray.html">MPI_Type_create_darray</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_delete_attr.html">MPI_Comm_delete_attr</A></TD>
+<TD><A HREF="MPI_Group_union.html">MPI_Group_union</A></TD>
+<TD><A HREF="MPI_Type_create_hindexed.html">MPI_Type_create_hindexed</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_disconnect.html">MPI_Comm_disconnect</A></TD>
+<TD><A HREF="MPI_Iallgather.html">MPI_Iallgather</A></TD>
+<TD><A HREF="MPI_Type_create_hindexed_block.html">MPI_Type_create_hindexed_block</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_dup.html">MPI_Comm_dup</A></TD>
+<TD><A HREF="MPI_Iallgatherv.html">MPI_Iallgatherv</A></TD>
+<TD><A HREF="MPI_Type_create_hvector.html">MPI_Type_create_hvector</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_dup_with_info.html">MPI_Comm_dup_with_info</A></TD>
+<TD><A HREF="MPI_Iallreduce.html">MPI_Iallreduce</A></TD>
+<TD><A HREF="MPI_Type_create_indexed_block.html">MPI_Type_create_indexed_block</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_free.html">MPI_Comm_free</A></TD>
+<TD><A HREF="MPI_Ialltoall.html">MPI_Ialltoall</A></TD>
+<TD><A HREF="MPI_Type_create_keyval.html">MPI_Type_create_keyval</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_free_keyval.html">MPI_Comm_free_keyval</A></TD>
+<TD><A HREF="MPI_Ialltoallv.html">MPI_Ialltoallv</A></TD>
+<TD><A HREF="MPI_Type_create_resized.html">MPI_Type_create_resized</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_get_attr.html">MPI_Comm_get_attr</A></TD>
+<TD><A HREF="MPI_Ialltoallw.html">MPI_Ialltoallw</A></TD>
+<TD><A HREF="MPI_Type_create_struct.html">MPI_Type_create_struct</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_get_errhandler.html">MPI_Comm_get_errhandler</A></TD>
+<TD><A HREF="MPI_Ibarrier.html">MPI_Ibarrier</A></TD>
+<TD><A HREF="MPI_Type_create_subarray.html">MPI_Type_create_subarray</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_get_info.html">MPI_Comm_get_info</A></TD>
+<TD><A HREF="MPI_Ibcast.html">MPI_Ibcast</A></TD>
+<TD><A HREF="MPI_Type_delete_attr.html">MPI_Type_delete_attr</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_get_name.html">MPI_Comm_get_name</A></TD>
+<TD><A HREF="MPI_Ibsend.html">MPI_Ibsend</A></TD>
+<TD><A HREF="MPI_Type_dup.html">MPI_Type_dup</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_get_parent.html">MPI_Comm_get_parent</A></TD>
+<TD><A HREF="MPI_Iexscan.html">MPI_Iexscan</A></TD>
+<TD><A HREF="MPI_Type_extent.html">MPI_Type_extent</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_group.html">MPI_Comm_group</A></TD>
+<TD><A HREF="MPI_Igather.html">MPI_Igather</A></TD>
+<TD><A HREF="MPI_Type_free.html">MPI_Type_free</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_idup.html">MPI_Comm_idup</A></TD>
+<TD><A HREF="MPI_Igatherv.html">MPI_Igatherv</A></TD>
+<TD><A HREF="MPI_Type_free_keyval.html">MPI_Type_free_keyval</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_join.html">MPI_Comm_join</A></TD>
+<TD><A HREF="MPI_Improbe.html">MPI_Improbe</A></TD>
+<TD><A HREF="MPI_Type_get_attr.html">MPI_Type_get_attr</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_rank.html">MPI_Comm_rank</A></TD>
+<TD><A HREF="MPI_Imrecv.html">MPI_Imrecv</A></TD>
+<TD><A HREF="MPI_Type_get_contents.html">MPI_Type_get_contents</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_remote_group.html">MPI_Comm_remote_group</A></TD>
+<TD><A HREF="MPI_Ineighbor_allgather.html">MPI_Ineighbor_allgather</A></TD>
+<TD><A HREF="MPI_Type_get_envelope.html">MPI_Type_get_envelope</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_remote_size.html">MPI_Comm_remote_size</A></TD>
+<TD><A HREF="MPI_Ineighbor_allgatherv.html">MPI_Ineighbor_allgatherv</A></TD>
+<TD><A HREF="MPI_Type_get_extent.html">MPI_Type_get_extent</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_set_attr.html">MPI_Comm_set_attr</A></TD>
+<TD><A HREF="MPI_Ineighbor_alltoall.html">MPI_Ineighbor_alltoall</A></TD>
+<TD><A HREF="MPI_Type_get_extent_x.html">MPI_Type_get_extent_x</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_set_errhandler.html">MPI_Comm_set_errhandler</A></TD>
+<TD><A HREF="MPI_Ineighbor_alltoallv.html">MPI_Ineighbor_alltoallv</A></TD>
+<TD><A HREF="MPI_Type_get_name.html">MPI_Type_get_name</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_set_info.html">MPI_Comm_set_info</A></TD>
+<TD><A HREF="MPI_Ineighbor_alltoallw.html">MPI_Ineighbor_alltoallw</A></TD>
+<TD><A HREF="MPI_Type_get_true_extent.html">MPI_Type_get_true_extent</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_set_name.html">MPI_Comm_set_name</A></TD>
+<TD><A HREF="MPI_Info_create.html">MPI_Info_create</A></TD>
+<TD><A HREF="MPI_Type_get_true_extent_x.html">MPI_Type_get_true_extent_x</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_size.html">MPI_Comm_size</A></TD>
+<TD><A HREF="MPI_Info_delete.html">MPI_Info_delete</A></TD>
+<TD><A HREF="MPI_Type_hindexed.html">MPI_Type_hindexed</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_spawn.html">MPI_Comm_spawn</A></TD>
+<TD><A HREF="MPI_Info_dup.html">MPI_Info_dup</A></TD>
+<TD><A HREF="MPI_Type_hvector.html">MPI_Type_hvector</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_spawn_multiple.html">MPI_Comm_spawn_multiple</A></TD>
+<TD><A HREF="MPI_Info_free.html">MPI_Info_free</A></TD>
+<TD><A HREF="MPI_Type_indexed.html">MPI_Type_indexed</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_split.html">MPI_Comm_split</A></TD>
+<TD><A HREF="MPI_Info_get.html">MPI_Info_get</A></TD>
+<TD><A HREF="MPI_Type_lb.html">MPI_Type_lb</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_split_type.html">MPI_Comm_split_type</A></TD>
+<TD><A HREF="MPI_Info_get_nkeys.html">MPI_Info_get_nkeys</A></TD>
+<TD><A HREF="MPI_Type_match_size.html">MPI_Type_match_size</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Comm_test_inter.html">MPI_Comm_test_inter</A></TD>
+<TD><A HREF="MPI_Info_get_nthkey.html">MPI_Info_get_nthkey</A></TD>
+<TD><A HREF="MPI_Type_set_attr.html">MPI_Type_set_attr</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Compare_and_swap.html">MPI_Compare_and_swap</A></TD>
+<TD><A HREF="MPI_Info_get_valuelen.html">MPI_Info_get_valuelen</A></TD>
+<TD><A HREF="MPI_Type_set_name.html">MPI_Type_set_name</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Dims_create.html">MPI_Dims_create</A></TD>
+<TD><A HREF="MPI_Info_set.html">MPI_Info_set</A></TD>
+<TD><A HREF="MPI_Type_size.html">MPI_Type_size</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Dist_graph_create.html">MPI_Dist_graph_create</A></TD>
+<TD><A HREF="MPI_Init.html">MPI_Init</A></TD>
+<TD><A HREF="MPI_Type_size_x.html">MPI_Type_size_x</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Dist_graph_create_adjacent.html">MPI_Dist_graph_create_adjacent</A></TD>
+<TD><A HREF="MPI_Init_thread.html">MPI_Init_thread</A></TD>
+<TD><A HREF="MPI_Type_struct.html">MPI_Type_struct</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Dist_graph_neighbors.html">MPI_Dist_graph_neighbors</A></TD>
+<TD><A HREF="MPI_Initialized.html">MPI_Initialized</A></TD>
+<TD><A HREF="MPI_Type_ub.html">MPI_Type_ub</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Dist_graph_neighbors_count.html">MPI_Dist_graph_neighbors_count</A></TD>
+<TD><A HREF="MPI_Intercomm_create.html">MPI_Intercomm_create</A></TD>
+<TD><A HREF="MPI_Type_vector.html">MPI_Type_vector</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Errhandler_create.html">MPI_Errhandler_create</A></TD>
+<TD><A HREF="MPI_Intercomm_merge.html">MPI_Intercomm_merge</A></TD>
+<TD><A HREF="MPI_Unpack.html">MPI_Unpack</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Errhandler_free.html">MPI_Errhandler_free</A></TD>
+<TD><A HREF="MPI_Iprobe.html">MPI_Iprobe</A></TD>
+<TD><A HREF="MPI_Unpack_external.html">MPI_Unpack_external</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Errhandler_get.html">MPI_Errhandler_get</A></TD>
+<TD><A HREF="MPI_Irecv.html">MPI_Irecv</A></TD>
+<TD><A HREF="MPI_Unpublish_name.html">MPI_Unpublish_name</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Errhandler_set.html">MPI_Errhandler_set</A></TD>
+<TD><A HREF="MPI_Ireduce.html">MPI_Ireduce</A></TD>
+<TD><A HREF="MPI_Wait.html">MPI_Wait</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Error_class.html">MPI_Error_class</A></TD>
+<TD><A HREF="MPI_Ireduce_scatter.html">MPI_Ireduce_scatter</A></TD>
+<TD><A HREF="MPI_Waitall.html">MPI_Waitall</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Error_string.html">MPI_Error_string</A></TD>
+<TD><A HREF="MPI_Ireduce_scatter_block.html">MPI_Ireduce_scatter_block</A></TD>
+<TD><A HREF="MPI_Waitany.html">MPI_Waitany</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Exscan.html">MPI_Exscan</A></TD>
+<TD><A HREF="MPI_Irsend.html">MPI_Irsend</A></TD>
+<TD><A HREF="MPI_Waitsome.html">MPI_Waitsome</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_Fetch_and_op.html">MPI_Fetch_and_op</A></TD>
+<TD><A HREF="MPI_Is_thread_main.html">MPI_Is_thread_main</A></TD>
+<TD><A HREF="MPI_Win_allocate.html">MPI_Win_allocate</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_c2f.html">MPI_File_c2f</A></TD>
+<TD><A HREF="MPI_Iscan.html">MPI_Iscan</A></TD>
+<TD><A HREF="MPI_Win_allocate_shared.html">MPI_Win_allocate_shared</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_call_errhandler.html">MPI_File_call_errhandler</A></TD>
+<TD><A HREF="MPI_Iscatter.html">MPI_Iscatter</A></TD>
+<TD><A HREF="MPI_Win_attach.html">MPI_Win_attach</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_close.html">MPI_File_close</A></TD>
+<TD><A HREF="MPI_Iscatterv.html">MPI_Iscatterv</A></TD>
+<TD><A HREF="MPI_Win_call_errhandler.html">MPI_Win_call_errhandler</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_create_errhandler.html">MPI_File_create_errhandler</A></TD>
+<TD><A HREF="MPI_Isend.html">MPI_Isend</A></TD>
+<TD><A HREF="MPI_Win_complete.html">MPI_Win_complete</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_delete.html">MPI_File_delete</A></TD>
+<TD><A HREF="MPI_Issend.html">MPI_Issend</A></TD>
+<TD><A HREF="MPI_Win_create.html">MPI_Win_create</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_f2c.html">MPI_File_f2c</A></TD>
+<TD><A HREF="MPI_Keyval_create.html">MPI_Keyval_create</A></TD>
+<TD><A HREF="MPI_Win_create_dynamic.html">MPI_Win_create_dynamic</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_get_amode.html">MPI_File_get_amode</A></TD>
+<TD><A HREF="MPI_Keyval_free.html">MPI_Keyval_free</A></TD>
+<TD><A HREF="MPI_Win_create_errhandler.html">MPI_Win_create_errhandler</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_get_atomicity.html">MPI_File_get_atomicity</A></TD>
+<TD><A HREF="MPI_Lookup_name.html">MPI_Lookup_name</A></TD>
+<TD><A HREF="MPI_Win_create_keyval.html">MPI_Win_create_keyval</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_get_byte_offset.html">MPI_File_get_byte_offset</A></TD>
+<TD><A HREF="MPI_Mprobe.html">MPI_Mprobe</A></TD>
+<TD><A HREF="MPI_Win_delete_attr.html">MPI_Win_delete_attr</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_get_errhandler.html">MPI_File_get_errhandler</A></TD>
+<TD><A HREF="MPI_Mrecv.html">MPI_Mrecv</A></TD>
+<TD><A HREF="MPI_Win_detach.html">MPI_Win_detach</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_get_group.html">MPI_File_get_group</A></TD>
+<TD><A HREF="MPI_Neighbor_allgather.html">MPI_Neighbor_allgather</A></TD>
+<TD><A HREF="MPI_Win_fence.html">MPI_Win_fence</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_get_info.html">MPI_File_get_info</A></TD>
+<TD><A HREF="MPI_Neighbor_allgatherv.html">MPI_Neighbor_allgatherv</A></TD>
+<TD><A HREF="MPI_Win_flush.html">MPI_Win_flush</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_get_position.html">MPI_File_get_position</A></TD>
+<TD><A HREF="MPI_Neighbor_alltoall.html">MPI_Neighbor_alltoall</A></TD>
+<TD><A HREF="MPI_Win_flush_all.html">MPI_Win_flush_all</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_get_position_shared.html">MPI_File_get_position_shared</A></TD>
+<TD><A HREF="MPI_Neighbor_alltoallv.html">MPI_Neighbor_alltoallv</A></TD>
+<TD><A HREF="MPI_Win_flush_local.html">MPI_Win_flush_local</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_get_size.html">MPI_File_get_size</A></TD>
+<TD><A HREF="MPI_Neighbor_alltoallw.html">MPI_Neighbor_alltoallw</A></TD>
+<TD><A HREF="MPI_Win_flush_local_all.html">MPI_Win_flush_local_all</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_get_type_extent.html">MPI_File_get_type_extent</A></TD>
+<TD><A HREF="MPI_Op_commute.html">MPI_Op_commute</A></TD>
+<TD><A HREF="MPI_Win_free.html">MPI_Win_free</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_get_view.html">MPI_File_get_view</A></TD>
+<TD><A HREF="MPI_Op_create.html">MPI_Op_create</A></TD>
+<TD><A HREF="MPI_Win_free_keyval.html">MPI_Win_free_keyval</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_iread.html">MPI_File_iread</A></TD>
+<TD><A HREF="MPI_Op_free.html">MPI_Op_free</A></TD>
+<TD><A HREF="MPI_Win_get_attr.html">MPI_Win_get_attr</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_iread_all.html">MPI_File_iread_all</A></TD>
+<TD><A HREF="MPI_Open_port.html">MPI_Open_port</A></TD>
+<TD><A HREF="MPI_Win_get_errhandler.html">MPI_Win_get_errhandler</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_iread_at.html">MPI_File_iread_at</A></TD>
+<TD><A HREF="MPI_Pack.html">MPI_Pack</A></TD>
+<TD><A HREF="MPI_Win_get_group.html">MPI_Win_get_group</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_iread_at_all.html">MPI_File_iread_at_all</A></TD>
+<TD><A HREF="MPI_Pack_external.html">MPI_Pack_external</A></TD>
+<TD><A HREF="MPI_Win_get_info.html">MPI_Win_get_info</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_iread_shared.html">MPI_File_iread_shared</A></TD>
+<TD><A HREF="MPI_Pack_external_size.html">MPI_Pack_external_size</A></TD>
+<TD><A HREF="MPI_Win_get_name.html">MPI_Win_get_name</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_iwrite.html">MPI_File_iwrite</A></TD>
+<TD><A HREF="MPI_Pack_size.html">MPI_Pack_size</A></TD>
+<TD><A HREF="MPI_Win_lock.html">MPI_Win_lock</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_iwrite_all.html">MPI_File_iwrite_all</A></TD>
+<TD><A HREF="MPI_Pcontrol.html">MPI_Pcontrol</A></TD>
+<TD><A HREF="MPI_Win_lock_all.html">MPI_Win_lock_all</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_iwrite_at.html">MPI_File_iwrite_at</A></TD>
+<TD><A HREF="MPI_Probe.html">MPI_Probe</A></TD>
+<TD><A HREF="MPI_Win_post.html">MPI_Win_post</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_iwrite_at_all.html">MPI_File_iwrite_at_all</A></TD>
+<TD><A HREF="MPI_Publish_name.html">MPI_Publish_name</A></TD>
+<TD><A HREF="MPI_Win_set_attr.html">MPI_Win_set_attr</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_iwrite_shared.html">MPI_File_iwrite_shared</A></TD>
+<TD><A HREF="MPI_Put.html">MPI_Put</A></TD>
+<TD><A HREF="MPI_Win_set_errhandler.html">MPI_Win_set_errhandler</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_open.html">MPI_File_open</A></TD>
+<TD><A HREF="MPI_Query_thread.html">MPI_Query_thread</A></TD>
+<TD><A HREF="MPI_Win_set_info.html">MPI_Win_set_info</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_preallocate.html">MPI_File_preallocate</A></TD>
+<TD><A HREF="MPI_Raccumulate.html">MPI_Raccumulate</A></TD>
+<TD><A HREF="MPI_Win_set_name.html">MPI_Win_set_name</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_read.html">MPI_File_read</A></TD>
+<TD><A HREF="MPI_Recv.html">MPI_Recv</A></TD>
+<TD><A HREF="MPI_Win_shared_query.html">MPI_Win_shared_query</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_read_all.html">MPI_File_read_all</A></TD>
+<TD><A HREF="MPI_Recv_init.html">MPI_Recv_init</A></TD>
+<TD><A HREF="MPI_Win_start.html">MPI_Win_start</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_read_all_begin.html">MPI_File_read_all_begin</A></TD>
+<TD><A HREF="MPI_Reduce.html">MPI_Reduce</A></TD>
+<TD><A HREF="MPI_Win_sync.html">MPI_Win_sync</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_read_all_end.html">MPI_File_read_all_end</A></TD>
+<TD><A HREF="MPI_Reduce_local.html">MPI_Reduce_local</A></TD>
+<TD><A HREF="MPI_Win_test.html">MPI_Win_test</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_read_at.html">MPI_File_read_at</A></TD>
+<TD><A HREF="MPI_Reduce_scatter.html">MPI_Reduce_scatter</A></TD>
+<TD><A HREF="MPI_Win_unlock.html">MPI_Win_unlock</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_read_at_all.html">MPI_File_read_at_all</A></TD>
+<TD><A HREF="MPI_Reduce_scatter_block.html">MPI_Reduce_scatter_block</A></TD>
+<TD><A HREF="MPI_Win_unlock_all.html">MPI_Win_unlock_all</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_read_at_all_begin.html">MPI_File_read_at_all_begin</A></TD>
+<TD><A HREF="MPI_Register_datarep.html">MPI_Register_datarep</A></TD>
+<TD><A HREF="MPI_Win_wait.html">MPI_Win_wait</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_read_at_all_end.html">MPI_File_read_at_all_end</A></TD>
+<TD><A HREF="MPI_Request_free.html">MPI_Request_free</A></TD>
+<TD><A HREF="MPI_Wtick.html">MPI_Wtick</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_read_ordered.html">MPI_File_read_ordered</A></TD>
+<TD><A HREF="MPI_Request_get_status.html">MPI_Request_get_status</A></TD>
+<TD><A HREF="MPI_Wtime.html">MPI_Wtime</A></TD>
+</TR>
+<TR><TD><A HREF="MPI_File_read_ordered_begin.html">MPI_File_read_ordered_begin</A></TD>
+<TD><A HREF="MPI_Rget.html">MPI_Rget</A></TD>
+<TD></TD>
+</TR>
+</TABLE>
+</BODY>
+</HTML>
diff --git a/linx64/mpi/mpich/share/doc/mpich/www3/mpi.cit b/linx64/mpi/mpich/share/doc/mpich/www3/mpi.cit
index 6a104bf8..bef31d2d 100644
--- a/linx64/mpi/mpich/share/doc/mpich/www3/mpi.cit
+++ b/linx64/mpi/mpich/share/doc/mpich/www3/mpi.cit
@@ -18,27 +18,28 @@ man:+MPI_Win_delete_attr++MPI_Win_delete_attr++++man+--your-url-here--/MPI_Win_d
 man:+MPI_Win_free_keyval++MPI_Win_free_keyval++++man+--your-url-here--/MPI_Win_free_keyval.html#MPI_Win_free_keyval
 man:+MPI_Win_get_attr++MPI_Win_get_attr++++man+--your-url-here--/MPI_Win_get_attr.html#MPI_Win_get_attr
 man:+MPI_Win_set_attr++MPI_Win_set_attr++++man+--your-url-here--/MPI_Win_set_attr.html#MPI_Win_set_attr
-man:+MPI_Allreduce++MPI_Allreduce++++man+--your-url-here--/MPI_Allreduce.html#MPI_Allreduce
-man:+MPI_Barrier++MPI_Barrier++++man+--your-url-here--/MPI_Barrier.html#MPI_Barrier
-man:+MPI_Op_create++MPI_Op_create++++man+--your-url-here--/MPI_Op_create.html#MPI_Op_create
-man:+MPI_Op_free++MPI_Op_free++++man+--your-url-here--/MPI_Op_free.html#MPI_Op_free
-man:+MPI_Bcast++MPI_Bcast++++man+--your-url-here--/MPI_Bcast.html#MPI_Bcast
-man:+MPI_Alltoall++MPI_Alltoall++++man+--your-url-here--/MPI_Alltoall.html#MPI_Alltoall
-man:+MPI_Alltoallv++MPI_Alltoallv++++man+--your-url-here--/MPI_Alltoallv.html#MPI_Alltoallv
-man:+MPI_Reduce++MPI_Reduce++++man+--your-url-here--/MPI_Reduce.html#MPI_Reduce
-man:+MPI_Scatter++MPI_Scatter++++man+--your-url-here--/MPI_Scatter.html#MPI_Scatter
-man:+MPI_Gather++MPI_Gather++++man+--your-url-here--/MPI_Gather.html#MPI_Gather
-man:+MPI_Scatterv++MPI_Scatterv++++man+--your-url-here--/MPI_Scatterv.html#MPI_Scatterv
-man:+MPI_Gatherv++MPI_Gatherv++++man+--your-url-here--/MPI_Gatherv.html#MPI_Gatherv
-man:+MPI_Scan++MPI_Scan++++man+--your-url-here--/MPI_Scan.html#MPI_Scan
-man:+MPI_Exscan++MPI_Exscan++++man+--your-url-here--/MPI_Exscan.html#MPI_Exscan
 man:+MPI_Allgather++MPI_Allgather++++man+--your-url-here--/MPI_Allgather.html#MPI_Allgather
 man:+MPI_Allgatherv++MPI_Allgatherv++++man+--your-url-here--/MPI_Allgatherv.html#MPI_Allgatherv
-man:+MPI_Reduce_scatter++MPI_Reduce_scatter++++man+--your-url-here--/MPI_Reduce_scatter.html#MPI_Reduce_scatter
+man:+MPI_Allreduce++MPI_Allreduce++++man+--your-url-here--/MPI_Allreduce.html#MPI_Allreduce
+man:+MPI_Alltoall++MPI_Alltoall++++man+--your-url-here--/MPI_Alltoall.html#MPI_Alltoall
+man:+MPI_Alltoallv++MPI_Alltoallv++++man+--your-url-here--/MPI_Alltoallv.html#MPI_Alltoallv
 man:+MPI_Alltoallw++MPI_Alltoallw++++man+--your-url-here--/MPI_Alltoallw.html#MPI_Alltoallw
-man:+MPI_Reduce_local++MPI_Reduce_local++++man+--your-url-here--/MPI_Reduce_local.html#MPI_Reduce_local
-man:+MPI_Op_commute++MPI_Op_commute++++man+--your-url-here--/MPI_Op_commute.html#MPI_Op_commute
+man:+MPI_Barrier++MPI_Barrier++++man+--your-url-here--/MPI_Barrier.html#MPI_Barrier
+man:+MPI_Bcast++MPI_Bcast++++man+--your-url-here--/MPI_Bcast.html#MPI_Bcast
+man:+MPI_Exscan++MPI_Exscan++++man+--your-url-here--/MPI_Exscan.html#MPI_Exscan
+man:+MPI_Gather++MPI_Gather++++man+--your-url-here--/MPI_Gather.html#MPI_Gather
+man:+MPI_Gatherv++MPI_Gatherv++++man+--your-url-here--/MPI_Gatherv.html#MPI_Gatherv
+man:+MPI_Reduce_scatter++MPI_Reduce_scatter++++man+--your-url-here--/MPI_Reduce_scatter.html#MPI_Reduce_scatter
 man:+MPI_Reduce_scatter_block++MPI_Reduce_scatter_block++++man+--your-url-here--/MPI_Reduce_scatter_block.html#MPI_Reduce_scatter_block
+man:+MPI_Reduce++MPI_Reduce++++man+--your-url-here--/MPI_Reduce.html#MPI_Reduce
+man:+MPI_Scan++MPI_Scan++++man+--your-url-here--/MPI_Scan.html#MPI_Scan
+man:+MPI_Scatter++MPI_Scatter++++man+--your-url-here--/MPI_Scatter.html#MPI_Scatter
+man:+MPI_Scatterv++MPI_Scatterv++++man+--your-url-here--/MPI_Scatterv.html#MPI_Scatterv
+man:+MPI_Neighbor_allgather++MPI_Neighbor_allgather++++man+--your-url-here--/MPI_Neighbor_allgather.html#MPI_Neighbor_allgather
+man:+MPI_Neighbor_allgatherv++MPI_Neighbor_allgatherv++++man+--your-url-here--/MPI_Neighbor_allgatherv.html#MPI_Neighbor_allgatherv
+man:+MPI_Neighbor_alltoall++MPI_Neighbor_alltoall++++man+--your-url-here--/MPI_Neighbor_alltoall.html#MPI_Neighbor_alltoall
+man:+MPI_Neighbor_alltoallv++MPI_Neighbor_alltoallv++++man+--your-url-here--/MPI_Neighbor_alltoallv.html#MPI_Neighbor_alltoallv
+man:+MPI_Neighbor_alltoallw++MPI_Neighbor_alltoallw++++man+--your-url-here--/MPI_Neighbor_alltoallw.html#MPI_Neighbor_alltoallw
 man:+MPI_Iallgather++MPI_Iallgather++++man+--your-url-here--/MPI_Iallgather.html#MPI_Iallgather
 man:+MPI_Iallgatherv++MPI_Iallgatherv++++man+--your-url-here--/MPI_Iallgatherv.html#MPI_Iallgatherv
 man:+MPI_Iallreduce++MPI_Iallreduce++++man+--your-url-here--/MPI_Iallreduce.html#MPI_Iallreduce
@@ -56,6 +57,15 @@ man:+MPI_Ireduce++MPI_Ireduce++++man+--your-url-here--/MPI_Ireduce.html#MPI_Ired
 man:+MPI_Iscan++MPI_Iscan++++man+--your-url-here--/MPI_Iscan.html#MPI_Iscan
 man:+MPI_Iscatter++MPI_Iscatter++++man+--your-url-here--/MPI_Iscatter.html#MPI_Iscatter
 man:+MPI_Iscatterv++MPI_Iscatterv++++man+--your-url-here--/MPI_Iscatterv.html#MPI_Iscatterv
+man:+MPI_Ineighbor_allgather++MPI_Ineighbor_allgather++++man+--your-url-here--/MPI_Ineighbor_allgather.html#MPI_Ineighbor_allgather
+man:+MPI_Ineighbor_allgatherv++MPI_Ineighbor_allgatherv++++man+--your-url-here--/MPI_Ineighbor_allgatherv.html#MPI_Ineighbor_allgatherv
+man:+MPI_Ineighbor_alltoall++MPI_Ineighbor_alltoall++++man+--your-url-here--/MPI_Ineighbor_alltoall.html#MPI_Ineighbor_alltoall
+man:+MPI_Ineighbor_alltoallv++MPI_Ineighbor_alltoallv++++man+--your-url-here--/MPI_Ineighbor_alltoallv.html#MPI_Ineighbor_alltoallv
+man:+MPI_Ineighbor_alltoallw++MPI_Ineighbor_alltoallw++++man+--your-url-here--/MPI_Ineighbor_alltoallw.html#MPI_Ineighbor_alltoallw
+man:+MPI_Op_create++MPI_Op_create++++man+--your-url-here--/MPI_Op_create.html#MPI_Op_create
+man:+MPI_Op_free++MPI_Op_free++++man+--your-url-here--/MPI_Op_free.html#MPI_Op_free
+man:+MPI_Op_commute++MPI_Op_commute++++man+--your-url-here--/MPI_Op_commute.html#MPI_Op_commute
+man:+MPI_Reduce_local++MPI_Reduce_local++++man+--your-url-here--/MPI_Reduce_local.html#MPI_Reduce_local
 man:+MPI_Comm_compare++MPI_Comm_compare++++man+--your-url-here--/MPI_Comm_compare.html#MPI_Comm_compare
 man:+MPI_Comm_create++MPI_Comm_create++++man+--your-url-here--/MPI_Comm_create.html#MPI_Comm_create
 man:+MPI_Comm_create_group++MPI_Comm_create_group++++man+--your-url-here--/MPI_Comm_create_group.html#MPI_Comm_create_group
@@ -88,7 +98,8 @@ man:+MPI_Get_count++MPI_Get_count++++man+--your-url-here--/MPI_Get_count.html#MP
 man:+MPI_Get_elements++MPI_Get_elements++++man+--your-url-here--/MPI_Get_elements.html#MPI_Get_elements
 man:+MPI_Get_elements_x++MPI_Get_elements_x++++man+--your-url-here--/MPI_Get_elements_x.html#MPI_Get_elements_x
 man:+MPI_Pack++MPI_Pack++++man+--your-url-here--/MPI_Pack.html#MPI_Pack
-man:+MPI_Unpack++MPI_Unpack++++man+--your-url-here--/MPI_Unpack.html#MPI_Unpack
+man:+MPI_Pack_external++MPI_Pack_external++++man+--your-url-here--/MPI_Pack_external.html#MPI_Pack_external
+man:+MPI_Pack_external_size++MPI_Pack_external_size++++man+--your-url-here--/MPI_Pack_external_size.html#MPI_Pack_external_size
 man:+MPI_Pack_size++MPI_Pack_size++++man+--your-url-here--/MPI_Pack_size.html#MPI_Pack_size
 man:+MPI_Status_set_elements++MPI_Status_set_elements++++man+--your-url-here--/MPI_Status_set_elements.html#MPI_Status_set_elements
 man:+MPI_Status_set_elements_x++MPI_Status_set_elements_x++++man+--your-url-here--/MPI_Status_set_elements_x.html#MPI_Status_set_elements_x
@@ -97,16 +108,23 @@ man:+MPI_Type_set_name++MPI_Type_set_name++++man+--your-url-here--/MPI_Type_set_
 man:+MPI_Type_size++MPI_Type_size++++man+--your-url-here--/MPI_Type_size.html#MPI_Type_size
 man:+MPI_Type_size_x++MPI_Type_size_x++++man+--your-url-here--/MPI_Type_size_x.html#MPI_Type_size_x
 man:+MPI_Type_extent++MPI_Type_extent++++man+--your-url-here--/MPI_Type_extent.html#MPI_Type_extent
+man:+MPIR_Type_vector++MPIR_Type_vector++++man+--your-url-here--/MPIR_Type_vector.html#MPIR_Type_vector
 man:+MPI_Type_vector++MPI_Type_vector++++man+--your-url-here--/MPI_Type_vector.html#MPI_Type_vector
+man:+MPIR_Type_commit++MPIR_Type_commit++++man+--your-url-here--/MPIR_Type_commit.html#MPIR_Type_commit
 man:+MPI_Type_commit++MPI_Type_commit++++man+--your-url-here--/MPI_Type_commit.html#MPI_Type_commit
+man:+MPIR_Type_indexed++MPIR_Type_indexed++++man+--your-url-here--/MPIR_Type_indexed.html#MPIR_Type_indexed
 man:+MPI_Type_indexed++MPI_Type_indexed++++man+--your-url-here--/MPI_Type_indexed.html#MPI_Type_indexed
 man:+MPI_Type_hindexed++MPI_Type_hindexed++++man+--your-url-here--/MPI_Type_hindexed.html#MPI_Type_hindexed
+man:+MPIR_Type_struct++MPIR_Type_struct++++man+--your-url-here--/MPIR_Type_struct.html#MPIR_Type_struct
 man:+MPI_Type_struct++MPI_Type_struct++++man+--your-url-here--/MPI_Type_struct.html#MPI_Type_struct
+man:+MPIR_Type_contiguous++MPIR_Type_contiguous++++man+--your-url-here--/MPIR_Type_contiguous.html#MPIR_Type_contiguous
 man:+MPI_Type_contiguous++MPI_Type_contiguous++++man+--your-url-here--/MPI_Type_contiguous.html#MPI_Type_contiguous
 man:+MPI_Type_free++MPI_Type_free++++man+--your-url-here--/MPI_Type_free.html#MPI_Type_free
 man:+MPI_Type_hvector++MPI_Type_hvector++++man+--your-url-here--/MPI_Type_hvector.html#MPI_Type_hvector
+man:+MPIR_Type_dup++MPIR_Type_dup++++man+--your-url-here--/MPIR_Type_dup.html#MPIR_Type_dup
 man:+MPI_Type_dup++MPI_Type_dup++++man+--your-url-here--/MPI_Type_dup.html#MPI_Type_dup
 man:+MPI_Type_get_envelope++MPI_Type_get_envelope++++man+--your-url-here--/MPI_Type_get_envelope.html#MPI_Type_get_envelope
+man:+MPIR_Type_get_contents++MPIR_Type_get_contents++++man+--your-url-here--/MPIR_Type_get_contents.html#MPIR_Type_get_contents
 man:+MPI_Type_get_contents++MPI_Type_get_contents++++man+--your-url-here--/MPI_Type_get_contents.html#MPI_Type_get_contents
 man:+MPI_Type_ub++MPI_Type_ub++++man+--your-url-here--/MPI_Type_ub.html#MPI_Type_ub
 man:+MPI_Type_lb++MPI_Type_lb++++man+--your-url-here--/MPI_Type_lb.html#MPI_Type_lb
@@ -118,14 +136,13 @@ man:+MPI_Type_match_size++MPI_Type_match_size++++man+--your-url-here--/MPI_Type_
 man:+MPI_Type_create_struct++MPI_Type_create_struct++++man+--your-url-here--/MPI_Type_create_struct.html#MPI_Type_create_struct
 man:+MPI_Type_create_hindexed++MPI_Type_create_hindexed++++man+--your-url-here--/MPI_Type_create_hindexed.html#MPI_Type_create_hindexed
 man:+MPI_Type_create_hvector++MPI_Type_create_hvector++++man+--your-url-here--/MPI_Type_create_hvector.html#MPI_Type_create_hvector
-man:+MPI_Pack_external++MPI_Pack_external++++man+--your-url-here--/MPI_Pack_external.html#MPI_Pack_external
-man:+MPI_Pack_external_size++MPI_Pack_external_size++++man+--your-url-here--/MPI_Pack_external_size.html#MPI_Pack_external_size
-man:+MPI_Unpack_external++MPI_Unpack_external++++man+--your-url-here--/MPI_Unpack_external.html#MPI_Unpack_external
 man:+MPI_Type_create_indexed_block++MPI_Type_create_indexed_block++++man+--your-url-here--/MPI_Type_create_indexed_block.html#MPI_Type_create_indexed_block
 man:+MPI_Type_create_hindexed_block++MPI_Type_create_hindexed_block++++man+--your-url-here--/MPI_Type_create_hindexed_block.html#MPI_Type_create_hindexed_block
 man:+MPI_Type_create_resized++MPI_Type_create_resized++++man+--your-url-here--/MPI_Type_create_resized.html#MPI_Type_create_resized
 man:+MPI_Type_create_darray++MPI_Type_create_darray++++man+--your-url-here--/MPI_Type_create_darray.html#MPI_Type_create_darray
 man:+MPI_Type_create_subarray++MPI_Type_create_subarray++++man+--your-url-here--/MPI_Type_create_subarray.html#MPI_Type_create_subarray
+man:+MPI_Unpack++MPI_Unpack++++man+--your-url-here--/MPI_Unpack.html#MPI_Unpack
+man:+MPI_Unpack_external++MPI_Unpack_external++++man+--your-url-here--/MPI_Unpack_external.html#MPI_Unpack_external
 man:+MPI_Add_error_code++MPI_Add_error_code++++man+--your-url-here--/MPI_Add_error_code.html#MPI_Add_error_code
 man:+MPI_Add_error_class++MPI_Add_error_class++++man+--your-url-here--/MPI_Add_error_class.html#MPI_Add_error_class
 man:+MPI_Add_error_string++MPI_Add_error_string++++man+--your-url-here--/MPI_Add_error_string.html#MPI_Add_error_string
@@ -186,9 +203,6 @@ man:+MPI_Bsend++MPI_Bsend++++man+--your-url-here--/MPI_Bsend.html#MPI_Bsend
 man:+MPI_Bsend_init++MPI_Bsend_init++++man+--your-url-here--/MPI_Bsend_init.html#MPI_Bsend_init
 man:+MPI_Buffer_attach++MPI_Buffer_attach++++man+--your-url-here--/MPI_Buffer_attach.html#MPI_Buffer_attach
 man:+MPI_Buffer_detach++MPI_Buffer_detach++++man+--your-url-here--/MPI_Buffer_detach.html#MPI_Buffer_detach
-man:+MPI_Cancel++MPI_Cancel++++man+--your-url-here--/MPI_Cancel.html#MPI_Cancel
-man:+MPI_Grequest_start++MPI_Grequest_start++++man+--your-url-here--/MPI_Grequest_start.html#MPI_Grequest_start
-man:+MPI_Grequest_complete++MPI_Grequest_complete++++man+--your-url-here--/MPI_Grequest_complete.html#MPI_Grequest_complete
 man:+MPI_Ibsend++MPI_Ibsend++++man+--your-url-here--/MPI_Ibsend.html#MPI_Ibsend
 man:+MPI_Improbe++MPI_Improbe++++man+--your-url-here--/MPI_Improbe.html#MPI_Improbe
 man:+MPI_Imrecv++MPI_Imrecv++++man+--your-url-here--/MPI_Imrecv.html#MPI_Imrecv
@@ -202,17 +216,20 @@ man:+MPI_Mrecv++MPI_Mrecv++++man+--your-url-here--/MPI_Mrecv.html#MPI_Mrecv
 man:+MPI_Probe++MPI_Probe++++man+--your-url-here--/MPI_Probe.html#MPI_Probe
 man:+MPI_Recv++MPI_Recv++++man+--your-url-here--/MPI_Recv.html#MPI_Recv
 man:+MPI_Recv_init++MPI_Recv_init++++man+--your-url-here--/MPI_Recv_init.html#MPI_Recv_init
-man:+MPI_Request_free++MPI_Request_free++++man+--your-url-here--/MPI_Request_free.html#MPI_Request_free
-man:+MPI_Request_get_status++MPI_Request_get_status++++man+--your-url-here--/MPI_Request_get_status.html#MPI_Request_get_status
 man:+MPI_Rsend++MPI_Rsend++++man+--your-url-here--/MPI_Rsend.html#MPI_Rsend
 man:+MPI_Rsend_init++MPI_Rsend_init++++man+--your-url-here--/MPI_Rsend_init.html#MPI_Rsend_init
 man:+MPI_Send++MPI_Send++++man+--your-url-here--/MPI_Send.html#MPI_Send
 man:+MPI_Send_init++MPI_Send_init++++man+--your-url-here--/MPI_Send_init.html#MPI_Send_init
 man:+MPI_Sendrecv++MPI_Sendrecv++++man+--your-url-here--/MPI_Sendrecv.html#MPI_Sendrecv
 man:+MPI_Sendrecv_replace++MPI_Sendrecv_replace++++man+--your-url-here--/MPI_Sendrecv_replace.html#MPI_Sendrecv_replace
-man:+MPI_Status_set_cancelled++MPI_Status_set_cancelled++++man+--your-url-here--/MPI_Status_set_cancelled.html#MPI_Status_set_cancelled
 man:+MPI_Ssend++MPI_Ssend++++man+--your-url-here--/MPI_Ssend.html#MPI_Ssend
 man:+MPI_Ssend_init++MPI_Ssend_init++++man+--your-url-here--/MPI_Ssend_init.html#MPI_Ssend_init
+man:+MPI_Cancel++MPI_Cancel++++man+--your-url-here--/MPI_Cancel.html#MPI_Cancel
+man:+MPI_Grequest_start++MPI_Grequest_start++++man+--your-url-here--/MPI_Grequest_start.html#MPI_Grequest_start
+man:+MPI_Grequest_complete++MPI_Grequest_complete++++man+--your-url-here--/MPI_Grequest_complete.html#MPI_Grequest_complete
+man:+MPI_Request_free++MPI_Request_free++++man+--your-url-here--/MPI_Request_free.html#MPI_Request_free
+man:+MPI_Request_get_status++MPI_Request_get_status++++man+--your-url-here--/MPI_Request_get_status.html#MPI_Request_get_status
+man:+MPI_Status_set_cancelled++MPI_Status_set_cancelled++++man+--your-url-here--/MPI_Status_set_cancelled.html#MPI_Status_set_cancelled
 man:+MPI_Start++MPI_Start++++man+--your-url-here--/MPI_Start.html#MPI_Start
 man:+MPI_Startall++MPI_Startall++++man+--your-url-here--/MPI_Startall.html#MPI_Startall
 man:+MPI_Test++MPI_Test++++man+--your-url-here--/MPI_Test.html#MPI_Test
@@ -298,16 +315,6 @@ man:+MPI_Dist_graph_create_adjacent++MPI_Dist_graph_create_adjacent++++man+--you
 man:+MPI_Dist_graph_create++MPI_Dist_graph_create++++man+--your-url-here--/MPI_Dist_graph_create.html#MPI_Dist_graph_create
 man:+MPI_Dist_graph_neighbors_count++MPI_Dist_graph_neighbors_count++++man+--your-url-here--/MPI_Dist_graph_neighbors_count.html#MPI_Dist_graph_neighbors_count
 man:+MPI_Dist_graph_neighbors++MPI_Dist_graph_neighbors++++man+--your-url-here--/MPI_Dist_graph_neighbors.html#MPI_Dist_graph_neighbors
-man:+MPI_Ineighbor_allgather++MPI_Ineighbor_allgather++++man+--your-url-here--/MPI_Ineighbor_allgather.html#MPI_Ineighbor_allgather
-man:+MPI_Ineighbor_allgatherv++MPI_Ineighbor_allgatherv++++man+--your-url-here--/MPI_Ineighbor_allgatherv.html#MPI_Ineighbor_allgatherv
-man:+MPI_Ineighbor_alltoall++MPI_Ineighbor_alltoall++++man+--your-url-here--/MPI_Ineighbor_alltoall.html#MPI_Ineighbor_alltoall
-man:+MPI_Ineighbor_alltoallv++MPI_Ineighbor_alltoallv++++man+--your-url-here--/MPI_Ineighbor_alltoallv.html#MPI_Ineighbor_alltoallv
-man:+MPI_Ineighbor_alltoallw++MPI_Ineighbor_alltoallw++++man+--your-url-here--/MPI_Ineighbor_alltoallw.html#MPI_Ineighbor_alltoallw
-man:+MPI_Neighbor_allgather++MPI_Neighbor_allgather++++man+--your-url-here--/MPI_Neighbor_allgather.html#MPI_Neighbor_allgather
-man:+MPI_Neighbor_allgatherv++MPI_Neighbor_allgatherv++++man+--your-url-here--/MPI_Neighbor_allgatherv.html#MPI_Neighbor_allgatherv
-man:+MPI_Neighbor_alltoall++MPI_Neighbor_alltoall++++man+--your-url-here--/MPI_Neighbor_alltoall.html#MPI_Neighbor_alltoall
-man:+MPI_Neighbor_alltoallv++MPI_Neighbor_alltoallv++++man+--your-url-here--/MPI_Neighbor_alltoallv.html#MPI_Neighbor_alltoallv
-man:+MPI_Neighbor_alltoallw++MPI_Neighbor_alltoallw++++man+--your-url-here--/MPI_Neighbor_alltoallw.html#MPI_Neighbor_alltoallw
 man:+MPI_T_category_changed++MPI_T_category_changed++++man+--your-url-here--/MPI_T_category_changed.html#MPI_T_category_changed
 man:+MPI_T_category_get_categories++MPI_T_category_get_categories++++man+--your-url-here--/MPI_T_category_get_categories.html#MPI_T_category_get_categories
 man:+MPI_T_category_get_cvars++MPI_T_category_get_cvars++++man+--your-url-here--/MPI_T_category_get_cvars.html#MPI_T_category_get_cvars
diff --git a/linx64/mpi/mpich/share/man/man1/hydra_nameserver.1 b/linx64/mpi/mpich/share/man/man1/hydra_nameserver.1
index b2f6e160..2240d851 100644
--- a/linx64/mpi/mpich/share/man/man1/hydra_nameserver.1
+++ b/linx64/mpi/mpich/share/man/man1/hydra_nameserver.1
@@ -1,4 +1,4 @@
-.TH hydra_nameserver 1 "11/10/2017" " " "HYDRA"
+.TH hydra_nameserver 1 "6/5/2019" " " "HYDRA"
 .SH NAME
 hydra_nameserver \-  Internal executable used by Hydra 
 .SH DESCRIPTION
@@ -7,4 +7,4 @@ support the Hydra process manager. As such, no documentation will be
 provided here.
 
 .SH LOCATION
-/tmp/_HMuTRgPPE/mpich-3.2.1/src/pm/hydra/tools/nameserver/hydra_nameserver.txt
+/tmp/kS7n0Mi0xa/mpich-3.3.1/src/pm/hydra/tools/nameserver/hydra_nameserver.txt
diff --git a/linx64/mpi/mpich/share/man/man1/hydra_persist.1 b/linx64/mpi/mpich/share/man/man1/hydra_persist.1
index aacb0a92..ac93d489 100644
--- a/linx64/mpi/mpich/share/man/man1/hydra_persist.1
+++ b/linx64/mpi/mpich/share/man/man1/hydra_persist.1
@@ -1,4 +1,4 @@
-.TH hydra_persist 1 "11/10/2017" " " "HYDRA"
+.TH hydra_persist 1 "6/5/2019" " " "HYDRA"
 .SH NAME
 hydra_persist \-  Internal executable used by Hydra 
 .SH DESCRIPTION
@@ -7,4 +7,4 @@ support the Hydra process manager. As such, no documentation will be
 provided here.
 
 .SH LOCATION
-/tmp/_HMuTRgPPE/mpich-3.2.1/src/pm/hydra/tools/bootstrap/persist/hydra_persist.txt
+/tmp/kS7n0Mi0xa/mpich-3.3.1/src/pm/hydra/tools/bootstrap/persist/hydra_persist.txt
diff --git a/linx64/mpi/mpich/share/man/man1/hydra_pmi_proxy.1 b/linx64/mpi/mpich/share/man/man1/hydra_pmi_proxy.1
index 617558dd..137a796a 100644
--- a/linx64/mpi/mpich/share/man/man1/hydra_pmi_proxy.1
+++ b/linx64/mpi/mpich/share/man/man1/hydra_pmi_proxy.1
@@ -1,4 +1,4 @@
-.TH hydra_pmi_proxy 1 "11/10/2017" " " "HYDRA"
+.TH hydra_pmi_proxy 1 "6/5/2019" " " "HYDRA"
 .SH NAME
 hydra_pmi_proxy \-  Internal exectuable used by Hydra 
 .SH DESCRIPTION
@@ -7,4 +7,4 @@ support the Hydra process manager. As such, no documentation will be
 provided here.
 
 .SH LOCATION
-/tmp/_HMuTRgPPE/mpich-3.2.1/src/pm/hydra/pm/pmiserv/hydra_pmi_proxy.txt
+/tmp/kS7n0Mi0xa/mpich-3.3.1/src/pm/hydra/pm/pmiserv/hydra_pmi_proxy.txt
diff --git a/linx64/mpi/mpich/share/man/man1/mpicc.1 b/linx64/mpi/mpich/share/man/man1/mpicc.1
index 7419402e..56f825a7 100644
--- a/linx64/mpi/mpich/share/man/man1/mpicc.1
+++ b/linx64/mpi/mpich/share/man/man1/mpicc.1
@@ -1,4 +1,4 @@
-.TH mpicc 1 "11/10/2017" " " "MPI"
+.TH mpicc 1 "6/5/2019" " " "MPI"
 .SH NAME
 mpicc \-  Compiles and links MPI programs written in C 
 .SH DESCRIPTION
@@ -67,6 +67,12 @@ This option should normally not be used.
 .PD 1
 .PD 0
 .TP
+.B -static
+- mpi - Use a statically compile MPI library, but shared libraries
+for all of the other dependencies.
+.PD 1
+.PD 0
+.TP
 .B others     
 - are passed to the compiler or linker.  For example, 
 .I \\-c
diff --git a/linx64/mpi/mpich/share/man/man1/mpicxx.1 b/linx64/mpi/mpich/share/man/man1/mpicxx.1
index 65bdf515..2c481fb9 100644
--- a/linx64/mpi/mpich/share/man/man1/mpicxx.1
+++ b/linx64/mpi/mpich/share/man/man1/mpicxx.1
@@ -1,4 +1,4 @@
-.TH mpicxx 1 "11/10/2017" " " "MPI"
+.TH mpicxx 1 "6/5/2019" " " "MPI"
 .SH NAME
 mpicxx \-  Compiles and links MPI programs written in C++ 
 .SH DESCRIPTION
@@ -67,6 +67,12 @@ This option should normally not be used.
 .PD 1
 .PD 0
 .TP
+.B -static
+- mpi - Use a statically compile MPI library, but shared libraries
+for all of the other dependencies.
+.PD 1
+.PD 0
+.TP
 .B others     
 - are passed to the compiler or linker.  For example, 
 .I \\-c
diff --git a/linx64/mpi/mpich/share/man/man1/mpiexec.1 b/linx64/mpi/mpich/share/man/man1/mpiexec.1
index ba43f059..fc136c0c 100644
--- a/linx64/mpi/mpich/share/man/man1/mpiexec.1
+++ b/linx64/mpi/mpich/share/man/man1/mpiexec.1
@@ -1,4 +1,4 @@
-.TH mpiexec 1 "11/10/2017" " " "MPI"
+.TH mpiexec 1 "6/5/2019" " " "MPI"
 .SH NAME
 mpiexec \-  Run an MPI program 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man1/mpif77.1 b/linx64/mpi/mpich/share/man/man1/mpif77.1
index 62f849e6..aa55e916 100644
--- a/linx64/mpi/mpich/share/man/man1/mpif77.1
+++ b/linx64/mpi/mpich/share/man/man1/mpif77.1
@@ -1,4 +1,4 @@
-.TH mpif77 1 "11/10/2017" " " "MPI"
+.TH mpif77 1 "6/5/2019" " " "MPI"
 .SH NAME
 mpif77 \-  Compiles and links MPI programs written in Fortran 77 
 .SH DESCRIPTION
@@ -67,6 +67,12 @@ This option should normally not be used.
 .PD 1
 .PD 0
 .TP
+.B -static
+- mpi - Use a statically compile MPI library, but shared libraries
+for all of the other dependencies.
+.PD 1
+.PD 0
+.TP
 .B others     
 - are passed to the compiler or linker.  For example, 
 .I \\-c
diff --git a/linx64/mpi/mpich/share/man/man1/mpifort.1 b/linx64/mpi/mpich/share/man/man1/mpifort.1
index 611b9fcd..371dfaa9 100644
--- a/linx64/mpi/mpich/share/man/man1/mpifort.1
+++ b/linx64/mpi/mpich/share/man/man1/mpifort.1
@@ -1,4 +1,4 @@
-.TH mpifort 1 "11/10/2017" " " "MPI"
+.TH mpifort 1 "6/5/2019" " " "MPI"
 .SH NAME
 mpifort \-  Compiles and links MPI programs written in Fortran 90 
 .SH DESCRIPTION
@@ -67,6 +67,12 @@ This option should normally not be used.
 .PD 1
 .PD 0
 .TP
+.B -static
+- mpi - Use a statically compile MPI library, but shared libraries
+for all of the other dependencies.
+.PD 1
+.PD 0
+.TP
 .B others     
 - are passed to the compiler or linker.  For example, 
 .I \\-c
diff --git a/linx64/mpi/mpich/share/man/man3/Constants.3 b/linx64/mpi/mpich/share/man/man3/Constants.3
index 04368e84..68c6176e 100644
--- a/linx64/mpi/mpich/share/man/man3/Constants.3
+++ b/linx64/mpi/mpich/share/man/man3/Constants.3
@@ -1,4 +1,4 @@
-.TH Constants 3 "11/10/2017" " " "MPI"
+.TH Constants 3 "6/5/2019" " " "MPI"
 .SH NAME
 Constants \-  Meaning of MPI's defined constants 
 .SH DATA TYPES
diff --git a/linx64/mpi/mpich/share/man/man3/MPIR_Type_commit.3 b/linx64/mpi/mpich/share/man/man3/MPIR_Type_commit.3
new file mode 100644
index 00000000..fc4cf0f6
--- /dev/null
+++ b/linx64/mpi/mpich/share/man/man3/MPIR_Type_commit.3
@@ -0,0 +1,11 @@
+.TH MPIR_Type_commit 3 "6/5/2019" " " "MPI"
+.SH NAME
+MPIR_Type_commit \-  nput Parameters: . datatype_p - pointer to MPI datatype 
+.SH SYNOPSIS
+.nf
+int MPIR_Type_commit(MPI_Datatype * datatype_p)
+.fi
+.SH OUTPUT PARAMETERS
+
+.SH RETURN VALUE
+0 on success, -1 on failure.
diff --git a/linx64/mpi/mpich/share/man/man3/MPIR_Type_contiguous.3 b/linx64/mpi/mpich/share/man/man3/MPIR_Type_contiguous.3
new file mode 100644
index 00000000..b44f320e
--- /dev/null
+++ b/linx64/mpi/mpich/share/man/man3/MPIR_Type_contiguous.3
@@ -0,0 +1,28 @@
+.TH MPIR_Type_contiguous 3 "6/5/2019" " " "MPI"
+.SH NAME
+MPIR_Type_contiguous \-  create a contiguous datatype 
+.SH SYNOPSIS
+.nf
+int MPIR_Type_contiguous(int count, MPI_Datatype oldtype, MPI_Datatype * newtype)
+.fi
+.SH INPUT PARAMETERS
+.PD 0
+.TP
+.B count 
+- number of elements in the contiguous block
+.PD 1
+.PD 0
+.TP
+.B oldtype 
+- type (using handle) of datatype on which vector is based
+.PD 1
+
+.SH OUTPUT PARAMETERS
+.PD 0
+.TP
+.B newtype 
+- handle of new contiguous datatype
+.PD 1
+
+.SH RETURN VALUE
+MPI_SUCCESS on success, MPI error code on failure.
diff --git a/linx64/mpi/mpich/share/man/man3/MPIR_Type_dup.3 b/linx64/mpi/mpich/share/man/man3/MPIR_Type_dup.3
new file mode 100644
index 00000000..065d7811
--- /dev/null
+++ b/linx64/mpi/mpich/share/man/man3/MPIR_Type_dup.3
@@ -0,0 +1,27 @@
+.TH MPIR_Type_dup 3 "6/5/2019" " " "MPI"
+.SH NAME
+MPIR_Type_dup \-  create a copy of a datatype 
+.SH SYNOPSIS
+.nf
+#undef FUNCNAME
+#define FUNCNAME MPIR_Type_dup
+#undef FCNAME
+#define FCNAME MPL_QUOTE(FUNCNAME)
+int MPIR_Type_dup(MPI_Datatype oldtype, MPI_Datatype * newtype)
+.fi
+.SH INPUT PARAMETERS
+.PD 0
+.TP
+.B oldtype 
+- handle of original datatype
+.PD 1
+
+.SH OUTPUT PARAMETERS
+.PD 0
+.TP
+.B newtype 
+- handle of newly created copy of datatype
+.PD 1
+
+.SH RETURN VALUE
+0 on success, MPI error code on failure.
diff --git a/linx64/mpi/mpich/share/man/man3/MPIR_Type_get_contents.3 b/linx64/mpi/mpich/share/man/man3/MPIR_Type_get_contents.3
new file mode 100644
index 00000000..95b81b10
--- /dev/null
+++ b/linx64/mpi/mpich/share/man/man3/MPIR_Type_get_contents.3
@@ -0,0 +1,51 @@
+.TH MPIR_Type_get_contents 3 "6/5/2019" " " "MPI"
+.SH NAME
+MPIR_Type_get_contents \-  get content information from datatype 
+.SH SYNOPSIS
+.nf
+int MPIR_Type_get_contents(MPI_Datatype datatype,
+                           int max_integers,
+                           int max_addresses,
+                           int max_datatypes,
+                           int array_of_integers[],
+                           MPI_Aint array_of_addresses[], MPI_Datatype array_of_datatypes[])
+.fi
+.SH INPUT PARAMETERS
+.PD 0
+.TP
+.B datatype 
+- MPI datatype
+.PD 1
+.PD 0
+.TP
+.B max_integers 
+- size of array_of_integers
+.PD 1
+.PD 0
+.TP
+.B max_addresses 
+- size of array_of_addresses
+.PD 1
+.PD 0
+.TP
+.B max_datatypes 
+- size of array_of_datatypes
+.PD 1
+
+.SH OUTPUT PARAMETERS
+.PD 0
+.TP
+.B array_of_integers 
+- integers used in creating type
+.PD 1
+.PD 0
+.TP
+.B array_of_addresses 
+- MPI_Aints used in creating type
+.PD 1
+.PD 0
+.TP
+.B array_of_datatypes 
+- MPI_Datatypes used in creating type
+.PD 1
+
diff --git a/linx64/mpi/mpich/share/man/man3/MPIR_Type_indexed.3 b/linx64/mpi/mpich/share/man/man3/MPIR_Type_indexed.3
new file mode 100644
index 00000000..e7550616
--- /dev/null
+++ b/linx64/mpi/mpich/share/man/man3/MPIR_Type_indexed.3
@@ -0,0 +1,49 @@
+.TH MPIR_Type_indexed 3 "6/5/2019" " " "MPI"
+.SH NAME
+MPIR_Type_indexed \-  create an indexed datatype 
+.SH SYNOPSIS
+.nf
+int MPIR_Type_indexed(int count,
+                      const int *blocklength_array,
+                      const void *displacement_array,
+                      int dispinbytes, MPI_Datatype oldtype, MPI_Datatype * newtype)
+.fi
+.SH INPUT PARAMETERS
+.PD 0
+.TP
+.B count 
+- number of blocks in type
+.PD 1
+.PD 0
+.TP
+.B blocklength_array 
+- number of elements in each block
+.PD 1
+.PD 0
+.TP
+.B displacement_array 
+- offsets of blocks from start of type (see next
+parameter for units)
+.PD 1
+.PD 0
+.TP
+.B dispinbytes 
+- if nonzero, then displacements are in bytes (the
+displacement_array is an array of ints), otherwise they in terms of
+extent of oldtype (the displacement_array is an array of MPI_Aints)
+.PD 1
+.PD 0
+.TP
+.B oldtype 
+- type (using handle) of datatype on which new type is based
+.PD 1
+
+.SH OUTPUT PARAMETERS
+.PD 0
+.TP
+.B newtype 
+- handle of new indexed datatype
+.PD 1
+
+.SH RETURN VALUE
+0 on success, -1 on failure.
diff --git a/linx64/mpi/mpich/share/man/man3/MPIR_Type_struct.3 b/linx64/mpi/mpich/share/man/man3/MPIR_Type_struct.3
new file mode 100644
index 00000000..77f49609
--- /dev/null
+++ b/linx64/mpi/mpich/share/man/man3/MPIR_Type_struct.3
@@ -0,0 +1,45 @@
+.TH MPIR_Type_struct 3 "6/5/2019" " " "MPI"
+.SH NAME
+MPIR_Type_struct \-  create a struct datatype 
+.SH SYNOPSIS
+.nf
+#undef FUNCNAME
+#define FUNCNAME MPIR_Type_struct
+#undef FCNAME
+#define FCNAME MPL_QUOTE(FUNCNAME)
+int MPIR_Type_struct(int count,
+                     const int *blocklength_array,
+                     const MPI_Aint * displacement_array,
+                     const MPI_Datatype * oldtype_array, MPI_Datatype * newtype)
+.fi
+.SH INPUT PARAMETERS
+.PD 0
+.TP
+.B count 
+- number of blocks in vector
+.PD 1
+.PD 0
+.TP
+.B blocklength_array 
+- number of elements in each block
+.PD 1
+.PD 0
+.TP
+.B displacement_array 
+- offsets of blocks from start of type in bytes
+.PD 1
+.PD 0
+.TP
+.B oldtype_array 
+- types (using handle) of datatypes on which vector is based
+.PD 1
+
+.SH OUTPUT PARAMETERS
+.PD 0
+.TP
+.B newtype 
+- handle of new struct datatype
+.PD 1
+
+.SH RETURN VALUE
+MPI_SUCCESS on success, MPI errno on failure.
diff --git a/linx64/mpi/mpich/share/man/man3/MPIR_Type_vector.3 b/linx64/mpi/mpich/share/man/man3/MPIR_Type_vector.3
new file mode 100644
index 00000000..e3cd0273
--- /dev/null
+++ b/linx64/mpi/mpich/share/man/man3/MPIR_Type_vector.3
@@ -0,0 +1,48 @@
+.TH MPIR_Type_vector 3 "6/5/2019" " " "MPI"
+.SH NAME
+MPIR_Type_vector \-  create a vector datatype 
+.SH SYNOPSIS
+.nf
+int MPIR_Type_vector(int count,
+                     int blocklength,
+                     MPI_Aint stride,
+                     int strideinbytes, MPI_Datatype oldtype, MPI_Datatype * newtype)
+.fi
+.SH INPUT PARAMETERS
+.PD 0
+.TP
+.B count 
+- number of blocks in vector
+.PD 1
+.PD 0
+.TP
+.B blocklength 
+- number of elements in each block
+.PD 1
+.PD 0
+.TP
+.B stride 
+- distance from beginning of one block to the next (see next
+parameter for units)
+.PD 1
+.PD 0
+.TP
+.B strideinbytes 
+- if nonzero, then stride is in bytes, otherwise stride
+is in terms of extent of oldtype
+.PD 1
+.PD 0
+.TP
+.B oldtype 
+- type (using handle) of datatype on which vector is based
+.PD 1
+
+.SH OUTPUT PARAMETERS
+.PD 0
+.TP
+.B newtype 
+- handle of new vector datatype
+.PD 1
+
+.SH RETURN VALUE
+0 on success, MPI error code on failure.
diff --git a/linx64/mpi/mpich/share/man/man3/MPIX_Comm_agree.3 b/linx64/mpi/mpich/share/man/man3/MPIX_Comm_agree.3
index a6441686..bd3df512 100644
--- a/linx64/mpi/mpich/share/man/man3/MPIX_Comm_agree.3
+++ b/linx64/mpi/mpich/share/man/man3/MPIX_Comm_agree.3
@@ -1,4 +1,4 @@
-.TH MPIX_Comm_agree 3 "11/10/2017" " " "MPI"
+.TH MPIX_Comm_agree 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPIX_Comm_agree \-  Performs agreement operation on comm 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPIX_Comm_failure_ack.3 b/linx64/mpi/mpich/share/man/man3/MPIX_Comm_failure_ack.3
index 9c9bb260..35713a4c 100644
--- a/linx64/mpi/mpich/share/man/man3/MPIX_Comm_failure_ack.3
+++ b/linx64/mpi/mpich/share/man/man3/MPIX_Comm_failure_ack.3
@@ -1,9 +1,9 @@
-.TH MPIX_Comm_failure_ack 3 "11/10/2017" " " "MPI"
+.TH MPIX_Comm_failure_ack 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPIX_Comm_failure_ack \-  Acknowledge the current group of failed processes 
 .SH SYNOPSIS
 .nf
-int MPIX_Comm_failure_ack( MPI_Comm comm )
+int MPIX_Comm_failure_ack(MPI_Comm comm)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPIX_Comm_failure_get_acked.3 b/linx64/mpi/mpich/share/man/man3/MPIX_Comm_failure_get_acked.3
index 7c1deaad..1174b026 100644
--- a/linx64/mpi/mpich/share/man/man3/MPIX_Comm_failure_get_acked.3
+++ b/linx64/mpi/mpich/share/man/man3/MPIX_Comm_failure_get_acked.3
@@ -1,9 +1,9 @@
-.TH MPIX_Comm_failure_get_acked 3 "11/10/2017" " " "MPI"
+.TH MPIX_Comm_failure_get_acked 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPIX_Comm_failure_get_acked \-  Get the group of acknowledged failures. 
 .SH SYNOPSIS
 .nf
-int MPIX_Comm_failure_get_acked( MPI_Comm comm, MPI_Group *failedgrp )
+int MPIX_Comm_failure_get_acked(MPI_Comm comm, MPI_Group * failedgrp)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPIX_Comm_revoke.3 b/linx64/mpi/mpich/share/man/man3/MPIX_Comm_revoke.3
index 8d54c7ad..9bc05e86 100644
--- a/linx64/mpi/mpich/share/man/man3/MPIX_Comm_revoke.3
+++ b/linx64/mpi/mpich/share/man/man3/MPIX_Comm_revoke.3
@@ -1,4 +1,4 @@
-.TH MPIX_Comm_revoke 3 "11/10/2017" " " "MPI"
+.TH MPIX_Comm_revoke 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPIX_Comm_revoke \-  Prevent a communicator from being used in the future 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPIX_Comm_shrink.3 b/linx64/mpi/mpich/share/man/man3/MPIX_Comm_shrink.3
index 80a31269..bb792c81 100644
--- a/linx64/mpi/mpich/share/man/man3/MPIX_Comm_shrink.3
+++ b/linx64/mpi/mpich/share/man/man3/MPIX_Comm_shrink.3
@@ -1,9 +1,9 @@
-.TH MPIX_Comm_shrink 3 "11/10/2017" " " "MPI"
+.TH MPIX_Comm_shrink 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPIX_Comm_shrink \-  Creates a new communitor from an existing communicator while excluding failed processes 
 .SH SYNOPSIS
 .nf
-int MPIX_Comm_shrink(MPI_Comm comm, MPI_Comm *newcomm)
+int MPIX_Comm_shrink(MPI_Comm comm, MPI_Comm * newcomm)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Abort.3 b/linx64/mpi/mpich/share/man/man3/MPI_Abort.3
index 12456d5c..67ba30fe 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Abort.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Abort.3
@@ -1,4 +1,4 @@
-.TH MPI_Abort 3 "11/10/2017" " " "MPI"
+.TH MPI_Abort 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Abort \-  Terminates MPI execution environment 
 .SH SYNOPSIS
@@ -9,12 +9,12 @@ int MPI_Abort(MPI_Comm comm, int errorcode)
 .PD 0
 .TP
 .B comm 
-- communicator of tasks to abort 
+- communicator of tasks to abort
 .PD 1
 .PD 0
 .TP
 .B errorcode 
-- error code to return to invoking environment 
+- error code to return to invoking environment
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Accumulate.3 b/linx64/mpi/mpich/share/man/man3/MPI_Accumulate.3
index ad000bd8..d1622ff8 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Accumulate.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Accumulate.3
@@ -1,59 +1,59 @@
-.TH MPI_Accumulate 3 "11/10/2017" " " "MPI"
+.TH MPI_Accumulate 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Accumulate \-  Accumulate data into the target process using remote  memory access  
+MPI_Accumulate \-  Accumulate data into the target process using remote memory access 
 .SH SYNOPSIS
 .nf
 int MPI_Accumulate(const void *origin_addr, int origin_count, MPI_Datatype
                    origin_datatype, int target_rank, MPI_Aint
                    target_disp, int target_count, MPI_Datatype
-                   target_datatype, MPI_Op op, MPI_Win win) 
+                   target_datatype, MPI_Op op, MPI_Win win)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B origin_addr 
-- initial address of buffer (choice) 
+- initial address of buffer (choice)
 .PD 1
 .PD 0
 .TP
 .B origin_count 
-- number of entries in buffer (nonnegative integer) 
+- number of entries in buffer (nonnegative integer)
 .PD 1
 .PD 0
 .TP
 .B origin_datatype 
-- datatype of each buffer entry (handle) 
+- datatype of each buffer entry (handle)
 .PD 1
 .PD 0
 .TP
 .B target_rank 
-- rank of target (nonnegative integer) 
+- rank of target (nonnegative integer)
 .PD 1
 .PD 0
 .TP
 .B target_disp 
-- displacement from start of window to beginning of target 
-buffer (nonnegative integer)  
+- displacement from start of window to beginning of target
+buffer (nonnegative integer)
 .PD 1
 .PD 0
 .TP
 .B target_count 
-- number of entries in target buffer (nonnegative integer) 
+- number of entries in target buffer (nonnegative integer)
 .PD 1
 .PD 0
 .TP
 .B target_datatype 
-- datatype of each entry in target buffer (handle) 
+- datatype of each entry in target buffer (handle)
 .PD 1
 .PD 0
 .TP
 .B op 
-- predefined reduce operation (handle) 
+- predefined reduce operation (handle)
 .PD 1
 .PD 0
 .TP
 .B win 
-- window object (handle) 
+- window object (handle)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Add_error_class.3 b/linx64/mpi/mpich/share/man/man3/MPI_Add_error_class.3
index 8fdcd13e..926a7cd1 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Add_error_class.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Add_error_class.3
@@ -1,4 +1,4 @@
-.TH MPI_Add_error_class 3 "11/10/2017" " " "MPI"
+.TH MPI_Add_error_class 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Add_error_class \-  Add an MPI error class to the known classes 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Add_error_code.3 b/linx64/mpi/mpich/share/man/man3/MPI_Add_error_code.3
index 9eed5b89..1f27ffe8 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Add_error_code.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Add_error_code.3
@@ -1,4 +1,4 @@
-.TH MPI_Add_error_code 3 "11/10/2017" " " "MPI"
+.TH MPI_Add_error_code 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Add_error_code \-  Add an MPI error code to an MPI error class 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Add_error_string.3 b/linx64/mpi/mpich/share/man/man3/MPI_Add_error_string.3
index de4df8d4..0ce90124 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Add_error_string.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Add_error_string.3
@@ -1,6 +1,6 @@
-.TH MPI_Add_error_string 3 "11/10/2017" " " "MPI"
+.TH MPI_Add_error_string 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Add_error_string \-  Associates an error string with an MPI error code or  class 
+MPI_Add_error_string \-  Associates an error string with an MPI error code or class 
 .SH SYNOPSIS
 .nf
 int MPI_Add_error_string(int errorcode, const char *string)
@@ -9,12 +9,12 @@ int MPI_Add_error_string(int errorcode, const char *string)
 .PD 0
 .TP
 .B errorcode 
-- error code or class (integer) 
+- error code or class (integer)
 .PD 1
 .PD 0
 .TP
 .B string 
-- text corresponding to errorcode (string) 
+- text corresponding to errorcode (string)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Address.3 b/linx64/mpi/mpich/share/man/man3/MPI_Address.3
index dcc6079a..4c78b525 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Address.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Address.3
@@ -1,9 +1,9 @@
-.TH MPI_Address 3 "11/10/2017" " " "MPI"
+.TH MPI_Address 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Address \-  Gets the address of a location in memory 
 .SH SYNOPSIS
 .nf
-int MPI_Address(void *location, MPI_Aint *address)
+int MPI_Address(void *location, MPI_Aint * address)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Aint_add.3 b/linx64/mpi/mpich/share/man/man3/MPI_Aint_add.3
index 90d8f004..6cee7182 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Aint_add.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Aint_add.3
@@ -1,4 +1,4 @@
-.TH MPI_Aint_add 3 "11/10/2017" " " "MPI"
+.TH MPI_Aint_add 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Aint_add \-  Returns the sum of base and disp 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Aint_diff.3 b/linx64/mpi/mpich/share/man/man3/MPI_Aint_diff.3
index e357103c..58daaa1f 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Aint_diff.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Aint_diff.3
@@ -1,4 +1,4 @@
-.TH MPI_Aint_diff 3 "11/10/2017" " " "MPI"
+.TH MPI_Aint_diff 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Aint_diff \-  Returns the difference between addr1 and addr2 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Allgather.3 b/linx64/mpi/mpich/share/man/man3/MPI_Allgather.3
index 4ae490ca..154aa0e5 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Allgather.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Allgather.3
@@ -1,49 +1,48 @@
-.TH MPI_Allgather 3 "11/10/2017" " " "MPI"
+.TH MPI_Allgather 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Allgather \-  Gathers data from all tasks and distribute the combined data to all tasks 
 .SH SYNOPSIS
 .nf
 int MPI_Allgather(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
-                  void *recvbuf, int recvcount, MPI_Datatype recvtype,
-                  MPI_Comm comm)
+                  void *recvbuf, int recvcount, MPI_Datatype recvtype, MPI_Comm comm)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B sendbuf 
-- starting address of send buffer (choice) 
+- starting address of send buffer (choice)
 .PD 1
 .PD 0
 .TP
 .B sendcount 
-- number of elements in send buffer (integer) 
+- number of elements in send buffer (integer)
 .PD 1
 .PD 0
 .TP
 .B sendtype 
-- data type of send buffer elements (handle) 
+- data type of send buffer elements (handle)
 .PD 1
 .PD 0
 .TP
 .B recvcount 
-- number of elements received from any process (integer) 
+- number of elements received from any process (integer)
 .PD 1
 .PD 0
 .TP
 .B recvtype 
-- data type of receive buffer elements (handle) 
+- data type of receive buffer elements (handle)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B recvbuf 
-- address of receive buffer (choice) 
+- address of receive buffer (choice)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Allgatherv.3 b/linx64/mpi/mpich/share/man/man3/MPI_Allgatherv.3
index ab93d3a5..622217b9 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Allgatherv.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Allgatherv.3
@@ -1,4 +1,4 @@
-.TH MPI_Allgatherv 3 "11/10/2017" " " "MPI"
+.TH MPI_Allgatherv 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Allgatherv \-  Gathers data from all tasks and deliver the combined data to all tasks 
 .SH SYNOPSIS
@@ -11,30 +11,30 @@ int MPI_Allgatherv(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
 .PD 0
 .TP
 .B sendbuf 
-- starting address of send buffer (choice) 
+- starting address of send buffer (choice)
 .PD 1
 .PD 0
 .TP
 .B sendcount 
-- number of elements in send buffer (integer) 
+- number of elements in send buffer (integer)
 .PD 1
 .PD 0
 .TP
 .B sendtype 
-- data type of send buffer elements (handle) 
+- data type of send buffer elements (handle)
 .PD 1
 .PD 0
 .TP
 .B recvcounts 
-- integer array (of length group size) 
-containing the number of elements that are to be received from each process 
+- integer array (of length group size)
+containing the number of elements that are to be received from each process
 .PD 1
 .PD 0
 .TP
 .B displs 
-- integer array (of length group size). Entry 
+- integer array (of length group size). Entry
 .I i
-specifies the displacement (relative to recvbuf ) at
+specifies the displacement (relative to recvbuf) at
 which to place the incoming data from process  
 .I i
 
@@ -42,19 +42,19 @@ which to place the incoming data from process
 .PD 0
 .TP
 .B recvtype 
-- data type of receive buffer elements (handle) 
+- data type of receive buffer elements (handle)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B recvbuf 
-- address of receive buffer (choice) 
+- address of receive buffer (choice)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Alloc_mem.3 b/linx64/mpi/mpich/share/man/man3/MPI_Alloc_mem.3
index 4a695f9c..6004f1f8 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Alloc_mem.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Alloc_mem.3
@@ -1,4 +1,4 @@
-.TH MPI_Alloc_mem 3 "11/10/2017" " " "MPI"
+.TH MPI_Alloc_mem 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Alloc_mem \-  Allocate memory for message passing and RMA 
 .SH SYNOPSIS
@@ -9,19 +9,19 @@ int MPI_Alloc_mem(MPI_Aint size, MPI_Info info, void *baseptr)
 .PD 0
 .TP
 .B size 
-- size of memory segment in bytes (nonnegative integer) 
+- size of memory segment in bytes (nonnegative integer)
 .PD 1
 .PD 0
 .TP
 .B info 
-- info argument (handle) 
+- info argument (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B baseptr 
-- pointer to beginning of memory segment allocated 
+- pointer to beginning of memory segment allocated
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Allreduce.3 b/linx64/mpi/mpich/share/man/man3/MPI_Allreduce.3
index 6e5411ad..138db559 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Allreduce.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Allreduce.3
@@ -1,4 +1,4 @@
-.TH MPI_Allreduce 3 "11/10/2017" " " "MPI"
+.TH MPI_Allreduce 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Allreduce \-  Combines values from all processes and distributes the result back to all processes 
 .SH SYNOPSIS
@@ -10,34 +10,34 @@ int MPI_Allreduce(const void *sendbuf, void *recvbuf, int count,
 .PD 0
 .TP
 .B sendbuf 
-- starting address of send buffer (choice) 
+- starting address of send buffer (choice)
 .PD 1
 .PD 0
 .TP
 .B count 
-- number of elements in send buffer (integer) 
+- number of elements in send buffer (integer)
 .PD 1
 .PD 0
 .TP
 .B datatype 
-- data type of elements of send buffer (handle) 
+- data type of elements of send buffer (handle)
 .PD 1
 .PD 0
 .TP
 .B op 
-- operation (handle) 
+- operation (handle)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B recvbuf 
-- starting address of receive buffer (choice) 
+- starting address of receive buffer (choice)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Alltoall.3 b/linx64/mpi/mpich/share/man/man3/MPI_Alltoall.3
index ce565778..bfebf0a7 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Alltoall.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Alltoall.3
@@ -1,49 +1,48 @@
-.TH MPI_Alltoall 3 "11/10/2017" " " "MPI"
+.TH MPI_Alltoall 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Alltoall \-  Sends data from all to all processes 
 .SH SYNOPSIS
 .nf
 int MPI_Alltoall(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
-                 void *recvbuf, int recvcount, MPI_Datatype recvtype,
-                 MPI_Comm comm)
+                 void *recvbuf, int recvcount, MPI_Datatype recvtype, MPI_Comm comm)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B sendbuf 
-- starting address of send buffer (choice) 
+- starting address of send buffer (choice)
 .PD 1
 .PD 0
 .TP
 .B sendcount 
-- number of elements to send to each process (integer) 
+- number of elements to send to each process (integer)
 .PD 1
 .PD 0
 .TP
 .B sendtype 
-- data type of send buffer elements (handle) 
+- data type of send buffer elements (handle)
 .PD 1
 .PD 0
 .TP
 .B recvcount 
-- number of elements received from any process (integer) 
+- number of elements received from any process (integer)
 .PD 1
 .PD 0
 .TP
 .B recvtype 
-- data type of receive buffer elements (handle) 
+- data type of receive buffer elements (handle)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B recvbuf 
-- address of receive buffer (choice) 
+- address of receive buffer (choice)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Alltoallv.3 b/linx64/mpi/mpich/share/man/man3/MPI_Alltoallv.3
index 768adb7d..b76894a2 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Alltoallv.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Alltoallv.3
@@ -1,29 +1,28 @@
-.TH MPI_Alltoallv 3 "11/10/2017" " " "MPI"
+.TH MPI_Alltoallv 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Alltoallv \-  Sends data from all to all processes; each process may  send a different amount of data and provide displacements for the input and output data. 
+MPI_Alltoallv \-  Sends data from all to all processes; each process may send a different amount of data and provide displacements for the input and output data. 
 .SH SYNOPSIS
 .nf
 int MPI_Alltoallv(const void *sendbuf, const int *sendcounts,
                   const int *sdispls, MPI_Datatype sendtype, void *recvbuf,
-                  const int *recvcounts, const int *rdispls, MPI_Datatype recvtype,
-                  MPI_Comm comm)
+                  const int *recvcounts, const int *rdispls, MPI_Datatype recvtype, MPI_Comm comm)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B sendbuf 
-- starting address of send buffer (choice) 
+- starting address of send buffer (choice)
 .PD 1
 .PD 0
 .TP
 .B sendcounts 
-- integer array equal to the group size 
-specifying the number of elements to send to each processor 
+- integer array equal to the group size
+specifying the number of elements to send to each processor
 .PD 1
 .PD 0
 .TP
 .B sdispls 
-- integer array (of length group size). Entry 
+- integer array (of length group size). Entry
 .I j
 specifies the displacement (relative to sendbuf  from
 which to take the outgoing data destined for process  
@@ -33,19 +32,19 @@ which to take the outgoing data destined for process
 .PD 0
 .TP
 .B sendtype 
-- data type of send buffer elements (handle) 
+- data type of send buffer elements (handle)
 .PD 1
 .PD 0
 .TP
 .B recvcounts 
-- integer array equal to the group size 
+- integer array equal to the group size
 specifying the maximum number of elements that can be received from
-each processor 
+each processor
 .PD 1
 .PD 0
 .TP
 .B rdispls 
-- integer array (of length group size). Entry 
+- integer array (of length group size). Entry
 .I i
 specifies the displacement (relative to recvbuf  at
 which to place the incoming data from process  
@@ -55,19 +54,19 @@ which to place the incoming data from process
 .PD 0
 .TP
 .B recvtype 
-- data type of receive buffer elements (handle) 
+- data type of receive buffer elements (handle)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B recvbuf 
-- address of receive buffer (choice) 
+- address of receive buffer (choice)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Alltoallw.3 b/linx64/mpi/mpich/share/man/man3/MPI_Alltoallw.3
index 1e5fae63..9b194151 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Alltoallw.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Alltoallw.3
@@ -1,4 +1,4 @@
-.TH MPI_Alltoallw 3 "11/10/2017" " " "MPI"
+.TH MPI_Alltoallw 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Alltoallw \-  Generalized all-to-all communication allowing different datatypes, counts, and displacements for each partner 
 .SH SYNOPSIS
@@ -12,57 +12,57 @@ int MPI_Alltoallw(const void *sendbuf, const int sendcounts[],
 .PD 0
 .TP
 .B sendbuf 
-- starting address of send buffer (choice) 
+- starting address of send buffer (choice)
 .PD 1
 .PD 0
 .TP
 .B sendcounts 
-- integer array equal to the group size specifying the number of 
-elements to send to each processor (integer) 
+- integer array equal to the group size specifying the number of
+elements to send to each processor (integer)
 .PD 1
 .PD 0
 .TP
 .B sdispls 
-- integer array (of length group size). Entry j specifies the 
-displacement in bytes (relative to sendbuf) from which to take the outgoing 
-data destined for process j 
+- integer array (of length group size). Entry j specifies the
+displacement in bytes (relative to sendbuf) from which to take the outgoing
+data destined for process j
 .PD 1
 .PD 0
 .TP
 .B sendtypes 
-- array of datatypes (of length group size). Entry j specifies the 
-type of data to send to process j (handle) 
+- array of datatypes (of length group size). Entry j specifies the
+type of data to send to process j (handle)
 .PD 1
 .PD 0
 .TP
 .B recvcounts 
 - integer array equal to the group size specifying the number of
-elements that can be received from each processor (integer) 
+elements that can be received from each processor (integer)
 .PD 1
 .PD 0
 .TP
 .B rdispls 
-- integer array (of length group size). Entry i specifies the 
-displacement in bytes (relative to recvbuf) at which to place the incoming 
-data from process i 
+- integer array (of length group size). Entry i specifies the
+displacement in bytes (relative to recvbuf) at which to place the incoming
+data from process i
 .PD 1
 .PD 0
 .TP
 .B recvtypes 
-- array of datatypes (of length group size). Entry i specifies 
-the type of data received from process i (handle) 
+- array of datatypes (of length group size). Entry i specifies
+the type of data received from process i (handle)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B recvbuf 
-- address of receive buffer (choice) 
+- address of receive buffer (choice)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Attr_delete.3 b/linx64/mpi/mpich/share/man/man3/MPI_Attr_delete.3
index e9b9e525..97a1c9c6 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Attr_delete.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Attr_delete.3
@@ -1,6 +1,6 @@
-.TH MPI_Attr_delete 3 "11/10/2017" " " "MPI"
+.TH MPI_Attr_delete 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Attr_delete \-  Deletes an attribute value associated with a key on a  communicator 
+MPI_Attr_delete \-  Deletes an attribute value associated with a key on a communicator 
 .SH SYNOPSIS
 .nf
 int MPI_Attr_delete(MPI_Comm comm, int keyval)
@@ -9,12 +9,12 @@ int MPI_Attr_delete(MPI_Comm comm, int keyval)
 .PD 0
 .TP
 .B comm 
-- communicator to which attribute is attached (handle) 
+- communicator to which attribute is attached (handle)
 .PD 1
 .PD 0
 .TP
 .B keyval 
-- The key value of the deleted attribute (integer) 
+- The key value of the deleted attribute (integer)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Attr_get.3 b/linx64/mpi/mpich/share/man/man3/MPI_Attr_get.3
index 43fb35b8..ef3847aa 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Attr_get.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Attr_get.3
@@ -1,4 +1,4 @@
-.TH MPI_Attr_get 3 "11/10/2017" " " "MPI"
+.TH MPI_Attr_get 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Attr_get \-  Retrieves attribute value by key 
 .SH SYNOPSIS
@@ -9,12 +9,12 @@ int MPI_Attr_get(MPI_Comm comm, int keyval, void *attribute_val, int *flag)
 .PD 0
 .TP
 .B comm 
-- communicator to which attribute is attached (handle) 
+- communicator to which attribute is attached (handle)
 .PD 1
 .PD 0
 .TP
 .B keyval 
-- key value (integer) 
+- key value (integer)
 .PD 1
 
 .SH OUTPUT PARAMETERS
@@ -29,7 +29,7 @@ int MPI_Attr_get(MPI_Comm comm, int keyval, void *attribute_val, int *flag)
 .TP
 .B flag 
 - true if an attribute value was extracted;  false if no attribute is
-associated with the key 
+associated with the key
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Attr_put.3 b/linx64/mpi/mpich/share/man/man3/MPI_Attr_put.3
index 47012a7c..e2b73d62 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Attr_put.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Attr_put.3
@@ -1,4 +1,4 @@
-.TH MPI_Attr_put 3 "11/10/2017" " " "MPI"
+.TH MPI_Attr_put 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Attr_put \-  Stores attribute value associated with a key 
 .SH SYNOPSIS
@@ -9,19 +9,19 @@ int MPI_Attr_put(MPI_Comm comm, int keyval, void *attribute_val)
 .PD 0
 .TP
 .B comm 
-- communicator to which attribute will be attached (handle) 
+- communicator to which attribute will be attached (handle)
 .PD 1
 .PD 0
 .TP
 .B keyval 
 - key value, as returned by  
 .I MPI_KEYVAL_CREATE
-(integer) 
+(integer)
 .PD 1
 .PD 0
 .TP
 .B attribute_val 
-- attribute value 
+- attribute value
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Barrier.3 b/linx64/mpi/mpich/share/man/man3/MPI_Barrier.3
index a9b97ffa..6771c409 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Barrier.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Barrier.3
@@ -1,15 +1,15 @@
-.TH MPI_Barrier 3 "11/10/2017" " " "MPI"
+.TH MPI_Barrier 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Barrier \-  Blocks until all processes in the communicator have reached this routine.   
+MPI_Barrier \-  Blocks until all processes in the communicator have reached this routine. 
 .SH SYNOPSIS
 .nf
-int MPI_Barrier( MPI_Comm comm )
+int MPI_Barrier(MPI_Comm comm)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Bcast.3 b/linx64/mpi/mpich/share/man/man3/MPI_Bcast.3
index 1cc3689f..5de329ee 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Bcast.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Bcast.3
@@ -1,38 +1,37 @@
-.TH MPI_Bcast 3 "11/10/2017" " " "MPI"
+.TH MPI_Bcast 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Bcast \-  Broadcasts a message from the process with rank "root" to all other processes of the communicator 
 .SH SYNOPSIS
 .nf
-int MPI_Bcast( void *buffer, int count, MPI_Datatype datatype, int root, 
-               MPI_Comm comm )
+int MPI_Bcast(void *buffer, int count, MPI_Datatype datatype, int root, MPI_Comm comm)
 .fi
 .SH INPUT/OUTPUT PARAMETERS
 .PD 0
 .TP
 .B buffer 
-- starting address of buffer (choice) 
+- starting address of buffer (choice)
 .PD 1
 
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B count 
-- number of entries in buffer (integer) 
+- number of entries in buffer (integer)
 .PD 1
 .PD 0
 .TP
 .B datatype 
-- data type of buffer (handle) 
+- data type of buffer (handle)
 .PD 1
 .PD 0
 .TP
 .B root 
-- rank of broadcast root (integer) 
+- rank of broadcast root (integer)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Bsend.3 b/linx64/mpi/mpich/share/man/man3/MPI_Bsend.3
index 3b7d7588..331f1c32 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Bsend.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Bsend.3
@@ -1,41 +1,40 @@
-.TH MPI_Bsend 3 "11/10/2017" " " "MPI"
+.TH MPI_Bsend 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Bsend \-  Basic send with user-provided buffering 
 .SH SYNOPSIS
 .nf
-int MPI_Bsend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-              MPI_Comm comm)
+int MPI_Bsend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag, MPI_Comm comm)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B buf 
-- initial address of send buffer (choice) 
+- initial address of send buffer (choice)
 .PD 1
 .PD 0
 .TP
 .B count 
-- number of elements in send buffer (nonnegative integer) 
+- number of elements in send buffer (nonnegative integer)
 .PD 1
 .PD 0
 .TP
 .B datatype 
-- datatype of each send buffer element (handle) 
+- datatype of each send buffer element (handle)
 .PD 1
 .PD 0
 .TP
 .B dest 
-- rank of destination (integer) 
+- rank of destination (integer)
 .PD 1
 .PD 0
 .TP
 .B tag 
-- message tag (integer) 
+- message tag (integer)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH NOTES
@@ -55,9 +54,9 @@ that the message
 has been received (not just that it should have been received).  For example,
 this code does not allocate enough buffer space
 .nf
-MPI_Buffer_attach( b, n*sizeof(double) + MPI_BSEND_OVERHEAD );
+MPI_Buffer_attach(b, n*sizeof(double) + MPI_BSEND_OVERHEAD);
 for (i=0; i<m; i++) {
-MPI_Bsend( buf, n, MPI_DOUBLE, ... );
+MPI_Bsend(buf, n, MPI_DOUBLE, ...);
 }
 .fi
 
@@ -70,8 +69,8 @@ buffer.
 In C, you can
 force the messages to be delivered by
 .nf
-MPI_Buffer_detach( &b, &n );
-MPI_Buffer_attach( b, n );
+MPI_Buffer_detach(&b, &n);
+MPI_Buffer_attach(b, n);
 .fi
 
 (The 
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Bsend_init.3 b/linx64/mpi/mpich/share/man/man3/MPI_Bsend_init.3
index b3ad306b..6616ede5 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Bsend_init.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Bsend_init.3
@@ -1,48 +1,48 @@
-.TH MPI_Bsend_init 3 "11/10/2017" " " "MPI"
+.TH MPI_Bsend_init 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Bsend_init \-  Builds a handle for a buffered send 
 .SH SYNOPSIS
 .nf
 int MPI_Bsend_init(const void *buf, int count, MPI_Datatype datatype,
-                   int dest, int tag, MPI_Comm comm, MPI_Request *request)
+                   int dest, int tag, MPI_Comm comm, MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B buf 
-- initial address of send buffer (choice) 
+- initial address of send buffer (choice)
 .PD 1
 .PD 0
 .TP
 .B count 
-- number of elements sent (integer) 
+- number of elements sent (integer)
 .PD 1
 .PD 0
 .TP
 .B datatype 
-- type of each element (handle) 
+- type of each element (handle)
 .PD 1
 .PD 0
 .TP
 .B dest 
-- rank of destination (integer) 
+- rank of destination (integer)
 .PD 1
 .PD 0
 .TP
 .B tag 
-- message tag (integer) 
+- message tag (integer)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B request 
-- communication request (handle) 
+- communication request (handle)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Buffer_attach.3 b/linx64/mpi/mpich/share/man/man3/MPI_Buffer_attach.3
index 0932ca2f..88e9abe2 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Buffer_attach.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Buffer_attach.3
@@ -1,6 +1,6 @@
-.TH MPI_Buffer_attach 3 "11/10/2017" " " "MPI"
+.TH MPI_Buffer_attach 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Buffer_attach \-  Attaches a user-provided buffer for sending  
+MPI_Buffer_attach \-  Attaches a user-provided buffer for sending 
 .SH SYNOPSIS
 .nf
 int MPI_Buffer_attach(void *buffer, int size)
@@ -9,12 +9,12 @@ int MPI_Buffer_attach(void *buffer, int size)
 .PD 0
 .TP
 .B buffer 
-- initial buffer address (choice) 
+- initial buffer address (choice)
 .PD 1
 .PD 0
 .TP
 .B size 
-- buffer size, in bytes (integer) 
+- buffer size, in bytes (integer)
 .PD 1
 
 .SH NOTES
@@ -28,12 +28,12 @@ For the purposes of calculating size, you should use
 
 In other words, in the code
 .nf
-MPI_Buffer_attach( buffer, size );
-MPI_Bsend( ..., count=20, datatype=type1,  ... );
+MPI_Buffer_attach(buffer, size);
+MPI_Bsend(..., count=20, datatype=type1,  ...);
 \&.
 \&.
 \&.
-MPI_Bsend( ..., count=40, datatype=type2, ... );
+MPI_Bsend(..., count=40, datatype=type2, ...);
 .fi
 
 the value of 
@@ -43,8 +43,8 @@ in the
 call should be greater than
 the value computed by
 .nf
-MPI_Pack_size( 20, type1, comm, &s1 );
-MPI_Pack_size( 40, type2, comm, &s2 );
+MPI_Pack_size(20, type1, comm, &s1);
+MPI_Pack_size(40, type2, comm, &s2);
 size = s1 + s2 + 2 * MPI_BSEND_OVERHEAD;
 .fi
 
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Buffer_detach.3 b/linx64/mpi/mpich/share/man/man3/MPI_Buffer_detach.3
index 7e42f7fc..0fd408e0 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Buffer_detach.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Buffer_detach.3
@@ -1,4 +1,4 @@
-.TH MPI_Buffer_detach 3 "11/10/2017" " " "MPI"
+.TH MPI_Buffer_detach 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Buffer_detach \-  Removes an existing buffer (for use in MPI_Bsend etc) 
 .SH SYNOPSIS
@@ -14,7 +14,7 @@ int MPI_Buffer_detach(void *buffer_addr, int *size)
 .PD 0
 .TP
 .B size 
-- buffer size, in bytes (integer) 
+- buffer size, in bytes (integer)
 .PD 1
 
 .SH NOTES
@@ -26,9 +26,9 @@ the buffer.  For example, consider
 
 .nf
 int size, mysize, idummy;
-void *ptr, *myptr, *dummy;     
-MPI_Buffer_detach( &ptr, &size );
-MPI_Buffer_attach( myptr, mysize );
+void *ptr, *myptr, *dummy;
+MPI_Buffer_detach(&ptr, &size);
+MPI_Buffer_attach(myptr, mysize);
 \&.
 \&.
 \&.
@@ -39,8 +39,8 @@ library code ...
 \&.
 \&.
 \&.
-MPI_Buffer_detach( &dummy, &idummy );
-MPI_Buffer_attach( ptr, size );
+MPI_Buffer_detach(&dummy, &idummy);
+MPI_Buffer_attach(ptr, size);
 .fi
 
 
@@ -55,7 +55,7 @@ contains the text
 
 .nf
 The statements made in this section describe the behavior of MPI for
-buffered-mode sends. When no buffer is currently associated, MPI behaves 
+buffered-mode sends. When no buffer is currently associated, MPI behaves
 as if a zero-sized buffer is associated with the process.
 .fi
 
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Cancel.3 b/linx64/mpi/mpich/share/man/man3/MPI_Cancel.3
index c2bf635c..0bfa78f6 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Cancel.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Cancel.3
@@ -1,15 +1,15 @@
-.TH MPI_Cancel 3 "11/10/2017" " " "MPI"
+.TH MPI_Cancel 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Cancel \-  Cancels a communication request 
 .SH SYNOPSIS
 .nf
-int MPI_Cancel(MPI_Request *request)
+int MPI_Cancel(MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B request 
-- communication request (handle) 
+- communication request (handle)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Cart_coords.3 b/linx64/mpi/mpich/share/man/man3/MPI_Cart_coords.3
index 2e9530d9..0b368e60 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Cart_coords.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Cart_coords.3
@@ -1,4 +1,4 @@
-.TH MPI_Cart_coords 3 "11/10/2017" " " "MPI"
+.TH MPI_Cart_coords 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Cart_coords \-  Determines process coords in cartesian topology given rank in group 
 .SH SYNOPSIS
@@ -9,21 +9,21 @@ int MPI_Cart_coords(MPI_Comm comm, int rank, int maxdims, int coords[])
 .PD 0
 .TP
 .B comm 
-- communicator with cartesian structure (handle) 
+- communicator with cartesian structure (handle)
 .PD 1
 .PD 0
 .TP
 .B rank 
 - rank of a process within group of 
 .I comm
-(integer) 
+(integer)
 .PD 1
 .PD 0
 .TP
 .B maxdims 
 - length of vector 
 .I coords
-in the calling program (integer) 
+in the calling program (integer)
 .PD 1
 
 .SH OUTPUT PARAMETERS
@@ -32,8 +32,8 @@ in the calling program (integer)
 .B coords 
 - integer array (of size 
 .I ndims
-) containing the Cartesian 
-coordinates of specified process (integer) 
+) containing the Cartesian
+coordinates of specified process (integer)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Cart_create.3 b/linx64/mpi/mpich/share/man/man3/MPI_Cart_create.3
index 244d1161..8ab39d16 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Cart_create.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Cart_create.3
@@ -1,45 +1,45 @@
-.TH MPI_Cart_create 3 "11/10/2017" " " "MPI"
+.TH MPI_Cart_create 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Cart_create \-  Makes a new communicator to which topology information has been attached 
 .SH SYNOPSIS
 .nf
 int MPI_Cart_create(MPI_Comm comm_old, int ndims, const int dims[],
-                    const int periods[], int reorder, MPI_Comm *comm_cart)
+                    const int periods[], int reorder, MPI_Comm * comm_cart)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B comm_old 
-- input communicator (handle) 
+- input communicator (handle)
 .PD 1
 .PD 0
 .TP
 .B ndims 
-- number of dimensions of cartesian grid (integer) 
+- number of dimensions of cartesian grid (integer)
 .PD 1
 .PD 0
 .TP
 .B dims 
-- integer array of size ndims specifying the number of processes in 
-each dimension 
+- integer array of size ndims specifying the number of processes in
+each dimension
 .PD 1
 .PD 0
 .TP
 .B periods 
-- logical array of size ndims specifying whether the grid is 
-periodic (true) or not (false) in each dimension 
+- logical array of size ndims specifying whether the grid is
+periodic (true) or not (false) in each dimension
 .PD 1
 .PD 0
 .TP
 .B reorder 
-- ranking may be reordered (true) or not (false) (logical) 
+- ranking may be reordered (true) or not (false) (logical)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B comm_cart 
-- communicator with new cartesian topology (handle) 
+- communicator with new cartesian topology (handle)
 .PD 1
 
 .SH ALGORITHM
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Cart_get.3 b/linx64/mpi/mpich/share/man/man3/MPI_Cart_get.3
index 5d9c3983..e9216359 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Cart_get.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Cart_get.3
@@ -1,16 +1,15 @@
-.TH MPI_Cart_get 3 "11/10/2017" " " "MPI"
+.TH MPI_Cart_get 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Cart_get \-  Retrieves Cartesian topology information associated with a  communicator 
+MPI_Cart_get \-  Retrieves Cartesian topology information associated with a communicator 
 .SH SYNOPSIS
 .nf
-int MPI_Cart_get(MPI_Comm comm, int maxdims, int dims[], int periods[],
-                 int coords[])
+int MPI_Cart_get(MPI_Comm comm, int maxdims, int dims[], int periods[], int coords[])
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B comm 
-- communicator with cartesian structure (handle) 
+- communicator with cartesian structure (handle)
 .PD 1
 .PD 0
 .TP
@@ -21,26 +20,26 @@ int MPI_Cart_get(MPI_Comm comm, int maxdims, int dims[], int periods[],
 .I periods
 , and 
 .I coords
-in the calling program (integer) 
+in the calling program (integer)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B dims 
-- number of processes for each cartesian dimension (array of integer) 
+- number of processes for each cartesian dimension (array of integer)
 .PD 1
 .PD 0
 .TP
 .B periods 
-- periodicity (true/false) for each cartesian dimension 
-(array of logical) 
+- periodicity (true/false) for each cartesian dimension
+(array of logical)
 .PD 1
 .PD 0
 .TP
 .B coords 
-- coordinates of calling process in cartesian structure 
-(array of integer) 
+- coordinates of calling process in cartesian structure
+(array of integer)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Cart_map.3 b/linx64/mpi/mpich/share/man/man3/MPI_Cart_map.3
index 42d75e36..6380d991 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Cart_map.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Cart_map.3
@@ -1,37 +1,36 @@
-.TH MPI_Cart_map 3 "11/10/2017" " " "MPI"
+.TH MPI_Cart_map 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Cart_map \-  Maps process to Cartesian topology information  
+MPI_Cart_map \-  Maps process to Cartesian topology information 
 .SH SYNOPSIS
 .nf
-int MPI_Cart_map(MPI_Comm comm, int ndims, const int dims[], const int periods[],
-                int *newrank)
+int MPI_Cart_map(MPI_Comm comm, int ndims, const int dims[], const int periods[], int *newrank)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B comm 
-- input communicator (handle) 
+- input communicator (handle)
 .PD 1
 .PD 0
 .TP
 .B ndims 
-- number of dimensions of Cartesian structure (integer) 
+- number of dimensions of Cartesian structure (integer)
 .PD 1
 .PD 0
 .TP
 .B dims 
 - integer array of size 
 .I ndims
-specifying the number of processes in 
-each coordinate direction 
+specifying the number of processes in
+each coordinate direction
 .PD 1
 .PD 0
 .TP
 .B periods 
 - logical array of size 
 .I ndims
-specifying the periodicity 
-specification in each coordinate direction 
+specifying the periodicity
+specification in each coordinate direction
 .PD 1
 
 .SH OUTPUT PARAMETERS
@@ -40,8 +39,8 @@ specification in each coordinate direction
 .B newrank 
 - reordered rank of the calling process; 
 .I MPI_UNDEFINED
-if 
-calling process does not belong to grid (integer) 
+if
+calling process does not belong to grid (integer)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Cart_rank.3 b/linx64/mpi/mpich/share/man/man3/MPI_Cart_rank.3
index 68e88664..f477c35b 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Cart_rank.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Cart_rank.3
@@ -1,4 +1,4 @@
-.TH MPI_Cart_rank 3 "11/10/2017" " " "MPI"
+.TH MPI_Cart_rank 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Cart_rank \-  Determines process rank in communicator given Cartesian location 
 .SH SYNOPSIS
@@ -9,7 +9,7 @@ int MPI_Cart_rank(MPI_Comm comm, const int coords[], int *rank)
 .PD 0
 .TP
 .B comm 
-- communicator with cartesian structure (handle) 
+- communicator with cartesian structure (handle)
 .PD 1
 .PD 0
 .TP
@@ -19,15 +19,15 @@ int MPI_Cart_rank(MPI_Comm comm, const int coords[], int *rank)
 , the number of dimensions of
 the Cartesian topology associated with 
 .I comm
-) specifying the cartesian 
-coordinates of a process 
+) specifying the cartesian
+coordinates of a process
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B rank 
-- rank of specified process (integer) 
+- rank of specified process (integer)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Cart_shift.3 b/linx64/mpi/mpich/share/man/man3/MPI_Cart_shift.3
index 212ccc79..bc98d29a 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Cart_shift.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Cart_shift.3
@@ -1,21 +1,20 @@
-.TH MPI_Cart_shift 3 "11/10/2017" " " "MPI"
+.TH MPI_Cart_shift 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Cart_shift \-  Returns the shifted source and destination ranks, given a  shift direction and amount 
+MPI_Cart_shift \-  Returns the shifted source and destination ranks, given a shift direction and amount 
 .SH SYNOPSIS
 .nf
-int MPI_Cart_shift(MPI_Comm comm, int direction, int disp, int *rank_source,
-                  int *rank_dest)
+int MPI_Cart_shift(MPI_Comm comm, int direction, int disp, int *rank_source, int *rank_dest)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B comm 
-- communicator with cartesian structure (handle) 
+- communicator with cartesian structure (handle)
 .PD 1
 .PD 0
 .TP
 .B direction 
-- coordinate dimension of shift (integer) 
+- coordinate dimension of shift (integer)
 .PD 1
 .PD 0
 .TP
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Cart_sub.3 b/linx64/mpi/mpich/share/man/man3/MPI_Cart_sub.3
index a22d19f3..ace6278d 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Cart_sub.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Cart_sub.3
@@ -1,15 +1,15 @@
-.TH MPI_Cart_sub 3 "11/10/2017" " " "MPI"
+.TH MPI_Cart_sub 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Cart_sub \-  Partitions a communicator into subgroups which  form lower-dimensional cartesian subgrids 
+MPI_Cart_sub \-  Partitions a communicator into subgroups which form lower-dimensional cartesian subgrids 
 .SH SYNOPSIS
 .nf
-int MPI_Cart_sub(MPI_Comm comm, const int remain_dims[], MPI_Comm *newcomm)
+int MPI_Cart_sub(MPI_Comm comm, const int remain_dims[], MPI_Comm * newcomm)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B comm 
-- communicator with cartesian structure (handle) 
+- communicator with cartesian structure (handle)
 .PD 1
 .PD 0
 .TP
@@ -18,17 +18,17 @@ int MPI_Cart_sub(MPI_Comm comm, const int remain_dims[], MPI_Comm *newcomm)
 .I i
 th entry of remain_dims specifies whether the 
 .I i
-th 
-dimension is kept in the subgrid (true) or is dropped (false) (logical 
-vector) 
+th
+dimension is kept in the subgrid (true) or is dropped (false) (logical
+vector)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B newcomm 
-- communicator containing the subgrid that includes the calling 
-process (handle) 
+- communicator containing the subgrid that includes the calling
+process (handle)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Cartdim_get.3 b/linx64/mpi/mpich/share/man/man3/MPI_Cartdim_get.3
index 50a9556f..7ca0fd9d 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Cartdim_get.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Cartdim_get.3
@@ -1,6 +1,6 @@
-.TH MPI_Cartdim_get 3 "11/10/2017" " " "MPI"
+.TH MPI_Cartdim_get 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Cartdim_get \-  Retrieves Cartesian topology information associated with a  communicator 
+MPI_Cartdim_get \-  Retrieves Cartesian topology information associated with a communicator 
 .SH SYNOPSIS
 .nf
 int MPI_Cartdim_get(MPI_Comm comm, int *ndims)
@@ -9,14 +9,14 @@ int MPI_Cartdim_get(MPI_Comm comm, int *ndims)
 .PD 0
 .TP
 .B comm 
-- communicator with cartesian structure (handle) 
+- communicator with cartesian structure (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B ndims 
-- number of dimensions of the cartesian structure (integer) 
+- number of dimensions of the cartesian structure (integer)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Close_port.3 b/linx64/mpi/mpich/share/man/man3/MPI_Close_port.3
index d5e1b4a7..6dc6c7a2 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Close_port.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Close_port.3
@@ -1,4 +1,4 @@
-.TH MPI_Close_port 3 "11/10/2017" " " "MPI"
+.TH MPI_Close_port 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Close_port \-  close port 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_accept.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_accept.3
index 8c3e85b5..0b2b1642 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_accept.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_accept.3
@@ -1,26 +1,26 @@
-.TH MPI_Comm_accept 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_accept 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Comm_accept \-  Accept a request to form a new intercommunicator 
 .SH SYNOPSIS
 .nf
 int MPI_Comm_accept(const char *port_name, MPI_Info info, int root, MPI_Comm comm,
-                    MPI_Comm *newcomm)
+                    MPI_Comm * newcomm)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B port_name 
-- port name (string, used only on root) 
+- port name (string, used only on root)
 .PD 1
 .PD 0
 .TP
 .B info 
-- implementation-dependent information (handle, used only on root) 
+- implementation-dependent information (handle, used only on root)
 .PD 1
 .PD 0
 .TP
 .B root 
-- rank in comm of root node (integer) 
+- rank in comm of root node (integer)
 .PD 1
 .PD 0
 .TP
@@ -32,7 +32,7 @@ int MPI_Comm_accept(const char *port_name, MPI_Info info, int root, MPI_Comm com
 .PD 0
 .TP
 .B newcomm 
-- intercommunicator with client as remote group (handle) 
+- intercommunicator with client as remote group (handle)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_call_errhandler.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_call_errhandler.3
index 666390f1..b85a9518 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_call_errhandler.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_call_errhandler.3
@@ -1,6 +1,6 @@
-.TH MPI_Comm_call_errhandler 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_call_errhandler 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Comm_call_errhandler \-  Call the error handler installed on a  communicator 
+MPI_Comm_call_errhandler \-  Call the error handler installed on a communicator 
 .SH SYNOPSIS
 .nf
 int MPI_Comm_call_errhandler(MPI_Comm comm, int errorcode)
@@ -9,12 +9,12 @@ int MPI_Comm_call_errhandler(MPI_Comm comm, int errorcode)
 .PD 0
 .TP
 .B comm 
-- communicator with error handler (handle) 
+- communicator with error handler (handle)
 .PD 1
 .PD 0
 .TP
 .B errorcode 
-- error code (integer) 
+- error code (integer)
 .PD 1
 
 .SH NOTE
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_compare.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_compare.3
index 25839152..ca6e5c7d 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_compare.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_compare.3
@@ -1,4 +1,4 @@
-.TH MPI_Comm_compare 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_compare 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Comm_compare \-  Compares two communicators 
 .SH SYNOPSIS
@@ -9,12 +9,12 @@ int MPI_Comm_compare(MPI_Comm comm1, MPI_Comm comm2, int *result)
 .PD 0
 .TP
 .B comm1 
-- comm1 (handle) 
+- comm1 (handle)
 .PD 1
 .PD 0
 .TP
 .B comm2 
-- comm2 (handle) 
+- comm2 (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_connect.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_connect.3
index f39648c2..0cf25f14 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_connect.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_connect.3
@@ -1,38 +1,38 @@
-.TH MPI_Comm_connect 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_connect 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Comm_connect \-  Make a request to form a new intercommunicator 
 .SH SYNOPSIS
 .nf
 int MPI_Comm_connect(const char *port_name, MPI_Info info, int root, MPI_Comm comm,
-                     MPI_Comm *newcomm)
+                     MPI_Comm * newcomm)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B port_name 
-- network address (string, used only on root) 
+- network address (string, used only on root)
 .PD 1
 .PD 0
 .TP
 .B info 
-- implementation-dependent information (handle, used only on root) 
+- implementation-dependent information (handle, used only on root)
 .PD 1
 .PD 0
 .TP
 .B root 
-- rank in comm of root node (integer) 
+- rank in comm of root node (integer)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- intracommunicator over which call is collective (handle) 
+- intracommunicator over which call is collective (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B newcomm 
-- intercommunicator with server as remote group (handle) 
+- intercommunicator with server as remote group (handle)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_create.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_create.3
index ae5a1575..43a23e2b 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_create.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_create.3
@@ -1,22 +1,22 @@
-.TH MPI_Comm_create 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_create 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Comm_create \-  Creates a new communicator 
 .SH SYNOPSIS
 .nf
-int MPI_Comm_create(MPI_Comm comm, MPI_Group group, MPI_Comm *newcomm)
+int MPI_Comm_create(MPI_Comm comm, MPI_Group group, MPI_Comm * newcomm)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 .PD 0
 .TP
 .B group 
 - group, which is a subset of the group of 
 .I comm
-(handle) 
+(handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_create_errhandler.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_create_errhandler.3
index f4d0480d..db71ee88 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_create_errhandler.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_create_errhandler.3
@@ -1,10 +1,10 @@
-.TH MPI_Comm_create_errhandler 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_create_errhandler 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Comm_create_errhandler \-  Create a communicator error handler 
 .SH SYNOPSIS
 .nf
-int MPI_Comm_create_errhandler(MPI_Comm_errhandler_function *comm_errhandler_fn,
-                               MPI_Errhandler *errhandler)
+int MPI_Comm_create_errhandler(MPI_Comm_errhandler_function * comm_errhandler_fn,
+                               MPI_Errhandler * errhandler)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
@@ -17,7 +17,7 @@ int MPI_Comm_create_errhandler(MPI_Comm_errhandler_function *comm_errhandler_fn,
 .PD 0
 .TP
 .B errhandler 
-- MPI error handler (handle) 
+- MPI error handler (handle)
 .PD 1
 
 .SH ERROR HANDLER
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_create_group.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_create_group.3
index 0c66654c..20714856 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_create_group.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_create_group.3
@@ -1,4 +1,4 @@
-.TH MPI_Comm_create_group 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_create_group 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Comm_create_group \-  Creates a new communicator 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_create_keyval.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_create_keyval.3
index fb35a544..0cccc337 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_create_keyval.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_create_keyval.3
@@ -1,11 +1,11 @@
-.TH MPI_Comm_create_keyval 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_create_keyval 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Comm_create_keyval \-  Create a new attribute key  
+MPI_Comm_create_keyval \-  Create a new attribute key 
 .SH SYNOPSIS
 .nf
-int MPI_Comm_create_keyval(MPI_Comm_copy_attr_function *comm_copy_attr_fn, 
-                         MPI_Comm_delete_attr_function *comm_delete_attr_fn, 
-                         int *comm_keyval, void *extra_state)
+int MPI_Comm_create_keyval(MPI_Comm_copy_attr_function * comm_copy_attr_fn,
+                           MPI_Comm_delete_attr_function * comm_delete_attr_fn,
+                           int *comm_keyval, void *extra_state)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
@@ -25,14 +25,14 @@ int MPI_Comm_create_keyval(MPI_Comm_copy_attr_function *comm_copy_attr_fn,
 .PD 0
 .TP
 .B extra_state 
-- Extra state for callback functions 
+- Extra state for callback functions
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B comm_keyval 
-- key value for future access (integer) 
+- key value for future access (integer)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_delete_attr.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_delete_attr.3
index e0dc3aef..426a72e3 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_delete_attr.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_delete_attr.3
@@ -1,6 +1,6 @@
-.TH MPI_Comm_delete_attr 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_delete_attr 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Comm_delete_attr \-  Deletes an attribute value associated with a key on  a  communicator 
+MPI_Comm_delete_attr \-  Deletes an attribute value associated with a key on a  communicator 
 .SH SYNOPSIS
 .nf
 int MPI_Comm_delete_attr(MPI_Comm comm, int comm_keyval)
@@ -9,12 +9,12 @@ int MPI_Comm_delete_attr(MPI_Comm comm, int comm_keyval)
 .PD 0
 .TP
 .B comm 
-- communicator to which attribute is attached (handle) 
+- communicator to which attribute is attached (handle)
 .PD 1
 .PD 0
 .TP
 .B comm_keyval 
-- The key value of the deleted attribute (integer) 
+- The key value of the deleted attribute (integer)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_disconnect.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_disconnect.3
index 68a7448e..db93adf1 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_disconnect.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_disconnect.3
@@ -1,4 +1,4 @@
-.TH MPI_Comm_disconnect 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_disconnect 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Comm_disconnect \-  Disconnect from a communicator 
 .SH SYNOPSIS
@@ -9,7 +9,7 @@ int MPI_Comm_disconnect(MPI_Comm * comm)
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_dup.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_dup.3
index 57e10442..c95549fc 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_dup.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_dup.3
@@ -1,15 +1,15 @@
-.TH MPI_Comm_dup 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_dup 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Comm_dup \-  Duplicates an existing communicator with all its cached information 
 .SH SYNOPSIS
 .nf
-int MPI_Comm_dup(MPI_Comm comm, MPI_Comm *newcomm)
+int MPI_Comm_dup(MPI_Comm comm, MPI_Comm * newcomm)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B comm 
-- Communicator to be duplicated (handle) 
+- Communicator to be duplicated (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
@@ -19,7 +19,7 @@ int MPI_Comm_dup(MPI_Comm comm, MPI_Comm *newcomm)
 - A new communicator over the same group as 
 .I comm
 but with a new
-context. See notes.  (handle) 
+context. See notes.  (handle)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_dup_with_info.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_dup_with_info.3
index 4bdfd472..b1cbe78e 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_dup_with_info.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_dup_with_info.3
@@ -1,4 +1,4 @@
-.TH MPI_Comm_dup_with_info 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_dup_with_info 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Comm_dup_with_info \-  Duplicates an existing communicator with all its cached information 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_free.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_free.3
index cd6d5a74..bd7521e7 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_free.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_free.3
@@ -1,15 +1,15 @@
-.TH MPI_Comm_free 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_free 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Comm_free \-  Marks the communicator object for deallocation 
 .SH SYNOPSIS
 .nf
-int MPI_Comm_free(MPI_Comm *comm)
+int MPI_Comm_free(MPI_Comm * comm)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B comm 
-- Communicator to be destroyed (handle) 
+- Communicator to be destroyed (handle)
 .PD 1
 
 .SH NOTES
@@ -28,7 +28,7 @@ The MPI 1.1 specification, in the section on opaque objects, explicitly
 A null handle argument is an erroneous IN argument in MPI calls, unless an
 exception is explicitly stated in the text that defines the function. Such
 exception is allowed for handles to request objects in Wait and Test calls
-(sections Communication Completion and Multiple Completions ). Otherwise, a
+(sections Communication Completion and Multiple Completions). Otherwise, a
 null handle can only be passed to a function that allocates a new object and
 returns a reference to it in the handle.
 .fi
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_free_keyval.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_free_keyval.3
index ff13a1a5..c8f0035f 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_free_keyval.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_free_keyval.3
@@ -1,4 +1,4 @@
-.TH MPI_Comm_free_keyval 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_free_keyval 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Comm_free_keyval \-  Frees an attribute key for communicators 
 .SH SYNOPSIS
@@ -9,7 +9,7 @@ int MPI_Comm_free_keyval(int *comm_keyval)
 .PD 0
 .TP
 .B comm_keyval 
-- Frees the integer key value (integer) 
+- Frees the integer key value (integer)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_get_attr.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_get_attr.3
index efcd2c15..b2d8de92 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_get_attr.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_get_attr.3
@@ -1,16 +1,15 @@
-.TH MPI_Comm_get_attr 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_get_attr 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Comm_get_attr \-  Retrieves attribute value by key 
 .SH SYNOPSIS
 .nf
-int MPI_Comm_get_attr(MPI_Comm comm, int comm_keyval, void *attribute_val, 
-                     int *flag)
+int MPI_Comm_get_attr(MPI_Comm comm, int comm_keyval, void *attribute_val, int *flag)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B comm 
-- communicator to which attribute is attached (handle) 
+- communicator to which attribute is attached (handle)
 .PD 1
 .PD 0
 .TP
@@ -30,7 +29,7 @@ int MPI_Comm_get_attr(MPI_Comm comm, int comm_keyval, void *attribute_val,
 .TP
 .B flag 
 - true if an attribute value was extracted;  false if no attribute is
-associated with the key 
+associated with the key
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_get_errhandler.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_get_errhandler.3
index acaeb2eb..073d9a21 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_get_errhandler.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_get_errhandler.3
@@ -1,22 +1,22 @@
-.TH MPI_Comm_get_errhandler 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_get_errhandler 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Comm_get_errhandler \-  Get the error handler attached to a communicator 
 .SH SYNOPSIS
 .nf
-int MPI_Comm_get_errhandler(MPI_Comm comm, MPI_Errhandler *errhandler)
+int MPI_Comm_get_errhandler(MPI_Comm comm, MPI_Errhandler * errhandler)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B errhandler 
-- handler currently associated with communicator (handle) 
+- handler currently associated with communicator (handle)
 .PD 1
 
 
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_get_info.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_get_info.3
index 459821aa..6e0cf74b 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_get_info.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_get_info.3
@@ -1,4 +1,4 @@
-.TH MPI_Comm_get_info 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_get_info 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Comm_get_info \-  Returns a new info object containing the hints of the communicator associated with comm. The current setting of all hints actually used by the system related to this communicator is returned in info_used.  If no such hints exist, a handle to a newly created info object is returned that contains no key/value pair.  The user is responsible for freeing info_used via MPI_INFO_FREE. 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_get_name.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_get_name.3
index 599bc414..131b1e00 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_get_name.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_get_name.3
@@ -1,4 +1,4 @@
-.TH MPI_Comm_get_name 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_get_name 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Comm_get_name \-  Return the print name from the communicator 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_get_parent.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_get_parent.3
index 4acc7cfa..54189db3 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_get_parent.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_get_parent.3
@@ -1,15 +1,15 @@
-.TH MPI_Comm_get_parent 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_get_parent 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Comm_get_parent \-  Return the parent communicator for this process 
 .SH SYNOPSIS
 .nf
-int MPI_Comm_get_parent(MPI_Comm *parent)
+int MPI_Comm_get_parent(MPI_Comm * parent)
 .fi
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B parent 
-- the parent communicator (handle) 
+- the parent communicator (handle)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_group.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_group.3
index d7dbc5cf..69981c84 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_group.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_group.3
@@ -1,9 +1,9 @@
-.TH MPI_Comm_group 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_group 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Comm_group \-  Accesses the group associated with given communicator 
 .SH SYNOPSIS
 .nf
-int MPI_Comm_group(MPI_Comm comm, MPI_Group *group)
+int MPI_Comm_group(MPI_Comm comm, MPI_Group * group)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_idup.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_idup.3
index 7ba8b827..15874ea1 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_idup.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_idup.3
@@ -1,9 +1,9 @@
-.TH MPI_Comm_idup 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_idup 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Comm_idup \-  nonblocking communicator duplication 
 .SH SYNOPSIS
 .nf
-int MPI_Comm_idup(MPI_Comm comm, MPI_Comm *newcomm, MPI_Request *request)
+int MPI_Comm_idup(MPI_Comm comm, MPI_Comm * newcomm, MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_join.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_join.3
index a99ea101..92903a8a 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_join.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_join.3
@@ -1,22 +1,22 @@
-.TH MPI_Comm_join 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_join 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Comm_join \-  Create a communicator by joining two processes connected by  a socket. 
+MPI_Comm_join \-  Create a communicator by joining two processes connected by a socket. 
 .SH SYNOPSIS
 .nf
-int MPI_Comm_join(int fd, MPI_Comm *intercomm)
+int MPI_Comm_join(int fd, MPI_Comm * intercomm)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B fd 
-- socket file descriptor 
+- socket file descriptor
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B intercomm 
-- new intercommunicator (handle) 
+- new intercommunicator (handle)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_rank.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_rank.3
index dc190c3a..11bfe2a3 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_rank.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_rank.3
@@ -1,15 +1,15 @@
-.TH MPI_Comm_rank 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_rank 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Comm_rank \-  Determines the rank of the calling process in the communicator 
 .SH SYNOPSIS
 .nf
-int MPI_Comm_rank( MPI_Comm comm, int *rank ) 
+int MPI_Comm_rank(MPI_Comm comm, int *rank)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
@@ -18,7 +18,7 @@ int MPI_Comm_rank( MPI_Comm comm, int *rank )
 .B rank 
 - rank of the calling process in the group of 
 .I comm
-(integer) 
+(integer)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_remote_group.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_remote_group.3
index 50c25bf4..ff0875c7 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_remote_group.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_remote_group.3
@@ -1,9 +1,9 @@
-.TH MPI_Comm_remote_group 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_remote_group 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Comm_remote_group \-  Accesses the remote group associated with  the given inter-communicator 
+MPI_Comm_remote_group \-  Accesses the remote group associated with the given inter-communicator 
 .SH SYNOPSIS
 .nf
-int MPI_Comm_remote_group(MPI_Comm comm, MPI_Group *group)
+int MPI_Comm_remote_group(MPI_Comm comm, MPI_Group * group)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_remote_size.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_remote_size.3
index 0c7db58e..fe168a0c 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_remote_size.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_remote_size.3
@@ -1,6 +1,6 @@
-.TH MPI_Comm_remote_size 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_remote_size 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Comm_remote_size \-  Determines the size of the remote group  associated with an inter-communictor 
+MPI_Comm_remote_size \-  Determines the size of the remote group associated with an inter-communictor 
 .SH SYNOPSIS
 .nf
 int MPI_Comm_remote_size(MPI_Comm comm, int *size)
@@ -9,7 +9,7 @@ int MPI_Comm_remote_size(MPI_Comm comm, int *size)
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
@@ -18,7 +18,7 @@ int MPI_Comm_remote_size(MPI_Comm comm, int *size)
 .B size 
 - number of processes in the remote group of 
 .I comm
-(integer) 
+(integer)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_set_attr.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_set_attr.3
index 681f72b3..50a0b7bd 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_set_attr.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_set_attr.3
@@ -1,4 +1,4 @@
-.TH MPI_Comm_set_attr 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_set_attr 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Comm_set_attr \-  Stores attribute value associated with a key 
 .SH SYNOPSIS
@@ -9,7 +9,7 @@ int MPI_Comm_set_attr(MPI_Comm comm, int comm_keyval, void *attribute_val)
 .PD 0
 .TP
 .B comm 
-- communicator to which attribute will be attached (handle) 
+- communicator to which attribute will be attached (handle)
 .PD 1
 .PD 0
 .TP
@@ -21,7 +21,7 @@ int MPI_Comm_set_attr(MPI_Comm comm, int comm_keyval, void *attribute_val)
 .PD 0
 .TP
 .B attribute_val 
-- attribute value 
+- attribute value
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_set_errhandler.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_set_errhandler.3
index 5090685e..ca1009fe 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_set_errhandler.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_set_errhandler.3
@@ -1,4 +1,4 @@
-.TH MPI_Comm_set_errhandler 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_set_errhandler 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Comm_set_errhandler \-  Set the error handler for a communicator 
 .SH SYNOPSIS
@@ -9,12 +9,12 @@ int MPI_Comm_set_errhandler(MPI_Comm comm, MPI_Errhandler errhandler)
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 .PD 0
 .TP
 .B errhandler 
-- new error handler for communicator (handle) 
+- new error handler for communicator (handle)
 .PD 1
 
 
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_set_info.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_set_info.3
index 4e2553a8..7815b509 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_set_info.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_set_info.3
@@ -1,4 +1,4 @@
-.TH MPI_Comm_set_info 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_set_info 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Comm_set_info \-  Set new values for the hints of the communicator associated with comm.  The call is collective on the group of comm.  The info object may be different on each process, but any info entries that an implementation requires to be the same on all processes must appear with the same value in each process' info object. 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_set_name.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_set_name.3
index 77334f9a..b4011da0 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_set_name.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_set_name.3
@@ -1,4 +1,4 @@
-.TH MPI_Comm_set_name 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_set_name 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Comm_set_name \-  Sets the print name for a communicator 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_size.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_size.3
index c6352adb..28439fa6 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_size.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_size.3
@@ -1,15 +1,15 @@
-.TH MPI_Comm_size 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_size 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Comm_size \-  Determines the size of the group associated with a communicator 
 .SH SYNOPSIS
 .nf
-int MPI_Comm_size( MPI_Comm comm, int *size ) 
+int MPI_Comm_size(MPI_Comm comm, int *size)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
@@ -18,7 +18,7 @@ int MPI_Comm_size( MPI_Comm comm, int *size )
 .B size 
 - number of processes in the group of 
 .I comm
-(integer) 
+(integer)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_spawn.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_spawn.3
index 482ec082..2ff91b85 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_spawn.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_spawn.3
@@ -1,57 +1,56 @@
-.TH MPI_Comm_spawn 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_spawn 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Comm_spawn \-  Spawn up to maxprocs instances of a single MPI application 
 .SH SYNOPSIS
 .nf
 int MPI_Comm_spawn(const char *command, char *argv[], int maxprocs, MPI_Info info,
-                  int root, MPI_Comm comm, MPI_Comm *intercomm,
-                  int array_of_errcodes[])
+                   int root, MPI_Comm comm, MPI_Comm * intercomm, int array_of_errcodes[])
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B command 
-- name of program to be spawned (string, significant only at root) 
+- name of program to be spawned (string, significant only at root)
 .PD 1
 .PD 0
 .TP
 .B argv 
-- arguments to command (array of strings, significant only at root) 
+- arguments to command (array of strings, significant only at root)
 .PD 1
 .PD 0
 .TP
 .B maxprocs 
-- maximum number of processes to start (integer, significant only 
-at root) 
+- maximum number of processes to start (integer, significant only
+at root)
 .PD 1
 .PD 0
 .TP
 .B info 
-- a set of key-value pairs telling the runtime system where and how 
-to start the processes (handle, significant only at root) 
+- a set of key-value pairs telling the runtime system where and how
+to start the processes (handle, significant only at root)
 .PD 1
 .PD 0
 .TP
 .B root 
-- rank of process in which previous arguments are examined (integer) 
+- rank of process in which previous arguments are examined (integer)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- intracommunicator containing group of spawning processes (handle) 
+- intracommunicator containing group of spawning processes (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B intercomm 
-- intercommunicator between original group and the 
-newly spawned group (handle) 
+- intercommunicator between original group and the
+newly spawned group (handle)
 .PD 1
 .PD 0
 .TP
 .B array_of_errcodes 
-- one code per process (array of integer) 
+- one code per process (array of integer)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_spawn_multiple.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_spawn_multiple.3
index dcd3f846..5e1cf7df 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_spawn_multiple.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_spawn_multiple.3
@@ -1,53 +1,53 @@
-.TH MPI_Comm_spawn_multiple 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_spawn_multiple 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Comm_spawn_multiple \-  short description 
 .SH SYNOPSIS
 .nf
 int MPI_Comm_spawn_multiple(int count, char *array_of_commands[],
-                          char **array_of_argv[], const int array_of_maxprocs[],
-                          const MPI_Info array_of_info[], int root, MPI_Comm comm,
-                          MPI_Comm *intercomm, int array_of_errcodes[])
+                            char **array_of_argv[], const int array_of_maxprocs[],
+                            const MPI_Info array_of_info[], int root, MPI_Comm comm,
+                            MPI_Comm * intercomm, int array_of_errcodes[])
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B count 
-- number of commands (positive integer, significant to MPI only at 
-root 
+- number of commands (positive integer, significant to MPI only at
+root
 .PD 1
 .PD 0
 .TP
 .B array_of_commands 
-- programs to be executed (array of strings, significant 
-only at root) 
+- programs to be executed (array of strings, significant
+only at root)
 .PD 1
 .PD 0
 .TP
 .B array_of_argv 
-- arguments for commands (array of array of strings, 
-significant only at root) 
+- arguments for commands (array of array of strings,
+significant only at root)
 .PD 1
 .PD 0
 .TP
 .B array_of_maxprocs 
-- maximum number of processes to start for each command 
-(array of integer, significant only at root) 
+- maximum number of processes to start for each command
+(array of integer, significant only at root)
 .PD 1
 .PD 0
 .TP
 .B array_of_info 
-- info objects telling the runtime system where and how to 
-start processes (array of handles, significant only at root) 
+- info objects telling the runtime system where and how to
+start processes (array of handles, significant only at root)
 .PD 1
 .PD 0
 .TP
 .B root 
-- rank of process in which previous arguments are examined (integer) 
+- rank of process in which previous arguments are examined (integer)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- intracommunicator containing group of spawning processes (handle) 
+- intracommunicator containing group of spawning processes (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
@@ -55,12 +55,12 @@ start processes (array of handles, significant only at root)
 .TP
 .B intercomm 
 - intercommunicator between original group and newly spawned group
-(handle) 
+(handle)
 .PD 1
 .PD 0
 .TP
 .B array_of_errcodes 
-- one error code per process (array of integer) 
+- one error code per process (array of integer)
 .PD 1
 
 .SH NOTES FOR FORTRAN
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_split.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_split.3
index b71692f0..6400859c 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_split.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_split.3
@@ -1,21 +1,21 @@
-.TH MPI_Comm_split 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_split 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Comm_split \-  Creates new communicators based on colors and keys 
 .SH SYNOPSIS
 .nf
-int MPI_Comm_split(MPI_Comm comm, int color, int key, MPI_Comm *newcomm)
+int MPI_Comm_split(MPI_Comm comm, int color, int key, MPI_Comm * newcomm)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 .PD 0
 .TP
 .B color 
-- control of subset assignment (nonnegative integer).  Processes 
-with the same color are in the same new communicator 
+- control of subset assignment (nonnegative integer).  Processes
+with the same color are in the same new communicator
 .PD 1
 .PD 0
 .TP
@@ -27,7 +27,7 @@ with the same color are in the same new communicator
 .PD 0
 .TP
 .B newcomm 
-- new communicator (handle) 
+- new communicator (handle)
 .PD 1
 
 .SH NOTES
@@ -73,7 +73,7 @@ in Fortran.
 .SH ALGORITHM
 .nf
 1. Use MPI_Allgather to get the color and key from each process
-2. Count the number of processes with the same color; create a 
+2. Count the number of processes with the same color; create a
 communicator with that many processes.  If this process has
 .I MPI_UNDEFINED
 as the color, create a process with a single member.
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_split_type.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_split_type.3
index 4d2c67d2..3bda4853 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_split_type.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_split_type.3
@@ -1,10 +1,9 @@
-.TH MPI_Comm_split_type 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_split_type 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Comm_split_type \-  Creates new communicators based on split types and keys 
 .SH SYNOPSIS
 .nf
-int MPI_Comm_split_type(MPI_Comm comm, int split_type, int key, MPI_Info info,
-                        MPI_Comm * newcomm)
+int MPI_Comm_split_type(MPI_Comm comm, int split_type, int key, MPI_Info info, MPI_Comm * newcomm)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Comm_test_inter.3 b/linx64/mpi/mpich/share/man/man3/MPI_Comm_test_inter.3
index 23eae8d0..71d30023 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Comm_test_inter.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Comm_test_inter.3
@@ -1,4 +1,4 @@
-.TH MPI_Comm_test_inter 3 "11/10/2017" " " "MPI"
+.TH MPI_Comm_test_inter 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Comm_test_inter \-  Tests to see if a comm is an inter-communicator 
 .SH SYNOPSIS
@@ -9,14 +9,14 @@ int MPI_Comm_test_inter(MPI_Comm comm, int *flag)
 .PD 0
 .TP
 .B comm 
-- communicator to test (handle) 
+- communicator to test (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B flag 
-- true if this is an inter-communicator(logical) 
+- true if this is an inter-communicator(logical)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Compare_and_swap.3 b/linx64/mpi/mpich/share/man/man3/MPI_Compare_and_swap.3
index 7846bd4c..06f53bf3 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Compare_and_swap.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Compare_and_swap.3
@@ -1,11 +1,11 @@
-.TH MPI_Compare_and_swap 3 "11/10/2017" " " "MPI"
+.TH MPI_Compare_and_swap 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Compare_and_swap \-  Perform one-sided atomic compare-and-swap. 
 .SH SYNOPSIS
 .nf
 int MPI_Compare_and_swap(const void *origin_addr, const void *compare_addr,
-        void *result_addr, MPI_Datatype datatype, int target_rank,
-        MPI_Aint target_disp, MPI_Win win)
+                         void *result_addr, MPI_Datatype datatype, int target_rank,
+                         MPI_Aint target_disp, MPI_Win win)
 .fi
 
 This function compares one element of type datatype in the compare buffer
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Dims_create.3 b/linx64/mpi/mpich/share/man/man3/MPI_Dims_create.3
index d8f3d6d3..eefe125b 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Dims_create.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Dims_create.3
@@ -1,4 +1,4 @@
-.TH MPI_Dims_create 3 "11/10/2017" " " "MPI"
+.TH MPI_Dims_create 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Dims_create \-  Creates a division of processors in a cartesian grid 
 .SH SYNOPSIS
@@ -9,12 +9,12 @@ int MPI_Dims_create(int nnodes, int ndims, int dims[])
 .PD 0
 .TP
 .B nnodes 
-- number of nodes in a grid (integer) 
+- number of nodes in a grid (integer)
 .PD 1
 .PD 0
 .TP
 .B ndims 
-- number of cartesian dimensions (integer) 
+- number of cartesian dimensions (integer)
 .PD 1
 
 .SH INPUT/OUTPUT PARAMETERS
@@ -23,7 +23,7 @@ int MPI_Dims_create(int nnodes, int ndims, int dims[])
 .B dims 
 - integer array of size  
 .I ndims
-specifying the number of nodes in each 
+specifying the number of nodes in each
 dimension.  A value of 0 indicates that 
 .I MPI_Dims_create
 should fill in a
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Dist_graph_create.3 b/linx64/mpi/mpich/share/man/man3/MPI_Dist_graph_create.3
index 7ee5221b..a997bf4c 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Dist_graph_create.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Dist_graph_create.3
@@ -1,4 +1,4 @@
-.TH MPI_Dist_graph_create 3 "11/10/2017" " " "MPI"
+.TH MPI_Dist_graph_create 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Dist_graph_create \-  MPI_DIST_GRAPH_CREATE returns a handle to a new communicator to which the distributed graph topology information is attached. 
 .SH SYNOPSIS
@@ -6,7 +6,7 @@ MPI_Dist_graph_create \-  MPI_DIST_GRAPH_CREATE returns a handle to a new commun
 int MPI_Dist_graph_create(MPI_Comm comm_old, int n, const int sources[],
                           const int degrees[], const int destinations[],
                           const int weights[],
-                          MPI_Info info, int reorder, MPI_Comm *comm_dist_graph)
+                          MPI_Info info, int reorder, MPI_Comm * comm_dist_graph)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
@@ -17,31 +17,31 @@ int MPI_Dist_graph_create(MPI_Comm comm_old, int n, const int sources[],
 .PD 0
 .TP
 .B n 
-- number of source nodes for which this process specifies edges 
+- number of source nodes for which this process specifies edges
 (non-negative integer)
 .PD 1
 .PD 0
 .TP
 .B sources 
-- array containing the n source nodes for which this process 
+- array containing the n source nodes for which this process
 specifies edges (array of non-negative integers)
 .PD 1
 .PD 0
 .TP
 .B degrees 
-- array specifying the number of destinations for each source node 
+- array specifying the number of destinations for each source node
 in the source node array (array of non-negative integers)
 .PD 1
 .PD 0
 .TP
 .B destinations 
-- destination nodes for the source nodes in the source node 
+- destination nodes for the source nodes in the source node
 array (array of non-negative integers)
 .PD 1
 .PD 0
 .TP
 .B weights 
-- weights for source to destination edges (array of non-negative 
+- weights for source to destination edges (array of non-negative
 integers or MPI_UNWEIGHTED)
 .PD 1
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Dist_graph_create_adjacent.3 b/linx64/mpi/mpich/share/man/man3/MPI_Dist_graph_create_adjacent.3
index 8e834687..7acb382d 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Dist_graph_create_adjacent.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Dist_graph_create_adjacent.3
@@ -1,4 +1,4 @@
-.TH MPI_Dist_graph_create_adjacent 3 "11/10/2017" " " "MPI"
+.TH MPI_Dist_graph_create_adjacent 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Dist_graph_create_adjacent \-  returns a handle to a new communicator to which the distributed graph topology information is attached. 
 .SH SYNOPSIS
@@ -8,7 +8,7 @@ int MPI_Dist_graph_create_adjacent(MPI_Comm comm_old,
                                    const int sourceweights[],
                                    int outdegree, const int destinations[],
                                    const int destweights[],
-                                   MPI_Info info, int reorder, MPI_Comm *comm_dist_graph)
+                                   MPI_Info info, int reorder, MPI_Comm * comm_dist_graph)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
@@ -47,7 +47,7 @@ source (array of non-negative integers)
 .PD 0
 .TP
 .B destweights 
-- weights of the edges out of the calling process 
+- weights of the edges out of the calling process
 (array of non-negative integers or MPI_UNWEIGHTED)
 .PD 1
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Dist_graph_neighbors.3 b/linx64/mpi/mpich/share/man/man3/MPI_Dist_graph_neighbors.3
index 319457fd..82172ceb 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Dist_graph_neighbors.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Dist_graph_neighbors.3
@@ -1,4 +1,4 @@
-.TH MPI_Dist_graph_neighbors 3 "11/10/2017" " " "MPI"
+.TH MPI_Dist_graph_neighbors 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Dist_graph_neighbors \-  Provides adjacency information for a distributed graph topology. 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Dist_graph_neighbors_count.3 b/linx64/mpi/mpich/share/man/man3/MPI_Dist_graph_neighbors_count.3
index d1cdb74e..24f1b5ed 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Dist_graph_neighbors_count.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Dist_graph_neighbors_count.3
@@ -1,4 +1,4 @@
-.TH MPI_Dist_graph_neighbors_count 3 "11/10/2017" " " "MPI"
+.TH MPI_Dist_graph_neighbors_count 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Dist_graph_neighbors_count \-  Provides adjacency information for a distributed graph topology. 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Errhandler_create.3 b/linx64/mpi/mpich/share/man/man3/MPI_Errhandler_create.3
index b090fe72..9b71b84c 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Errhandler_create.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Errhandler_create.3
@@ -1,23 +1,22 @@
-.TH MPI_Errhandler_create 3 "11/10/2017" " " "MPI"
+.TH MPI_Errhandler_create 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Errhandler_create \-  Creates an MPI-style errorhandler 
 .SH SYNOPSIS
 .nf
-int MPI_Errhandler_create(MPI_Handler_function *function, 
-                          MPI_Errhandler *errhandler)
+int MPI_Errhandler_create(MPI_Handler_function * function, MPI_Errhandler * errhandler)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B function 
-- user defined error handling procedure 
+- user defined error handling procedure
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B errhandler 
-- MPI error handler (handle) 
+- MPI error handler (handle)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Errhandler_free.3 b/linx64/mpi/mpich/share/man/man3/MPI_Errhandler_free.3
index fc9f5608..dd48631a 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Errhandler_free.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Errhandler_free.3
@@ -1,9 +1,9 @@
-.TH MPI_Errhandler_free 3 "11/10/2017" " " "MPI"
+.TH MPI_Errhandler_free 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Errhandler_free \-  Frees an MPI-style errorhandler 
 .SH SYNOPSIS
 .nf
-int MPI_Errhandler_free(MPI_Errhandler *errhandler)
+int MPI_Errhandler_free(MPI_Errhandler * errhandler)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
@@ -11,7 +11,7 @@ int MPI_Errhandler_free(MPI_Errhandler *errhandler)
 .B errhandler 
 - MPI error handler (handle).  Set to 
 .I MPI_ERRHANDLER_NULL
-on 
+on
 exit.
 .PD 1
 
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Errhandler_get.3 b/linx64/mpi/mpich/share/man/man3/MPI_Errhandler_get.3
index f0ecdbdc..2ed5df06 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Errhandler_get.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Errhandler_get.3
@@ -1,15 +1,15 @@
-.TH MPI_Errhandler_get 3 "11/10/2017" " " "MPI"
+.TH MPI_Errhandler_get 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Errhandler_get \-  Gets the error handler for a communicator 
 .SH SYNOPSIS
 .nf
-int MPI_Errhandler_get(MPI_Comm comm, MPI_Errhandler *errhandler)
+int MPI_Errhandler_get(MPI_Comm comm, MPI_Errhandler * errhandler)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B comm 
-- communicator to get the error handler from (handle) 
+- communicator to get the error handler from (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
@@ -17,7 +17,7 @@ int MPI_Errhandler_get(MPI_Comm comm, MPI_Errhandler *errhandler)
 .TP
 .B errhandler 
 - MPI error handler currently associated with communicator
-(handle) 
+(handle)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Errhandler_set.3 b/linx64/mpi/mpich/share/man/man3/MPI_Errhandler_set.3
index 5a4c584c..b679ea1f 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Errhandler_set.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Errhandler_set.3
@@ -1,4 +1,4 @@
-.TH MPI_Errhandler_set 3 "11/10/2017" " " "MPI"
+.TH MPI_Errhandler_set 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Errhandler_set \-  Sets the error handler for a communicator 
 .SH SYNOPSIS
@@ -9,12 +9,12 @@ int MPI_Errhandler_set(MPI_Comm comm, MPI_Errhandler errhandler)
 .PD 0
 .TP
 .B comm 
-- communicator to set the error handler for (handle) 
+- communicator to set the error handler for (handle)
 .PD 1
 .PD 0
 .TP
 .B errhandler 
-- new MPI error handler for communicator (handle) 
+- new MPI error handler for communicator (handle)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Error_class.3 b/linx64/mpi/mpich/share/man/man3/MPI_Error_class.3
index a4c95253..7adc1813 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Error_class.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Error_class.3
@@ -1,4 +1,4 @@
-.TH MPI_Error_class 3 "11/10/2017" " " "MPI"
+.TH MPI_Error_class 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Error_class \-  Converts an error code into an error class 
 .SH SYNOPSIS
@@ -9,7 +9,7 @@ int MPI_Error_class(int errorcode, int *errorclass)
 .PD 0
 .TP
 .B errorcode 
-- Error code returned by an MPI routine 
+- Error code returned by an MPI routine
 .PD 1
 
 .SH OUTPUT PARAMETERS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Error_string.3 b/linx64/mpi/mpich/share/man/man3/MPI_Error_string.3
index 46a0003a..2142e7b0 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Error_string.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Error_string.3
@@ -1,4 +1,4 @@
-.TH MPI_Error_string 3 "11/10/2017" " " "MPI"
+.TH MPI_Error_string 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Error_string \-  Return a string for a given error code 
 .SH SYNOPSIS
@@ -16,12 +16,12 @@ int MPI_Error_string(int errorcode, char *string, int *resultlen)
 .PD 0
 .TP
 .B string 
-- Text that corresponds to the errorcode 
+- Text that corresponds to the errorcode
 .PD 1
 .PD 0
 .TP
 .B resultlen 
-- Length of string 
+- Length of string
 .PD 1
 
 Notes:  Error codes are the values return by MPI routines (in C) or in the
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Exscan.3 b/linx64/mpi/mpich/share/man/man3/MPI_Exscan.3
index 13aff571..5a5e775e 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Exscan.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Exscan.3
@@ -1,6 +1,6 @@
-.TH MPI_Exscan 3 "11/10/2017" " " "MPI"
+.TH MPI_Exscan 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Exscan \-  Computes the exclusive scan (partial reductions) of data on a  collection of processes 
+MPI_Exscan \-  Computes the exclusive scan (partial reductions) of data on a collection of processes 
 .SH SYNOPSIS
 .nf
 int MPI_Exscan(const void *sendbuf, void *recvbuf, int count, MPI_Datatype datatype,
@@ -10,34 +10,34 @@ int MPI_Exscan(const void *sendbuf, void *recvbuf, int count, MPI_Datatype datat
 .PD 0
 .TP
 .B sendbuf 
-- starting address of send buffer (choice) 
+- starting address of send buffer (choice)
 .PD 1
 .PD 0
 .TP
 .B count 
-- number of elements in input buffer (integer) 
+- number of elements in input buffer (integer)
 .PD 1
 .PD 0
 .TP
 .B datatype 
-- data type of elements of input buffer (handle) 
+- data type of elements of input buffer (handle)
 .PD 1
 .PD 0
 .TP
 .B op 
-- operation (handle) 
+- operation (handle)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B recvbuf 
-- starting address of receive buffer (choice) 
+- starting address of receive buffer (choice)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Fetch_and_op.3 b/linx64/mpi/mpich/share/man/man3/MPI_Fetch_and_op.3
index 2394b980..ede6298d 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Fetch_and_op.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Fetch_and_op.3
@@ -1,11 +1,11 @@
-.TH MPI_Fetch_and_op 3 "11/10/2017" " " "MPI"
+.TH MPI_Fetch_and_op 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Fetch_and_op \-  Perform one-sided read-modify-write. 
 .SH SYNOPSIS
 .nf
 int MPI_Fetch_and_op(const void *origin_addr, void *result_addr,
-        MPI_Datatype datatype, int target_rank, MPI_Aint target_disp,
-        MPI_Op op, MPI_Win win)
+                     MPI_Datatype datatype, int target_rank, MPI_Aint target_disp,
+                     MPI_Op op, MPI_Win win)
 .fi
 
 Accumulate one element of type datatype from the origin buffer (origin_addr) to
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_c2f.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_c2f.3
index bfea1b9b..8be01499 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_c2f.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_c2f.3
@@ -1,4 +1,4 @@
-.TH MPI_File_c2f 3 "11/10/2017" " " "MPI"
+.TH MPI_File_c2f 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_c2f \-  Translates a C file handle to a Fortran file handle 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_call_errhandler.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_call_errhandler.3
index 367ddeca..2e79b717 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_call_errhandler.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_call_errhandler.3
@@ -1,6 +1,6 @@
-.TH MPI_File_call_errhandler 3 "11/10/2017" " " "MPI"
+.TH MPI_File_call_errhandler 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_File_call_errhandler \-  Call the error handler installed on a  file 
+MPI_File_call_errhandler \-  Call the error handler installed on a file 
 .SH SYNOPSIS
 .nf
 int MPI_File_call_errhandler(MPI_File fh, int errorcode)
@@ -9,12 +9,12 @@ int MPI_File_call_errhandler(MPI_File fh, int errorcode)
 .PD 0
 .TP
 .B fh 
-- MPI file with error handler (handle) 
+- MPI file with error handler (handle)
 .PD 1
 .PD 0
 .TP
 .B errorcode 
-- error code (integer) 
+- error code (integer)
 .PD 1
 
 
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_close.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_close.3
index 8e7f44e8..f37de123 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_close.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_close.3
@@ -1,9 +1,9 @@
-.TH MPI_File_close 3 "11/10/2017" " " "MPI"
+.TH MPI_File_close 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_close \-  Closes a file 
 .SH SYNOPSIS
 .nf
-int MPI_File_close(MPI_File *fh)
+int MPI_File_close(MPI_File * fh)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_create_errhandler.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_create_errhandler.3
index c46ca45a..c95cde09 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_create_errhandler.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_create_errhandler.3
@@ -1,10 +1,10 @@
-.TH MPI_File_create_errhandler 3 "11/10/2017" " " "MPI"
+.TH MPI_File_create_errhandler 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_create_errhandler \-  Create a file error handler 
 .SH SYNOPSIS
 .nf
-int MPI_File_create_errhandler(MPI_File_errhandler_function *file_errhandler_fn,
-                               MPI_Errhandler *errhandler)
+int MPI_File_create_errhandler(MPI_File_errhandler_function * file_errhandler_fn,
+                               MPI_Errhandler * errhandler)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
@@ -17,7 +17,7 @@ int MPI_File_create_errhandler(MPI_File_errhandler_function *file_errhandler_fn,
 .PD 0
 .TP
 .B errhandler 
-- MPI error handler (handle) 
+- MPI error handler (handle)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_delete.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_delete.3
index b90ea11e..755ba8ba 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_delete.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_delete.3
@@ -1,4 +1,4 @@
-.TH MPI_File_delete 3 "11/10/2017" " " "MPI"
+.TH MPI_File_delete 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_delete \-  Deletes a file 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_f2c.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_f2c.3
index 04f012de..18962bbe 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_f2c.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_f2c.3
@@ -1,4 +1,4 @@
-.TH MPI_File_f2c 3 "11/10/2017" " " "MPI"
+.TH MPI_File_f2c 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_f2c \-  Translates a Fortran file handle to a C file handle 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_get_amode.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_get_amode.3
index 7d2b2c43..78d4f92e 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_get_amode.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_get_amode.3
@@ -1,4 +1,4 @@
-.TH MPI_File_get_amode 3 "11/10/2017" " " "MPI"
+.TH MPI_File_get_amode 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_get_amode \-  Returns the file access mode 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_get_atomicity.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_get_atomicity.3
index 0238023f..98ab3d2a 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_get_atomicity.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_get_atomicity.3
@@ -1,4 +1,4 @@
-.TH MPI_File_get_atomicity 3 "11/10/2017" " " "MPI"
+.TH MPI_File_get_atomicity 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_get_atomicity \-  Returns the atomicity mode 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_get_byte_offset.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_get_byte_offset.3
index bb347192..943cbb4a 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_get_byte_offset.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_get_byte_offset.3
@@ -1,9 +1,9 @@
-.TH MPI_File_get_byte_offset 3 "11/10/2017" " " "MPI"
+.TH MPI_File_get_byte_offset 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_File_get_byte_offset \-  Returns the absolute byte position in  the file corresponding to "offset" etypes relative to the current view 
+MPI_File_get_byte_offset \-  Returns the absolute byte position in the file corresponding to "offset" etypes relative to the current view 
 .SH SYNOPSIS
 .nf
-int MPI_File_get_byte_offset(MPI_File fh, MPI_Offset offset, MPI_Offset *disp)
+int MPI_File_get_byte_offset(MPI_File fh, MPI_Offset offset, MPI_Offset * disp)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_get_errhandler.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_get_errhandler.3
index 2aee57eb..e41b2237 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_get_errhandler.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_get_errhandler.3
@@ -1,22 +1,22 @@
-.TH MPI_File_get_errhandler 3 "11/10/2017" " " "MPI"
+.TH MPI_File_get_errhandler 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_get_errhandler \-  Get the error handler attached to a file 
 .SH SYNOPSIS
 .nf
-int MPI_File_get_errhandler(MPI_File file, MPI_Errhandler *errhandler)
+int MPI_File_get_errhandler(MPI_File file, MPI_Errhandler * errhandler)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B file 
-- MPI file (handle) 
+- MPI file (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B errhandler 
-- handler currently associated with file (handle) 
+- handler currently associated with file (handle)
 .PD 1
 
 
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_get_group.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_get_group.3
index f08c05df..b6c5afad 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_get_group.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_get_group.3
@@ -1,9 +1,9 @@
-.TH MPI_File_get_group 3 "11/10/2017" " " "MPI"
+.TH MPI_File_get_group 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_File_get_group \-  Returns the group of processes that  opened the file 
+MPI_File_get_group \-  Returns the group of processes that opened the file 
 .SH SYNOPSIS
 .nf
-int MPI_File_get_group(MPI_File fh, MPI_Group *group)
+int MPI_File_get_group(MPI_File fh, MPI_Group * group)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_get_info.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_get_info.3
index 1d110ca5..d91a3682 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_get_info.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_get_info.3
@@ -1,9 +1,9 @@
-.TH MPI_File_get_info 3 "11/10/2017" " " "MPI"
+.TH MPI_File_get_info 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_get_info \-  Returns the hints for a file that are actually being used by MPI 
 .SH SYNOPSIS
 .nf
-int MPI_File_get_info(MPI_File fh, MPI_Info *info_used)
+int MPI_File_get_info(MPI_File fh, MPI_Info * info_used)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_get_position.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_get_position.3
index a8dd0ddc..8e3b63cc 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_get_position.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_get_position.3
@@ -1,9 +1,9 @@
-.TH MPI_File_get_position 3 "11/10/2017" " " "MPI"
+.TH MPI_File_get_position 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_File_get_position \-  Returns the current position of the  individual file pointer in etype units relative to the current view 
+MPI_File_get_position \-  Returns the current position of the individual file pointer in etype units relative to the current view 
 .SH SYNOPSIS
 .nf
-int MPI_File_get_position(MPI_File fh, MPI_Offset *offset)
+int MPI_File_get_position(MPI_File fh, MPI_Offset * offset)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_get_position_shared.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_get_position_shared.3
index 6af1fdfb..091a3e0f 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_get_position_shared.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_get_position_shared.3
@@ -1,9 +1,9 @@
-.TH MPI_File_get_position_shared 3 "11/10/2017" " " "MPI"
+.TH MPI_File_get_position_shared 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_File_get_position_shared \-  Returns the current position of the  shared file pointer in etype units relative to the current view 
+MPI_File_get_position_shared \-  Returns the current position of the shared file pointer in etype units relative to the current view 
 .SH SYNOPSIS
 .nf
-int MPI_File_get_position_shared(MPI_File fh, MPI_Offset *offset)
+int MPI_File_get_position_shared(MPI_File fh, MPI_Offset * offset)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_get_size.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_get_size.3
index 59ec483e..5aeff825 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_get_size.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_get_size.3
@@ -1,9 +1,9 @@
-.TH MPI_File_get_size 3 "11/10/2017" " " "MPI"
+.TH MPI_File_get_size 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_get_size \-  Returns the file size 
 .SH SYNOPSIS
 .nf
-int MPI_File_get_size(MPI_File fh, MPI_Offset *size)
+int MPI_File_get_size(MPI_File fh, MPI_Offset * size)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_get_type_extent.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_get_type_extent.3
index 24a3d065..721bbb94 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_get_type_extent.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_get_type_extent.3
@@ -1,9 +1,9 @@
-.TH MPI_File_get_type_extent 3 "11/10/2017" " " "MPI"
+.TH MPI_File_get_type_extent 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_get_type_extent \-  Returns the extent of datatype in the file 
 .SH SYNOPSIS
 .nf
-int MPI_File_get_type_extent(MPI_File fh, MPI_Datatype datatype, MPI_Aint *extent)
+int MPI_File_get_type_extent(MPI_File fh, MPI_Datatype datatype, MPI_Aint * extent)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_get_view.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_get_view.3
index f9a20b5a..49730805 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_get_view.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_get_view.3
@@ -1,10 +1,10 @@
-.TH MPI_File_get_view 3 "11/10/2017" " " "MPI"
+.TH MPI_File_get_view 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_get_view \-  Returns the file view 
 .SH SYNOPSIS
 .nf
-int MPI_File_get_view(MPI_File fh, MPI_Offset *disp, MPI_Datatype *etype,
-                      MPI_Datatype *filetype, char *datarep)
+int MPI_File_get_view(MPI_File fh, MPI_Offset * disp, MPI_Datatype * etype,
+                      MPI_Datatype * filetype, char *datarep)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_iread.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_iread.3
index f72e2f35..4e2edfb9 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_iread.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_iread.3
@@ -1,9 +1,9 @@
-.TH MPI_File_iread 3 "11/10/2017" " " "MPI"
+.TH MPI_File_iread 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_iread \-  Nonblocking read using individual file pointer 
 .SH SYNOPSIS
 .nf
-int MPI_File_iread(MPI_File fh, void *buf, int count, MPI_Datatype datatype, MPI_Request *request)
+int MPI_File_iread(MPI_File fh, void *buf, int count, MPI_Datatype datatype, MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_iread_all.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_iread_all.3
index 6300a2fe..92b6858a 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_iread_all.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_iread_all.3
@@ -1,10 +1,10 @@
-.TH MPI_File_iread_all 3 "11/10/2017" " " "MPI"
+.TH MPI_File_iread_all 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_iread_all \-  Nonblocking collective read using individual file pointer 
 .SH SYNOPSIS
 .nf
 int MPI_File_iread_all(MPI_File fh, void *buf, int count,
-                       MPI_Datatype datatype, MPI_Request *request)
+                       MPI_Datatype datatype, MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_iread_at.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_iread_at.3
index a31e900b..fdae6464 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_iread_at.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_iread_at.3
@@ -1,10 +1,10 @@
-.TH MPI_File_iread_at 3 "11/10/2017" " " "MPI"
+.TH MPI_File_iread_at 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_iread_at \-  Nonblocking read using explicit offset 
 .SH SYNOPSIS
 .nf
-int MPI_File_iread_at(MPI_File fh, MPI_Offset offset, void *buf, int count, MPI_Datatype datatype, 
-                      MPIO_Request *request)
+int MPI_File_iread_at(MPI_File fh, MPI_Offset offset, void *buf, int count, MPI_Datatype datatype,
+                      MPIO_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_iread_at_all.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_iread_at_all.3
index 4ed6e1a6..75984076 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_iread_at_all.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_iread_at_all.3
@@ -1,11 +1,10 @@
-.TH MPI_File_iread_at_all 3 "11/10/2017" " " "MPI"
+.TH MPI_File_iread_at_all 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_iread_at_all \-  Nonblocking collective read using explicit offset 
 .SH SYNOPSIS
 .nf
 int MPI_File_iread_at_all(MPI_File fh, MPI_Offset offset, void *buf,
-                          int count, MPI_Datatype datatype,
-                          MPI_Request *request)
+                          int count, MPI_Datatype datatype, MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_iread_shared.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_iread_shared.3
index 269a2e1a..791f0598 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_iread_shared.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_iread_shared.3
@@ -1,10 +1,10 @@
-.TH MPI_File_iread_shared 3 "11/10/2017" " " "MPI"
+.TH MPI_File_iread_shared 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_iread_shared \-  Nonblocking read using shared file pointer 
 .SH SYNOPSIS
 .nf
 int MPI_File_iread_shared(MPI_File fh, void *buf, int count,
-                          MPI_Datatype datatype, MPI_Request *request)
+                          MPI_Datatype datatype, MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_iwrite.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_iwrite.3
index 6f13921c..d3a03028 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_iwrite.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_iwrite.3
@@ -1,4 +1,4 @@
-.TH MPI_File_iwrite 3 "11/10/2017" " " "MPI"
+.TH MPI_File_iwrite 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_iwrite \-  Nonblocking write using individual file pointer 
 .SH SYNOPSIS
@@ -8,7 +8,7 @@ MPI_File_iwrite \-  Nonblocking write using individual file pointer
 #endif
 
 int MPI_File_iwrite(MPI_File fh, ROMIO_CONST void *buf, int count,
-                   MPI_Datatype datatype, MPI_Request *request)
+                    MPI_Datatype datatype, MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_iwrite_all.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_iwrite_all.3
index f570b823..ba0edd3f 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_iwrite_all.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_iwrite_all.3
@@ -1,10 +1,10 @@
-.TH MPI_File_iwrite_all 3 "11/10/2017" " " "MPI"
+.TH MPI_File_iwrite_all 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_iwrite_all \-  Nonblocking collective write using individual file pointer 
 .SH SYNOPSIS
 .nf
 int MPI_File_iwrite_all(MPI_File fh, ROMIO_CONST void *buf, int count,
-                        MPI_Datatype datatype, MPI_Request *request)
+                        MPI_Datatype datatype, MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_iwrite_at.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_iwrite_at.3
index 640eb8f2..f13f65a7 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_iwrite_at.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_iwrite_at.3
@@ -1,4 +1,4 @@
-.TH MPI_File_iwrite_at 3 "11/10/2017" " " "MPI"
+.TH MPI_File_iwrite_at 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_iwrite_at \-  Nonblocking write using explicit offset 
 .SH SYNOPSIS
@@ -8,8 +8,7 @@ MPI_File_iwrite_at \-  Nonblocking write using explicit offset
 #endif
 
 int MPI_File_iwrite_at(MPI_File fh, MPI_Offset offset, ROMIO_CONST void *buf,
-                       int count, MPI_Datatype datatype, 
-                       MPIO_Request *request)
+                       int count, MPI_Datatype datatype, MPIO_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_iwrite_at_all.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_iwrite_at_all.3
index 9b1d3c1a..d000c699 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_iwrite_at_all.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_iwrite_at_all.3
@@ -1,11 +1,10 @@
-.TH MPI_File_iwrite_at_all 3 "11/10/2017" " " "MPI"
+.TH MPI_File_iwrite_at_all 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_iwrite_at_all \-  Nonblocking collective write using explicit offset 
 .SH SYNOPSIS
 .nf
 int MPI_File_iwrite_at_all(MPI_File fh, MPI_Offset offset, ROMIO_CONST void *buf,
-                           int count, MPI_Datatype datatype,
-                           MPI_Request *request)
+                           int count, MPI_Datatype datatype, MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_iwrite_shared.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_iwrite_shared.3
index d70c2ec6..acda923f 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_iwrite_shared.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_iwrite_shared.3
@@ -1,4 +1,4 @@
-.TH MPI_File_iwrite_shared 3 "11/10/2017" " " "MPI"
+.TH MPI_File_iwrite_shared 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_iwrite_shared \-  Nonblocking write using shared file pointer 
 .SH SYNOPSIS
@@ -8,7 +8,7 @@ MPI_File_iwrite_shared \-  Nonblocking write using shared file pointer
 #endif
 
 int MPI_File_iwrite_shared(MPI_File fh, ROMIO_CONST void *buf, int count,
-                         MPI_Datatype datatype, MPIO_Request *request)
+                           MPI_Datatype datatype, MPIO_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_open.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_open.3
index 5cea50ad..d6d74b20 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_open.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_open.3
@@ -1,10 +1,10 @@
-.TH MPI_File_open 3 "11/10/2017" " " "MPI"
+.TH MPI_File_open 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_open \-  Opens a file 
 .SH SYNOPSIS
 .nf
 int MPI_File_open(MPI_Comm comm, ROMIO_CONST char *filename, int amode,
-                  MPI_Info info, MPI_File *fh)
+                  MPI_Info info, MPI_File * fh)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_preallocate.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_preallocate.3
index aa07313d..93a0cdc4 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_preallocate.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_preallocate.3
@@ -1,4 +1,4 @@
-.TH MPI_File_preallocate 3 "11/10/2017" " " "MPI"
+.TH MPI_File_preallocate 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_preallocate \-  Preallocates storage space for a file 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_read.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_read.3
index ae323b10..10aa750e 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_read.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_read.3
@@ -1,10 +1,9 @@
-.TH MPI_File_read 3 "11/10/2017" " " "MPI"
+.TH MPI_File_read 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_read \-  Read using individual file pointer 
 .SH SYNOPSIS
 .nf
-int MPI_File_read(MPI_File fh, void *buf, int count,
-                  MPI_Datatype datatype, MPI_Status *status)
+int MPI_File_read(MPI_File fh, void *buf, int count, MPI_Datatype datatype, MPI_Status * status)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_read_all.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_read_all.3
index cd89847b..3d2f1df2 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_read_all.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_read_all.3
@@ -1,10 +1,9 @@
-.TH MPI_File_read_all 3 "11/10/2017" " " "MPI"
+.TH MPI_File_read_all 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_read_all \-  Collective read using individual file pointer 
 .SH SYNOPSIS
 .nf
-int MPI_File_read_all(MPI_File fh, void *buf, int count,
-                      MPI_Datatype datatype, MPI_Status *status)
+int MPI_File_read_all(MPI_File fh, void *buf, int count, MPI_Datatype datatype, MPI_Status * status)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_read_all_begin.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_read_all_begin.3
index c73ae028..8234aa92 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_read_all_begin.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_read_all_begin.3
@@ -1,10 +1,9 @@
-.TH MPI_File_read_all_begin 3 "11/10/2017" " " "MPI"
+.TH MPI_File_read_all_begin 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_read_all_begin \-  Begin a split collective read using individual file pointer 
 .SH SYNOPSIS
 .nf
-int MPI_File_read_all_begin(MPI_File fh, void *buf, int count,
-                            MPI_Datatype datatype)
+int MPI_File_read_all_begin(MPI_File fh, void *buf, int count, MPI_Datatype datatype)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_read_all_end.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_read_all_end.3
index 7774654b..30bd88be 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_read_all_end.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_read_all_end.3
@@ -1,9 +1,9 @@
-.TH MPI_File_read_all_end 3 "11/10/2017" " " "MPI"
+.TH MPI_File_read_all_end 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_read_all_end \-  Complete a split collective read using individual file pointer 
 .SH SYNOPSIS
 .nf
-int MPI_File_read_all_end(MPI_File fh, void *buf, MPI_Status *status)
+int MPI_File_read_all_end(MPI_File fh, void *buf, MPI_Status * status)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_read_at.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_read_at.3
index 1b041034..8db740c7 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_read_at.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_read_at.3
@@ -1,10 +1,10 @@
-.TH MPI_File_read_at 3 "11/10/2017" " " "MPI"
+.TH MPI_File_read_at 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_read_at \-  Read using explicit offset 
 .SH SYNOPSIS
 .nf
 int MPI_File_read_at(MPI_File fh, MPI_Offset offset, void *buf,
-                    int count, MPI_Datatype datatype, MPI_Status *status)
+                     int count, MPI_Datatype datatype, MPI_Status * status)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_read_at_all.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_read_at_all.3
index 2771c423..2c45476a 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_read_at_all.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_read_at_all.3
@@ -1,11 +1,10 @@
-.TH MPI_File_read_at_all 3 "11/10/2017" " " "MPI"
+.TH MPI_File_read_at_all 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_read_at_all \-  Collective read using explicit offset 
 .SH SYNOPSIS
 .nf
 int MPI_File_read_at_all(MPI_File fh, MPI_Offset offset, void *buf,
-                         int count, MPI_Datatype datatype, 
-                         MPI_Status *status)
+                         int count, MPI_Datatype datatype, MPI_Status * status)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_read_at_all_begin.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_read_at_all_begin.3
index e09af052..855f8025 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_read_at_all_begin.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_read_at_all_begin.3
@@ -1,10 +1,10 @@
-.TH MPI_File_read_at_all_begin 3 "11/10/2017" " " "MPI"
+.TH MPI_File_read_at_all_begin 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_read_at_all_begin \-  Begin a split collective read using explicit offset 
 .SH SYNOPSIS
 .nf
 int MPI_File_read_at_all_begin(MPI_File fh, MPI_Offset offset, void *buf,
-                             int count, MPI_Datatype datatype)
+                               int count, MPI_Datatype datatype)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_read_at_all_end.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_read_at_all_end.3
index 054c97ba..79bf0533 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_read_at_all_end.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_read_at_all_end.3
@@ -1,9 +1,9 @@
-.TH MPI_File_read_at_all_end 3 "11/10/2017" " " "MPI"
+.TH MPI_File_read_at_all_end 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_read_at_all_end \-  Complete a split collective read using explicit offset 
 .SH SYNOPSIS
 .nf
-int MPI_File_read_at_all_end(MPI_File fh, void *buf, MPI_Status *status)
+int MPI_File_read_at_all_end(MPI_File fh, void *buf, MPI_Status * status)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_read_ordered.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_read_ordered.3
index 3cdd1b8e..bdd36f22 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_read_ordered.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_read_ordered.3
@@ -1,10 +1,10 @@
-.TH MPI_File_read_ordered 3 "11/10/2017" " " "MPI"
+.TH MPI_File_read_ordered 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_read_ordered \-  Collective read using shared file pointer 
 .SH SYNOPSIS
 .nf
 int MPI_File_read_ordered(MPI_File fh, void *buf, int count,
-                          MPI_Datatype datatype, MPI_Status *status)
+                          MPI_Datatype datatype, MPI_Status * status)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_read_ordered_begin.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_read_ordered_begin.3
index 449e0d0f..4c8e08dc 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_read_ordered_begin.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_read_ordered_begin.3
@@ -1,10 +1,9 @@
-.TH MPI_File_read_ordered_begin 3 "11/10/2017" " " "MPI"
+.TH MPI_File_read_ordered_begin 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_read_ordered_begin \-  Begin a split collective read using shared file pointer 
 .SH SYNOPSIS
 .nf
-int MPI_File_read_ordered_begin(MPI_File fh, void *buf, int count,
-                             MPI_Datatype datatype)
+int MPI_File_read_ordered_begin(MPI_File fh, void *buf, int count, MPI_Datatype datatype)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_read_ordered_end.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_read_ordered_end.3
index 2773326c..755a7213 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_read_ordered_end.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_read_ordered_end.3
@@ -1,9 +1,9 @@
-.TH MPI_File_read_ordered_end 3 "11/10/2017" " " "MPI"
+.TH MPI_File_read_ordered_end 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_read_ordered_end \-  Complete a split collective read using shared file pointer 
 .SH SYNOPSIS
 .nf
-int MPI_File_read_ordered_end(MPI_File fh, void *buf, MPI_Status *status)
+int MPI_File_read_ordered_end(MPI_File fh, void *buf, MPI_Status * status)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_read_shared.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_read_shared.3
index e7c77000..92fcb1f9 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_read_shared.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_read_shared.3
@@ -1,10 +1,10 @@
-.TH MPI_File_read_shared 3 "11/10/2017" " " "MPI"
+.TH MPI_File_read_shared 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_read_shared \-  Read using shared file pointer 
 .SH SYNOPSIS
 .nf
 int MPI_File_read_shared(MPI_File fh, void *buf, int count,
-                       MPI_Datatype datatype, MPI_Status *status)
+                         MPI_Datatype datatype, MPI_Status * status)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_seek.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_seek.3
index 0ca8c4e3..ffa1e0a7 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_seek.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_seek.3
@@ -1,4 +1,4 @@
-.TH MPI_File_seek 3 "11/10/2017" " " "MPI"
+.TH MPI_File_seek 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_seek \-  Updates the individual file pointer 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_seek_shared.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_seek_shared.3
index 1e78615a..d38d6d40 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_seek_shared.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_seek_shared.3
@@ -1,4 +1,4 @@
-.TH MPI_File_seek_shared 3 "11/10/2017" " " "MPI"
+.TH MPI_File_seek_shared 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_seek_shared \-  Updates the shared file pointer 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_set_atomicity.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_set_atomicity.3
index bca4cb56..5b1d8a30 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_set_atomicity.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_set_atomicity.3
@@ -1,4 +1,4 @@
-.TH MPI_File_set_atomicity 3 "11/10/2017" " " "MPI"
+.TH MPI_File_set_atomicity 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_set_atomicity \-  Sets the atomicity mode 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_set_errhandler.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_set_errhandler.3
index 484774d5..a9929256 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_set_errhandler.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_set_errhandler.3
@@ -1,4 +1,4 @@
-.TH MPI_File_set_errhandler 3 "11/10/2017" " " "MPI"
+.TH MPI_File_set_errhandler 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_set_errhandler \-  Set the error handler for an MPI file 
 .SH SYNOPSIS
@@ -9,12 +9,12 @@ int MPI_File_set_errhandler(MPI_File file, MPI_Errhandler errhandler)
 .PD 0
 .TP
 .B file 
-- MPI file (handle) 
+- MPI file (handle)
 .PD 1
 .PD 0
 .TP
 .B errhandler 
-- new error handler for file (handle) 
+- new error handler for file (handle)
 .PD 1
 
 
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_set_info.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_set_info.3
index 2bc70e7a..7c74eb36 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_set_info.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_set_info.3
@@ -1,4 +1,4 @@
-.TH MPI_File_set_info 3 "11/10/2017" " " "MPI"
+.TH MPI_File_set_info 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_set_info \-  Sets new values for the hints associated with a file 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_set_size.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_set_size.3
index 67ef6fdf..aa3be5a9 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_set_size.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_set_size.3
@@ -1,4 +1,4 @@
-.TH MPI_File_set_size 3 "11/10/2017" " " "MPI"
+.TH MPI_File_set_size 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_set_size \-  Sets the file size 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_set_view.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_set_view.3
index 5aad507c..48457d29 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_set_view.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_set_view.3
@@ -1,10 +1,10 @@
-.TH MPI_File_set_view 3 "11/10/2017" " " "MPI"
+.TH MPI_File_set_view 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_set_view \-  Sets the file view 
 .SH SYNOPSIS
 .nf
 int MPI_File_set_view(MPI_File fh, MPI_Offset disp, MPI_Datatype etype,
-                     MPI_Datatype filetype, ROMIO_CONST char *datarep, MPI_Info info)
+                      MPI_Datatype filetype, ROMIO_CONST char *datarep, MPI_Info info)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_sync.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_sync.3
index 1666cb2d..ed71f1a0 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_sync.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_sync.3
@@ -1,4 +1,4 @@
-.TH MPI_File_sync 3 "11/10/2017" " " "MPI"
+.TH MPI_File_sync 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_sync \-  Causes all previous writes to be transferred to the storage device 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_write.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_write.3
index 40a61a88..692c8943 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_write.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_write.3
@@ -1,10 +1,10 @@
-.TH MPI_File_write 3 "11/10/2017" " " "MPI"
+.TH MPI_File_write 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_write \-  Write using individual file pointer 
 .SH SYNOPSIS
 .nf
 int MPI_File_write(MPI_File fh, ROMIO_CONST void *buf, int count,
-                   MPI_Datatype datatype, MPI_Status *status)
+                   MPI_Datatype datatype, MPI_Status * status)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_write_all.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_write_all.3
index 4c853632..ffb22aa3 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_write_all.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_write_all.3
@@ -1,10 +1,10 @@
-.TH MPI_File_write_all 3 "11/10/2017" " " "MPI"
+.TH MPI_File_write_all 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_write_all \-  Collective write using individual file pointer 
 .SH SYNOPSIS
 .nf
 int MPI_File_write_all(MPI_File fh, ROMIO_CONST void *buf, int count,
-                       MPI_Datatype datatype, MPI_Status *status)
+                       MPI_Datatype datatype, MPI_Status * status)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_write_all_begin.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_write_all_begin.3
index d4422091..a325e979 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_write_all_begin.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_write_all_begin.3
@@ -1,10 +1,9 @@
-.TH MPI_File_write_all_begin 3 "11/10/2017" " " "MPI"
+.TH MPI_File_write_all_begin 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_write_all_begin \-  Begin a split collective write using individual file pointer 
 .SH SYNOPSIS
 .nf
-int MPI_File_write_all_begin(MPI_File fh, ROMIO_CONST void *buf, int count,
-                           MPI_Datatype datatype)
+int MPI_File_write_all_begin(MPI_File fh, ROMIO_CONST void *buf, int count, MPI_Datatype datatype)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_write_all_end.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_write_all_end.3
index 0d63e98c..3779e5c9 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_write_all_end.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_write_all_end.3
@@ -1,9 +1,9 @@
-.TH MPI_File_write_all_end 3 "11/10/2017" " " "MPI"
+.TH MPI_File_write_all_end 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_write_all_end \-  Complete a split collective write using individual file pointer 
 .SH SYNOPSIS
 .nf
-int MPI_File_write_all_end(MPI_File fh, ROMIO_CONST void *buf, MPI_Status *status)
+int MPI_File_write_all_end(MPI_File fh, ROMIO_CONST void *buf, MPI_Status * status)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_write_at.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_write_at.3
index a60d7c7d..451622c1 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_write_at.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_write_at.3
@@ -1,10 +1,10 @@
-.TH MPI_File_write_at 3 "11/10/2017" " " "MPI"
+.TH MPI_File_write_at 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_write_at \-  Write using explicit offset 
 .SH SYNOPSIS
 .nf
 int MPI_File_write_at(MPI_File fh, MPI_Offset offset, ROMIO_CONST void *buf,
-                      int count, MPI_Datatype datatype, MPI_Status *status)
+                      int count, MPI_Datatype datatype, MPI_Status * status)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_write_at_all.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_write_at_all.3
index f744388a..c3e01588 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_write_at_all.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_write_at_all.3
@@ -1,11 +1,10 @@
-.TH MPI_File_write_at_all 3 "11/10/2017" " " "MPI"
+.TH MPI_File_write_at_all 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_write_at_all \-  Collective write using explicit offset 
 .SH SYNOPSIS
 .nf
 int MPI_File_write_at_all(MPI_File fh, MPI_Offset offset, ROMIO_CONST void *buf,
-                          int count, MPI_Datatype datatype, 
-                          MPI_Status *status)
+                          int count, MPI_Datatype datatype, MPI_Status * status)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_write_at_all_begin.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_write_at_all_begin.3
index 87d91a8d..7eb49128 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_write_at_all_begin.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_write_at_all_begin.3
@@ -1,10 +1,10 @@
-.TH MPI_File_write_at_all_begin 3 "11/10/2017" " " "MPI"
+.TH MPI_File_write_at_all_begin 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_write_at_all_begin \-  Begin a split collective write using explicit offset 
 .SH SYNOPSIS
 .nf
 int MPI_File_write_at_all_begin(MPI_File fh, MPI_Offset offset, ROMIO_CONST void *buf,
-                             int count, MPI_Datatype datatype)
+                                int count, MPI_Datatype datatype)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_write_at_all_end.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_write_at_all_end.3
index 80e3af4b..0f1a3757 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_write_at_all_end.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_write_at_all_end.3
@@ -1,9 +1,9 @@
-.TH MPI_File_write_at_all_end 3 "11/10/2017" " " "MPI"
+.TH MPI_File_write_at_all_end 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_write_at_all_end \-  Complete a split collective write using explicit offset 
 .SH SYNOPSIS
 .nf
-int MPI_File_write_at_all_end(MPI_File fh, ROMIO_CONST void *buf, MPI_Status *status)
+int MPI_File_write_at_all_end(MPI_File fh, ROMIO_CONST void *buf, MPI_Status * status)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_write_ordered.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_write_ordered.3
index c7f3d9dd..01977289 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_write_ordered.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_write_ordered.3
@@ -1,10 +1,10 @@
-.TH MPI_File_write_ordered 3 "11/10/2017" " " "MPI"
+.TH MPI_File_write_ordered 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_write_ordered \-  Collective write using shared file pointer 
 .SH SYNOPSIS
 .nf
 int MPI_File_write_ordered(MPI_File fh, ROMIO_CONST void *buf, int count,
-                         MPI_Datatype datatype, MPI_Status *status)
+                           MPI_Datatype datatype, MPI_Status * status)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_write_ordered_begin.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_write_ordered_begin.3
index 3fdc50c5..8bbdf7b2 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_write_ordered_begin.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_write_ordered_begin.3
@@ -1,10 +1,10 @@
-.TH MPI_File_write_ordered_begin 3 "11/10/2017" " " "MPI"
+.TH MPI_File_write_ordered_begin 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_write_ordered_begin \-  Begin a split collective write using shared file pointer 
 .SH SYNOPSIS
 .nf
 int MPI_File_write_ordered_begin(MPI_File fh, ROMIO_CONST void *buf, int count,
-                              MPI_Datatype datatype)
+                                 MPI_Datatype datatype)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_write_ordered_end.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_write_ordered_end.3
index 9b336678..20375e77 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_write_ordered_end.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_write_ordered_end.3
@@ -1,9 +1,9 @@
-.TH MPI_File_write_ordered_end 3 "11/10/2017" " " "MPI"
+.TH MPI_File_write_ordered_end 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_write_ordered_end \-  Complete a split collective write using shared file pointer 
 .SH SYNOPSIS
 .nf
-int MPI_File_write_ordered_end(MPI_File fh, ROMIO_CONST void *buf, MPI_Status *status)
+int MPI_File_write_ordered_end(MPI_File fh, ROMIO_CONST void *buf, MPI_Status * status)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_File_write_shared.3 b/linx64/mpi/mpich/share/man/man3/MPI_File_write_shared.3
index c526ebd0..0b0fda7a 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_File_write_shared.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_File_write_shared.3
@@ -1,10 +1,10 @@
-.TH MPI_File_write_shared 3 "11/10/2017" " " "MPI"
+.TH MPI_File_write_shared 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_File_write_shared \-  Write using shared file pointer 
 .SH SYNOPSIS
 .nf
 int MPI_File_write_shared(MPI_File fh, ROMIO_CONST void *buf, int count,
-                          MPI_Datatype datatype, MPI_Status *status)
+                          MPI_Datatype datatype, MPI_Status * status)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Finalize.3 b/linx64/mpi/mpich/share/man/man3/MPI_Finalize.3
index 9b7e8fca..2ffeab93 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Finalize.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Finalize.3
@@ -1,9 +1,9 @@
-.TH MPI_Finalize 3 "11/10/2017" " " "MPI"
+.TH MPI_Finalize 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Finalize \-  Terminates MPI execution environment 
 .SH SYNOPSIS
 .nf
-int MPI_Finalize( void )
+int MPI_Finalize(void)
 .fi
 .SH NOTES
 All processes must call this routine before exiting.  The number of
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Finalized.3 b/linx64/mpi/mpich/share/man/man3/MPI_Finalized.3
index 69944f6f..b74d0f10 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Finalized.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Finalized.3
@@ -1,11 +1,11 @@
-.TH MPI_Finalized 3 "11/10/2017" " " "MPI"
+.TH MPI_Finalized 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Finalized \-  Indicates whether 
 .I MPI_Finalize
 has been called. 
 .SH SYNOPSIS
 .nf
-int MPI_Finalized( int *flag )
+int MPI_Finalized(int *flag)
 .fi
 .SH OUTPUT PARAMETERS
 .PD 0
@@ -13,7 +13,7 @@ int MPI_Finalized( int *flag )
 .B flag 
 - Flag is true if 
 .I MPI_Finalize
-has been called and false otherwise. 
+has been called and false otherwise.
 (logical)
 .PD 1
 
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Free_mem.3 b/linx64/mpi/mpich/share/man/man3/MPI_Free_mem.3
index 17eb61c9..a5b3fc6b 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Free_mem.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Free_mem.3
@@ -1,4 +1,4 @@
-.TH MPI_Free_mem 3 "11/10/2017" " " "MPI"
+.TH MPI_Free_mem 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Free_mem \-  Free memory allocated with MPI_Alloc_mem 
 .SH SYNOPSIS
@@ -11,8 +11,7 @@ int MPI_Free_mem(void *base)
 .B base 
 - initial address of memory segment allocated by 
 .I MPI_ALLOC_MEM
-
-(choice) 
+(choice)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Gather.3 b/linx64/mpi/mpich/share/man/man3/MPI_Gather.3
index 9bbdad4a..01617428 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Gather.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Gather.3
@@ -1,49 +1,48 @@
-.TH MPI_Gather 3 "11/10/2017" " " "MPI"
+.TH MPI_Gather 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Gather \-  Gathers together values from a group of processes 
 .SH SYNOPSIS
 .nf
 int MPI_Gather(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
-               void *recvbuf, int recvcount, MPI_Datatype recvtype,
-               int root, MPI_Comm comm)
+               void *recvbuf, int recvcount, MPI_Datatype recvtype, int root, MPI_Comm comm)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B sendbuf 
-- starting address of send buffer (choice) 
+- starting address of send buffer (choice)
 .PD 1
 .PD 0
 .TP
 .B sendcount 
-- number of elements in send buffer (integer) 
+- number of elements in send buffer (integer)
 .PD 1
 .PD 0
 .TP
 .B sendtype 
-- data type of send buffer elements (handle) 
+- data type of send buffer elements (handle)
 .PD 1
 .PD 0
 .TP
 .B recvcount 
-- number of elements for any single receive (integer, 
-significant only at root) 
+- number of elements for any single receive (integer,
+significant only at root)
 .PD 1
 .PD 0
 .TP
 .B recvtype 
-- data type of recv buffer elements 
-(significant only at root) (handle) 
+- data type of recv buffer elements
+(significant only at root) (handle)
 .PD 1
 .PD 0
 .TP
 .B root 
-- rank of receiving process (integer) 
+- rank of receiving process (integer)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
@@ -52,7 +51,7 @@ significant only at root)
 .B recvbuf 
 - address of receive buffer (choice, significant only at 
 .I root
-) 
+)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Gatherv.3 b/linx64/mpi/mpich/share/man/man3/MPI_Gatherv.3
index 288fd163..e9bf75ce 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Gatherv.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Gatherv.3
@@ -1,4 +1,4 @@
-.TH MPI_Gatherv 3 "11/10/2017" " " "MPI"
+.TH MPI_Gatherv 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Gatherv \-  Gathers into specified locations from all processes in a group 
 .SH SYNOPSIS
@@ -11,55 +11,55 @@ int MPI_Gatherv(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
 .PD 0
 .TP
 .B sendbuf 
-- starting address of send buffer (choice) 
+- starting address of send buffer (choice)
 .PD 1
 .PD 0
 .TP
 .B sendcount 
-- number of elements in send buffer (integer) 
+- number of elements in send buffer (integer)
 .PD 1
 .PD 0
 .TP
 .B sendtype 
-- data type of send buffer elements (handle) 
+- data type of send buffer elements (handle)
 .PD 1
 .PD 0
 .TP
 .B recvcounts 
-- integer array (of length group size) 
+- integer array (of length group size)
 containing the number of elements that are received from each process
 (significant only at 
 .I root
-) 
+)
 .PD 1
 .PD 0
 .TP
 .B displs 
-- integer array (of length group size). Entry 
+- integer array (of length group size). Entry
 .I i
 specifies the displacement relative to recvbuf  at
 which to place the incoming data from process  
 .I i
 (significant only
-at root) 
+at root)
 .PD 1
 .PD 0
 .TP
 .B recvtype 
-- data type of recv buffer elements 
+- data type of recv buffer elements
 (significant only at 
 .I root
-) (handle) 
+) (handle)
 .PD 1
 .PD 0
 .TP
 .B root 
-- rank of receiving process (integer) 
+- rank of receiving process (integer)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
@@ -68,7 +68,7 @@ at root)
 .B recvbuf 
 - address of receive buffer (choice, significant only at 
 .I root
-) 
+)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Get.3 b/linx64/mpi/mpich/share/man/man3/MPI_Get.3
index 18bbf9e6..0ad05ac4 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Get.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Get.3
@@ -1,12 +1,11 @@
-.TH MPI_Get 3 "11/10/2017" " " "MPI"
+.TH MPI_Get 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Get \-  Get data from a memory window on a remote process 
 .SH SYNOPSIS
 .nf
 int MPI_Get(void *origin_addr, int origin_count, MPI_Datatype
             origin_datatype, int target_rank, MPI_Aint target_disp,
-            int target_count, MPI_Datatype target_datatype, MPI_Win
-            win)
+            int target_count, MPI_Datatype target_datatype, MPI_Win win)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
@@ -17,38 +16,38 @@ int MPI_Get(void *origin_addr, int origin_count, MPI_Datatype
 .PD 0
 .TP
 .B origin_count 
-- number of entries in origin buffer (nonnegative integer) 
+- number of entries in origin buffer (nonnegative integer)
 .PD 1
 .PD 0
 .TP
 .B origin_datatype 
-- datatype of each entry in origin buffer (handle) 
+- datatype of each entry in origin buffer (handle)
 .PD 1
 .PD 0
 .TP
 .B target_rank 
-- rank of target (nonnegative integer) 
+- rank of target (nonnegative integer)
 .PD 1
 .PD 0
 .TP
 .B target_disp 
-- displacement from window start to the beginning of the 
-target buffer (nonnegative integer) 
+- displacement from window start to the beginning of the
+target buffer (nonnegative integer)
 .PD 1
 .PD 0
 .TP
 .B target_count 
-- number of entries in target buffer (nonnegative integer) 
+- number of entries in target buffer (nonnegative integer)
 .PD 1
 .PD 0
 .TP
 .B target_datatype 
-- datatype of each entry in target buffer (handle) 
+- datatype of each entry in target buffer (handle)
 .PD 1
 .PD 0
 .TP
 .B win 
-- window object used for communication (handle) 
+- window object used for communication (handle)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Get_accumulate.3 b/linx64/mpi/mpich/share/man/man3/MPI_Get_accumulate.3
index 58cf5388..37ebd704 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Get_accumulate.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Get_accumulate.3
@@ -1,12 +1,12 @@
-.TH MPI_Get_accumulate 3 "11/10/2017" " " "MPI"
+.TH MPI_Get_accumulate 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Get_accumulate \-  Perform an atomic, one-sided read-and-accumulate operation. 
 .SH SYNOPSIS
 .nf
 int MPI_Get_accumulate(const void *origin_addr, int origin_count,
-        MPI_Datatype origin_datatype, void *result_addr, int result_count,
-        MPI_Datatype result_datatype, int target_rank, MPI_Aint target_disp,
-        int target_count, MPI_Datatype target_datatype, MPI_Op op, MPI_Win win)
+                       MPI_Datatype origin_datatype, void *result_addr, int result_count,
+                       MPI_Datatype result_datatype, int target_rank, MPI_Aint target_disp,
+                       int target_count, MPI_Datatype target_datatype, MPI_Op op, MPI_Win win)
 .fi
 
 Accumulate origin_count elements of type origin_datatype from the origin buffer
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Get_address.3 b/linx64/mpi/mpich/share/man/man3/MPI_Get_address.3
index 193868d3..e653da7a 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Get_address.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Get_address.3
@@ -1,9 +1,9 @@
-.TH MPI_Get_address 3 "11/10/2017" " " "MPI"
+.TH MPI_Get_address 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Get_address \-  Get the address of a location in memory 
 .SH SYNOPSIS
 .nf
-int MPI_Get_address(const void *location, MPI_Aint *address)
+int MPI_Get_address(const void *location, MPI_Aint * address)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Get_count.3 b/linx64/mpi/mpich/share/man/man3/MPI_Get_count.3
index c9bf9f4f..c5cd0163 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Get_count.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Get_count.3
@@ -1,32 +1,32 @@
-.TH MPI_Get_count 3 "11/10/2017" " " "MPI"
+.TH MPI_Get_count 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Get_count \-  Gets the number of "top level" elements 
 .SH SYNOPSIS
 .nf
-int MPI_Get_count( const MPI_Status *status, MPI_Datatype datatype, int *count )
+int MPI_Get_count(const MPI_Status * status, MPI_Datatype datatype, int *count)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B status 
-- return status of receive operation (Status) 
+- return status of receive operation (Status)
 .PD 1
 .PD 0
 .TP
 .B datatype 
-- datatype of each receive buffer element (handle) 
+- datatype of each receive buffer element (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B count 
-- number of received elements (integer) 
+- number of received elements (integer)
 Notes:
 If the size of the datatype is zero, this routine will return a count of
 zero.  If the amount of data in 
 .I status
-is not an exact multiple of the 
+is not an exact multiple of the
 size of 
 .I datatype
 (so that 
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Get_elements.3 b/linx64/mpi/mpich/share/man/man3/MPI_Get_elements.3
index 2ca6da5e..bc8c8bed 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Get_elements.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Get_elements.3
@@ -1,9 +1,9 @@
-.TH MPI_Get_elements 3 "11/10/2017" " " "MPI"
+.TH MPI_Get_elements 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Get_elements \-  Returns the number of basic elements in a datatype 
 .SH SYNOPSIS
 .nf
-int MPI_Get_elements(const MPI_Status *status, MPI_Datatype datatype, int *count)
+int MPI_Get_elements(const MPI_Status * status, MPI_Datatype datatype, int *count)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Get_elements_x.3 b/linx64/mpi/mpich/share/man/man3/MPI_Get_elements_x.3
index 31247075..38f34fe6 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Get_elements_x.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Get_elements_x.3
@@ -1,9 +1,9 @@
-.TH MPI_Get_elements_x 3 "11/10/2017" " " "MPI"
+.TH MPI_Get_elements_x 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Get_elements_x \-  Returns the number of basic elements in a datatype 
 .SH SYNOPSIS
 .nf
-int MPI_Get_elements_x(const MPI_Status *status, MPI_Datatype datatype, MPI_Count *count)
+int MPI_Get_elements_x(const MPI_Status * status, MPI_Datatype datatype, MPI_Count * count)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Get_library_version.3 b/linx64/mpi/mpich/share/man/man3/MPI_Get_library_version.3
index 86c5acc0..cf7886e2 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Get_library_version.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Get_library_version.3
@@ -1,4 +1,4 @@
-.TH MPI_Get_library_version 3 "11/10/2017" " " "MPI"
+.TH MPI_Get_library_version 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Get_library_version \-  Return the version number of MPI library 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Get_processor_name.3 b/linx64/mpi/mpich/share/man/man3/MPI_Get_processor_name.3
index c5561ac3..bf410935 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Get_processor_name.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Get_processor_name.3
@@ -1,9 +1,9 @@
-.TH MPI_Get_processor_name 3 "11/10/2017" " " "MPI"
+.TH MPI_Get_processor_name 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Get_processor_name \-  Gets the name of the processor 
 .SH SYNOPSIS
 .nf
-int MPI_Get_processor_name( char *name, int *resultlen )
+int MPI_Get_processor_name(char *name, int *resultlen)
 .fi
 .SH OUTPUT PARAMETERS
 .PD 0
@@ -18,7 +18,7 @@ must be an array of size at least
 .PD 0
 .TP
 .B resultlen 
-- Length (in characters) of the name 
+- Length (in characters) of the name
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Get_version.3 b/linx64/mpi/mpich/share/man/man3/MPI_Get_version.3
index 14175b2a..b793c462 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Get_version.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Get_version.3
@@ -1,9 +1,9 @@
-.TH MPI_Get_version 3 "11/10/2017" " " "MPI"
+.TH MPI_Get_version 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Get_version \-  Return the version number of MPI 
 .SH SYNOPSIS
 .nf
-int MPI_Get_version( int *version, int *subversion )
+int MPI_Get_version(int *version, int *subversion)
 .fi
 .SH OUTPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Graph_create.3 b/linx64/mpi/mpich/share/man/man3/MPI_Graph_create.3
index d621a668..0d3ee472 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Graph_create.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Graph_create.3
@@ -1,43 +1,43 @@
-.TH MPI_Graph_create 3 "11/10/2017" " " "MPI"
+.TH MPI_Graph_create 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Graph_create \-  Makes a new communicator to which topology information has been attached 
 .SH SYNOPSIS
 .nf
 int MPI_Graph_create(MPI_Comm comm_old, int nnodes, const int indx[],
-                     const int edges[], int reorder, MPI_Comm *comm_graph)
+                     const int edges[], int reorder, MPI_Comm * comm_graph)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B comm_old 
-- input communicator without topology (handle) 
+- input communicator without topology (handle)
 .PD 1
 .PD 0
 .TP
 .B nnodes 
-- number of nodes in graph (integer) 
+- number of nodes in graph (integer)
 .PD 1
 .PD 0
 .TP
 .B indx 
-- array of integers describing node degrees (see below) 
+- array of integers describing node degrees (see below)
 .PD 1
 .PD 0
 .TP
 .B edges 
-- array of integers describing graph edges (see below) 
+- array of integers describing graph edges (see below)
 .PD 1
 .PD 0
 .TP
 .B reorder 
-- ranking may be reordered (true) or not (false) (logical) 
+- ranking may be reordered (true) or not (false) (logical)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B comm_graph 
-- communicator with graph topology added (handle) 
+- communicator with graph topology added (handle)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Graph_get.3 b/linx64/mpi/mpich/share/man/man3/MPI_Graph_get.3
index 9a732b40..18177f4d 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Graph_get.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Graph_get.3
@@ -1,30 +1,29 @@
-.TH MPI_Graph_get 3 "11/10/2017" " " "MPI"
+.TH MPI_Graph_get 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Graph_get \-  Retrieves graph topology information associated with a  communicator 
+MPI_Graph_get \-  Retrieves graph topology information associated with a communicator 
 .SH SYNOPSIS
 .nf
-int MPI_Graph_get(MPI_Comm comm, int maxindex, int maxedges, 
-                  int indx[], int edges[])
+int MPI_Graph_get(MPI_Comm comm, int maxindex, int maxedges, int indx[], int edges[])
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B comm 
-- communicator with graph structure (handle) 
+- communicator with graph structure (handle)
 .PD 1
 .PD 0
 .TP
 .B maxindex 
 - length of vector 
 .I indx
-in the calling program  (integer) 
+in the calling program  (integer)
 .PD 1
 .PD 0
 .TP
 .B maxedges 
 - length of vector 
 .I edges
-in the calling program  (integer) 
+in the calling program  (integer)
 .PD 1
 
 .SH OUTPUT PARAMETERS
@@ -33,12 +32,12 @@ in the calling program  (integer)
 .B indx 
 - array of integers containing the graph structure (for details see the definition of 
 .I MPI_GRAPH_CREATE
-) 
+)
 .PD 1
 .PD 0
 .TP
 .B edges 
-- array of integers containing the graph structure 
+- array of integers containing the graph structure
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Graph_map.3 b/linx64/mpi/mpich/share/man/man3/MPI_Graph_map.3
index e1b0366c..5c3258c7 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Graph_map.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Graph_map.3
@@ -1,21 +1,20 @@
-.TH MPI_Graph_map 3 "11/10/2017" " " "MPI"
+.TH MPI_Graph_map 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Graph_map \-  Maps process to graph topology information 
 .SH SYNOPSIS
 .nf
-int MPI_Graph_map(MPI_Comm comm, int nnodes, const int indx[], const int edges[],
-                  int *newrank)
+int MPI_Graph_map(MPI_Comm comm, int nnodes, const int indx[], const int edges[], int *newrank)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B comm 
-- input communicator (handle) 
+- input communicator (handle)
 .PD 1
 .PD 0
 .TP
 .B nnodes 
-- number of graph nodes (integer) 
+- number of graph nodes (integer)
 .PD 1
 .PD 0
 .TP
@@ -27,7 +26,7 @@ int MPI_Graph_map(MPI_Comm comm, int nnodes, const int indx[], const int edges[]
 .PD 0
 .TP
 .B edges 
-- integer array specifying the graph structure 
+- integer array specifying the graph structure
 .PD 1
 
 .SH OUTPUT PARAMETERS
@@ -36,8 +35,8 @@ int MPI_Graph_map(MPI_Comm comm, int nnodes, const int indx[], const int edges[]
 .B newrank 
 - reordered rank of the calling process; 
 .I MPI_UNDEFINED
-if the 
-calling process does not belong to graph (integer) 
+if the
+calling process does not belong to graph (integer)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Graph_neighbors.3 b/linx64/mpi/mpich/share/man/man3/MPI_Graph_neighbors.3
index fd23c8b8..a5a7cd99 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Graph_neighbors.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Graph_neighbors.3
@@ -1,26 +1,25 @@
-.TH MPI_Graph_neighbors 3 "11/10/2017" " " "MPI"
+.TH MPI_Graph_neighbors 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Graph_neighbors \-  Returns the neighbors of a node associated  with a graph topology 
+MPI_Graph_neighbors \-  Returns the neighbors of a node associated with a graph topology 
 .SH SYNOPSIS
 .nf
-int MPI_Graph_neighbors(MPI_Comm comm, int rank, int maxneighbors, 
-                      int neighbors[])
+int MPI_Graph_neighbors(MPI_Comm comm, int rank, int maxneighbors, int neighbors[])
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B comm 
-- communicator with graph topology (handle) 
+- communicator with graph topology (handle)
 .PD 1
 .PD 0
 .TP
 .B rank 
-- rank of process in group of comm (integer) 
+- rank of process in group of comm (integer)
 .PD 1
 .PD 0
 .TP
 .B maxneighbors 
-- size of array neighbors (integer) 
+- size of array neighbors (integer)
 .PD 1
 
 .SH OUTPUT PARAMETERS
@@ -28,7 +27,7 @@ int MPI_Graph_neighbors(MPI_Comm comm, int rank, int maxneighbors,
 .TP
 .B neighbors 
 - ranks of processes that are neighbors to specified process
-(array of integer) 
+(array of integer)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Graph_neighbors_count.3 b/linx64/mpi/mpich/share/man/man3/MPI_Graph_neighbors_count.3
index 1d27e837..e4c3a488 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Graph_neighbors_count.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Graph_neighbors_count.3
@@ -1,4 +1,4 @@
-.TH MPI_Graph_neighbors_count 3 "11/10/2017" " " "MPI"
+.TH MPI_Graph_neighbors_count 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Graph_neighbors_count \-  Returns the number of neighbors of a node associated with a graph topology 
 .SH SYNOPSIS
@@ -9,21 +9,21 @@ int MPI_Graph_neighbors_count(MPI_Comm comm, int rank, int *nneighbors)
 .PD 0
 .TP
 .B comm 
-- communicator with graph topology (handle) 
+- communicator with graph topology (handle)
 .PD 1
 .PD 0
 .TP
 .B rank 
 - rank of process in group of 
 .I comm
-(integer) 
+(integer)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B nneighbors 
-- number of neighbors of specified process (integer) 
+- number of neighbors of specified process (integer)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Graphdims_get.3 b/linx64/mpi/mpich/share/man/man3/MPI_Graphdims_get.3
index 67035237..f2ca1988 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Graphdims_get.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Graphdims_get.3
@@ -1,6 +1,6 @@
-.TH MPI_Graphdims_get 3 "11/10/2017" " " "MPI"
+.TH MPI_Graphdims_get 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Graphdims_get \-  Retrieves graph topology information associated with a  communicator 
+MPI_Graphdims_get \-  Retrieves graph topology information associated with a communicator 
 .SH SYNOPSIS
 .nf
 int MPI_Graphdims_get(MPI_Comm comm, int *nnodes, int *nedges)
@@ -9,19 +9,19 @@ int MPI_Graphdims_get(MPI_Comm comm, int *nnodes, int *nedges)
 .PD 0
 .TP
 .B comm 
-- communicator for group with graph structure (handle) 
+- communicator for group with graph structure (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B nnodes 
-- number of nodes in graph (integer) 
+- number of nodes in graph (integer)
 .PD 1
 .PD 0
 .TP
 .B nedges 
-- number of edges in graph (integer) 
+- number of edges in graph (integer)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Grequest_complete.3 b/linx64/mpi/mpich/share/man/man3/MPI_Grequest_complete.3
index 3eb70f23..252ac1c2 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Grequest_complete.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Grequest_complete.3
@@ -1,9 +1,9 @@
-.TH MPI_Grequest_complete 3 "11/10/2017" " " "MPI"
+.TH MPI_Grequest_complete 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Grequest_complete \-  Notify MPI that a user-defined request is complete 
 .SH SYNOPSIS
 .nf
-int MPI_Grequest_complete( MPI_Request request )
+int MPI_Grequest_complete(MPI_Request request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Grequest_start.3 b/linx64/mpi/mpich/share/man/man3/MPI_Grequest_start.3
index 88cfa6e7..cdcfc6e9 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Grequest_start.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Grequest_start.3
@@ -1,28 +1,28 @@
-.TH MPI_Grequest_start 3 "11/10/2017" " " "MPI"
+.TH MPI_Grequest_start 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Grequest_start \-  Create and return a user-defined request 
 .SH SYNOPSIS
 .nf
-int MPI_Grequest_start( MPI_Grequest_query_function *query_fn, 
-                      MPI_Grequest_free_function *free_fn, 
-                      MPI_Grequest_cancel_function *cancel_fn, 
-                      void *extra_state, MPI_Request *request )
+int MPI_Grequest_start(MPI_Grequest_query_function * query_fn,
+                       MPI_Grequest_free_function * free_fn,
+                       MPI_Grequest_cancel_function * cancel_fn,
+                       void *extra_state, MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B query_fn 
-- callback function invoked when request status is queried (function)  
+- callback function invoked when request status is queried (function)
 .PD 1
 .PD 0
 .TP
 .B free_fn 
-- callback function invoked when request is freed (function) 
+- callback function invoked when request is freed (function)
 .PD 1
 .PD 0
 .TP
 .B cancel_fn 
-- callback function invoked when request is cancelled (function) 
+- callback function invoked when request is cancelled (function)
 .PD 1
 .PD 0
 .TP
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Group_compare.3 b/linx64/mpi/mpich/share/man/man3/MPI_Group_compare.3
index dc378f9e..0e21819d 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Group_compare.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Group_compare.3
@@ -1,4 +1,4 @@
-.TH MPI_Group_compare 3 "11/10/2017" " " "MPI"
+.TH MPI_Group_compare 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Group_compare \-  Compares two groups 
 .SH SYNOPSIS
@@ -9,12 +9,12 @@ int MPI_Group_compare(MPI_Group group1, MPI_Group group2, int *result)
 .PD 0
 .TP
 .B group1 
-- group1 (handle) 
+- group1 (handle)
 .PD 1
 .PD 0
 .TP
 .B group2 
-- group2 (handle) 
+- group2 (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Group_difference.3 b/linx64/mpi/mpich/share/man/man3/MPI_Group_difference.3
index cf83eefe..fe429818 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Group_difference.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Group_difference.3
@@ -1,27 +1,27 @@
-.TH MPI_Group_difference 3 "11/10/2017" " " "MPI"
+.TH MPI_Group_difference 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Group_difference \-  Makes a group from the difference of two groups 
 .SH SYNOPSIS
 .nf
-int MPI_Group_difference(MPI_Group group1, MPI_Group group2, MPI_Group *newgroup)
+int MPI_Group_difference(MPI_Group group1, MPI_Group group2, MPI_Group * newgroup)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B group1 
-- first group (handle) 
+- first group (handle)
 .PD 1
 .PD 0
 .TP
 .B group2 
-- second group (handle) 
+- second group (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B newgroup 
-- difference group (handle) 
+- difference group (handle)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Group_excl.3 b/linx64/mpi/mpich/share/man/man3/MPI_Group_excl.3
index f900490b..93b71a2d 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Group_excl.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Group_excl.3
@@ -1,22 +1,22 @@
-.TH MPI_Group_excl 3 "11/10/2017" " " "MPI"
+.TH MPI_Group_excl 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Group_excl \-  Produces a group by reordering an existing group and taking only unlisted members 
 .SH SYNOPSIS
 .nf
-int MPI_Group_excl(MPI_Group group, int n, const int ranks[], MPI_Group *newgroup)
+int MPI_Group_excl(MPI_Group group, int n, const int ranks[], MPI_Group * newgroup)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B group 
-- group (handle) 
+- group (handle)
 .PD 1
 .PD 0
 .TP
 .B n 
 - number of elements in array 
 .I ranks
-(integer) 
+(integer)
 .PD 1
 .PD 0
 .TP
@@ -32,9 +32,9 @@ not to appear in
 .PD 0
 .TP
 .B newgroup 
-- new group derived from above, preserving the order defined by 
+- new group derived from above, preserving the order defined by
 .I group
-(handle) 
+(handle)
 .PD 1
 
 .SH NOTE
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Group_free.3 b/linx64/mpi/mpich/share/man/man3/MPI_Group_free.3
index 17e83265..5a6a6642 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Group_free.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Group_free.3
@@ -1,15 +1,15 @@
-.TH MPI_Group_free 3 "11/10/2017" " " "MPI"
+.TH MPI_Group_free 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Group_free \-  Frees a group 
 .SH SYNOPSIS
 .nf
-int MPI_Group_free(MPI_Group *group)
+int MPI_Group_free(MPI_Group * group)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B group 
-- group to free (handle) 
+- group to free (handle)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Group_incl.3 b/linx64/mpi/mpich/share/man/man3/MPI_Group_incl.3
index 1dd1437c..f8ece65b 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Group_incl.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Group_incl.3
@@ -1,22 +1,22 @@
-.TH MPI_Group_incl 3 "11/10/2017" " " "MPI"
+.TH MPI_Group_incl 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Group_incl \-  Produces a group by reordering an existing group and taking only listed members 
 .SH SYNOPSIS
 .nf
-int MPI_Group_incl(MPI_Group group, int n, const int ranks[], MPI_Group *newgroup)
+int MPI_Group_incl(MPI_Group group, int n, const int ranks[], MPI_Group * newgroup)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B group 
-- group (handle) 
+- group (handle)
 .PD 1
 .PD 0
 .TP
 .B n 
 - number of elements in array 
 .I ranks
-(and size of newgroup ) (integer) 
+(and size of newgroup) (integer)
 .PD 1
 .PD 0
 .TP
@@ -25,8 +25,8 @@ int MPI_Group_incl(MPI_Group group, int n, const int ranks[], MPI_Group *newgrou
 .I group
 to appear in 
 .I newgroup
-(array of 
-integers) 
+(array of
+integers)
 .PD 1
 
 .SH OUTPUT PARAMETERS
@@ -35,8 +35,7 @@ integers)
 .B newgroup 
 - new group derived from above, in the order defined by 
 .I ranks
-
-(handle) 
+(handle)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Group_intersection.3 b/linx64/mpi/mpich/share/man/man3/MPI_Group_intersection.3
index cece8008..ec9c1000 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Group_intersection.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Group_intersection.3
@@ -1,27 +1,27 @@
-.TH MPI_Group_intersection 3 "11/10/2017" " " "MPI"
+.TH MPI_Group_intersection 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Group_intersection \-  Produces a group as the intersection of two existing groups 
 .SH SYNOPSIS
 .nf
-int MPI_Group_intersection(MPI_Group group1, MPI_Group group2, MPI_Group *newgroup)
+int MPI_Group_intersection(MPI_Group group1, MPI_Group group2, MPI_Group * newgroup)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B group1 
-- first group (handle) 
+- first group (handle)
 .PD 1
 .PD 0
 .TP
 .B group2 
-- second group (handle) 
+- second group (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B newgroup 
-- intersection group (handle) 
+- intersection group (handle)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Group_range_excl.3 b/linx64/mpi/mpich/share/man/man3/MPI_Group_range_excl.3
index 12a020be..8377d2b6 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Group_range_excl.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Group_range_excl.3
@@ -1,23 +1,22 @@
-.TH MPI_Group_range_excl 3 "11/10/2017" " " "MPI"
+.TH MPI_Group_range_excl 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Group_range_excl \-  Produces a group by excluding ranges of processes from an existing group 
 .SH SYNOPSIS
 .nf
-int MPI_Group_range_excl(MPI_Group group, int n, int ranges[][3], 
-                         MPI_Group *newgroup)
+int MPI_Group_range_excl(MPI_Group group, int n, int ranges[][3], MPI_Group * newgroup)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B group 
-- group (handle) 
+- group (handle)
 .PD 1
 .PD 0
 .TP
 .B n 
 - number of elements in array 
 .I ranks
-(integer) 
+(integer)
 .PD 1
 .PD 0
 .TP
@@ -35,10 +34,10 @@ of processes to be excluded from the output group
 .PD 0
 .TP
 .B newgroup 
-- new group derived from above, preserving the 
+- new group derived from above, preserving the
 order in 
 .I group
-(handle) 
+(handle)
 .PD 1
 
 .SH NOTE
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Group_range_incl.3 b/linx64/mpi/mpich/share/man/man3/MPI_Group_range_incl.3
index ad9cbc85..16b4261e 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Group_range_incl.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Group_range_incl.3
@@ -1,28 +1,27 @@
-.TH MPI_Group_range_incl 3 "11/10/2017" " " "MPI"
+.TH MPI_Group_range_incl 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Group_range_incl \-  Creates a new group from ranges of ranks in an  existing group 
+MPI_Group_range_incl \-  Creates a new group from ranges of ranks in an existing group 
 .SH SYNOPSIS
 .nf
-int MPI_Group_range_incl(MPI_Group group, int n, int ranges[][3], 
-                         MPI_Group *newgroup)
+int MPI_Group_range_incl(MPI_Group group, int n, int ranges[][3], MPI_Group * newgroup)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B group 
-- group (handle) 
+- group (handle)
 .PD 1
 .PD 0
 .TP
 .B n 
 - number of triplets in array  
 .I ranges
-(integer) 
+(integer)
 .PD 1
 .PD 0
 .TP
 .B ranges 
-- a one-dimensional array of integer triplets, of the 
+- a one-dimensional array of integer triplets, of the
 form (first rank, last rank, stride) indicating ranks in
 .I group
 or processes to be included in 
@@ -35,7 +34,7 @@ or processes to be included in
 .PD 0
 .TP
 .B newgroup 
-- new group derived from above, in the 
+- new group derived from above, in the
 order defined by  
 .I ranges
 (handle)
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Group_rank.3 b/linx64/mpi/mpich/share/man/man3/MPI_Group_rank.3
index 0ca8f08e..dc393c8d 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Group_rank.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Group_rank.3
@@ -1,4 +1,4 @@
-.TH MPI_Group_rank 3 "11/10/2017" " " "MPI"
+.TH MPI_Group_rank 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Group_rank \-  Returns the rank of this process in the given group 
 .SH SYNOPSIS
@@ -9,7 +9,7 @@ int MPI_Group_rank(MPI_Group group, int *rank)
 .PD 0
 .TP
 .B group 
-- group (handle) 
+- group (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
@@ -18,8 +18,8 @@ int MPI_Group_rank(MPI_Group group, int *rank)
 .B rank 
 - rank of the calling process in group, or 
 .I MPI_UNDEFINED
-if the 
-process is not a member (integer) 
+if the
+process is not a member (integer)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Group_size.3 b/linx64/mpi/mpich/share/man/man3/MPI_Group_size.3
index cf923aa0..1d641578 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Group_size.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Group_size.3
@@ -1,4 +1,4 @@
-.TH MPI_Group_size 3 "11/10/2017" " " "MPI"
+.TH MPI_Group_size 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Group_size \-  Returns the size of a group 
 .SH SYNOPSIS
@@ -9,14 +9,14 @@ int MPI_Group_size(MPI_Group group, int *size)
 .PD 0
 .TP
 .B group 
-- group (handle) 
+- group (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B size 
-- number of processes in the group (integer) 
+- number of processes in the group (integer)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Group_translate_ranks.3 b/linx64/mpi/mpich/share/man/man3/MPI_Group_translate_ranks.3
index 0b8fbb05..aa5b260d 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Group_translate_ranks.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Group_translate_ranks.3
@@ -1,16 +1,16 @@
-.TH MPI_Group_translate_ranks 3 "11/10/2017" " " "MPI"
+.TH MPI_Group_translate_ranks 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Group_translate_ranks \-  Translates the ranks of processes in one group to  those in another group 
+MPI_Group_translate_ranks \-  Translates the ranks of processes in one group to those in another group 
 .SH SYNOPSIS
 .nf
 int MPI_Group_translate_ranks(MPI_Group group1, int n, const int ranks1[],
-                            MPI_Group group2, int ranks2[])
+                              MPI_Group group2, int ranks2[])
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B group1 
-- group1 (handle) 
+- group1 (handle)
 .PD 1
 .PD 0
 .TP
@@ -19,7 +19,7 @@ int MPI_Group_translate_ranks(MPI_Group group1, int n, const int ranks1[],
 .I ranks1
 and 
 .I ranks2
-arrays (integer) 
+arrays (integer)
 .PD 1
 .PD 0
 .TP
@@ -31,7 +31,7 @@ arrays (integer)
 .PD 0
 .TP
 .B group2 
-- group2 (handle) 
+- group2 (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
@@ -40,8 +40,8 @@ arrays (integer)
 .B ranks2 
 - array of corresponding ranks in group2,  
 .I MPI_UNDEFINED
-when no 
-correspondence exists. 
+when no
+correspondence exists.
 .PD 1
 
 As a special case (see the MPI-2 errata), if the input rank is
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Group_union.3 b/linx64/mpi/mpich/share/man/man3/MPI_Group_union.3
index 97701db9..1095df03 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Group_union.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Group_union.3
@@ -1,27 +1,27 @@
-.TH MPI_Group_union 3 "11/10/2017" " " "MPI"
+.TH MPI_Group_union 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Group_union \-  Produces a group by combining two groups 
 .SH SYNOPSIS
 .nf
-int MPI_Group_union(MPI_Group group1, MPI_Group group2, MPI_Group *newgroup)
+int MPI_Group_union(MPI_Group group1, MPI_Group group2, MPI_Group * newgroup)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B group1 
-- first group (handle) 
+- first group (handle)
 .PD 1
 .PD 0
 .TP
 .B group2 
-- second group (handle) 
+- second group (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B newgroup 
-- union group (handle) 
+- union group (handle)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Iallgather.3 b/linx64/mpi/mpich/share/man/man3/MPI_Iallgather.3
index 0d0ff18a..20512c82 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Iallgather.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Iallgather.3
@@ -1,11 +1,11 @@
-.TH MPI_Iallgather 3 "11/10/2017" " " "MPI"
+.TH MPI_Iallgather 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Iallgather \-  Gathers data from all tasks and distribute the combined data to all tasks in a nonblocking way 
 .SH SYNOPSIS
 .nf
 int MPI_Iallgather(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
                    void *recvbuf, int recvcount, MPI_Datatype recvtype,
-                   MPI_Comm comm, MPI_Request *request)
+                   MPI_Comm comm, MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Iallgatherv.3 b/linx64/mpi/mpich/share/man/man3/MPI_Iallgatherv.3
index c77f4f99..8256bc00 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Iallgatherv.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Iallgatherv.3
@@ -1,11 +1,11 @@
-.TH MPI_Iallgatherv 3 "11/10/2017" " " "MPI"
+.TH MPI_Iallgatherv 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Iallgatherv \-  Gathers data from all tasks and deliver the combined data to all tasks in a nonblocking way 
 .SH SYNOPSIS
 .nf
 int MPI_Iallgatherv(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
                     const int recvcounts[], const int displs[], MPI_Datatype recvtype,
-                    MPI_Comm comm, MPI_Request *request)
+                    MPI_Comm comm, MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Iallreduce.3 b/linx64/mpi/mpich/share/man/man3/MPI_Iallreduce.3
index b823650b..4c91e6b6 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Iallreduce.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Iallreduce.3
@@ -1,11 +1,10 @@
-.TH MPI_Iallreduce 3 "11/10/2017" " " "MPI"
+.TH MPI_Iallreduce 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Iallreduce \-  Combines values from all processes and distributes the result back to all processes in a nonblocking way 
 .SH SYNOPSIS
 .nf
 int MPI_Iallreduce(const void *sendbuf, void *recvbuf, int count,
-                   MPI_Datatype datatype, MPI_Op op, MPI_Comm comm,
-                   MPI_Request *request)
+                   MPI_Datatype datatype, MPI_Op op, MPI_Comm comm, MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Ialltoall.3 b/linx64/mpi/mpich/share/man/man3/MPI_Ialltoall.3
index 2aefbe2e..b2149f68 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Ialltoall.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Ialltoall.3
@@ -1,11 +1,11 @@
-.TH MPI_Ialltoall 3 "11/10/2017" " " "MPI"
+.TH MPI_Ialltoall 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Ialltoall \-  Sends data from all to all processes in a nonblocking way 
 .SH SYNOPSIS
 .nf
 int MPI_Ialltoall(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
                   void *recvbuf, int recvcount, MPI_Datatype recvtype,
-                  MPI_Comm comm, MPI_Request *request)
+                  MPI_Comm comm, MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Ialltoallv.3 b/linx64/mpi/mpich/share/man/man3/MPI_Ialltoallv.3
index 9689450b..8dbe1bed 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Ialltoallv.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Ialltoallv.3
@@ -1,11 +1,11 @@
-.TH MPI_Ialltoallv 3 "11/10/2017" " " "MPI"
+.TH MPI_Ialltoallv 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Ialltoallv \-  Sends data from all to all processes in a nonblocking way; each process may send a different amount of data and provide displacements for the input and output data. 
 .SH SYNOPSIS
 .nf
 int MPI_Ialltoallv(const void *sendbuf, const int sendcounts[], const int sdispls[],
                    MPI_Datatype sendtype, void *recvbuf, const int recvcounts[],
-                   const int rdispls[], MPI_Datatype recvtype, MPI_Comm comm, MPI_Request *request)
+                   const int rdispls[], MPI_Datatype recvtype, MPI_Comm comm, MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Ialltoallw.3 b/linx64/mpi/mpich/share/man/man3/MPI_Ialltoallw.3
index 6595cc52..1a1e3e23 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Ialltoallw.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Ialltoallw.3
@@ -1,4 +1,4 @@
-.TH MPI_Ialltoallw 3 "11/10/2017" " " "MPI"
+.TH MPI_Ialltoallw 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Ialltoallw \-  Nonblocking generalized all-to-all communication allowing different datatypes, counts, and displacements for each partner 
 .SH SYNOPSIS
@@ -6,7 +6,7 @@ MPI_Ialltoallw \-  Nonblocking generalized all-to-all communication allowing dif
 int MPI_Ialltoallw(const void *sendbuf, const int sendcounts[], const int sdispls[],
                    const MPI_Datatype sendtypes[], void *recvbuf, const int recvcounts[],
                    const int rdispls[], const MPI_Datatype recvtypes[], MPI_Comm comm,
-                   MPI_Request *request)
+                   MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Ibarrier.3 b/linx64/mpi/mpich/share/man/man3/MPI_Ibarrier.3
index 79607db3..262dc2c5 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Ibarrier.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Ibarrier.3
@@ -1,9 +1,9 @@
-.TH MPI_Ibarrier 3 "11/10/2017" " " "MPI"
+.TH MPI_Ibarrier 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Ibarrier \-  Notifies the process that it has reached the barrier and returns immediately 
 .SH SYNOPSIS
 .nf
-int MPI_Ibarrier(MPI_Comm comm, MPI_Request *request)
+int MPI_Ibarrier(MPI_Comm comm, MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Ibcast.3 b/linx64/mpi/mpich/share/man/man3/MPI_Ibcast.3
index 12e47b70..590d709d 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Ibcast.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Ibcast.3
@@ -1,9 +1,10 @@
-.TH MPI_Ibcast 3 "11/10/2017" " " "MPI"
+.TH MPI_Ibcast 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Ibcast \-  Broadcasts a message from the process with rank "root" to all other processes of the communicator in a nonblocking way 
 .SH SYNOPSIS
 .nf
-int MPI_Ibcast(void *buffer, int count, MPI_Datatype datatype, int root, MPI_Comm comm, MPI_Request *request)
+int MPI_Ibcast(void *buffer, int count, MPI_Datatype datatype, int root, MPI_Comm comm,
+               MPI_Request * request)
 .fi
 .SH INPUT/OUTPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Ibsend.3 b/linx64/mpi/mpich/share/man/man3/MPI_Ibsend.3
index 43945487..1fdce330 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Ibsend.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Ibsend.3
@@ -1,48 +1,48 @@
-.TH MPI_Ibsend 3 "11/10/2017" " " "MPI"
+.TH MPI_Ibsend 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Ibsend \-  Starts a nonblocking buffered send 
 .SH SYNOPSIS
 .nf
 int MPI_Ibsend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-               MPI_Comm comm, MPI_Request *request)
+               MPI_Comm comm, MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B buf 
-- initial address of send buffer (choice) 
+- initial address of send buffer (choice)
 .PD 1
 .PD 0
 .TP
 .B count 
-- number of elements in send buffer (integer) 
+- number of elements in send buffer (integer)
 .PD 1
 .PD 0
 .TP
 .B datatype 
-- datatype of each send buffer element (handle) 
+- datatype of each send buffer element (handle)
 .PD 1
 .PD 0
 .TP
 .B dest 
-- rank of destination (integer) 
+- rank of destination (integer)
 .PD 1
 .PD 0
 .TP
 .B tag 
-- message tag (integer) 
+- message tag (integer)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B request 
-- communication request (handle) 
+- communication request (handle)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Iexscan.3 b/linx64/mpi/mpich/share/man/man3/MPI_Iexscan.3
index be25c764..bde783bc 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Iexscan.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Iexscan.3
@@ -1,10 +1,10 @@
-.TH MPI_Iexscan 3 "11/10/2017" " " "MPI"
+.TH MPI_Iexscan 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Iexscan \-  Computes the exclusive scan (partial reductions) of data on a collection of processes in a nonblocking way 
 .SH SYNOPSIS
 .nf
 int MPI_Iexscan(const void *sendbuf, void *recvbuf, int count, MPI_Datatype datatype,
-                MPI_Op op, MPI_Comm comm, MPI_Request *request)
+                MPI_Op op, MPI_Comm comm, MPI_Request * request)
 .fi
 
 .SH INPUT PARAMETERS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Igather.3 b/linx64/mpi/mpich/share/man/man3/MPI_Igather.3
index 59a890c5..0de15084 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Igather.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Igather.3
@@ -1,11 +1,11 @@
-.TH MPI_Igather 3 "11/10/2017" " " "MPI"
+.TH MPI_Igather 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Igather \-  Gathers together values from a group of processes in a nonblocking way 
 .SH SYNOPSIS
 .nf
 int MPI_Igather(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
                 void *recvbuf, int recvcount, MPI_Datatype recvtype,
-                int root, MPI_Comm comm, MPI_Request *request)
+                int root, MPI_Comm comm, MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
@@ -26,7 +26,7 @@ int MPI_Igather(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
 .PD 0
 .TP
 .B recvcount 
-- number of elements in receive buffer (significant only at root) (non-negative integer)
+- number of elements for any single receive (non-negative integer, significant only at root)
 .PD 1
 .PD 0
 .TP
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Igatherv.3 b/linx64/mpi/mpich/share/man/man3/MPI_Igatherv.3
index 940896fc..2c88f698 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Igatherv.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Igatherv.3
@@ -1,11 +1,11 @@
-.TH MPI_Igatherv 3 "11/10/2017" " " "MPI"
+.TH MPI_Igatherv 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Igatherv \-  Gathers into specified locations from all processes in a group in a nonblocking way 
 .SH SYNOPSIS
 .nf
 int MPI_Igatherv(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
                  const int recvcounts[], const int displs[], MPI_Datatype recvtype, int root,
-                 MPI_Comm comm, MPI_Request *request)
+                 MPI_Comm comm, MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Improbe.3 b/linx64/mpi/mpich/share/man/man3/MPI_Improbe.3
index b9099f87..fdebd807 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Improbe.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Improbe.3
@@ -1,9 +1,10 @@
-.TH MPI_Improbe 3 "11/10/2017" " " "MPI"
+.TH MPI_Improbe 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Improbe \-  Nonblocking matched probe. 
 .SH SYNOPSIS
 .nf
-int MPI_Improbe(int source, int tag, MPI_Comm comm, int *flag, MPI_Message *message, MPI_Status *status)
+int MPI_Improbe(int source, int tag, MPI_Comm comm, int *flag, MPI_Message * message,
+                MPI_Status * status)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Imrecv.3 b/linx64/mpi/mpich/share/man/man3/MPI_Imrecv.3
index cf6d1110..297c47aa 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Imrecv.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Imrecv.3
@@ -1,9 +1,10 @@
-.TH MPI_Imrecv 3 "11/10/2017" " " "MPI"
+.TH MPI_Imrecv 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Imrecv \-  Nonblocking receive of message matched by MPI_Mprobe or MPI_Improbe. 
 .SH SYNOPSIS
 .nf
-int MPI_Imrecv(void *buf, int count, MPI_Datatype datatype, MPI_Message *message, MPI_Request *request)
+int MPI_Imrecv(void *buf, int count, MPI_Datatype datatype, MPI_Message * message,
+               MPI_Request * request)
 .fi
 .SH INPUT/OUTPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Ineighbor_allgather.3 b/linx64/mpi/mpich/share/man/man3/MPI_Ineighbor_allgather.3
index 668febfc..753f2292 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Ineighbor_allgather.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Ineighbor_allgather.3
@@ -1,9 +1,11 @@
-.TH MPI_Ineighbor_allgather 3 "11/10/2017" " " "MPI"
+.TH MPI_Ineighbor_allgather 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Ineighbor_allgather \-  Nonblocking version of MPI_Neighbor_allgather. 
 .SH SYNOPSIS
 .nf
-int MPI_Ineighbor_allgather(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf, int recvcount, MPI_Datatype recvtype, MPI_Comm comm, MPI_Request *request)
+int MPI_Ineighbor_allgather(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
+                            void *recvbuf, int recvcount, MPI_Datatype recvtype, MPI_Comm comm,
+                            MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Ineighbor_allgatherv.3 b/linx64/mpi/mpich/share/man/man3/MPI_Ineighbor_allgatherv.3
index de82e529..83fc0306 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Ineighbor_allgatherv.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Ineighbor_allgatherv.3
@@ -1,9 +1,11 @@
-.TH MPI_Ineighbor_allgatherv 3 "11/10/2017" " " "MPI"
+.TH MPI_Ineighbor_allgatherv 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Ineighbor_allgatherv \-  Nonblocking version of MPI_Neighbor_allgatherv. 
 .SH SYNOPSIS
 .nf
-int MPI_Ineighbor_allgatherv(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf, const int recvcounts[], const int displs[], MPI_Datatype recvtype, MPI_Comm comm, MPI_Request *request)
+int MPI_Ineighbor_allgatherv(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
+                             void *recvbuf, const int recvcounts[], const int displs[],
+                             MPI_Datatype recvtype, MPI_Comm comm, MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Ineighbor_alltoall.3 b/linx64/mpi/mpich/share/man/man3/MPI_Ineighbor_alltoall.3
index 6142daea..a9bd1ccd 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Ineighbor_alltoall.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Ineighbor_alltoall.3
@@ -1,9 +1,11 @@
-.TH MPI_Ineighbor_alltoall 3 "11/10/2017" " " "MPI"
+.TH MPI_Ineighbor_alltoall 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Ineighbor_alltoall \-  Nonblocking version of MPI_Neighbor_alltoall. 
 .SH SYNOPSIS
 .nf
-int MPI_Ineighbor_alltoall(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf, int recvcount, MPI_Datatype recvtype, MPI_Comm comm, MPI_Request *request)
+int MPI_Ineighbor_alltoall(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
+                           int recvcount, MPI_Datatype recvtype, MPI_Comm comm,
+                           MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Ineighbor_alltoallv.3 b/linx64/mpi/mpich/share/man/man3/MPI_Ineighbor_alltoallv.3
index be179c66..76322194 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Ineighbor_alltoallv.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Ineighbor_alltoallv.3
@@ -1,9 +1,12 @@
-.TH MPI_Ineighbor_alltoallv 3 "11/10/2017" " " "MPI"
+.TH MPI_Ineighbor_alltoallv 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Ineighbor_alltoallv \-  Nonblocking version of MPI_Neighbor_alltoallv. 
 .SH SYNOPSIS
 .nf
-int MPI_Ineighbor_alltoallv(const void *sendbuf, const int sendcounts[], const int sdispls[], MPI_Datatype sendtype, void *recvbuf, const int recvcounts[], const int rdispls[], MPI_Datatype recvtype, MPI_Comm comm, MPI_Request *request)
+int MPI_Ineighbor_alltoallv(const void *sendbuf, const int sendcounts[], const int sdispls[],
+                            MPI_Datatype sendtype, void *recvbuf, const int recvcounts[],
+                            const int rdispls[], MPI_Datatype recvtype, MPI_Comm comm,
+                            MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Ineighbor_alltoallw.3 b/linx64/mpi/mpich/share/man/man3/MPI_Ineighbor_alltoallw.3
index cfd65344..f082276b 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Ineighbor_alltoallw.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Ineighbor_alltoallw.3
@@ -1,9 +1,12 @@
-.TH MPI_Ineighbor_alltoallw 3 "11/10/2017" " " "MPI"
+.TH MPI_Ineighbor_alltoallw 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Ineighbor_alltoallw \-  Nonblocking version of MPI_Neighbor_alltoallw. 
 .SH SYNOPSIS
 .nf
-int MPI_Ineighbor_alltoallw(const void *sendbuf, const int sendcounts[], const MPI_Aint sdispls[], const MPI_Datatype sendtypes[], void *recvbuf, const int recvcounts[], const MPI_Aint rdispls[], const MPI_Datatype recvtypes[], MPI_Comm comm, MPI_Request *request)
+int MPI_Ineighbor_alltoallw(const void *sendbuf, const int sendcounts[], const MPI_Aint sdispls[],
+                            const MPI_Datatype sendtypes[], void *recvbuf, const int recvcounts[],
+                            const MPI_Aint rdispls[], const MPI_Datatype recvtypes[], MPI_Comm comm,
+                            MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Info_create.3 b/linx64/mpi/mpich/share/man/man3/MPI_Info_create.3
index a9ba4e9e..8da139d6 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Info_create.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Info_create.3
@@ -1,9 +1,9 @@
-.TH MPI_Info_create 3 "11/10/2017" " " "MPI"
+.TH MPI_Info_create 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Info_create \-  Creates a new info object 
 .SH SYNOPSIS
 .nf
-int MPI_Info_create( MPI_Info *info )
+int MPI_Info_create(MPI_Info * info)
 .fi
 .SH OUTPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Info_delete.3 b/linx64/mpi/mpich/share/man/man3/MPI_Info_delete.3
index 65ee333c..da5e684c 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Info_delete.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Info_delete.3
@@ -1,9 +1,9 @@
-.TH MPI_Info_delete 3 "11/10/2017" " " "MPI"
+.TH MPI_Info_delete 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Info_delete \-  Deletes a (key,value) pair from info 
 .SH SYNOPSIS
 .nf
-int MPI_Info_delete( MPI_Info info, const char *key )
+int MPI_Info_delete(MPI_Info info, const char *key)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Info_dup.3 b/linx64/mpi/mpich/share/man/man3/MPI_Info_dup.3
index 97dc6ed6..c3d0cc42 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Info_dup.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Info_dup.3
@@ -1,9 +1,9 @@
-.TH MPI_Info_dup 3 "11/10/2017" " " "MPI"
+.TH MPI_Info_dup 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Info_dup \-  Returns a duplicate of the info object 
 .SH SYNOPSIS
 .nf
-int MPI_Info_dup( MPI_Info info, MPI_Info *newinfo )
+int MPI_Info_dup(MPI_Info info, MPI_Info * newinfo)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Info_free.3 b/linx64/mpi/mpich/share/man/man3/MPI_Info_free.3
index ce6f5ec3..383d4914 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Info_free.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Info_free.3
@@ -1,9 +1,9 @@
-.TH MPI_Info_free 3 "11/10/2017" " " "MPI"
+.TH MPI_Info_free 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Info_free \-  Frees an info object 
 .SH SYNOPSIS
 .nf
-int MPI_Info_free( MPI_Info *info )
+int MPI_Info_free(MPI_Info * info)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Info_get.3 b/linx64/mpi/mpich/share/man/man3/MPI_Info_get.3
index 85c220ee..5a2baea1 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Info_get.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Info_get.3
@@ -1,4 +1,4 @@
-.TH MPI_Info_get 3 "11/10/2017" " " "MPI"
+.TH MPI_Info_get 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Info_get \-  Retrieves the value associated with a key 
 .SH SYNOPSIS
@@ -7,8 +7,7 @@ MPI_Info_get \-  Retrieves the value associated with a key
 #define FUNCNAME MPI_Info_get
 #undef FCNAME
 #define FCNAME MPL_QUOTE(FUNCNAME)
-int MPI_Info_get(MPI_Info info, const char *key, int valuelen, char *value,
-                int *flag)
+int MPI_Info_get(MPI_Info info, const char *key, int valuelen, char *value, int *flag)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Info_get_nkeys.3 b/linx64/mpi/mpich/share/man/man3/MPI_Info_get_nkeys.3
index 3156c1d6..eec78fa8 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Info_get_nkeys.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Info_get_nkeys.3
@@ -1,4 +1,4 @@
-.TH MPI_Info_get_nkeys 3 "11/10/2017" " " "MPI"
+.TH MPI_Info_get_nkeys 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Info_get_nkeys \-  Returns the number of currently defined keys in info 
 .SH SYNOPSIS
@@ -7,7 +7,7 @@ MPI_Info_get_nkeys \-  Returns the number of currently defined keys in info
 #define FUNCNAME MPI_Info_get_nkeys
 #undef FCNAME
 #define FCNAME MPL_QUOTE(FUNCNAME)
-int MPI_Info_get_nkeys( MPI_Info info, int *nkeys )
+int MPI_Info_get_nkeys(MPI_Info info, int *nkeys)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Info_get_nthkey.3 b/linx64/mpi/mpich/share/man/man3/MPI_Info_get_nthkey.3
index b678adda..3da13f26 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Info_get_nthkey.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Info_get_nthkey.3
@@ -1,4 +1,4 @@
-.TH MPI_Info_get_nthkey 3 "11/10/2017" " " "MPI"
+.TH MPI_Info_get_nthkey 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Info_get_nthkey \-  Returns the nth defined key in info 
 .SH SYNOPSIS
@@ -7,7 +7,7 @@ MPI_Info_get_nthkey \-  Returns the nth defined key in info
 #define FUNCNAME MPI_Info_get_nthkey
 #undef FCNAME
 #define FCNAME MPL_QUOTE(FUNCNAME)
-int MPI_Info_get_nthkey( MPI_Info info, int n, char *key )
+int MPI_Info_get_nthkey(MPI_Info info, int n, char *key)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Info_get_valuelen.3 b/linx64/mpi/mpich/share/man/man3/MPI_Info_get_valuelen.3
index ef38830f..89bbf6a8 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Info_get_valuelen.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Info_get_valuelen.3
@@ -1,13 +1,13 @@
-.TH MPI_Info_get_valuelen 3 "11/10/2017" " " "MPI"
+.TH MPI_Info_get_valuelen 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Info_get_valuelen \-  Retrieves the length of the value associated with  a key 
+MPI_Info_get_valuelen \-  Retrieves the length of the value associated with a key 
 .SH SYNOPSIS
 .nf
 #undef FUNCNAME
 #define FUNCNAME MPIRInfo_get_valuelen
 #undef FCNAME
 #define FCNAME MPL_QUOTE(FUNCNAME)
-int MPI_Info_get_valuelen( MPI_Info info, const char *key, int *valuelen, int *flag )
+int MPI_Info_get_valuelen(MPI_Info info, const char *key, int *valuelen, int *flag)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Info_set.3 b/linx64/mpi/mpich/share/man/man3/MPI_Info_set.3
index e7484ec5..0f1cf327 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Info_set.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Info_set.3
@@ -1,9 +1,9 @@
-.TH MPI_Info_set 3 "11/10/2017" " " "MPI"
+.TH MPI_Info_set 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Info_set \-  Adds a (key,value) pair to info 
 .SH SYNOPSIS
 .nf
-int MPI_Info_set( MPI_Info info, const char *key, const char *value )
+int MPI_Info_set(MPI_Info info, const char *key, const char *value)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Init.3 b/linx64/mpi/mpich/share/man/man3/MPI_Init.3
index 7c7874a9..c345c587 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Init.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Init.3
@@ -1,15 +1,15 @@
-.TH MPI_Init 3 "11/10/2017" " " "MPI"
+.TH MPI_Init 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Init \-  Initialize the MPI execution environment 
 .SH SYNOPSIS
 .nf
-int MPI_Init( int *argc, char ***argv )
+int MPI_Init(int *argc, char ***argv)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B argc 
-- Pointer to the number of arguments 
+- Pointer to the number of arguments
 .PD 1
 .PD 0
 .TP
@@ -52,7 +52,7 @@ The Fortran binding for
 .I MPI_Init
 has only the error return
 .nf
-subroutine MPI_INIT( ierr )
+subroutine MPI_INIT(ierr)
 integer ierr
 .fi
 
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Init_thread.3 b/linx64/mpi/mpich/share/man/man3/MPI_Init_thread.3
index ff29175d..99e4a0a5 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Init_thread.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Init_thread.3
@@ -1,15 +1,15 @@
-.TH MPI_Init_thread 3 "11/10/2017" " " "MPI"
+.TH MPI_Init_thread 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Init_thread \-  Initialize the MPI execution environment 
 .SH SYNOPSIS
 .nf
-int MPI_Init_thread( int *argc, char ***argv, int required, int *provided )
+int MPI_Init_thread(int *argc, char ***argv, int required, int *provided)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B argc 
-- Pointer to the number of arguments 
+- Pointer to the number of arguments
 .PD 1
 .PD 0
 .TP
@@ -46,26 +46,26 @@ The valid values for the level of thread support are:
 .PD 0
 .TP
 .B MPI_THREAD_SINGLE 
-- Only one thread will execute. 
+- Only one thread will execute.
 .PD 1
 .PD 0
 .TP
 .B MPI_THREAD_FUNNELED 
-- The process may be multi-threaded, but only the main 
-thread will make MPI calls (all MPI calls are funneled to the 
-main thread). 
+- The process may be multi-threaded, but only the main
+thread will make MPI calls (all MPI calls are funneled to the
+main thread).
 .PD 1
 .PD 0
 .TP
 .B MPI_THREAD_SERIALIZED 
-- The process may be multi-threaded, and multiple 
-threads may make MPI calls, but only one at a time: MPI calls are not 
-made concurrently from two distinct threads (all MPI calls are serialized). 
+- The process may be multi-threaded, and multiple
+threads may make MPI calls, but only one at a time: MPI calls are not
+made concurrently from two distinct threads (all MPI calls are serialized).
 .PD 1
 .PD 0
 .TP
 .B MPI_THREAD_MULTIPLE 
-- Multiple threads may call MPI, with no restrictions. 
+- Multiple threads may call MPI, with no restrictions.
 .PD 1
 
 .SH NOTES FOR FORTRAN
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Initialized.3 b/linx64/mpi/mpich/share/man/man3/MPI_Initialized.3
index 085c152e..4b5bb2bd 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Initialized.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Initialized.3
@@ -1,11 +1,11 @@
-.TH MPI_Initialized 3 "11/10/2017" " " "MPI"
+.TH MPI_Initialized 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Initialized \-  Indicates whether 
 .I MPI_Init
 has been called. 
 .SH SYNOPSIS
 .nf
-int MPI_Initialized( int *flag )
+int MPI_Initialized(int *flag)
 .fi
 .SH OUTPUT PARAMETERS
 .PD 0
@@ -15,8 +15,8 @@ int MPI_Initialized( int *flag )
 .I MPI_Init
 or 
 .I MPI_Init_thread
-has been called and 
-false otherwise.  
+has been called and
+false otherwise.
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Intercomm_create.3 b/linx64/mpi/mpich/share/man/man3/MPI_Intercomm_create.3
index e3321cc4..f3f11bfc 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Intercomm_create.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Intercomm_create.3
@@ -1,11 +1,10 @@
-.TH MPI_Intercomm_create 3 "11/10/2017" " " "MPI"
+.TH MPI_Intercomm_create 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Intercomm_create \-  Creates an intercommuncator from two intracommunicators 
 .SH SYNOPSIS
 .nf
-int MPI_Intercomm_create(MPI_Comm local_comm, int local_leader, 
-                       MPI_Comm peer_comm, int remote_leader, int tag, 
-                       MPI_Comm *newintercomm)
+int MPI_Intercomm_create(MPI_Comm local_comm, int local_leader,
+                         MPI_Comm peer_comm, int remote_leader, int tag, MPI_Comm * newintercomm)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
@@ -21,8 +20,8 @@ int MPI_Intercomm_create(MPI_Comm local_comm, int local_leader,
 .PD 0
 .TP
 .B peer_comm 
-- Communicator used to communicate between a 
-designated process in the other communicator.  
+- Communicator used to communicate between a
+designated process in the other communicator.
 Significant only at the process in 
 .I local_comm
 with
@@ -198,7 +197,7 @@ zero and the size of the communicator minus one; ranks in a receive
 .PD 1
 
 .SH SEE ALSO
-MPI_Intercomm_merge, MPI_Comm_free, MPI_Comm_remote_group, 
+MPI_Intercomm_merge, MPI_Comm_free, MPI_Comm_remote_group,
 .br
 MPI_Comm_remote_size
 
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Intercomm_merge.3 b/linx64/mpi/mpich/share/man/man3/MPI_Intercomm_merge.3
index ce61a843..f66f0d90 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Intercomm_merge.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Intercomm_merge.3
@@ -1,9 +1,9 @@
-.TH MPI_Intercomm_merge 3 "11/10/2017" " " "MPI"
+.TH MPI_Intercomm_merge 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Intercomm_merge \-  Creates an intracommuncator from an intercommunicator 
 .SH SYNOPSIS
 .nf
-int MPI_Intercomm_merge(MPI_Comm intercomm, int high, MPI_Comm *newintracomm)
+int MPI_Intercomm_merge(MPI_Comm intercomm, int high, MPI_Comm * newintracomm)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
@@ -18,7 +18,7 @@ int MPI_Intercomm_merge(MPI_Comm intercomm, int high, MPI_Comm *newintracomm)
 when creating the new communicator.  This is a boolean value; the group
 that sets high true has its processes ordered 
 .B after
-the group that sets 
+the group that sets
 this value to false.  If all processes in the intercommunicator provide
 the same value, the choice of which group is ordered first is arbitrary.
 .PD 1
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Iprobe.3 b/linx64/mpi/mpich/share/man/man3/MPI_Iprobe.3
index 6a8e994d..7b5415a5 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Iprobe.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Iprobe.3
@@ -1,10 +1,9 @@
-.TH MPI_Iprobe 3 "11/10/2017" " " "MPI"
+.TH MPI_Iprobe 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Iprobe \-  Nonblocking test for a message 
 .SH SYNOPSIS
 .nf
-int MPI_Iprobe(int source, int tag, MPI_Comm comm, int *flag, 
-               MPI_Status *status)
+int MPI_Iprobe(int source, int tag, MPI_Comm comm, int *flag, MPI_Status * status)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
@@ -12,32 +11,32 @@ int MPI_Iprobe(int source, int tag, MPI_Comm comm, int *flag,
 .B source 
 - source rank, or  
 .I MPI_ANY_SOURCE
-(integer) 
+(integer)
 .PD 1
 .PD 0
 .TP
 .B tag 
 - tag value or  
 .I MPI_ANY_TAG
-(integer) 
+(integer)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B flag 
-- True if a message with the specified source, tag, and communicator 
-is available (logical) 
+- True if a message with the specified source, tag, and communicator
+is available (logical)
 .PD 1
 .PD 0
 .TP
 .B status 
-- status object (Status) 
+- status object (Status)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Irecv.3 b/linx64/mpi/mpich/share/man/man3/MPI_Irecv.3
index 026dcf46..6667855c 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Irecv.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Irecv.3
@@ -1,48 +1,48 @@
-.TH MPI_Irecv 3 "11/10/2017" " " "MPI"
+.TH MPI_Irecv 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Irecv \-  Begins a nonblocking receive 
 .SH SYNOPSIS
 .nf
 int MPI_Irecv(void *buf, int count, MPI_Datatype datatype, int source,
-              int tag, MPI_Comm comm, MPI_Request *request)
+              int tag, MPI_Comm comm, MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B buf 
-- initial address of receive buffer (choice) 
+- initial address of receive buffer (choice)
 .PD 1
 .PD 0
 .TP
 .B count 
-- number of elements in receive buffer (integer) 
+- number of elements in receive buffer (integer)
 .PD 1
 .PD 0
 .TP
 .B datatype 
-- datatype of each receive buffer element (handle) 
+- datatype of each receive buffer element (handle)
 .PD 1
 .PD 0
 .TP
 .B source 
-- rank of source (integer) 
+- rank of source (integer)
 .PD 1
 .PD 0
 .TP
 .B tag 
-- message tag (integer) 
+- message tag (integer)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B request 
-- communication request (handle) 
+- communication request (handle)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Ireduce.3 b/linx64/mpi/mpich/share/man/man3/MPI_Ireduce.3
index f322a715..9a7550a4 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Ireduce.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Ireduce.3
@@ -1,10 +1,10 @@
-.TH MPI_Ireduce 3 "11/10/2017" " " "MPI"
+.TH MPI_Ireduce 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Ireduce \-  Reduces values on all processes to a single value in a nonblocking way 
 .SH SYNOPSIS
 .nf
 int MPI_Ireduce(const void *sendbuf, void *recvbuf, int count, MPI_Datatype datatype,
-                MPI_Op op, int root, MPI_Comm comm, MPI_Request *request)
+                MPI_Op op, int root, MPI_Comm comm, MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Ireduce_scatter.3 b/linx64/mpi/mpich/share/man/man3/MPI_Ireduce_scatter.3
index 9d266f58..ad7bdff0 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Ireduce_scatter.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Ireduce_scatter.3
@@ -1,10 +1,10 @@
-.TH MPI_Ireduce_scatter 3 "11/10/2017" " " "MPI"
+.TH MPI_Ireduce_scatter 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Ireduce_scatter \-  Combines values and scatters the results in a nonblocking way 
 .SH SYNOPSIS
 .nf
 int MPI_Ireduce_scatter(const void *sendbuf, void *recvbuf, const int recvcounts[],
-                        MPI_Datatype datatype, MPI_Op op, MPI_Comm comm, MPI_Request *request)
+                        MPI_Datatype datatype, MPI_Op op, MPI_Comm comm, MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Ireduce_scatter_block.3 b/linx64/mpi/mpich/share/man/man3/MPI_Ireduce_scatter_block.3
index 2dd018f7..27a66c32 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Ireduce_scatter_block.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Ireduce_scatter_block.3
@@ -1,4 +1,4 @@
-.TH MPI_Ireduce_scatter_block 3 "11/10/2017" " " "MPI"
+.TH MPI_Ireduce_scatter_block 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Ireduce_scatter_block \-  Combines values and scatters the results in a nonblocking way 
 .SH SYNOPSIS
@@ -6,7 +6,7 @@ MPI_Ireduce_scatter_block \-  Combines values and scatters the results in a nonb
 int MPI_Ireduce_scatter_block(const void *sendbuf, void *recvbuf,
                               int recvcount,
                               MPI_Datatype datatype, MPI_Op op, MPI_Comm comm,
-                              MPI_Request *request)
+                              MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Irsend.3 b/linx64/mpi/mpich/share/man/man3/MPI_Irsend.3
index 919ee704..f9d5578d 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Irsend.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Irsend.3
@@ -1,48 +1,48 @@
-.TH MPI_Irsend 3 "11/10/2017" " " "MPI"
+.TH MPI_Irsend 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Irsend \-  Starts a nonblocking ready send 
 .SH SYNOPSIS
 .nf
 int MPI_Irsend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-               MPI_Comm comm, MPI_Request *request)
+               MPI_Comm comm, MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B buf 
-- initial address of send buffer (choice) 
+- initial address of send buffer (choice)
 .PD 1
 .PD 0
 .TP
 .B count 
-- number of elements in send buffer (integer) 
+- number of elements in send buffer (integer)
 .PD 1
 .PD 0
 .TP
 .B datatype 
-- datatype of each send buffer element (handle) 
+- datatype of each send buffer element (handle)
 .PD 1
 .PD 0
 .TP
 .B dest 
-- rank of destination (integer) 
+- rank of destination (integer)
 .PD 1
 .PD 0
 .TP
 .B tag 
-- message tag (integer) 
+- message tag (integer)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B request 
-- communication request (handle) 
+- communication request (handle)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Is_thread_main.3 b/linx64/mpi/mpich/share/man/man3/MPI_Is_thread_main.3
index 4f634e94..4cf30d5f 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Is_thread_main.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Is_thread_main.3
@@ -1,12 +1,12 @@
-.TH MPI_Is_thread_main 3 "11/10/2017" " " "MPI"
+.TH MPI_Is_thread_main 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Is_thread_main \-  Returns a flag indicating whether this thread called  
+MPI_Is_thread_main \-  Returns a flag indicating whether this thread called 
 .I MPI_Init
 or 
 .I MPI_Init_thread
 .SH SYNOPSIS
 .nf
-int MPI_Is_thread_main( int *flag )
+int MPI_Is_thread_main(int *flag)
 .fi
 .SH OUTPUT PARAMETERS
 .PD 0
@@ -16,7 +16,7 @@ int MPI_Is_thread_main( int *flag )
 .I MPI_Init
 or 
 .I MPI_Init_thread
-has been called by 
+has been called by
 this thread and false otherwise.  (logical)
 .PD 1
 
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Iscan.3 b/linx64/mpi/mpich/share/man/man3/MPI_Iscan.3
index 253a0d4d..165b24ad 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Iscan.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Iscan.3
@@ -1,10 +1,10 @@
-.TH MPI_Iscan 3 "11/10/2017" " " "MPI"
+.TH MPI_Iscan 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Iscan \-  Computes the scan (partial reductions) of data on a collection of processes in a nonblocking way 
 .SH SYNOPSIS
 .nf
 int MPI_Iscan(const void *sendbuf, void *recvbuf, int count, MPI_Datatype datatype,
-              MPI_Op op, MPI_Comm comm, MPI_Request *request)
+              MPI_Op op, MPI_Comm comm, MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Iscatter.3 b/linx64/mpi/mpich/share/man/man3/MPI_Iscatter.3
index 50cbf264..898a6d30 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Iscatter.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Iscatter.3
@@ -1,11 +1,11 @@
-.TH MPI_Iscatter 3 "11/10/2017" " " "MPI"
+.TH MPI_Iscatter 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Iscatter \-  Sends data from one process to all other processes in a communicator in a nonblocking way 
 .SH SYNOPSIS
 .nf
 int MPI_Iscatter(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
                  void *recvbuf, int recvcount, MPI_Datatype recvtype, int root,
-                 MPI_Comm comm, MPI_Request *request)
+                 MPI_Comm comm, MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Iscatterv.3 b/linx64/mpi/mpich/share/man/man3/MPI_Iscatterv.3
index 2a53a07c..b9907223 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Iscatterv.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Iscatterv.3
@@ -1,11 +1,11 @@
-.TH MPI_Iscatterv 3 "11/10/2017" " " "MPI"
+.TH MPI_Iscatterv 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Iscatterv \-  Scatters a buffer in parts to all processes in a communicator in a nonblocking way 
 .SH SYNOPSIS
 .nf
 int MPI_Iscatterv(const void *sendbuf, const int sendcounts[], const int displs[],
                   MPI_Datatype sendtype, void *recvbuf, int recvcount, MPI_Datatype recvtype,
-                  int root, MPI_Comm comm, MPI_Request *request)
+                  int root, MPI_Comm comm, MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Isend.3 b/linx64/mpi/mpich/share/man/man3/MPI_Isend.3
index 1b32a374..1e536c36 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Isend.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Isend.3
@@ -1,48 +1,48 @@
-.TH MPI_Isend 3 "11/10/2017" " " "MPI"
+.TH MPI_Isend 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Isend \-  Begins a nonblocking send 
 .SH SYNOPSIS
 .nf
 int MPI_Isend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-              MPI_Comm comm, MPI_Request *request)
+              MPI_Comm comm, MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B buf 
-- initial address of send buffer (choice) 
+- initial address of send buffer (choice)
 .PD 1
 .PD 0
 .TP
 .B count 
-- number of elements in send buffer (integer) 
+- number of elements in send buffer (integer)
 .PD 1
 .PD 0
 .TP
 .B datatype 
-- datatype of each send buffer element (handle) 
+- datatype of each send buffer element (handle)
 .PD 1
 .PD 0
 .TP
 .B dest 
-- rank of destination (integer) 
+- rank of destination (integer)
 .PD 1
 .PD 0
 .TP
 .B tag 
-- message tag (integer) 
+- message tag (integer)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B request 
-- communication request (handle) 
+- communication request (handle)
 .PD 1
 
 .SH NOTES FOR FORTRAN
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Issend.3 b/linx64/mpi/mpich/share/man/man3/MPI_Issend.3
index 9c0d251b..1fb46c04 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Issend.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Issend.3
@@ -1,48 +1,48 @@
-.TH MPI_Issend 3 "11/10/2017" " " "MPI"
+.TH MPI_Issend 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Issend \-  Starts a nonblocking synchronous send 
 .SH SYNOPSIS
 .nf
 int MPI_Issend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-               MPI_Comm comm, MPI_Request *request)
+               MPI_Comm comm, MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B buf 
-- initial address of send buffer (choice) 
+- initial address of send buffer (choice)
 .PD 1
 .PD 0
 .TP
 .B count 
-- number of elements in send buffer (integer) 
+- number of elements in send buffer (integer)
 .PD 1
 .PD 0
 .TP
 .B datatype 
-- datatype of each send buffer element (handle) 
+- datatype of each send buffer element (handle)
 .PD 1
 .PD 0
 .TP
 .B dest 
-- rank of destination (integer) 
+- rank of destination (integer)
 .PD 1
 .PD 0
 .TP
 .B tag 
-- message tag (integer) 
+- message tag (integer)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B request 
-- communication request (handle) 
+- communication request (handle)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Keyval_create.3 b/linx64/mpi/mpich/share/man/man3/MPI_Keyval_create.3
index e021c236..2dfb1efe 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Keyval_create.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Keyval_create.3
@@ -1,11 +1,10 @@
-.TH MPI_Keyval_create 3 "11/10/2017" " " "MPI"
+.TH MPI_Keyval_create 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Keyval_create \-  Greates a new attribute key 
 .SH SYNOPSIS
 .nf
-int MPI_Keyval_create(MPI_Copy_function *copy_fn, 
-                     MPI_Delete_function *delete_fn, 
-                     int *keyval, void *extra_state)
+int MPI_Keyval_create(MPI_Copy_function * copy_fn,
+                      MPI_Delete_function * delete_fn, int *keyval, void *extra_state)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
@@ -25,14 +24,14 @@ int MPI_Keyval_create(MPI_Copy_function *copy_fn,
 .PD 0
 .TP
 .B extra_state 
-- Extra state for callback functions 
+- Extra state for callback functions
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B keyval 
-- key value for future access (integer) 
+- key value for future access (integer)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Keyval_free.3 b/linx64/mpi/mpich/share/man/man3/MPI_Keyval_free.3
index ed8a5a6f..7dbb8064 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Keyval_free.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Keyval_free.3
@@ -1,4 +1,4 @@
-.TH MPI_Keyval_free 3 "11/10/2017" " " "MPI"
+.TH MPI_Keyval_free 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Keyval_free \-  Frees an attribute key for communicators 
 .SH SYNOPSIS
@@ -9,7 +9,7 @@ int MPI_Keyval_free(int *keyval)
 .PD 0
 .TP
 .B keyval 
-- Frees the integer key value (integer) 
+- Frees the integer key value (integer)
 .PD 1
 
 .SH NOTE
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Lookup_name.3 b/linx64/mpi/mpich/share/man/man3/MPI_Lookup_name.3
index 49b1ff2a..cd6585e1 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Lookup_name.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Lookup_name.3
@@ -1,4 +1,4 @@
-.TH MPI_Lookup_name 3 "11/10/2017" " " "MPI"
+.TH MPI_Lookup_name 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Lookup_name \-  Lookup a port given a service name 
 .SH SYNOPSIS
@@ -9,12 +9,12 @@ int MPI_Lookup_name(const char *service_name, MPI_Info info, char *port_name)
 .PD 0
 .TP
 .B service_name 
-- a service name (string) 
+- a service name (string)
 .PD 1
 .PD 0
 .TP
 .B info 
-- implementation-specific information (handle) 
+- implementation-specific information (handle)
 .PD 1
 
 
@@ -22,7 +22,7 @@ int MPI_Lookup_name(const char *service_name, MPI_Info info, char *port_name)
 .PD 0
 .TP
 .B port_name 
-- a port name (string) 
+- a port name (string)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Mprobe.3 b/linx64/mpi/mpich/share/man/man3/MPI_Mprobe.3
index 5e9b6b1f..64bf61f8 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Mprobe.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Mprobe.3
@@ -1,9 +1,9 @@
-.TH MPI_Mprobe 3 "11/10/2017" " " "MPI"
+.TH MPI_Mprobe 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Mprobe \-  Blocking matched probe. 
 .SH SYNOPSIS
 .nf
-int MPI_Mprobe(int source, int tag, MPI_Comm comm, MPI_Message *message, MPI_Status *status)
+int MPI_Mprobe(int source, int tag, MPI_Comm comm, MPI_Message * message, MPI_Status * status)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Mrecv.3 b/linx64/mpi/mpich/share/man/man3/MPI_Mrecv.3
index 57a63ace..03aa2e2a 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Mrecv.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Mrecv.3
@@ -1,9 +1,10 @@
-.TH MPI_Mrecv 3 "11/10/2017" " " "MPI"
+.TH MPI_Mrecv 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Mrecv \-  Blocking receive of message matched by MPI_Mprobe or MPI_Improbe. 
 .SH SYNOPSIS
 .nf
-int MPI_Mrecv(void *buf, int count, MPI_Datatype datatype, MPI_Message *message, MPI_Status *status)
+int MPI_Mrecv(void *buf, int count, MPI_Datatype datatype, MPI_Message * message,
+              MPI_Status * status)
 .fi
 .SH INPUT/OUTPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Neighbor_allgather.3 b/linx64/mpi/mpich/share/man/man3/MPI_Neighbor_allgather.3
index 2773d782..b9d67f3b 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Neighbor_allgather.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Neighbor_allgather.3
@@ -1,9 +1,10 @@
-.TH MPI_Neighbor_allgather 3 "11/10/2017" " " "MPI"
+.TH MPI_Neighbor_allgather 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Neighbor_allgather \-  In this function, each process i gathers data items from each process j if an edge (j,i) exists in the topology graph, and each process i sends the same data items to all processes j where an edge (i,j) exists. The send buffer is sent to each neighboring process and the l-th block in the receive buffer is received from the l-th neighbor. 
 .SH SYNOPSIS
 .nf
-int MPI_Neighbor_allgather(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf, int recvcount, MPI_Datatype recvtype, MPI_Comm comm)
+int MPI_Neighbor_allgather(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
+                           int recvcount, MPI_Datatype recvtype, MPI_Comm comm)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Neighbor_allgatherv.3 b/linx64/mpi/mpich/share/man/man3/MPI_Neighbor_allgatherv.3
index e2595f46..7185f7dd 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Neighbor_allgatherv.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Neighbor_allgatherv.3
@@ -1,9 +1,11 @@
-.TH MPI_Neighbor_allgatherv 3 "11/10/2017" " " "MPI"
+.TH MPI_Neighbor_allgatherv 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Neighbor_allgatherv \-  The vector variant of MPI_Neighbor_allgather. 
 .SH SYNOPSIS
 .nf
-int MPI_Neighbor_allgatherv(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf, const int recvcounts[], const int displs[], MPI_Datatype recvtype, MPI_Comm comm)
+int MPI_Neighbor_allgatherv(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
+                            void *recvbuf, const int recvcounts[], const int displs[],
+                            MPI_Datatype recvtype, MPI_Comm comm)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Neighbor_alltoall.3 b/linx64/mpi/mpich/share/man/man3/MPI_Neighbor_alltoall.3
index 0883581b..e7bf9ccb 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Neighbor_alltoall.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Neighbor_alltoall.3
@@ -1,9 +1,10 @@
-.TH MPI_Neighbor_alltoall 3 "11/10/2017" " " "MPI"
+.TH MPI_Neighbor_alltoall 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Neighbor_alltoall \-  In this function, each process i receives data items from each process j if an edge (j,i) exists in the topology graph or Cartesian topology.  Similarly, each process i sends data items to all processes j where an edge (i,j) exists. This call is more general than MPI_NEIGHBOR_ALLGATHER in that different data items can be sent to each neighbor. The k-th block in send buffer is sent to the k-th neighboring process and the l-th block in the receive buffer is received from the l-th neighbor. 
 .SH SYNOPSIS
 .nf
-int MPI_Neighbor_alltoall(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf, int recvcount, MPI_Datatype recvtype, MPI_Comm comm)
+int MPI_Neighbor_alltoall(const void *sendbuf, int sendcount, MPI_Datatype sendtype, void *recvbuf,
+                          int recvcount, MPI_Datatype recvtype, MPI_Comm comm)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Neighbor_alltoallv.3 b/linx64/mpi/mpich/share/man/man3/MPI_Neighbor_alltoallv.3
index be0d5468..5c9427fc 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Neighbor_alltoallv.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Neighbor_alltoallv.3
@@ -1,9 +1,11 @@
-.TH MPI_Neighbor_alltoallv 3 "11/10/2017" " " "MPI"
+.TH MPI_Neighbor_alltoallv 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Neighbor_alltoallv \-  The vector variant of MPI_Neighbor_alltoall allows sending/receiving different numbers of elements to and from each neighbor. 
 .SH SYNOPSIS
 .nf
-int MPI_Neighbor_alltoallv(const void *sendbuf, const int sendcounts[], const int sdispls[], MPI_Datatype sendtype, void *recvbuf, const int recvcounts[], const int rdispls[], MPI_Datatype recvtype, MPI_Comm comm)
+int MPI_Neighbor_alltoallv(const void *sendbuf, const int sendcounts[], const int sdispls[],
+                           MPI_Datatype sendtype, void *recvbuf, const int recvcounts[],
+                           const int rdispls[], MPI_Datatype recvtype, MPI_Comm comm)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Neighbor_alltoallw.3 b/linx64/mpi/mpich/share/man/man3/MPI_Neighbor_alltoallw.3
index 5f71beb5..a322b2f5 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Neighbor_alltoallw.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Neighbor_alltoallw.3
@@ -1,9 +1,11 @@
-.TH MPI_Neighbor_alltoallw 3 "11/10/2017" " " "MPI"
+.TH MPI_Neighbor_alltoallw 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Neighbor_alltoallw \-  Like MPI_Neighbor_alltoallv but it allows one to send and receive with different types to and from each neighbor. 
 .SH SYNOPSIS
 .nf
-int MPI_Neighbor_alltoallw(const void *sendbuf, const int sendcounts[], const MPI_Aint sdispls[], const MPI_Datatype sendtypes[], void *recvbuf, const int recvcounts[], const MPI_Aint rdispls[], const MPI_Datatype recvtypes[], MPI_Comm comm)
+int MPI_Neighbor_alltoallw(const void *sendbuf, const int sendcounts[], const MPI_Aint sdispls[],
+                           const MPI_Datatype sendtypes[], void *recvbuf, const int recvcounts[],
+                           const MPI_Aint rdispls[], const MPI_Datatype recvtypes[], MPI_Comm comm)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Op_commute.3 b/linx64/mpi/mpich/share/man/man3/MPI_Op_commute.3
index 2e1416bc..c5e589cd 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Op_commute.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Op_commute.3
@@ -1,4 +1,4 @@
-.TH MPI_Op_commute 3 "11/10/2017" " " "MPI"
+.TH MPI_Op_commute 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Op_commute \-  Queries an MPI reduction operation for its commutativity. 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Op_create.3 b/linx64/mpi/mpich/share/man/man3/MPI_Op_create.3
index 3e2fed63..1d11fefc 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Op_create.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Op_create.3
@@ -1,9 +1,9 @@
-.TH MPI_Op_create 3 "11/10/2017" " " "MPI"
+.TH MPI_Op_create 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Op_create \-  Creates a user-defined combination function handle 
 .SH SYNOPSIS
 .nf
-int MPI_Op_create(MPI_User_function *user_fn, int commute, MPI_Op *op)
+int MPI_Op_create(MPI_User_function * user_fn, int commute, MPI_Op * op)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
@@ -21,14 +21,14 @@ int MPI_Op_create(MPI_User_function *user_fn, int commute, MPI_Op *op)
 .PD 0
 .TP
 .B op 
-- operation (handle) 
+- operation (handle)
 .PD 1
 
 .SH NOTES ON THE USER FUNCTION
 The calling list for the user function type is
 .nf
-typedef void (MPI_User_function) ( void * a, 
-void * b, int * len, MPI_Datatype * ); 
+typedef void (MPI_User_function) (void * a,
+void * b, int * len, MPI_Datatype *);
 .fi
 
 where the operation is 
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Op_free.3 b/linx64/mpi/mpich/share/man/man3/MPI_Op_free.3
index 103ce46c..f74e9591 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Op_free.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Op_free.3
@@ -1,15 +1,15 @@
-.TH MPI_Op_free 3 "11/10/2017" " " "MPI"
+.TH MPI_Op_free 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Op_free \-  Frees a user-defined combination function handle 
 .SH SYNOPSIS
 .nf
-int MPI_Op_free(MPI_Op *op)
+int MPI_Op_free(MPI_Op * op)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B op 
-- operation (handle) 
+- operation (handle)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Open_port.3 b/linx64/mpi/mpich/share/man/man3/MPI_Open_port.3
index 89e27a07..93480aae 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Open_port.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Open_port.3
@@ -1,6 +1,6 @@
-.TH MPI_Open_port 3 "11/10/2017" " " "MPI"
+.TH MPI_Open_port 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Open_port \-  Establish an address that can be used to establish  connections between groups of MPI processes 
+MPI_Open_port \-  Establish an address that can be used to establish connections between groups of MPI processes 
 .SH SYNOPSIS
 .nf
 int MPI_Open_port(MPI_Info info, char *port_name)
@@ -9,17 +9,17 @@ int MPI_Open_port(MPI_Info info, char *port_name)
 .PD 0
 .TP
 .B info 
-- implementation-specific information on how to establish a 
+- implementation-specific information on how to establish a
 port for 
 .I MPI_Comm_accept
-(handle) 
+(handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B port_name 
-- newly established port (string) 
+- newly established port (string)
 .PD 1
 
 .SH NOTES
@@ -38,7 +38,7 @@ The maximum size string that may be supplied by the system is
 .PD 0
 .TP
 .B ip_port 
-- Value contains IP port number at which to establish a port. 
+- Value contains IP port number at which to establish a port.
 .PD 1
 .PD 0
 .TP
@@ -46,7 +46,7 @@ The maximum size string that may be supplied by the system is
 - Value contains IP address at which to establish a port.
 If the address is not a valid IP address of the host on which the
 .I MPI_OPEN_PORT
-call is made, the results are undefined. 
+call is made, the results are undefined.
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Pack.3 b/linx64/mpi/mpich/share/man/man3/MPI_Pack.3
index 34b7cccf..f92378bd 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Pack.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Pack.3
@@ -1,15 +1,11 @@
-.TH MPI_Pack 3 "11/10/2017" " " "MPI"
+.TH MPI_Pack 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Pack \-  Packs a datatype into contiguous memory 
 .SH SYNOPSIS
 .nf
 int MPI_Pack(const void *inbuf,
              int incount,
-             MPI_Datatype datatype,
-             void *outbuf,
-             int outsize,
-             int *position,
-             MPI_Comm comm)
+             MPI_Datatype datatype, void *outbuf, int outsize, int *position, MPI_Comm comm)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Pack_external.3 b/linx64/mpi/mpich/share/man/man3/MPI_Pack_external.3
index 488106cd..61e9e8ca 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Pack_external.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Pack_external.3
@@ -1,15 +1,12 @@
-.TH MPI_Pack_external 3 "11/10/2017" " " "MPI"
+.TH MPI_Pack_external 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Pack_external \-  Packs a datatype into contiguous memory, using the external32 format 
 .SH SYNOPSIS
 .nf
 int MPI_Pack_external(const char datarep[],
-                     const void *inbuf,
-                     int incount,
-                     MPI_Datatype datatype,
-                     void *outbuf,
-                     MPI_Aint outsize,
-                     MPI_Aint *position)
+                      const void *inbuf,
+                      int incount,
+                      MPI_Datatype datatype, void *outbuf, MPI_Aint outsize, MPI_Aint * position)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Pack_external_size.3 b/linx64/mpi/mpich/share/man/man3/MPI_Pack_external_size.3
index ad17c671..dbb3883d 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Pack_external_size.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Pack_external_size.3
@@ -1,12 +1,10 @@
-.TH MPI_Pack_external_size 3 "11/10/2017" " " "MPI"
+.TH MPI_Pack_external_size 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Pack_external_size \-  Returns the upper bound on the amount of space needed to pack a message using MPI_Pack_external. 
 .SH SYNOPSIS
 .nf
 int MPI_Pack_external_size(const char datarep[],
-                         int incount,
-                         MPI_Datatype datatype,
-                         MPI_Aint *size)
+                           int incount, MPI_Datatype datatype, MPI_Aint * size)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Pack_size.3 b/linx64/mpi/mpich/share/man/man3/MPI_Pack_size.3
index e5b15b34..1a4d4602 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Pack_size.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Pack_size.3
@@ -1,35 +1,32 @@
-.TH MPI_Pack_size 3 "11/10/2017" " " "MPI"
+.TH MPI_Pack_size 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Pack_size \-  Returns the upper bound on the amount of space needed to pack a message 
 .SH SYNOPSIS
 .nf
-int MPI_Pack_size(int incount,
-                 MPI_Datatype datatype,
-                 MPI_Comm comm,
-                 int *size)
+int MPI_Pack_size(int incount, MPI_Datatype datatype, MPI_Comm comm, int *size)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B incount 
-- count argument to packing call (integer) 
+- count argument to packing call (integer)
 .PD 1
 .PD 0
 .TP
 .B datatype 
-- datatype argument to packing call (handle) 
+- datatype argument to packing call (handle)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator argument to packing call (handle) 
+- communicator argument to packing call (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B size 
-- upper bound on size of packed message, in bytes (integer) 
+- upper bound on size of packed message, in bytes (integer)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Pcontrol.3 b/linx64/mpi/mpich/share/man/man3/MPI_Pcontrol.3
index 045908fe..fb6ca015 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Pcontrol.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Pcontrol.3
@@ -1,4 +1,4 @@
-.TH MPI_Pcontrol 3 "11/10/2017" " " "MPI"
+.TH MPI_Pcontrol 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Pcontrol \-  Controls profiling 
 .SH SYNOPSIS
@@ -9,7 +9,7 @@ int MPI_Pcontrol(const int level, ...)
 .PD 0
 .TP
 .B level 
-- Profiling level 
+- Profiling level
 .PD 1
 .PD 0
 .TP
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Probe.3 b/linx64/mpi/mpich/share/man/man3/MPI_Probe.3
index 4e299e19..2d8ebb58 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Probe.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Probe.3
@@ -1,9 +1,9 @@
-.TH MPI_Probe 3 "11/10/2017" " " "MPI"
+.TH MPI_Probe 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Probe \-  Blocking test for a message 
 .SH SYNOPSIS
 .nf
-int MPI_Probe(int source, int tag, MPI_Comm comm, MPI_Status *status)
+int MPI_Probe(int source, int tag, MPI_Comm comm, MPI_Status * status)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
@@ -11,26 +11,26 @@ int MPI_Probe(int source, int tag, MPI_Comm comm, MPI_Status *status)
 .B source 
 - source rank, or 
 .I MPI_ANY_SOURCE
-(integer) 
+(integer)
 .PD 1
 .PD 0
 .TP
 .B tag 
 - tag value or 
 .I MPI_ANY_TAG
-(integer) 
+(integer)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B status 
-- status object (Status) 
+- status object (Status)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Publish_name.3 b/linx64/mpi/mpich/share/man/man3/MPI_Publish_name.3
index 875b0840..b7462a99 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Publish_name.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Publish_name.3
@@ -1,4 +1,4 @@
-.TH MPI_Publish_name 3 "11/10/2017" " " "MPI"
+.TH MPI_Publish_name 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Publish_name \-  Publish a service name for use with MPI_Comm_connect 
 .SH SYNOPSIS
@@ -9,17 +9,17 @@ int MPI_Publish_name(const char *service_name, MPI_Info info, const char *port_n
 .PD 0
 .TP
 .B service_name 
-- a service name to associate with the port (string) 
+- a service name to associate with the port (string)
 .PD 1
 .PD 0
 .TP
 .B info 
-- implementation-specific information (handle) 
+- implementation-specific information (handle)
 .PD 1
 .PD 0
 .TP
 .B port_name 
-- a port name (string) 
+- a port name (string)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Put.3 b/linx64/mpi/mpich/share/man/man3/MPI_Put.3
index 72f41b5c..a1da20d2 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Put.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Put.3
@@ -1,54 +1,53 @@
-.TH MPI_Put 3 "11/10/2017" " " "MPI"
+.TH MPI_Put 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Put \-  Put data into a memory window on a remote process 
 .SH SYNOPSIS
 .nf
 int MPI_Put(const void *origin_addr, int origin_count, MPI_Datatype
             origin_datatype, int target_rank, MPI_Aint target_disp,
-            int target_count, MPI_Datatype target_datatype, MPI_Win
-            win)
+            int target_count, MPI_Datatype target_datatype, MPI_Win win)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B origin_addr 
-- initial address of origin buffer (choice) 
+- initial address of origin buffer (choice)
 .PD 1
 .PD 0
 .TP
 .B origin_count 
-- number of entries in origin buffer (nonnegative integer) 
+- number of entries in origin buffer (nonnegative integer)
 .PD 1
 .PD 0
 .TP
 .B origin_datatype 
-- datatype of each entry in origin buffer (handle) 
+- datatype of each entry in origin buffer (handle)
 .PD 1
 .PD 0
 .TP
 .B target_rank 
-- rank of target (nonnegative integer) 
+- rank of target (nonnegative integer)
 .PD 1
 .PD 0
 .TP
 .B target_disp 
-- displacement from start of window to target buffer (nonnegative integer) 
+- displacement from start of window to target buffer (nonnegative integer)
 .PD 1
 .PD 0
 .TP
 .B target_count 
-- number of entries in target buffer (nonnegative integer) 
+- number of entries in target buffer (nonnegative integer)
 .PD 1
 .PD 0
 .TP
 .B target_datatype 
-- datatype of each entry in target buffer (handle) 
+- datatype of each entry in target buffer (handle)
 .PD 1
 
 .PD 0
 .TP
 .B win 
-- window object used for communication (handle) 
+- window object used for communication (handle)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Query_thread.3 b/linx64/mpi/mpich/share/man/man3/MPI_Query_thread.3
index bc2469c9..f36f2262 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Query_thread.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Query_thread.3
@@ -1,9 +1,9 @@
-.TH MPI_Query_thread 3 "11/10/2017" " " "MPI"
+.TH MPI_Query_thread 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Query_thread \-  Return the level of thread support provided by the MPI  library 
+MPI_Query_thread \-  Return the level of thread support provided by the MPI library 
 .SH SYNOPSIS
 .nf
-int MPI_Query_thread( int *provided )
+int MPI_Query_thread(int *provided)
 .fi
 .SH OUTPUT PARAMETERS
 .PD 0
@@ -23,26 +23,26 @@ The valid values for the level of thread support are:
 .PD 0
 .TP
 .B MPI_THREAD_SINGLE 
-- Only one thread will execute. 
+- Only one thread will execute.
 .PD 1
 .PD 0
 .TP
 .B MPI_THREAD_FUNNELED 
-- The process may be multi-threaded, but only the main 
-thread will make MPI calls (all MPI calls are funneled to the 
-main thread). 
+- The process may be multi-threaded, but only the main
+thread will make MPI calls (all MPI calls are funneled to the
+main thread).
 .PD 1
 .PD 0
 .TP
 .B MPI_THREAD_SERIALIZED 
-- The process may be multi-threaded, and multiple 
-threads may make MPI calls, but only one at a time: MPI calls are not 
-made concurrently from two distinct threads (all MPI calls are serialized). 
+- The process may be multi-threaded, and multiple
+threads may make MPI calls, but only one at a time: MPI calls are not
+made concurrently from two distinct threads (all MPI calls are serialized).
 .PD 1
 .PD 0
 .TP
 .B MPI_THREAD_MULTIPLE 
-- Multiple threads may call MPI, with no restrictions. 
+- Multiple threads may call MPI, with no restrictions.
 .PD 1
 
 If 
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Raccumulate.3 b/linx64/mpi/mpich/share/man/man3/MPI_Raccumulate.3
index 8fbfc064..6d4dec66 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Raccumulate.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Raccumulate.3
@@ -1,13 +1,12 @@
-.TH MPI_Raccumulate 3 "11/10/2017" " " "MPI"
+.TH MPI_Raccumulate 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Raccumulate \-  Accumulate data into the target process using remote memory access and return a request handle for the operation. 
 .SH SYNOPSIS
 .nf
 int MPI_Raccumulate(const void *origin_addr, int origin_count, MPI_Datatype
-                   origin_datatype, int target_rank, MPI_Aint
-                   target_disp, int target_count, MPI_Datatype
-                   target_datatype, MPI_Op op, MPI_Win win,
-                   MPI_Request *request) 
+                    origin_datatype, int target_rank, MPI_Aint
+                    target_disp, int target_count, MPI_Datatype
+                    target_datatype, MPI_Op op, MPI_Win win, MPI_Request * request)
 .fi
 
 .I MPI_Raccumulate
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Recv.3 b/linx64/mpi/mpich/share/man/man3/MPI_Recv.3
index 01271e45..ddb900b8 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Recv.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Recv.3
@@ -1,48 +1,48 @@
-.TH MPI_Recv 3 "11/10/2017" " " "MPI"
+.TH MPI_Recv 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Recv \-  Blocking receive for a message 
 .SH SYNOPSIS
 .nf
 int MPI_Recv(void *buf, int count, MPI_Datatype datatype, int source, int tag,
-             MPI_Comm comm, MPI_Status *status)
+             MPI_Comm comm, MPI_Status * status)
 .fi
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B buf 
-- initial address of receive buffer (choice) 
+- initial address of receive buffer (choice)
 .PD 1
 .PD 0
 .TP
 .B status 
-- status object (Status) 
+- status object (Status)
 .PD 1
 
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B count 
-- maximum number of elements in receive buffer (integer) 
+- maximum number of elements in receive buffer (integer)
 .PD 1
 .PD 0
 .TP
 .B datatype 
-- datatype of each receive buffer element (handle) 
+- datatype of each receive buffer element (handle)
 .PD 1
 .PD 0
 .TP
 .B source 
-- rank of source (integer) 
+- rank of source (integer)
 .PD 1
 .PD 0
 .TP
 .B tag 
-- message tag (integer) 
+- message tag (integer)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Recv_init.3 b/linx64/mpi/mpich/share/man/man3/MPI_Recv_init.3
index 3873a30e..0ebeadb8 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Recv_init.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Recv_init.3
@@ -1,52 +1,52 @@
-.TH MPI_Recv_init 3 "11/10/2017" " " "MPI"
+.TH MPI_Recv_init 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Recv_init \-  Create a persistent request for a receive 
 .SH SYNOPSIS
 .nf
-int MPI_Recv_init(void *buf, int count, MPI_Datatype datatype, int source, 
-                 int tag, MPI_Comm comm, MPI_Request *request)
+int MPI_Recv_init(void *buf, int count, MPI_Datatype datatype, int source,
+                  int tag, MPI_Comm comm, MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B buf 
-- initial address of receive buffer (choice) 
+- initial address of receive buffer (choice)
 .PD 1
 .PD 0
 .TP
 .B count 
-- number of elements received (integer) 
+- number of elements received (integer)
 .PD 1
 .PD 0
 .TP
 .B datatype 
-- type of each element (handle) 
+- type of each element (handle)
 .PD 1
 .PD 0
 .TP
 .B source 
 - rank of source or 
 .I MPI_ANY_SOURCE
-(integer) 
+(integer)
 .PD 1
 .PD 0
 .TP
 .B tag 
 - message tag or 
 .I MPI_ANY_TAG
-(integer) 
+(integer)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B request 
-- communication request (handle) 
+- communication request (handle)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Reduce.3 b/linx64/mpi/mpich/share/man/man3/MPI_Reduce.3
index 5ec6fe35..738fb41e 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Reduce.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Reduce.3
@@ -1,4 +1,4 @@
-.TH MPI_Reduce 3 "11/10/2017" " " "MPI"
+.TH MPI_Reduce 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Reduce \-  Reduces values on all processes to a single value 
 .SH SYNOPSIS
@@ -10,42 +10,42 @@ int MPI_Reduce(const void *sendbuf, void *recvbuf, int count, MPI_Datatype datat
 .PD 0
 .TP
 .B sendbuf 
-- address of send buffer (choice) 
+- address of send buffer (choice)
 .PD 1
 .PD 0
 .TP
 .B count 
-- number of elements in send buffer (integer) 
+- number of elements in send buffer (integer)
 .PD 1
 .PD 0
 .TP
 .B datatype 
-- data type of elements of send buffer (handle) 
+- data type of elements of send buffer (handle)
 .PD 1
 .PD 0
 .TP
 .B op 
-- reduce operation (handle) 
+- reduce operation (handle)
 .PD 1
 .PD 0
 .TP
 .B root 
-- rank of root process (integer) 
+- rank of root process (integer)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B recvbuf 
-- address of receive buffer (choice, 
+- address of receive buffer (choice,
 significant only at 
 .I root
-) 
+)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Reduce_local.3 b/linx64/mpi/mpich/share/man/man3/MPI_Reduce_local.3
index 1b932f5f..390d4716 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Reduce_local.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Reduce_local.3
@@ -1,4 +1,4 @@
-.TH MPI_Reduce_local 3 "11/10/2017" " " "MPI"
+.TH MPI_Reduce_local 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Reduce_local \-  Applies a reduction operator to local arguments. 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Reduce_scatter.3 b/linx64/mpi/mpich/share/man/man3/MPI_Reduce_scatter.3
index c8751995..3ea4f7bd 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Reduce_scatter.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Reduce_scatter.3
@@ -1,45 +1,45 @@
-.TH MPI_Reduce_scatter 3 "11/10/2017" " " "MPI"
+.TH MPI_Reduce_scatter 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Reduce_scatter \-  Combines values and scatters the results 
 .SH SYNOPSIS
 .nf
 int MPI_Reduce_scatter(const void *sendbuf, void *recvbuf, const int recvcounts[],
-                      MPI_Datatype datatype, MPI_Op op, MPI_Comm comm)
+                       MPI_Datatype datatype, MPI_Op op, MPI_Comm comm)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B sendbuf 
-- starting address of send buffer (choice) 
+- starting address of send buffer (choice)
 .PD 1
 .PD 0
 .TP
 .B recvcounts 
-- integer array specifying the 
+- integer array specifying the
 number of elements in result distributed to each process.
-Array must be identical on all calling processes. 
+Array must be identical on all calling processes.
 .PD 1
 .PD 0
 .TP
 .B datatype 
-- data type of elements of input buffer (handle) 
+- data type of elements of input buffer (handle)
 .PD 1
 .PD 0
 .TP
 .B op 
-- operation (handle) 
+- operation (handle)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B recvbuf 
-- starting address of receive buffer (choice) 
+- starting address of receive buffer (choice)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Reduce_scatter_block.3 b/linx64/mpi/mpich/share/man/man3/MPI_Reduce_scatter_block.3
index 4d614d4d..e6002883 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Reduce_scatter_block.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Reduce_scatter_block.3
@@ -1,17 +1,16 @@
-.TH MPI_Reduce_scatter_block 3 "11/10/2017" " " "MPI"
+.TH MPI_Reduce_scatter_block 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Reduce_scatter_block \-  Combines values and scatters the results 
 .SH SYNOPSIS
 .nf
-int MPI_Reduce_scatter_block(const void *sendbuf, void *recvbuf, 
-                             int recvcount, 
-                             MPI_Datatype datatype, MPI_Op op, MPI_Comm comm)
+int MPI_Reduce_scatter_block(const void *sendbuf, void *recvbuf,
+                             int recvcount, MPI_Datatype datatype, MPI_Op op, MPI_Comm comm)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B sendbuf 
-- starting address of send buffer (choice) 
+- starting address of send buffer (choice)
 .PD 1
 .PD 0
 .TP
@@ -21,24 +20,24 @@ int MPI_Reduce_scatter_block(const void *sendbuf, void *recvbuf,
 .PD 0
 .TP
 .B datatype 
-- data type of elements of input buffer (handle) 
+- data type of elements of input buffer (handle)
 .PD 1
 .PD 0
 .TP
 .B op 
-- operation (handle) 
+- operation (handle)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B recvbuf 
-- starting address of receive buffer (choice) 
+- starting address of receive buffer (choice)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Register_datarep.3 b/linx64/mpi/mpich/share/man/man3/MPI_Register_datarep.3
index 5213f8da..eaeb5dc1 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Register_datarep.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Register_datarep.3
@@ -1,13 +1,12 @@
-.TH MPI_Register_datarep 3 "11/10/2017" " " "MPI"
+.TH MPI_Register_datarep 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Register_datarep \-  Register functions for user-defined data  representations 
+MPI_Register_datarep \-  Register functions for user-defined data representations 
 .SH SYNOPSIS
 .nf
 int MPI_Register_datarep(ROMIO_CONST char *datarep,
-                       MPI_Datarep_conversion_function *read_conversion_fn,
-                       MPI_Datarep_conversion_function *write_conversion_fn,
-                       MPI_Datarep_extent_function *dtype_file_extent_fn,
-                       void *extra_state)
+                         MPI_Datarep_conversion_function * read_conversion_fn,
+                         MPI_Datarep_conversion_function * write_conversion_fn,
+                         MPI_Datarep_extent_function * dtype_file_extent_fn, void *extra_state)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Request_free.3 b/linx64/mpi/mpich/share/man/man3/MPI_Request_free.3
index 3d94d6e4..df1e2f11 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Request_free.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Request_free.3
@@ -1,15 +1,15 @@
-.TH MPI_Request_free 3 "11/10/2017" " " "MPI"
+.TH MPI_Request_free 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Request_free \-  Frees a communication request object 
 .SH SYNOPSIS
 .nf
-int MPI_Request_free(MPI_Request *request)
+int MPI_Request_free(MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B request 
-- communication request (handle) 
+- communication request (handle)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Request_get_status.3 b/linx64/mpi/mpich/share/man/man3/MPI_Request_get_status.3
index f2fbf826..2e5a746e 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Request_get_status.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Request_get_status.3
@@ -1,9 +1,9 @@
-.TH MPI_Request_get_status 3 "11/10/2017" " " "MPI"
+.TH MPI_Request_get_status 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Request_get_status \-  Nondestructive test for the completion of a Request 
 .SH SYNOPSIS
 .nf
-int MPI_Request_get_status(MPI_Request request, int *flag, MPI_Status *status)
+int MPI_Request_get_status(MPI_Request request, int *flag, MPI_Status * status)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Rget.3 b/linx64/mpi/mpich/share/man/man3/MPI_Rget.3
index eec9c38f..1b03eadb 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Rget.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Rget.3
@@ -1,12 +1,11 @@
-.TH MPI_Rget 3 "11/10/2017" " " "MPI"
+.TH MPI_Rget 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Rget \-  Get data from a memory window on a remote process 
 .SH SYNOPSIS
 .nf
 int MPI_Rget(void *origin_addr, int origin_count, MPI_Datatype
-            origin_datatype, int target_rank, MPI_Aint target_disp,
-            int target_count, MPI_Datatype target_datatype, MPI_Win
-            win, MPI_Request *request)
+             origin_datatype, int target_rank, MPI_Aint target_disp,
+             int target_count, MPI_Datatype target_datatype, MPI_Win win, MPI_Request * request)
 .fi
 
 .I MPI_Rget
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Rget_accumulate.3 b/linx64/mpi/mpich/share/man/man3/MPI_Rget_accumulate.3
index ae7e8762..c4dc052a 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Rget_accumulate.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Rget_accumulate.3
@@ -1,13 +1,13 @@
-.TH MPI_Rget_accumulate 3 "11/10/2017" " " "MPI"
+.TH MPI_Rget_accumulate 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Rget_accumulate \-  Perform an atomic, one-sided read-and-accumulate operation and return a request handle for the operation. 
 .SH SYNOPSIS
 .nf
 int MPI_Rget_accumulate(const void *origin_addr, int origin_count,
-        MPI_Datatype origin_datatype, void *result_addr, int result_count,
-        MPI_Datatype result_datatype, int target_rank, MPI_Aint target_disp,
-        int target_count, MPI_Datatype target_datatype, MPI_Op op, MPI_Win win,
-        MPI_Request *request)
+                        MPI_Datatype origin_datatype, void *result_addr, int result_count,
+                        MPI_Datatype result_datatype, int target_rank, MPI_Aint target_disp,
+                        int target_count, MPI_Datatype target_datatype, MPI_Op op, MPI_Win win,
+                        MPI_Request * request)
 .fi
 
 .I MPI_Rget_accumulate
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Rput.3 b/linx64/mpi/mpich/share/man/man3/MPI_Rput.3
index 196667b1..7f9dafee 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Rput.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Rput.3
@@ -1,12 +1,11 @@
-.TH MPI_Rput 3 "11/10/2017" " " "MPI"
+.TH MPI_Rput 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Rput \-  Put data into a memory window on a remote process and return a request handle for the operation. 
 .SH SYNOPSIS
 .nf
 int MPI_Rput(const void *origin_addr, int origin_count, MPI_Datatype
-            origin_datatype, int target_rank, MPI_Aint target_disp,
-            int target_count, MPI_Datatype target_datatype, MPI_Win
-            win, MPI_Request *request)
+             origin_datatype, int target_rank, MPI_Aint target_disp,
+             int target_count, MPI_Datatype target_datatype, MPI_Win win, MPI_Request * request)
 .fi
 
 .I MPI_Rput
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Rsend.3 b/linx64/mpi/mpich/share/man/man3/MPI_Rsend.3
index 35dda8cb..075173f8 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Rsend.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Rsend.3
@@ -1,41 +1,40 @@
-.TH MPI_Rsend 3 "11/10/2017" " " "MPI"
+.TH MPI_Rsend 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Rsend \-  Blocking ready send  
+MPI_Rsend \-  Blocking ready send 
 .SH SYNOPSIS
 .nf
-int MPI_Rsend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-              MPI_Comm comm)
+int MPI_Rsend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag, MPI_Comm comm)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B buf 
-- initial address of send buffer (choice) 
+- initial address of send buffer (choice)
 .PD 1
 .PD 0
 .TP
 .B count 
-- number of elements in send buffer (nonnegative integer) 
+- number of elements in send buffer (nonnegative integer)
 .PD 1
 .PD 0
 .TP
 .B datatype 
-- datatype of each send buffer element (handle) 
+- datatype of each send buffer element (handle)
 .PD 1
 .PD 0
 .TP
 .B dest 
-- rank of destination (integer) 
+- rank of destination (integer)
 .PD 1
 .PD 0
 .TP
 .B tag 
-- message tag (integer) 
+- message tag (integer)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Rsend_init.3 b/linx64/mpi/mpich/share/man/man3/MPI_Rsend_init.3
index 11af2120..ec1f961e 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Rsend_init.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Rsend_init.3
@@ -1,48 +1,48 @@
-.TH MPI_Rsend_init 3 "11/10/2017" " " "MPI"
+.TH MPI_Rsend_init 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Rsend_init \-  Creates a persistent request for a ready send 
 .SH SYNOPSIS
 .nf
 int MPI_Rsend_init(const void *buf, int count, MPI_Datatype datatype, int dest,
-                  int tag, MPI_Comm comm, MPI_Request *request)
+                   int tag, MPI_Comm comm, MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B buf 
-- initial address of send buffer (choice) 
+- initial address of send buffer (choice)
 .PD 1
 .PD 0
 .TP
 .B count 
-- number of elements sent (integer) 
+- number of elements sent (integer)
 .PD 1
 .PD 0
 .TP
 .B datatype 
-- type of each element (handle) 
+- type of each element (handle)
 .PD 1
 .PD 0
 .TP
 .B dest 
-- rank of destination (integer) 
+- rank of destination (integer)
 .PD 1
 .PD 0
 .TP
 .B tag 
-- message tag (integer) 
+- message tag (integer)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B request 
-- communication request (handle) 
+- communication request (handle)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Scan.3 b/linx64/mpi/mpich/share/man/man3/MPI_Scan.3
index 3f01393f..ecd1eea6 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Scan.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Scan.3
@@ -1,4 +1,4 @@
-.TH MPI_Scan 3 "11/10/2017" " " "MPI"
+.TH MPI_Scan 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Scan \-  Computes the scan (partial reductions) of data on a collection of processes 
 .SH SYNOPSIS
@@ -10,34 +10,34 @@ int MPI_Scan(const void *sendbuf, void *recvbuf, int count, MPI_Datatype datatyp
 .PD 0
 .TP
 .B sendbuf 
-- starting address of send buffer (choice) 
+- starting address of send buffer (choice)
 .PD 1
 .PD 0
 .TP
 .B count 
-- number of elements in input buffer (integer) 
+- number of elements in input buffer (integer)
 .PD 1
 .PD 0
 .TP
 .B datatype 
-- data type of elements of input buffer (handle) 
+- data type of elements of input buffer (handle)
 .PD 1
 .PD 0
 .TP
 .B op 
-- operation (handle) 
+- operation (handle)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B recvbuf 
-- starting address of receive buffer (choice) 
+- starting address of receive buffer (choice)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Scatter.3 b/linx64/mpi/mpich/share/man/man3/MPI_Scatter.3
index 1a1e0299..f89cdf25 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Scatter.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Scatter.3
@@ -1,63 +1,62 @@
-.TH MPI_Scatter 3 "11/10/2017" " " "MPI"
+.TH MPI_Scatter 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Scatter \-  Sends data from one process to all other processes in a  communicator 
+MPI_Scatter \-  Sends data from one process to all other processes in a communicator 
 .SH SYNOPSIS
 .nf
 int MPI_Scatter(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
-               void *recvbuf, int recvcount, MPI_Datatype recvtype, int root,
-               MPI_Comm comm)
+                void *recvbuf, int recvcount, MPI_Datatype recvtype, int root, MPI_Comm comm)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B sendbuf 
-- address of send buffer (choice, significant 
+- address of send buffer (choice, significant
 only at 
 .I root
-) 
+)
 .PD 1
 .PD 0
 .TP
 .B sendcount 
-- number of elements sent to each process 
+- number of elements sent to each process
 (integer, significant only at 
 .I root
-) 
+)
 .PD 1
 .PD 0
 .TP
 .B sendtype 
 - data type of send buffer elements (significant only at 
 .I root
-) 
-(handle) 
+)
+(handle)
 .PD 1
 .PD 0
 .TP
 .B recvcount 
-- number of elements in receive buffer (integer) 
+- number of elements in receive buffer (integer)
 .PD 1
 .PD 0
 .TP
 .B recvtype 
-- data type of receive buffer elements (handle) 
+- data type of receive buffer elements (handle)
 .PD 1
 .PD 0
 .TP
 .B root 
-- rank of sending process (integer) 
+- rank of sending process (integer)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B recvbuf 
-- address of receive buffer (choice) 
+- address of receive buffer (choice)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Scatterv.3 b/linx64/mpi/mpich/share/man/man3/MPI_Scatterv.3
index c6c9b30d..54ea828e 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Scatterv.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Scatterv.3
@@ -1,12 +1,11 @@
-.TH MPI_Scatterv 3 "11/10/2017" " " "MPI"
+.TH MPI_Scatterv 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Scatterv \-  Scatters a buffer in parts to all processes in a communicator 
 .SH SYNOPSIS
 .nf
 int MPI_Scatterv(const void *sendbuf, const int *sendcounts, const int *displs,
                  MPI_Datatype sendtype, void *recvbuf, int recvcount,
-                 MPI_Datatype recvtype,
-                 int root, MPI_Comm comm)
+                 MPI_Datatype recvtype, int root, MPI_Comm comm)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
@@ -14,18 +13,18 @@ int MPI_Scatterv(const void *sendbuf, const int *sendcounts, const int *displs,
 .B sendbuf 
 - address of send buffer (choice, significant only at 
 .I root
-) 
+)
 .PD 1
 .PD 0
 .TP
 .B sendcounts 
-- integer array (of length group size) 
-specifying the number of elements to send to each processor  
+- integer array (of length group size)
+specifying the number of elements to send to each processor
 .PD 1
 .PD 0
 .TP
 .B displs 
-- integer array (of length group size). Entry 
+- integer array (of length group size). Entry
 .I i
 specifies the displacement (relative to sendbuf  from
 which to take the outgoing data to process  
@@ -35,34 +34,34 @@ which to take the outgoing data to process
 .PD 0
 .TP
 .B sendtype 
-- data type of send buffer elements (handle) 
+- data type of send buffer elements (handle)
 .PD 1
 .PD 0
 .TP
 .B recvcount 
-- number of elements in receive buffer (integer) 
+- number of elements in receive buffer (integer)
 .PD 1
 .PD 0
 .TP
 .B recvtype 
-- data type of receive buffer elements (handle) 
+- data type of receive buffer elements (handle)
 .PD 1
 .PD 0
 .TP
 .B root 
-- rank of sending process (integer) 
+- rank of sending process (integer)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B recvbuf 
-- address of receive buffer (choice) 
+- address of receive buffer (choice)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Send.3 b/linx64/mpi/mpich/share/man/man3/MPI_Send.3
index 1b036061..21319a6c 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Send.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Send.3
@@ -1,41 +1,40 @@
-.TH MPI_Send 3 "11/10/2017" " " "MPI"
+.TH MPI_Send 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Send \-  Performs a blocking send 
 .SH SYNOPSIS
 .nf
-int MPI_Send(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-             MPI_Comm comm)
+int MPI_Send(const void *buf, int count, MPI_Datatype datatype, int dest, int tag, MPI_Comm comm)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B buf 
-- initial address of send buffer (choice) 
+- initial address of send buffer (choice)
 .PD 1
 .PD 0
 .TP
 .B count 
-- number of elements in send buffer (nonnegative integer) 
+- number of elements in send buffer (nonnegative integer)
 .PD 1
 .PD 0
 .TP
 .B datatype 
-- datatype of each send buffer element (handle) 
+- datatype of each send buffer element (handle)
 .PD 1
 .PD 0
 .TP
 .B dest 
-- rank of destination (integer) 
+- rank of destination (integer)
 .PD 1
 .PD 0
 .TP
 .B tag 
-- message tag (integer) 
+- message tag (integer)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Send_init.3 b/linx64/mpi/mpich/share/man/man3/MPI_Send_init.3
index 268a95ae..a10f3acb 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Send_init.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Send_init.3
@@ -1,48 +1,48 @@
-.TH MPI_Send_init 3 "11/10/2017" " " "MPI"
+.TH MPI_Send_init 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Send_init \-  Create a persistent request for a standard send 
 .SH SYNOPSIS
 .nf
 int MPI_Send_init(const void *buf, int count, MPI_Datatype datatype, int dest,
-                 int tag, MPI_Comm comm, MPI_Request *request)
+                  int tag, MPI_Comm comm, MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B buf 
-- initial address of send buffer (choice) 
+- initial address of send buffer (choice)
 .PD 1
 .PD 0
 .TP
 .B count 
-- number of elements sent (integer) 
+- number of elements sent (integer)
 .PD 1
 .PD 0
 .TP
 .B datatype 
-- type of each element (handle) 
+- type of each element (handle)
 .PD 1
 .PD 0
 .TP
 .B dest 
-- rank of destination (integer) 
+- rank of destination (integer)
 .PD 1
 .PD 0
 .TP
 .B tag 
-- message tag (integer) 
+- message tag (integer)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B request 
-- communication request (handle) 
+- communication request (handle)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Sendrecv.3 b/linx64/mpi/mpich/share/man/man3/MPI_Sendrecv.3
index 7409e71e..31b9eba1 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Sendrecv.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Sendrecv.3
@@ -1,71 +1,70 @@
-.TH MPI_Sendrecv 3 "11/10/2017" " " "MPI"
+.TH MPI_Sendrecv 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Sendrecv \-  Sends and receives a message 
 .SH SYNOPSIS
 .nf
 int MPI_Sendrecv(const void *sendbuf, int sendcount, MPI_Datatype sendtype,
-                int dest, int sendtag,
-                void *recvbuf, int recvcount, MPI_Datatype recvtype,
-                int source, int recvtag,
-                MPI_Comm comm, MPI_Status *status)
+                 int dest, int sendtag,
+                 void *recvbuf, int recvcount, MPI_Datatype recvtype,
+                 int source, int recvtag, MPI_Comm comm, MPI_Status * status)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B sendbuf 
-- initial address of send buffer (choice) 
+- initial address of send buffer (choice)
 .PD 1
 .PD 0
 .TP
 .B sendcount 
-- number of elements in send buffer (integer) 
+- number of elements in send buffer (integer)
 .PD 1
 .PD 0
 .TP
 .B sendtype 
-- type of elements in send buffer (handle) 
+- type of elements in send buffer (handle)
 .PD 1
 .PD 0
 .TP
 .B dest 
-- rank of destination (integer) 
+- rank of destination (integer)
 .PD 1
 .PD 0
 .TP
 .B sendtag 
-- send tag (integer) 
+- send tag (integer)
 .PD 1
 .PD 0
 .TP
 .B recvcount 
-- number of elements in receive buffer (integer) 
+- number of elements in receive buffer (integer)
 .PD 1
 .PD 0
 .TP
 .B recvtype 
-- type of elements in receive buffer (handle) 
+- type of elements in receive buffer (handle)
 .PD 1
 .PD 0
 .TP
 .B source 
-- rank of source (integer) 
+- rank of source (integer)
 .PD 1
 .PD 0
 .TP
 .B recvtag 
-- receive tag (integer) 
+- receive tag (integer)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B recvbuf 
-- initial address of receive buffer (choice) 
+- initial address of receive buffer (choice)
 .PD 1
 .PD 0
 .TP
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Sendrecv_replace.3 b/linx64/mpi/mpich/share/man/man3/MPI_Sendrecv_replace.3
index ce7bd6d9..c96a1127 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Sendrecv_replace.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Sendrecv_replace.3
@@ -1,59 +1,59 @@
-.TH MPI_Sendrecv_replace 3 "11/10/2017" " " "MPI"
+.TH MPI_Sendrecv_replace 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Sendrecv_replace \-  Sends and receives using a single buffer 
 .SH SYNOPSIS
 .nf
-int MPI_Sendrecv_replace(void *buf, int count, MPI_Datatype datatype, 
-                       int dest, int sendtag, int source, int recvtag,
-                       MPI_Comm comm, MPI_Status *status)
+int MPI_Sendrecv_replace(void *buf, int count, MPI_Datatype datatype,
+                         int dest, int sendtag, int source, int recvtag,
+                         MPI_Comm comm, MPI_Status * status)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B count 
-- number of elements in send and receive buffer (integer) 
+- number of elements in send and receive buffer (integer)
 .PD 1
 .PD 0
 .TP
 .B datatype 
-- type of elements in send and receive buffer (handle) 
+- type of elements in send and receive buffer (handle)
 .PD 1
 .PD 0
 .TP
 .B dest 
-- rank of destination (integer) 
+- rank of destination (integer)
 .PD 1
 .PD 0
 .TP
 .B sendtag 
-- send message tag (integer) 
+- send message tag (integer)
 .PD 1
 .PD 0
 .TP
 .B source 
-- rank of source (integer) 
+- rank of source (integer)
 .PD 1
 .PD 0
 .TP
 .B recvtag 
-- receive message tag (integer) 
+- receive message tag (integer)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B buf 
-- initial address of send and receive buffer (choice) 
+- initial address of send and receive buffer (choice)
 .PD 1
 .PD 0
 .TP
 .B status 
-- status object (Status) 
+- status object (Status)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Ssend.3 b/linx64/mpi/mpich/share/man/man3/MPI_Ssend.3
index 573e5a84..2390dfeb 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Ssend.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Ssend.3
@@ -1,41 +1,40 @@
-.TH MPI_Ssend 3 "11/10/2017" " " "MPI"
+.TH MPI_Ssend 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Ssend \-  Blocking synchronous send 
 .SH SYNOPSIS
 .nf
-int MPI_Ssend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag,
-              MPI_Comm comm)
+int MPI_Ssend(const void *buf, int count, MPI_Datatype datatype, int dest, int tag, MPI_Comm comm)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B buf 
-- initial address of send buffer (choice) 
+- initial address of send buffer (choice)
 .PD 1
 .PD 0
 .TP
 .B count 
-- number of elements in send buffer (nonnegative integer) 
+- number of elements in send buffer (nonnegative integer)
 .PD 1
 .PD 0
 .TP
 .B datatype 
-- datatype of each send buffer element (handle) 
+- datatype of each send buffer element (handle)
 .PD 1
 .PD 0
 .TP
 .B dest 
-- rank of destination (integer) 
+- rank of destination (integer)
 .PD 1
 .PD 0
 .TP
 .B tag 
-- message tag (integer) 
+- message tag (integer)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Ssend_init.3 b/linx64/mpi/mpich/share/man/man3/MPI_Ssend_init.3
index 055a87fd..4ebcebb8 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Ssend_init.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Ssend_init.3
@@ -1,48 +1,48 @@
-.TH MPI_Ssend_init 3 "11/10/2017" " " "MPI"
+.TH MPI_Ssend_init 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Ssend_init \-  Creates a persistent request for a synchronous send 
 .SH SYNOPSIS
 .nf
 int MPI_Ssend_init(const void *buf, int count, MPI_Datatype datatype, int dest,
-                  int tag, MPI_Comm comm, MPI_Request *request)
+                   int tag, MPI_Comm comm, MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B buf 
-- initial address of send buffer (choice) 
+- initial address of send buffer (choice)
 .PD 1
 .PD 0
 .TP
 .B count 
-- number of elements sent (integer) 
+- number of elements sent (integer)
 .PD 1
 .PD 0
 .TP
 .B datatype 
-- type of each element (handle) 
+- type of each element (handle)
 .PD 1
 .PD 0
 .TP
 .B dest 
-- rank of destination (integer) 
+- rank of destination (integer)
 .PD 1
 .PD 0
 .TP
 .B tag 
-- message tag (integer) 
+- message tag (integer)
 .PD 1
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B request 
-- communication request (handle) 
+- communication request (handle)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Start.3 b/linx64/mpi/mpich/share/man/man3/MPI_Start.3
index 79b7e8c1..066a8fed 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Start.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Start.3
@@ -1,15 +1,15 @@
-.TH MPI_Start 3 "11/10/2017" " " "MPI"
+.TH MPI_Start 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Start \-  Initiates a communication with a persistent request handle 
 .SH SYNOPSIS
 .nf
-int MPI_Start(MPI_Request *request)
+int MPI_Start(MPI_Request * request)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B request 
-- communication request (handle) 
+- communication request (handle)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Startall.3 b/linx64/mpi/mpich/share/man/man3/MPI_Startall.3
index ec002dd8..e1dd2bb0 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Startall.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Startall.3
@@ -1,6 +1,6 @@
-.TH MPI_Startall 3 "11/10/2017" " " "MPI"
+.TH MPI_Startall 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Startall \-  Starts a collection of persistent requests  
+MPI_Startall \-  Starts a collection of persistent requests 
 .SH SYNOPSIS
 .nf
 int MPI_Startall(int count, MPI_Request array_of_requests[])
@@ -9,12 +9,12 @@ int MPI_Startall(int count, MPI_Request array_of_requests[])
 .PD 0
 .TP
 .B count 
-- list length (integer) 
+- list length (integer)
 .PD 1
 .PD 0
 .TP
 .B array_of_requests 
-- array of requests (array of handle) 
+- array of requests (array of handle)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Status_set_cancelled.3 b/linx64/mpi/mpich/share/man/man3/MPI_Status_set_cancelled.3
index 6241c56c..f6269b79 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Status_set_cancelled.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Status_set_cancelled.3
@@ -1,9 +1,9 @@
-.TH MPI_Status_set_cancelled 3 "11/10/2017" " " "MPI"
+.TH MPI_Status_set_cancelled 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Status_set_cancelled \-  Sets the cancelled state associated with a  Status object 
+MPI_Status_set_cancelled \-  Sets the cancelled state associated with a Status object 
 .SH SYNOPSIS
 .nf
-int MPI_Status_set_cancelled(MPI_Status *status, int flag)
+int MPI_Status_set_cancelled(MPI_Status * status, int flag)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Status_set_elements.3 b/linx64/mpi/mpich/share/man/man3/MPI_Status_set_elements.3
index 86530178..54f4b9b1 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Status_set_elements.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Status_set_elements.3
@@ -1,26 +1,25 @@
-.TH MPI_Status_set_elements 3 "11/10/2017" " " "MPI"
+.TH MPI_Status_set_elements 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Status_set_elements \-  Set the number of elements in a status 
 .SH SYNOPSIS
 .nf
-int MPI_Status_set_elements(MPI_Status *status, MPI_Datatype datatype, 
-                          int count)
+int MPI_Status_set_elements(MPI_Status * status, MPI_Datatype datatype, int count)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B status 
-- status to associate count with (Status) 
+- status to associate count with (Status)
 .PD 1
 .PD 0
 .TP
 .B datatype 
-- datatype associated with count (handle) 
+- datatype associated with count (handle)
 .PD 1
 .PD 0
 .TP
 .B count 
-- number of elements to associate with status (integer) 
+- number of elements to associate with status (integer)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Status_set_elements_x.3 b/linx64/mpi/mpich/share/man/man3/MPI_Status_set_elements_x.3
index ce6ae517..c3419d20 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Status_set_elements_x.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Status_set_elements_x.3
@@ -1,9 +1,9 @@
-.TH MPI_Status_set_elements_x 3 "11/10/2017" " " "MPI"
+.TH MPI_Status_set_elements_x 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Status_set_elements_x \-  Set the number of elements in a status 
 .SH SYNOPSIS
 .nf
-int MPI_Status_set_elements_x(MPI_Status *status, MPI_Datatype datatype, MPI_Count count)
+int MPI_Status_set_elements_x(MPI_Status * status, MPI_Datatype datatype, MPI_Count count)
 .fi
 .SH INPUT/OUTPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_T_category_changed.3 b/linx64/mpi/mpich/share/man/man3/MPI_T_category_changed.3
index 5ac01cc8..518f7768 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_T_category_changed.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_T_category_changed.3
@@ -1,4 +1,4 @@
-.TH MPI_T_category_changed 3 "11/10/2017" " " "MPI"
+.TH MPI_T_category_changed 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_T_category_changed \-  Get the timestamp indicating the last change to the categories 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_T_category_get_categories.3 b/linx64/mpi/mpich/share/man/man3/MPI_T_category_get_categories.3
index e0016441..5d3aa1bb 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_T_category_get_categories.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_T_category_get_categories.3
@@ -1,4 +1,4 @@
-.TH MPI_T_category_get_categories 3 "11/10/2017" " " "MPI"
+.TH MPI_T_category_get_categories 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_T_category_get_categories \-  Get sub-categories in a category 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_T_category_get_cvars.3 b/linx64/mpi/mpich/share/man/man3/MPI_T_category_get_cvars.3
index 6698433f..03424429 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_T_category_get_cvars.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_T_category_get_cvars.3
@@ -1,4 +1,4 @@
-.TH MPI_T_category_get_cvars 3 "11/10/2017" " " "MPI"
+.TH MPI_T_category_get_cvars 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_T_category_get_cvars \-  Get control variables in a category 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_T_category_get_index.3 b/linx64/mpi/mpich/share/man/man3/MPI_T_category_get_index.3
index a350bb0a..5d89f804 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_T_category_get_index.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_T_category_get_index.3
@@ -1,4 +1,4 @@
-.TH MPI_T_category_get_index 3 "11/10/2017" " " "MPI"
+.TH MPI_T_category_get_index 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_T_category_get_index \-  Get the index of a category 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_T_category_get_info.3 b/linx64/mpi/mpich/share/man/man3/MPI_T_category_get_info.3
index 4d0feadd..61dffc15 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_T_category_get_info.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_T_category_get_info.3
@@ -1,10 +1,10 @@
-.TH MPI_T_category_get_info 3 "11/10/2017" " " "MPI"
+.TH MPI_T_category_get_info 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_T_category_get_info \-  Get the information about a category 
 .SH SYNOPSIS
 .nf
 int MPI_T_category_get_info(int cat_index, char *name, int *name_len, char *desc,
-        int *desc_len, int *num_cvars, int *num_pvars, int *num_categories)
+                            int *desc_len, int *num_cvars, int *num_pvars, int *num_categories)
 .fi
 .SH INPUT/OUTPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_T_category_get_num.3 b/linx64/mpi/mpich/share/man/man3/MPI_T_category_get_num.3
index 60ba5b4f..dbfb5a29 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_T_category_get_num.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_T_category_get_num.3
@@ -1,4 +1,4 @@
-.TH MPI_T_category_get_num 3 "11/10/2017" " " "MPI"
+.TH MPI_T_category_get_num 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_T_category_get_num \-  Get the number of categories 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_T_category_get_pvars.3 b/linx64/mpi/mpich/share/man/man3/MPI_T_category_get_pvars.3
index 9ed18b4d..e29adb83 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_T_category_get_pvars.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_T_category_get_pvars.3
@@ -1,4 +1,4 @@
-.TH MPI_T_category_get_pvars 3 "11/10/2017" " " "MPI"
+.TH MPI_T_category_get_pvars 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_T_category_get_pvars \-  Get performance variables in a category 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_T_cvar_get_index.3 b/linx64/mpi/mpich/share/man/man3/MPI_T_cvar_get_index.3
index a27dcc82..30912d43 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_T_cvar_get_index.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_T_cvar_get_index.3
@@ -1,4 +1,4 @@
-.TH MPI_T_cvar_get_index 3 "11/10/2017" " " "MPI"
+.TH MPI_T_cvar_get_index 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_T_cvar_get_index \-  Get the index of a control variable 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_T_cvar_get_info.3 b/linx64/mpi/mpich/share/man/man3/MPI_T_cvar_get_info.3
index 21da5ccb..42961034 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_T_cvar_get_info.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_T_cvar_get_info.3
@@ -1,11 +1,11 @@
-.TH MPI_T_cvar_get_info 3 "11/10/2017" " " "MPI"
+.TH MPI_T_cvar_get_info 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_T_cvar_get_info \-  Get the information about a control variable 
 .SH SYNOPSIS
 .nf
 int MPI_T_cvar_get_info(int cvar_index, char *name, int *name_len,
-    int *verbosity, MPI_Datatype *datatype, MPI_T_enum *enumtype,
-    char *desc, int *desc_len, int *binding, int *scope)
+                        int *verbosity, MPI_Datatype * datatype, MPI_T_enum * enumtype,
+                        char *desc, int *desc_len, int *binding, int *scope)
 .fi
 .SH INPUT/OUTPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_T_cvar_get_num.3 b/linx64/mpi/mpich/share/man/man3/MPI_T_cvar_get_num.3
index a05a21b6..9b1e30de 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_T_cvar_get_num.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_T_cvar_get_num.3
@@ -1,4 +1,4 @@
-.TH MPI_T_cvar_get_num 3 "11/10/2017" " " "MPI"
+.TH MPI_T_cvar_get_num 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_T_cvar_get_num \-  Get the number of control variables 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_T_cvar_handle_alloc.3 b/linx64/mpi/mpich/share/man/man3/MPI_T_cvar_handle_alloc.3
index d0e0d8ec..d049037f 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_T_cvar_handle_alloc.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_T_cvar_handle_alloc.3
@@ -1,9 +1,10 @@
-.TH MPI_T_cvar_handle_alloc 3 "11/10/2017" " " "MPI"
+.TH MPI_T_cvar_handle_alloc 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_T_cvar_handle_alloc \-  Allocate a handle for a control variable 
 .SH SYNOPSIS
 .nf
-int MPI_T_cvar_handle_alloc(int cvar_index, void *obj_handle, MPI_T_cvar_handle *handle, int *count)
+int MPI_T_cvar_handle_alloc(int cvar_index, void *obj_handle, MPI_T_cvar_handle * handle,
+                            int *count)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_T_cvar_handle_free.3 b/linx64/mpi/mpich/share/man/man3/MPI_T_cvar_handle_free.3
index 4ea94704..5057c259 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_T_cvar_handle_free.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_T_cvar_handle_free.3
@@ -1,9 +1,9 @@
-.TH MPI_T_cvar_handle_free 3 "11/10/2017" " " "MPI"
+.TH MPI_T_cvar_handle_free 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_T_cvar_handle_free \-  Free an existing handle for a control variable 
 .SH SYNOPSIS
 .nf
-int MPI_T_cvar_handle_free(MPI_T_cvar_handle *handle)
+int MPI_T_cvar_handle_free(MPI_T_cvar_handle * handle)
 .fi
 .SH INPUT/OUTPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_T_cvar_read.3 b/linx64/mpi/mpich/share/man/man3/MPI_T_cvar_read.3
index 26c3a10c..e39957b2 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_T_cvar_read.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_T_cvar_read.3
@@ -1,4 +1,4 @@
-.TH MPI_T_cvar_read 3 "11/10/2017" " " "MPI"
+.TH MPI_T_cvar_read 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_T_cvar_read \-  Read the value of a control variable 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_T_cvar_write.3 b/linx64/mpi/mpich/share/man/man3/MPI_T_cvar_write.3
index c366e048..6cad5590 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_T_cvar_write.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_T_cvar_write.3
@@ -1,4 +1,4 @@
-.TH MPI_T_cvar_write 3 "11/10/2017" " " "MPI"
+.TH MPI_T_cvar_write 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_T_cvar_write \-  Write a control variable 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_T_enum_get_info.3 b/linx64/mpi/mpich/share/man/man3/MPI_T_enum_get_info.3
index e39764a9..55837be9 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_T_enum_get_info.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_T_enum_get_info.3
@@ -1,4 +1,4 @@
-.TH MPI_T_enum_get_info 3 "11/10/2017" " " "MPI"
+.TH MPI_T_enum_get_info 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_T_enum_get_info \-  Get the information about an enumeration 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_T_enum_get_item.3 b/linx64/mpi/mpich/share/man/man3/MPI_T_enum_get_item.3
index f4c28d88..ce2c2081 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_T_enum_get_item.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_T_enum_get_item.3
@@ -1,4 +1,4 @@
-.TH MPI_T_enum_get_item 3 "11/10/2017" " " "MPI"
+.TH MPI_T_enum_get_item 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_T_enum_get_item \-  Get the information about an item in an enumeration 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_T_finalize.3 b/linx64/mpi/mpich/share/man/man3/MPI_T_finalize.3
index 4cd8e4d0..331be045 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_T_finalize.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_T_finalize.3
@@ -1,4 +1,4 @@
-.TH MPI_T_finalize 3 "11/10/2017" " " "MPI"
+.TH MPI_T_finalize 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_T_finalize \-  Finalize the MPI tool information interface 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_T_init_thread.3 b/linx64/mpi/mpich/share/man/man3/MPI_T_init_thread.3
index 779993c1..3b02e444 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_T_init_thread.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_T_init_thread.3
@@ -1,4 +1,4 @@
-.TH MPI_T_init_thread 3 "11/10/2017" " " "MPI"
+.TH MPI_T_init_thread 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_T_init_thread \-  Initialize the MPI_T execution environment 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_get_index.3 b/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_get_index.3
index 4e1bf5f9..f5e893d0 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_get_index.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_get_index.3
@@ -1,4 +1,4 @@
-.TH MPI_T_pvar_get_index 3 "11/10/2017" " " "MPI"
+.TH MPI_T_pvar_get_index 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_T_pvar_get_index \-  Get the index of a performance variable 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_get_info.3 b/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_get_info.3
index cab39efc..01bb7c00 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_get_info.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_get_info.3
@@ -1,11 +1,11 @@
-.TH MPI_T_pvar_get_info 3 "11/10/2017" " " "MPI"
+.TH MPI_T_pvar_get_info 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_T_pvar_get_info \-  Get the inforamtion about a performance variable 
 .SH SYNOPSIS
 .nf
 int MPI_T_pvar_get_info(int pvar_index, char *name, int *name_len, int *verbosity,
-    int *var_class, MPI_Datatype *datatype, MPI_T_enum *enumtype, char *desc,
-    int *desc_len, int *binding, int *readonly, int *continuous, int *atomic)
+                        int *var_class, MPI_Datatype * datatype, MPI_T_enum * enumtype, char *desc,
+                        int *desc_len, int *binding, int *readonly, int *continuous, int *atomic)
 .fi
 .SH INPUT/OUTPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_get_num.3 b/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_get_num.3
index 1f834274..fdc4a193 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_get_num.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_get_num.3
@@ -1,4 +1,4 @@
-.TH MPI_T_pvar_get_num 3 "11/10/2017" " " "MPI"
+.TH MPI_T_pvar_get_num 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_T_pvar_get_num \-  Get the number of performance variables 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_handle_alloc.3 b/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_handle_alloc.3
index 1eab5f9e..c91e6359 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_handle_alloc.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_handle_alloc.3
@@ -1,10 +1,10 @@
-.TH MPI_T_pvar_handle_alloc 3 "11/10/2017" " " "MPI"
+.TH MPI_T_pvar_handle_alloc 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_T_pvar_handle_alloc \-  Allocate a handle for a performance variable 
 .SH SYNOPSIS
 .nf
 int MPI_T_pvar_handle_alloc(MPI_T_pvar_session session, int pvar_index,
-                            void *obj_handle, MPI_T_pvar_handle *handle, int *count)
+                            void *obj_handle, MPI_T_pvar_handle * handle, int *count)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_handle_free.3 b/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_handle_free.3
index 0ed9e088..30e8fc76 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_handle_free.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_handle_free.3
@@ -1,9 +1,9 @@
-.TH MPI_T_pvar_handle_free 3 "11/10/2017" " " "MPI"
+.TH MPI_T_pvar_handle_free 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_T_pvar_handle_free \-  Free an existing handle for a performance variable 
 .SH SYNOPSIS
 .nf
-int MPI_T_pvar_handle_free(MPI_T_pvar_session session, MPI_T_pvar_handle *handle)
+int MPI_T_pvar_handle_free(MPI_T_pvar_session session, MPI_T_pvar_handle * handle)
 .fi
 .SH INPUT/OUTPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_read.3 b/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_read.3
index 28aa7982..dceef5a2 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_read.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_read.3
@@ -1,4 +1,4 @@
-.TH MPI_T_pvar_read 3 "11/10/2017" " " "MPI"
+.TH MPI_T_pvar_read 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_T_pvar_read \-  Read the value of a performance variable 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_readreset.3 b/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_readreset.3
index ec5ed2a2..1fa5d22c 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_readreset.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_readreset.3
@@ -1,4 +1,4 @@
-.TH MPI_T_pvar_readreset 3 "11/10/2017" " " "MPI"
+.TH MPI_T_pvar_readreset 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_T_pvar_readreset \-  Read the value of a performance variable and then reset it 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_reset.3 b/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_reset.3
index b12049c5..7a0e64d3 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_reset.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_reset.3
@@ -1,4 +1,4 @@
-.TH MPI_T_pvar_reset 3 "11/10/2017" " " "MPI"
+.TH MPI_T_pvar_reset 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_T_pvar_reset \-  Reset a performance variable 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_session_create.3 b/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_session_create.3
index d8158178..2d8c8f45 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_session_create.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_session_create.3
@@ -1,9 +1,9 @@
-.TH MPI_T_pvar_session_create 3 "11/10/2017" " " "MPI"
+.TH MPI_T_pvar_session_create 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_T_pvar_session_create \-  Create a new session for accessing performance variables 
 .SH SYNOPSIS
 .nf
-int MPI_T_pvar_session_create(MPI_T_pvar_session *session)
+int MPI_T_pvar_session_create(MPI_T_pvar_session * session)
 .fi
 .SH OUTPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_session_free.3 b/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_session_free.3
index 5159e74b..ae6860cd 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_session_free.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_session_free.3
@@ -1,9 +1,9 @@
-.TH MPI_T_pvar_session_free 3 "11/10/2017" " " "MPI"
+.TH MPI_T_pvar_session_free 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_T_pvar_session_free \-  Free an existing performance variable session 
 .SH SYNOPSIS
 .nf
-int MPI_T_pvar_session_free(MPI_T_pvar_session *session)
+int MPI_T_pvar_session_free(MPI_T_pvar_session * session)
 .fi
 .SH INPUT/OUTPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_start.3 b/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_start.3
index 036642e0..c72532c0 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_start.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_start.3
@@ -1,4 +1,4 @@
-.TH MPI_T_pvar_start 3 "11/10/2017" " " "MPI"
+.TH MPI_T_pvar_start 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_T_pvar_start \-  Start a performance variable 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_stop.3 b/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_stop.3
index 49def5ee..a2c141fa 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_stop.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_stop.3
@@ -1,4 +1,4 @@
-.TH MPI_T_pvar_stop 3 "11/10/2017" " " "MPI"
+.TH MPI_T_pvar_stop 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_T_pvar_stop \-  Stop a performance variable 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_write.3 b/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_write.3
index f15d4bd5..b33f5c65 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_write.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_T_pvar_write.3
@@ -1,4 +1,4 @@
-.TH MPI_T_pvar_write 3 "11/10/2017" " " "MPI"
+.TH MPI_T_pvar_write 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_T_pvar_write \-  Write a performance variable 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Test.3 b/linx64/mpi/mpich/share/man/man3/MPI_Test.3
index a780b8e0..aaa90c73 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Test.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Test.3
@@ -1,22 +1,22 @@
-.TH MPI_Test 3 "11/10/2017" " " "MPI"
+.TH MPI_Test 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Test \-  Tests for the completion of a request 
 .SH SYNOPSIS
 .nf
-int MPI_Test(MPI_Request *request, int *flag, MPI_Status *status)
+int MPI_Test(MPI_Request * request, int *flag, MPI_Status * status)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B request 
-- MPI request (handle) 
+- MPI request (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B flag 
-- true if operation completed (logical) 
+- true if operation completed (logical)
 .PD 1
 .PD 0
 .TP
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Test_cancelled.3 b/linx64/mpi/mpich/share/man/man3/MPI_Test_cancelled.3
index 05487ba1..5f5e9b37 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Test_cancelled.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Test_cancelled.3
@@ -1,22 +1,22 @@
-.TH MPI_Test_cancelled 3 "11/10/2017" " " "MPI"
+.TH MPI_Test_cancelled 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Test_cancelled \-  Tests to see if a request was cancelled 
 .SH SYNOPSIS
 .nf
-int MPI_Test_cancelled(const MPI_Status *status, int *flag)
+int MPI_Test_cancelled(const MPI_Status * status, int *flag)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B status 
-- status object (Status) 
+- status object (Status)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B flag 
-- true if the request was cancelled, false otherwise (logical) 
+- true if the request was cancelled, false otherwise (logical)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Testall.3 b/linx64/mpi/mpich/share/man/man3/MPI_Testall.3
index 3a4beb2e..ae86abfc 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Testall.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Testall.3
@@ -1,28 +1,28 @@
-.TH MPI_Testall 3 "11/10/2017" " " "MPI"
+.TH MPI_Testall 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Testall \-  Tests for the completion of all previously initiated requests 
 .SH SYNOPSIS
 .nf
-int MPI_Testall(int count, MPI_Request array_of_requests[], int *flag, 
-               MPI_Status array_of_statuses[])
+int MPI_Testall(int count, MPI_Request array_of_requests[], int *flag,
+                MPI_Status array_of_statuses[])
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B count 
-- lists length (integer) 
+- lists length (integer)
 .PD 1
 .PD 0
 .TP
 .B array_of_requests 
-- array of requests (array of handles) 
+- array of requests (array of handles)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B flag 
-- True if all requests have completed; false otherwise (logical) 
+- True if all requests have completed; false otherwise (logical)
 .PD 1
 .PD 0
 .TP
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Testany.3 b/linx64/mpi/mpich/share/man/man3/MPI_Testany.3
index 9c513d6b..dee4ffe6 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Testany.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Testany.3
@@ -1,21 +1,21 @@
-.TH MPI_Testany 3 "11/10/2017" " " "MPI"
+.TH MPI_Testany 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Testany \-  Tests for completion of any previdously initiated  requests 
+MPI_Testany \-  Tests for completion of any previdously initiated requests 
 .SH SYNOPSIS
 .nf
 int MPI_Testany(int count, MPI_Request array_of_requests[], int *indx,
-               int *flag, MPI_Status *status)
+                int *flag, MPI_Status * status)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B count 
-- list length (integer) 
+- list length (integer)
 .PD 1
 .PD 0
 .TP
 .B array_of_requests 
-- array of requests (array of handles) 
+- array of requests (array of handles)
 .PD 1
 
 .SH OUTPUT PARAMETERS
@@ -25,12 +25,12 @@ int MPI_Testany(int count, MPI_Request array_of_requests[], int *indx,
 - index of operation that completed, or 
 .I MPI_UNDEFINED
 if none
-completed (integer) 
+completed (integer)
 .PD 1
 .PD 0
 .TP
 .B flag 
-- true if one of the operations is complete (logical) 
+- true if one of the operations is complete (logical)
 .PD 1
 .PD 0
 .TP
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Testsome.3 b/linx64/mpi/mpich/share/man/man3/MPI_Testsome.3
index 7467e6db..a49f394a 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Testsome.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Testsome.3
@@ -1,39 +1,39 @@
-.TH MPI_Testsome 3 "11/10/2017" " " "MPI"
+.TH MPI_Testsome 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Testsome \-  Tests for some given requests to complete 
 .SH SYNOPSIS
 .nf
-int MPI_Testsome(int incount, MPI_Request array_of_requests[], int *outcount, 
-                int array_of_indices[], MPI_Status array_of_statuses[])
+int MPI_Testsome(int incount, MPI_Request array_of_requests[], int *outcount,
+                 int array_of_indices[], MPI_Status array_of_statuses[])
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B incount 
-- length of array_of_requests (integer) 
+- length of array_of_requests (integer)
 .PD 1
 .PD 0
 .TP
 .B array_of_requests 
-- array of requests (array of handles) 
+- array of requests (array of handles)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B outcount 
-- number of completed requests (integer) 
+- number of completed requests (integer)
 .PD 1
 .PD 0
 .TP
 .B array_of_indices 
-- array of indices of operations that 
-completed (array of integers) 
+- array of indices of operations that
+completed (array of integers)
 .PD 1
 .PD 0
 .TP
 .B array_of_statuses 
-- array of status objects for 
+- array of status objects for
 operations that completed (array of Status).  May be 
 .I MPI_STATUSES_IGNORE
 \&.
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Topo_test.3 b/linx64/mpi/mpich/share/man/man3/MPI_Topo_test.3
index b8a12a2b..856d1ad3 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Topo_test.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Topo_test.3
@@ -1,6 +1,6 @@
-.TH MPI_Topo_test 3 "11/10/2017" " " "MPI"
+.TH MPI_Topo_test 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Topo_test \-  Determines the type of topology (if any) associated with a  communicator 
+MPI_Topo_test \-  Determines the type of topology (if any) associated with a communicator 
 .SH SYNOPSIS
 .nf
 int MPI_Topo_test(MPI_Comm comm, int *status)
@@ -9,7 +9,7 @@ int MPI_Topo_test(MPI_Comm comm, int *status)
 .PD 0
 .TP
 .B comm 
-- communicator (handle) 
+- communicator (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_commit.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_commit.3
index 53951a88..94cd4247 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_commit.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_commit.3
@@ -1,15 +1,15 @@
-.TH MPI_Type_commit 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_commit 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_commit \-  Commits the datatype 
 .SH SYNOPSIS
 .nf
-int MPI_Type_commit(MPI_Datatype *datatype)
+int MPI_Type_commit(MPI_Datatype * datatype)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B datatype 
-- datatype (handle) 
+- datatype (handle)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_contiguous.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_contiguous.3
index 209211ea..e8e0da7d 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_contiguous.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_contiguous.3
@@ -1,29 +1,27 @@
-.TH MPI_Type_contiguous 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_contiguous 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_contiguous \-  Creates a contiguous datatype 
 .SH SYNOPSIS
 .nf
-int MPI_Type_contiguous(int count,
-                      MPI_Datatype oldtype,
-                      MPI_Datatype *newtype)
+int MPI_Type_contiguous(int count, MPI_Datatype oldtype, MPI_Datatype * newtype)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B count 
-- replication count (nonnegative integer) 
+- replication count (nonnegative integer)
 .PD 1
 .PD 0
 .TP
 .B oldtype 
-- old datatype (handle) 
+- old datatype (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B newtype 
-- new datatype (handle) 
+- new datatype (handle)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_create_darray.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_create_darray.3
index 85dc1780..5e5864d3 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_create_darray.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_create_darray.3
@@ -1,18 +1,16 @@
-.TH MPI_Type_create_darray 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_create_darray 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_create_darray \-  Create a datatype representing a distributed array 
 .SH SYNOPSIS
 .nf
 int MPI_Type_create_darray(int size,
-                         int rank,
-                         int ndims,
-                         const int array_of_gsizes[],
-                         const int array_of_distribs[],
-                         const int array_of_dargs[],
-                         const int array_of_psizes[],
-                         int order,
-                         MPI_Datatype oldtype,
-                         MPI_Datatype *newtype)
+                           int rank,
+                           int ndims,
+                           const int array_of_gsizes[],
+                           const int array_of_distribs[],
+                           const int array_of_dargs[],
+                           const int array_of_psizes[],
+                           int order, MPI_Datatype oldtype, MPI_Datatype * newtype)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_create_hindexed.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_create_hindexed.3
index 397581f5..a67a9370 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_create_hindexed.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_create_hindexed.3
@@ -1,13 +1,12 @@
-.TH MPI_Type_create_hindexed 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_create_hindexed 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_create_hindexed \-  Create a datatype for an indexed datatype with displacements in bytes 
 .SH SYNOPSIS
 .nf
 int MPI_Type_create_hindexed(int count,
-                           const int array_of_blocklengths[],
-                           const MPI_Aint array_of_displacements[],
-                           MPI_Datatype oldtype,
-                           MPI_Datatype *newtype)
+                             const int array_of_blocklengths[],
+                             const MPI_Aint array_of_displacements[],
+                             MPI_Datatype oldtype, MPI_Datatype * newtype)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_create_hindexed_block.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_create_hindexed_block.3
index b11fdcb8..bcd3e711 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_create_hindexed_block.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_create_hindexed_block.3
@@ -1,12 +1,12 @@
-.TH MPI_Type_create_hindexed_block 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_create_hindexed_block 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_create_hindexed_block \-  Create an hindexed datatype with constant-sized blocks 
 .SH SYNOPSIS
 .nf
 int MPI_Type_create_hindexed_block(int count,
-                                    int blocklength,
-                                    const MPI_Aint array_of_displacements[],
-                                    MPI_Datatype oldtype, MPI_Datatype * newtype)
+                                   int blocklength,
+                                   const MPI_Aint array_of_displacements[],
+                                   MPI_Datatype oldtype, MPI_Datatype * newtype)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_create_hvector.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_create_hvector.3
index 8812aafb..840dbbf2 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_create_hvector.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_create_hvector.3
@@ -1,13 +1,11 @@
-.TH MPI_Type_create_hvector 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_create_hvector 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_create_hvector \-  Create a datatype with a constant stride given in bytes 
 .SH SYNOPSIS
 .nf
 int MPI_Type_create_hvector(int count,
-                          int blocklength,
-                          MPI_Aint stride,
-                          MPI_Datatype oldtype,
-                          MPI_Datatype *newtype)
+                            int blocklength,
+                            MPI_Aint stride, MPI_Datatype oldtype, MPI_Datatype * newtype)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_create_indexed_block.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_create_indexed_block.3
index 5a655b1d..a9b28533 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_create_indexed_block.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_create_indexed_block.3
@@ -1,41 +1,40 @@
-.TH MPI_Type_create_indexed_block 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_create_indexed_block 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_create_indexed_block \-  Create an indexed datatype with constant-sized blocks 
 .SH SYNOPSIS
 .nf
 int MPI_Type_create_indexed_block(int count,
-                               int blocklength,
-                               const int array_of_displacements[],
-                               MPI_Datatype oldtype,
-                               MPI_Datatype *newtype)
+                                  int blocklength,
+                                  const int array_of_displacements[],
+                                  MPI_Datatype oldtype, MPI_Datatype * newtype)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B count 
-- length of array of displacements (integer) 
+- length of array of displacements (integer)
 .PD 1
 .PD 0
 .TP
 .B blocklength 
-- size of block (integer) 
+- size of block (integer)
 .PD 1
 .PD 0
 .TP
 .B array_of_displacements 
-- array of displacements (array of integer) 
+- array of displacements (array of integer)
 .PD 1
 .PD 0
 .TP
 .B oldtype 
-- old datatype (handle) 
+- old datatype (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B newtype 
-- new datatype (handle) 
+- new datatype (handle)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_create_keyval.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_create_keyval.3
index fb8fa15f..91f874ec 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_create_keyval.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_create_keyval.3
@@ -1,34 +1,34 @@
-.TH MPI_Type_create_keyval 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_create_keyval 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_create_keyval \-  Create an attribute keyval for MPI datatypes 
 .SH SYNOPSIS
 .nf
-int MPI_Type_create_keyval(MPI_Type_copy_attr_function *type_copy_attr_fn, 
-                         MPI_Type_delete_attr_function *type_delete_attr_fn,
-                         int *type_keyval, void *extra_state)
+int MPI_Type_create_keyval(MPI_Type_copy_attr_function * type_copy_attr_fn,
+                           MPI_Type_delete_attr_function * type_delete_attr_fn,
+                           int *type_keyval, void *extra_state)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B type_copy_attr_fn 
-- copy callback function for type_keyval (function) 
+- copy callback function for type_keyval (function)
 .PD 1
 .PD 0
 .TP
 .B type_delete_attr_fn 
-- delete callback function for type_keyval (function) 
+- delete callback function for type_keyval (function)
 .PD 1
 .PD 0
 .TP
 .B extra_state 
-- extra state for callback functions 
+- extra state for callback functions
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B type_keyval 
-- key value for future access (integer) 
+- key value for future access (integer)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_create_resized.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_create_resized.3
index 55d4689d..b2953516 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_create_resized.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_create_resized.3
@@ -1,12 +1,10 @@
-.TH MPI_Type_create_resized 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_create_resized 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_create_resized \-  Create a datatype with a new lower bound and extent from an existing datatype 
 .SH SYNOPSIS
 .nf
 int MPI_Type_create_resized(MPI_Datatype oldtype,
-                          MPI_Aint lb,
-                          MPI_Aint extent,
-                          MPI_Datatype *newtype)
+                            MPI_Aint lb, MPI_Aint extent, MPI_Datatype * newtype)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_create_struct.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_create_struct.3
index c521ceed..99423772 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_create_struct.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_create_struct.3
@@ -1,13 +1,12 @@
-.TH MPI_Type_create_struct 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_create_struct 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_create_struct \-  Create an MPI datatype from a general set of datatypes, displacements, and block sizes 
 .SH SYNOPSIS
 .nf
 int MPI_Type_create_struct(int count,
-                         const int array_of_blocklengths[],
-                         const MPI_Aint array_of_displacements[],
-                         const MPI_Datatype array_of_types[],
-                         MPI_Datatype *newtype)
+                           const int array_of_blocklengths[],
+                           const MPI_Aint array_of_displacements[],
+                           const MPI_Datatype array_of_types[], MPI_Datatype * newtype)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_create_subarray.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_create_subarray.3
index 9df9745e..026d29e3 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_create_subarray.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_create_subarray.3
@@ -1,15 +1,13 @@
-.TH MPI_Type_create_subarray 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_create_subarray 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_create_subarray \-  Create a datatype for a subarray of a regular, multidimensional array 
 .SH SYNOPSIS
 .nf
 int MPI_Type_create_subarray(int ndims,
-                           const int array_of_sizes[],
-                           const int array_of_subsizes[],
-                           const int array_of_starts[],
-                           int order,
-                           MPI_Datatype oldtype,
-                           MPI_Datatype *newtype)
+                             const int array_of_sizes[],
+                             const int array_of_subsizes[],
+                             const int array_of_starts[],
+                             int order, MPI_Datatype oldtype, MPI_Datatype * newtype)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_delete_attr.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_delete_attr.3
index 5eadd1ba..4d706b3a 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_delete_attr.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_delete_attr.3
@@ -1,6 +1,6 @@
-.TH MPI_Type_delete_attr 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_delete_attr 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Type_delete_attr \-  Deletes an attribute value associated with a key on  a datatype 
+MPI_Type_delete_attr \-  Deletes an attribute value associated with a key on a datatype 
 .SH SYNOPSIS
 .nf
 int MPI_Type_delete_attr(MPI_Datatype datatype, int type_keyval)
@@ -14,7 +14,7 @@ int MPI_Type_delete_attr(MPI_Datatype datatype, int type_keyval)
 .PD 0
 .TP
 .B type_keyval 
-- The key value of the deleted attribute (integer) 
+- The key value of the deleted attribute (integer)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_dup.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_dup.3
index e7d78859..5050874c 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_dup.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_dup.3
@@ -1,9 +1,13 @@
-.TH MPI_Type_dup 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_dup 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_dup \-  Duplicate a datatype 
 .SH SYNOPSIS
 .nf
-int MPI_Type_dup(MPI_Datatype oldtype, MPI_Datatype *newtype)
+#undef FUNCNAME
+#define FUNCNAME MPI_Type_dup
+#undef FCNAME
+#define FCNAME MPL_QUOTE(FUNCNAME)
+int MPI_Type_dup(MPI_Datatype oldtype, MPI_Datatype * newtype)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
@@ -16,7 +20,7 @@ int MPI_Type_dup(MPI_Datatype oldtype, MPI_Datatype *newtype)
 .PD 0
 .TP
 .B newtype 
-- copy of type (handle) 
+- copy of type (handle)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_extent.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_extent.3
index 159a1121..811af5c4 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_extent.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_extent.3
@@ -1,9 +1,9 @@
-.TH MPI_Type_extent 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_extent 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_extent \-  Returns the extent of a datatype 
 .SH SYNOPSIS
 .nf
-int MPI_Type_extent(MPI_Datatype datatype, MPI_Aint *extent)
+int MPI_Type_extent(MPI_Datatype datatype, MPI_Aint * extent)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_free.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_free.3
index f34f7bd6..a1ad702a 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_free.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_free.3
@@ -1,15 +1,15 @@
-.TH MPI_Type_free 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_free 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_free \-  Frees the datatype 
 .SH SYNOPSIS
 .nf
-int MPI_Type_free(MPI_Datatype *datatype)
+int MPI_Type_free(MPI_Datatype * datatype)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B datatype 
-- datatype that is freed (handle) 
+- datatype that is freed (handle)
 .PD 1
 
 .SH PREDEFINED TYPES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_free_keyval.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_free_keyval.3
index 4a3dcba8..3f2d734d 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_free_keyval.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_free_keyval.3
@@ -1,4 +1,4 @@
-.TH MPI_Type_free_keyval 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_free_keyval 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_free_keyval \-  Frees an attribute key for datatypes 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_get_attr.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_get_attr.3
index 9fba8989..82dbfb89 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_get_attr.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_get_attr.3
@@ -1,10 +1,9 @@
-.TH MPI_Type_get_attr 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_get_attr 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_get_attr \-  Retrieves attribute value by key 
 .SH SYNOPSIS
 .nf
-int MPI_Type_get_attr(MPI_Datatype datatype, int type_keyval, void *attribute_val,
-                     int *flag)
+int MPI_Type_get_attr(MPI_Datatype datatype, int type_keyval, void *attribute_val, int *flag)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
@@ -15,19 +14,19 @@ int MPI_Type_get_attr(MPI_Datatype datatype, int type_keyval, void *attribute_va
 .PD 0
 .TP
 .B type_keyval 
-- key value (integer) 
+- key value (integer)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B attribute_val 
-- attribute value, unless flag = false 
+- attribute value, unless flag = false
 .PD 1
 .PD 0
 .TP
 .B flag 
-- false if no attribute is associated with the key (logical) 
+- false if no attribute is associated with the key (logical)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_get_contents.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_get_contents.3
index 33850703..638340a7 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_get_contents.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_get_contents.3
@@ -1,15 +1,14 @@
-.TH MPI_Type_get_contents 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_get_contents 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_get_contents \-  get type contents 
 .SH SYNOPSIS
 .nf
 int MPI_Type_get_contents(MPI_Datatype datatype,
-                        int max_integers,
-                        int max_addresses,
-                        int max_datatypes,
-                        int array_of_integers[],
-                        MPI_Aint array_of_addresses[],
-                        MPI_Datatype array_of_datatypes[])
+                          int max_integers,
+                          int max_addresses,
+                          int max_datatypes,
+                          int array_of_integers[],
+                          MPI_Aint array_of_addresses[], MPI_Datatype array_of_datatypes[])
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_get_envelope.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_get_envelope.3
index 45c6272b..7fe4af97 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_get_envelope.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_get_envelope.3
@@ -1,13 +1,10 @@
-.TH MPI_Type_get_envelope 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_get_envelope 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_get_envelope \-  get type envelope 
 .SH SYNOPSIS
 .nf
 int MPI_Type_get_envelope(MPI_Datatype datatype,
-                        int *num_integers,
-                        int *num_addresses,
-                        int *num_datatypes,
-                        int *combiner)
+                          int *num_integers, int *num_addresses, int *num_datatypes, int *combiner)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_get_extent.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_get_extent.3
index 05fe7d50..11143f0e 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_get_extent.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_get_extent.3
@@ -1,9 +1,9 @@
-.TH MPI_Type_get_extent 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_get_extent 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_get_extent \-  Get the lower bound and extent for a Datatype 
 .SH SYNOPSIS
 .nf
-int MPI_Type_get_extent(MPI_Datatype datatype, MPI_Aint *lb, MPI_Aint *extent)
+int MPI_Type_get_extent(MPI_Datatype datatype, MPI_Aint * lb, MPI_Aint * extent)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_get_extent_x.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_get_extent_x.3
index 66cc28e4..5efa1757 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_get_extent_x.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_get_extent_x.3
@@ -1,9 +1,9 @@
-.TH MPI_Type_get_extent_x 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_get_extent_x 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_get_extent_x \-  Get the lower bound and extent as MPI_Count values for a Datatype 
 .SH SYNOPSIS
 .nf
-int MPI_Type_get_extent_x(MPI_Datatype datatype, MPI_Count *lb, MPI_Count *extent)
+int MPI_Type_get_extent_x(MPI_Datatype datatype, MPI_Count * lb, MPI_Count * extent)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_get_name.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_get_name.3
index d4be9a4e..393cb463 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_get_name.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_get_name.3
@@ -1,4 +1,4 @@
-.TH MPI_Type_get_name 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_get_name 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_get_name \-  Get the print name for a datatype 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_get_true_extent.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_get_true_extent.3
index eb810aec..d5b40edd 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_get_true_extent.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_get_true_extent.3
@@ -1,10 +1,9 @@
-.TH MPI_Type_get_true_extent 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_get_true_extent 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_get_true_extent \-  Get the true lower bound and extent for a datatype 
 .SH SYNOPSIS
 .nf
-int MPI_Type_get_true_extent(MPI_Datatype datatype, MPI_Aint *true_lb,
-                           MPI_Aint *true_extent)
+int MPI_Type_get_true_extent(MPI_Datatype datatype, MPI_Aint * true_lb, MPI_Aint * true_extent)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_get_true_extent_x.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_get_true_extent_x.3
index 9a19fe8c..17169174 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_get_true_extent_x.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_get_true_extent_x.3
@@ -1,9 +1,9 @@
-.TH MPI_Type_get_true_extent_x 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_get_true_extent_x 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_get_true_extent_x \-  Get the true lower bound and extent as MPI_Count values for a datatype 
 .SH SYNOPSIS
 .nf
-int MPI_Type_get_true_extent_x(MPI_Datatype datatype, MPI_Count *true_lb, MPI_Count *true_extent)
+int MPI_Type_get_true_extent_x(MPI_Datatype datatype, MPI_Count * true_lb, MPI_Count * true_extent)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_hindexed.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_hindexed.3
index 947f38f5..8f14096d 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_hindexed.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_hindexed.3
@@ -1,13 +1,12 @@
-.TH MPI_Type_hindexed 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_hindexed 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_hindexed \-  Creates an indexed datatype with offsets in bytes 
 .SH SYNOPSIS
 .nf
 int MPI_Type_hindexed(int count,
-                     int *array_of_blocklengths,
-                     MPI_Aint *array_of_displacements,
-                     MPI_Datatype oldtype,
-                     MPI_Datatype *newtype)
+                      int *array_of_blocklengths,
+                      MPI_Aint * array_of_displacements,
+                      MPI_Datatype oldtype, MPI_Datatype * newtype)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
@@ -35,7 +34,7 @@ int MPI_Type_hindexed(int count,
 .PD 0
 .TP
 .B newtype 
-- new datatype (handle) 
+- new datatype (handle)
 .PD 1
 
 .SH DEPRECATED FUNCTION
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_hvector.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_hvector.3
index bf2f816c..b1281e46 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_hvector.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_hvector.3
@@ -1,35 +1,32 @@
-.TH MPI_Type_hvector 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_hvector 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_hvector \-  type_hvector 
 .SH SYNOPSIS
 .nf
 int MPI_Type_hvector(int count,
-                    int blocklength,
-                    MPI_Aint stride,
-                    MPI_Datatype oldtype,
-                    MPI_Datatype *newtype)
+                     int blocklength, MPI_Aint stride, MPI_Datatype oldtype, MPI_Datatype * newtype)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B count 
-- number of blocks (nonnegative integer) 
+- number of blocks (nonnegative integer)
 .PD 1
 .PD 0
 .TP
 .B blocklength 
-- number of elements in each block 
+- number of elements in each block
 (nonnegative integer)
 .PD 1
 .PD 0
 .TP
 .B stride 
-- number of bytes between start of each block (integer) 
+- number of bytes between start of each block (integer)
 .PD 1
 .PD 0
 .TP
 .B oldtype 
-- old datatype (handle) 
+- old datatype (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_indexed.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_indexed.3
index 99564dca..249e975a 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_indexed.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_indexed.3
@@ -1,13 +1,12 @@
-.TH MPI_Type_indexed 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_indexed 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_indexed \-  Creates an indexed datatype 
 .SH SYNOPSIS
 .nf
 int MPI_Type_indexed(int count,
-                    const int *array_of_blocklengths,
-                    const int *array_of_displacements,
-                    MPI_Datatype oldtype,
-                    MPI_Datatype *newtype)
+                     const int *array_of_blocklengths,
+                     const int *array_of_displacements,
+                     MPI_Datatype oldtype, MPI_Datatype * newtype)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
@@ -36,7 +35,7 @@ integers)
 .PD 0
 .TP
 .B newtype 
-- new datatype (handle) 
+- new datatype (handle)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_lb.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_lb.3
index 643c3e4d..1f0538a8 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_lb.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_lb.3
@@ -1,9 +1,9 @@
-.TH MPI_Type_lb 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_lb 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_lb \-  Returns the lower-bound of a datatype 
 .SH SYNOPSIS
 .nf
-int MPI_Type_lb(MPI_Datatype datatype, MPI_Aint *displacement)
+int MPI_Type_lb(MPI_Datatype datatype, MPI_Aint * displacement)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_match_size.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_match_size.3
index d6f69a1b..74e262a3 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_match_size.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_match_size.3
@@ -1,20 +1,20 @@
-.TH MPI_Type_match_size 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_match_size 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_match_size \-  Find an MPI datatype matching a specified size 
 .SH SYNOPSIS
 .nf
-int MPI_Type_match_size(int typeclass, int size, MPI_Datatype *datatype)
+int MPI_Type_match_size(int typeclass, int size, MPI_Datatype * datatype)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B typeclass 
-- generic type specifier (integer) 
+- generic type specifier (integer)
 .PD 1
 .PD 0
 .TP
 .B size 
-- size, in bytes, of representation (integer) 
+- size, in bytes, of representation (integer)
 .PD 1
 
 .SH OUTPUT PARAMETERS
@@ -34,7 +34,7 @@ and
 .I MPI_TYPECLASS_COMPLEX
 , corresponding to the desired typeclass.
 The function returns an MPI datatype matching a local variable of type
-.I ( typeclass, size )
+.I (typeclass, size)
 \&.
 
 
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_set_attr.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_set_attr.3
index b63b253b..12506340 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_set_attr.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_set_attr.3
@@ -1,4 +1,4 @@
-.TH MPI_Type_set_attr 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_set_attr 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_set_attr \-  Stores attribute value associated with a key 
 .SH SYNOPSIS
@@ -21,7 +21,7 @@ int MPI_Type_set_attr(MPI_Datatype datatype, int type_keyval, void *attribute_va
 .PD 0
 .TP
 .B attribute_val 
-- attribute value 
+- attribute value
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_set_name.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_set_name.3
index 6a5a5358..cec0bcff 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_set_name.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_set_name.3
@@ -1,4 +1,4 @@
-.TH MPI_Type_set_name 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_set_name 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_set_name \-  set datatype name 
 .SH SYNOPSIS
@@ -14,7 +14,7 @@ int MPI_Type_set_name(MPI_Datatype datatype, const char *type_name)
 .PD 0
 .TP
 .B type_name 
-- the character string which is remembered as the name (string) 
+- the character string which is remembered as the name (string)
 .PD 1
 
 .SH NOTES FOR FORTRAN
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_size.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_size.3
index 786232dc..452e28fc 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_size.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_size.3
@@ -1,4 +1,4 @@
-.TH MPI_Type_size 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_size 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_size \-  Return the number of bytes occupied by entries in the datatype 
 .SH SYNOPSIS
@@ -9,14 +9,14 @@ int MPI_Type_size(MPI_Datatype datatype, int *size)
 .PD 0
 .TP
 .B datatype 
-- datatype (handle) 
+- datatype (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B size 
-- datatype size (integer) 
+- datatype size (integer)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_size_x.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_size_x.3
index 83e89647..e22674ca 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_size_x.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_size_x.3
@@ -1,9 +1,9 @@
-.TH MPI_Type_size_x 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_size_x 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_size_x \-  Return the number of bytes occupied by entries in the datatype 
 .SH SYNOPSIS
 .nf
-int MPI_Type_size_x(MPI_Datatype datatype, MPI_Count *size)
+int MPI_Type_size_x(MPI_Datatype datatype, MPI_Count * size)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_struct.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_struct.3
index 95e40229..5a045c64 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_struct.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_struct.3
@@ -1,21 +1,20 @@
-.TH MPI_Type_struct 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_struct 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_struct \-  Creates a struct datatype 
 .SH SYNOPSIS
 .nf
 int MPI_Type_struct(int count,
-                   int *array_of_blocklengths,
-                   MPI_Aint *array_of_displacements,
-                   MPI_Datatype *array_of_types,
-                   MPI_Datatype *newtype)
+                    int *array_of_blocklengths,
+                    MPI_Aint * array_of_displacements,
+                    MPI_Datatype * array_of_types, MPI_Datatype * newtype)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B count 
-- number of blocks (integer) -- also number of 
+- number of blocks (integer) -- also number of
 entries in arrays array_of_types ,
-array_of_displacements  and array_of_blocklengths  
+array_of_displacements  and array_of_blocklengths
 .PD 1
 .PD 0
 .TP
@@ -31,14 +30,14 @@ array_of_displacements  and array_of_blocklengths
 .TP
 .B array_of_types 
 - type of elements in each block (array
-of handles to datatype objects) 
+of handles to datatype objects)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B newtype 
-- new datatype (handle) 
+- new datatype (handle)
 .PD 1
 
 .SH DEPRECATED FUNCTION
@@ -101,7 +100,7 @@ for the structure foo
 blen[0] = 1; array_of_displacements[0] = 0; oldtypes[0] = MPI_INT;
 blen[1] = 1; array_of_displacements[1] = &foo.b - &foo; oldtypes[1] = MPI_CHAR;
 blen[2] = 1; array_of_displacements[2] = sizeof(foo); oldtypes[2] = MPI_UB;
-MPI_Type_struct( 3, blen, array_of_displacements, oldtypes, &newtype );
+MPI_Type_struct(3, blen, array_of_displacements, oldtypes, &newtype);
 .fi
 
 
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_ub.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_ub.3
index d81a7d7e..7947f382 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_ub.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_ub.3
@@ -1,9 +1,9 @@
-.TH MPI_Type_ub 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_ub 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_ub \-  Returns the upper bound of a datatype 
 .SH SYNOPSIS
 .nf
-int MPI_Type_ub(MPI_Datatype datatype, MPI_Aint *displacement)
+int MPI_Type_ub(MPI_Datatype datatype, MPI_Aint * displacement)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Type_vector.3 b/linx64/mpi/mpich/share/man/man3/MPI_Type_vector.3
index 24660031..e2233da4 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Type_vector.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Type_vector.3
@@ -1,24 +1,21 @@
-.TH MPI_Type_vector 3 "11/10/2017" " " "MPI"
+.TH MPI_Type_vector 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Type_vector \-  Creates a vector (strided) datatype 
 .SH SYNOPSIS
 .nf
 int MPI_Type_vector(int count,
-                   int blocklength,
-                   int stride, 
-                   MPI_Datatype oldtype,
-                   MPI_Datatype *newtype)
+                    int blocklength, int stride, MPI_Datatype oldtype, MPI_Datatype * newtype)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B count 
-- number of blocks (nonnegative integer) 
+- number of blocks (nonnegative integer)
 .PD 1
 .PD 0
 .TP
 .B blocklength 
-- number of elements in each block 
+- number of elements in each block
 (nonnegative integer)
 .PD 1
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Unpack.3 b/linx64/mpi/mpich/share/man/man3/MPI_Unpack.3
index 4b233259..84e548d2 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Unpack.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Unpack.3
@@ -1,11 +1,10 @@
-.TH MPI_Unpack 3 "11/10/2017" " " "MPI"
+.TH MPI_Unpack 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Unpack \-  Unpack a buffer according to a datatype into contiguous memory 
 .SH SYNOPSIS
 .nf
 int MPI_Unpack(const void *inbuf, int insize, int *position,
-               void *outbuf, int outcount, MPI_Datatype datatype,
-               MPI_Comm comm)
+               void *outbuf, int outcount, MPI_Datatype datatype, MPI_Comm comm)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Unpack_external.3 b/linx64/mpi/mpich/share/man/man3/MPI_Unpack_external.3
index 4b41423c..408d12ac 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Unpack_external.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Unpack_external.3
@@ -1,15 +1,12 @@
-.TH MPI_Unpack_external 3 "11/10/2017" " " "MPI"
+.TH MPI_Unpack_external 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Unpack_external \-  Unpack a buffer (packed with MPI_Pack_external) according to a datatype into contiguous memory 
 .SH SYNOPSIS
 .nf
 int MPI_Unpack_external(const char datarep[],
-                      const void *inbuf,
-                      MPI_Aint insize,
-                      MPI_Aint *position,
-                      void *outbuf,
-                      int outcount,
-                      MPI_Datatype datatype)
+                        const void *inbuf,
+                        MPI_Aint insize,
+                        MPI_Aint * position, void *outbuf, int outcount, MPI_Datatype datatype)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Unpublish_name.3 b/linx64/mpi/mpich/share/man/man3/MPI_Unpublish_name.3
index efe74d7c..d3d6d69a 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Unpublish_name.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Unpublish_name.3
@@ -1,6 +1,6 @@
-.TH MPI_Unpublish_name 3 "11/10/2017" " " "MPI"
+.TH MPI_Unpublish_name 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Unpublish_name \-  Unpublish a service name published with  MPI_Publish_name 
+MPI_Unpublish_name \-  Unpublish a service name published with MPI_Publish_name 
 .SH SYNOPSIS
 .nf
 int MPI_Unpublish_name(const char *service_name, MPI_Info info, const char *port_name)
@@ -9,17 +9,17 @@ int MPI_Unpublish_name(const char *service_name, MPI_Info info, const char *port
 .PD 0
 .TP
 .B service_name 
-- a service name (string) 
+- a service name (string)
 .PD 1
 .PD 0
 .TP
 .B info 
-- implementation-specific information (handle) 
+- implementation-specific information (handle)
 .PD 1
 .PD 0
 .TP
 .B port_name 
-- a port name (string) 
+- a port name (string)
 .PD 1
 
 
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Wait.3 b/linx64/mpi/mpich/share/man/man3/MPI_Wait.3
index 60e033d0..0207ba2f 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Wait.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Wait.3
@@ -1,15 +1,15 @@
-.TH MPI_Wait 3 "11/10/2017" " " "MPI"
+.TH MPI_Wait 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Wait \-  Waits for an MPI request to complete 
 .SH SYNOPSIS
 .nf
-int MPI_Wait(MPI_Request *request, MPI_Status *status)
+int MPI_Wait(MPI_Request * request, MPI_Status * status)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B request 
-- request (handle) 
+- request (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Waitall.3 b/linx64/mpi/mpich/share/man/man3/MPI_Waitall.3
index c559e577..0f228102 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Waitall.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Waitall.3
@@ -1,16 +1,15 @@
-.TH MPI_Waitall 3 "11/10/2017" " " "MPI"
+.TH MPI_Waitall 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Waitall \-  Waits for all given MPI Requests to complete 
 .SH SYNOPSIS
 .nf
-int MPI_Waitall(int count, MPI_Request array_of_requests[], 
-               MPI_Status array_of_statuses[])
+int MPI_Waitall(int count, MPI_Request array_of_requests[], MPI_Status array_of_statuses[])
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B count 
-- list length (integer) 
+- list length (integer)
 .PD 1
 .PD 0
 .TP
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Waitany.3 b/linx64/mpi/mpich/share/man/man3/MPI_Waitany.3
index df14c293..b3427ba9 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Waitany.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Waitany.3
@@ -1,21 +1,20 @@
-.TH MPI_Waitany 3 "11/10/2017" " " "MPI"
+.TH MPI_Waitany 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Waitany \-  Waits for any specified MPI Request to complete 
 .SH SYNOPSIS
 .nf
-int MPI_Waitany(int count, MPI_Request array_of_requests[], int *indx,
-               MPI_Status *status)
+int MPI_Waitany(int count, MPI_Request array_of_requests[], int *indx, MPI_Status * status)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B count 
-- list length (integer) 
+- list length (integer)
 .PD 1
 .PD 0
 .TP
 .B array_of_requests 
-- array of requests (array of handles) 
+- array of requests (array of handles)
 .PD 1
 
 .SH OUTPUT PARAMETERS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Waitsome.3 b/linx64/mpi/mpich/share/man/man3/MPI_Waitsome.3
index 1a6529c9..fdeb1faf 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Waitsome.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Waitsome.3
@@ -1,40 +1,39 @@
-.TH MPI_Waitsome 3 "11/10/2017" " " "MPI"
+.TH MPI_Waitsome 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Waitsome \-  Waits for some given MPI Requests to complete 
 .SH SYNOPSIS
 .nf
-int MPI_Waitsome(int incount, MPI_Request array_of_requests[], 
-                int *outcount, int array_of_indices[],
-                MPI_Status array_of_statuses[])
+int MPI_Waitsome(int incount, MPI_Request array_of_requests[],
+                 int *outcount, int array_of_indices[], MPI_Status array_of_statuses[])
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B incount 
-- length of array_of_requests (integer) 
+- length of array_of_requests (integer)
 .PD 1
 .PD 0
 .TP
 .B array_of_requests 
-- array of requests (array of handles) 
+- array of requests (array of handles)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B outcount 
-- number of completed requests (integer) 
+- number of completed requests (integer)
 .PD 1
 .PD 0
 .TP
 .B array_of_indices 
-- array of indices of operations that 
-completed (array of integers) 
+- array of indices of operations that
+completed (array of integers)
 .PD 1
 .PD 0
 .TP
 .B array_of_statuses 
-- array of status objects for 
+- array of status objects for
 operations that completed (array of Status).  May be 
 .I MPI_STATUSES_IGNORE
 \&.
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_allocate.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_allocate.3
index a8e65ca1..1f9e9866 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_allocate.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_allocate.3
@@ -1,10 +1,10 @@
-.TH MPI_Win_allocate 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_allocate 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_allocate \-  Create and allocate an MPI Window object for one-sided communication. 
 .SH SYNOPSIS
 .nf
-int MPI_Win_allocate(MPI_Aint size, int disp_unit, MPI_Info info, 
-                  MPI_Comm comm, void *baseptr, MPI_Win *win)
+int MPI_Win_allocate(MPI_Aint size, int disp_unit, MPI_Info info,
+                     MPI_Comm comm, void *baseptr, MPI_Win * win)
 .fi
 
 This is a collective call executed by all processes in the group of comm. On
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_allocate_shared.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_allocate_shared.3
index cd21d4bf..e587a8f5 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_allocate_shared.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_allocate_shared.3
@@ -1,10 +1,10 @@
-.TH MPI_Win_allocate_shared 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_allocate_shared 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_allocate_shared \-  Create an MPI Window object for one-sided communication and shared memory access, and allocate memory at each process. 
 .SH SYNOPSIS
 .nf
 int MPI_Win_allocate_shared(MPI_Aint size, int disp_unit, MPI_Info info, MPI_Comm comm,
-                             void *baseptr, MPI_Win *win)
+                            void *baseptr, MPI_Win * win)
 .fi
 This is a collective call executed by all processes in the group of comm. On
 each process i, it allocates memory of at least size bytes that is shared among
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_attach.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_attach.3
index 9f69c60e..07396bea 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_attach.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_attach.3
@@ -1,4 +1,4 @@
-.TH MPI_Win_attach 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_attach 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_attach \-  Attach memory to a dynamic window. 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_call_errhandler.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_call_errhandler.3
index 17b2c892..f9c46b90 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_call_errhandler.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_call_errhandler.3
@@ -1,6 +1,6 @@
-.TH MPI_Win_call_errhandler 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_call_errhandler 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Win_call_errhandler \-  Call the error handler installed on a  window object 
+MPI_Win_call_errhandler \-  Call the error handler installed on a window object 
 .SH SYNOPSIS
 .nf
 int MPI_Win_call_errhandler(MPI_Win win, int errorcode)
@@ -9,12 +9,12 @@ int MPI_Win_call_errhandler(MPI_Win win, int errorcode)
 .PD 0
 .TP
 .B win 
-- window with error handler (handle) 
+- window with error handler (handle)
 .PD 1
 .PD 0
 .TP
 .B errorcode 
-- error code (integer) 
+- error code (integer)
 .PD 1
 
 .SH NOTE
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_complete.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_complete.3
index 15f0510b..3cf9ace7 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_complete.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_complete.3
@@ -1,4 +1,4 @@
-.TH MPI_Win_complete 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_complete 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_complete \-  Completes an RMA operations begun after an MPI_Win_start. 
 .SH SYNOPSIS
@@ -9,7 +9,7 @@ int MPI_Win_complete(MPI_Win win)
 .PD 0
 .TP
 .B win 
-- window object (handle) 
+- window object (handle)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_create.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_create.3
index 485ec496..8e5ffac6 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_create.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_create.3
@@ -1,10 +1,10 @@
-.TH MPI_Win_create 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_create 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_create \-  Create an MPI Window object for one-sided communication 
 .SH SYNOPSIS
 .nf
-int MPI_Win_create(void *base, MPI_Aint size, int disp_unit, MPI_Info info, 
-                  MPI_Comm comm, MPI_Win *win)
+int MPI_Win_create(void *base, MPI_Aint size, int disp_unit, MPI_Info info,
+                   MPI_Comm comm, MPI_Win * win)
 .fi
 
 This is a collective call executed by all processes in the group of comm. It
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_create_dynamic.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_create_dynamic.3
index 56e096af..f109fffe 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_create_dynamic.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_create_dynamic.3
@@ -1,9 +1,9 @@
-.TH MPI_Win_create_dynamic 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_create_dynamic 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_create_dynamic \-  Create an MPI Window object for one-sided communication.  This window allows memory to be dynamically exposed and un-exposed for RMA operations. 
 .SH SYNOPSIS
 .nf
-int MPI_Win_create_dynamic(MPI_Info info, MPI_Comm comm, MPI_Win *win)
+int MPI_Win_create_dynamic(MPI_Info info, MPI_Comm comm, MPI_Win * win)
 .fi
 
 This is a collective call executed by all processes in the group of comm. It
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_create_errhandler.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_create_errhandler.3
index deaa5737..ed4d2145 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_create_errhandler.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_create_errhandler.3
@@ -1,10 +1,10 @@
-.TH MPI_Win_create_errhandler 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_create_errhandler 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_create_errhandler \-  Create an error handler for use with MPI window objects 
 .SH SYNOPSIS
 .nf
-int MPI_Win_create_errhandler(MPI_Win_errhandler_function *win_errhandler_fn,
-                            MPI_Errhandler *errhandler)
+int MPI_Win_create_errhandler(MPI_Win_errhandler_function * win_errhandler_fn,
+                              MPI_Errhandler * errhandler)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
@@ -17,7 +17,7 @@ int MPI_Win_create_errhandler(MPI_Win_errhandler_function *win_errhandler_fn,
 .PD 0
 .TP
 .B errhandler 
-- MPI error handler (handle) 
+- MPI error handler (handle)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_create_keyval.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_create_keyval.3
index 403930d0..06b9fc55 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_create_keyval.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_create_keyval.3
@@ -1,34 +1,34 @@
-.TH MPI_Win_create_keyval 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_create_keyval 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_create_keyval \-  Create an attribute keyval for MPI window objects 
 .SH SYNOPSIS
 .nf
-int MPI_Win_create_keyval(MPI_Win_copy_attr_function *win_copy_attr_fn, 
-                        MPI_Win_delete_attr_function *win_delete_attr_fn, 
-                        int *win_keyval, void *extra_state)
+int MPI_Win_create_keyval(MPI_Win_copy_attr_function * win_copy_attr_fn,
+                          MPI_Win_delete_attr_function * win_delete_attr_fn,
+                          int *win_keyval, void *extra_state)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B win_copy_attr_fn 
-- copy callback function for win_keyval (function) 
+- copy callback function for win_keyval (function)
 .PD 1
 .PD 0
 .TP
 .B win_delete_attr_fn 
-- delete callback function for win_keyval (function) 
+- delete callback function for win_keyval (function)
 .PD 1
 .PD 0
 .TP
 .B extra_state 
-- extra state for callback functions 
+- extra state for callback functions
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B win_keyval 
-- key value for future access (integer) 
+- key value for future access (integer)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_delete_attr.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_delete_attr.3
index 58ac0aaf..ec75437e 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_delete_attr.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_delete_attr.3
@@ -1,6 +1,6 @@
-.TH MPI_Win_delete_attr 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_delete_attr 3 "6/5/2019" " " "MPI"
 .SH NAME
-MPI_Win_delete_attr \-  Deletes an attribute value associated with a key on  a datatype 
+MPI_Win_delete_attr \-  Deletes an attribute value associated with a key on a datatype 
 .SH SYNOPSIS
 .nf
 int MPI_Win_delete_attr(MPI_Win win, int win_keyval)
@@ -9,12 +9,12 @@ int MPI_Win_delete_attr(MPI_Win win, int win_keyval)
 .PD 0
 .TP
 .B win 
-- window from which the attribute is deleted (handle) 
+- window from which the attribute is deleted (handle)
 .PD 1
 .PD 0
 .TP
 .B win_keyval 
-- key value (integer) 
+- key value (integer)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_detach.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_detach.3
index 8a88456e..448a9dbf 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_detach.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_detach.3
@@ -1,4 +1,4 @@
-.TH MPI_Win_detach 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_detach 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_detach \-  Detach memory from a dynamic window 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_fence.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_fence.3
index bc739435..63d957d7 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_fence.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_fence.3
@@ -1,4 +1,4 @@
-.TH MPI_Win_fence 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_fence 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_fence \-  Perform an MPI fence synchronization on a MPI window 
 .SH SYNOPSIS
@@ -9,12 +9,12 @@ int MPI_Win_fence(int assert, MPI_Win win)
 .PD 0
 .TP
 .B assert 
-- program assertion (integer) 
+- program assertion (integer)
 .PD 1
 .PD 0
 .TP
 .B win 
-- window object (handle) 
+- window object (handle)
 .PD 1
 
 .SH NOTES
@@ -31,28 +31,28 @@ are:
 .PD 0
 .TP
 .B MPI_MODE_NOSTORE 
-- the local window was not updated by local stores 
-(or local get or receive calls) since last synchronization. 
+- the local window was not updated by local stores
+(or local get or receive calls) since last synchronization.
 .PD 1
 .PD 0
 .TP
 .B MPI_MODE_NOPUT 
-- the local window will not be updated by put or accumulate 
-calls after the fence call, until the ensuing (fence) synchronization. 
+- the local window will not be updated by put or accumulate
+calls after the fence call, until the ensuing (fence) synchronization.
 .PD 1
 .PD 0
 .TP
 .B MPI_MODE_NOPRECEDE 
-- the fence does not complete any sequence of locally 
-issued RMA calls. If this assertion is given by any process in the window 
-group, then it must be given by all processes in the group. 
+- the fence does not complete any sequence of locally
+issued RMA calls. If this assertion is given by any process in the window
+group, then it must be given by all processes in the group.
 .PD 1
 .PD 0
 .TP
 .B MPI_MODE_NOSUCCEED 
-- the fence does not start any sequence of locally 
-issued RMA calls. If the assertion is given by any process in the window 
-group, then it must be given by all processes in the group. 
+- the fence does not start any sequence of locally
+issued RMA calls. If the assertion is given by any process in the window
+group, then it must be given by all processes in the group.
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_flush.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_flush.3
index 304b1324..69dc9664 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_flush.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_flush.3
@@ -1,4 +1,4 @@
-.TH MPI_Win_flush 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_flush 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_flush \-  Complete all outstanding RMA operations at the given target. 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_flush_all.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_flush_all.3
index ca71eaec..2915e16c 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_flush_all.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_flush_all.3
@@ -1,4 +1,4 @@
-.TH MPI_Win_flush_all 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_flush_all 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_flush_all \-  Complete all outstanding RMA operations at all targets 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_flush_local.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_flush_local.3
index c289f978..35755ac6 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_flush_local.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_flush_local.3
@@ -1,4 +1,4 @@
-.TH MPI_Win_flush_local 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_flush_local 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_flush_local \-  Complete locally all outstanding RMA operations at the given target 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_flush_local_all.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_flush_local_all.3
index bebaa883..95bfa900 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_flush_local_all.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_flush_local_all.3
@@ -1,4 +1,4 @@
-.TH MPI_Win_flush_local_all 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_flush_local_all 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_flush_local_all \-  Complete locally all outstanding RMA operations at all targets 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_free.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_free.3
index 8bd302ee..655e13d1 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_free.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_free.3
@@ -1,15 +1,15 @@
-.TH MPI_Win_free 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_free 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_free \-  Free an MPI RMA window 
 .SH SYNOPSIS
 .nf
-int MPI_Win_free(MPI_Win *win)
+int MPI_Win_free(MPI_Win * win)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B win 
-- window object (handle) 
+- window object (handle)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_free_keyval.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_free_keyval.3
index c85fb61e..49d8098e 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_free_keyval.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_free_keyval.3
@@ -1,4 +1,4 @@
-.TH MPI_Win_free_keyval 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_free_keyval 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_free_keyval \-  Frees an attribute key for MPI RMA windows 
 .SH SYNOPSIS
@@ -9,7 +9,7 @@ int MPI_Win_free_keyval(int *win_keyval)
 .PD 0
 .TP
 .B win_keyval 
-- key value (integer) 
+- key value (integer)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_get_attr.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_get_attr.3
index 7a97f1bc..8b96bd6f 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_get_attr.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_get_attr.3
@@ -1,33 +1,32 @@
-.TH MPI_Win_get_attr 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_get_attr 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_get_attr \-  Get attribute cached on an MPI window object 
 .SH SYNOPSIS
 .nf
-int MPI_Win_get_attr(MPI_Win win, int win_keyval, void *attribute_val, 
-                    int *flag)
+int MPI_Win_get_attr(MPI_Win win, int win_keyval, void *attribute_val, int *flag)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B win 
-- window to which the attribute is attached (handle) 
+- window to which the attribute is attached (handle)
 .PD 1
 .PD 0
 .TP
 .B win_keyval 
-- key value (integer) 
+- key value (integer)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B attribute_val 
-- attribute value, unless flag is false 
+- attribute value, unless flag is false
 .PD 1
 .PD 0
 .TP
 .B flag 
-- false if no attribute is associated with the key (logical) 
+- false if no attribute is associated with the key (logical)
 .PD 1
 
 .SH NOTES
@@ -36,17 +35,17 @@ The following attributes are predefined for all MPI Window objects:
 .PD 0
 .TP
 .B MPI_WIN_BASE 
-- window base address. 
+- window base address.
 .PD 1
 .PD 0
 .TP
 .B MPI_WIN_SIZE 
-- window size, in bytes. 
+- window size, in bytes.
 .PD 1
 .PD 0
 .TP
 .B MPI_WIN_DISP_UNIT 
-- displacement unit associated with the window. 
+- displacement unit associated with the window.
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_get_errhandler.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_get_errhandler.3
index 2fce414c..48723d2e 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_get_errhandler.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_get_errhandler.3
@@ -1,22 +1,22 @@
-.TH MPI_Win_get_errhandler 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_get_errhandler 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_get_errhandler \-  Get the error handler for the MPI RMA window 
 .SH SYNOPSIS
 .nf
-int MPI_Win_get_errhandler(MPI_Win win, MPI_Errhandler *errhandler)
+int MPI_Win_get_errhandler(MPI_Win win, MPI_Errhandler * errhandler)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B win 
-- window (handle) 
+- window (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B errhandler 
-- error handler currently associated with window (handle) 
+- error handler currently associated with window (handle)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_get_group.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_get_group.3
index 0bdebdf5..da28b313 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_get_group.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_get_group.3
@@ -1,22 +1,22 @@
-.TH MPI_Win_get_group 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_get_group 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_get_group \-  Get the MPI Group of the window object 
 .SH SYNOPSIS
 .nf
-int MPI_Win_get_group(MPI_Win win, MPI_Group *group)
+int MPI_Win_get_group(MPI_Win win, MPI_Group * group)
 .fi
 .SH INPUT PARAMETERS
 .PD 0
 .TP
 .B win 
-- window object (handle) 
+- window object (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B group 
-- group of processes which share access to the window (handle) 
+- group of processes which share access to the window (handle)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_get_info.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_get_info.3
index 553cb085..5b3f41a2 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_get_info.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_get_info.3
@@ -1,9 +1,9 @@
-.TH MPI_Win_get_info 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_get_info 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_get_info \-  Returns a new info object containing the hints of the window associated with win. 
 .SH SYNOPSIS
 .nf
-int MPI_Win_get_info(MPI_Win win, MPI_Info *info_used)
+int MPI_Win_get_info(MPI_Win win, MPI_Info * info_used)
 .fi
 
 The current setting of all hints actually used by the system related to this
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_get_name.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_get_name.3
index d3df98e7..6f1ed623 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_get_name.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_get_name.3
@@ -1,4 +1,4 @@
-.TH MPI_Win_get_name 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_get_name 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_get_name \-  Get the print name associated with the MPI RMA window 
 .SH SYNOPSIS
@@ -9,20 +9,20 @@ int MPI_Win_get_name(MPI_Win win, char *win_name, int *resultlen)
 .PD 0
 .TP
 .B win 
-- window whose name is to be returned (handle) 
+- window whose name is to be returned (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B win_name 
-- the name previously stored on the window, or a empty string if 
-no such name exists (string) 
+- the name previously stored on the window, or a empty string if
+no such name exists (string)
 .PD 1
 .PD 0
 .TP
 .B resultlen 
-- length of returned name (integer) 
+- length of returned name (integer)
 .PD 1
 
 
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_lock.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_lock.3
index 0bbcb601..a9fdff56 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_lock.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_lock.3
@@ -1,4 +1,4 @@
-.TH MPI_Win_lock 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_lock 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_lock \-  Begin an RMA access epoch at the target process. 
 .SH SYNOPSIS
@@ -9,7 +9,7 @@ int MPI_Win_lock(int lock_type, int rank, int assert, MPI_Win win)
 .PD 0
 .TP
 .B lock_type 
-- Indicates whether other processes may access the target 
+- Indicates whether other processes may access the target
 window at the same time (if 
 .I MPI_LOCK_SHARED
 ) or not (
@@ -19,18 +19,18 @@ window at the same time (if
 .PD 0
 .TP
 .B rank 
-- rank of locked window (nonnegative integer) 
+- rank of locked window (nonnegative integer)
 .PD 1
 .PD 0
 .TP
 .B assert 
 - Used to optimize this call; zero may be used as a default.
-See notes. (integer) 
+See notes. (integer)
 .PD 1
 .PD 0
 .TP
 .B win 
-- window object (handle) 
+- window object (handle)
 .PD 1
 
 .SH NOTES
@@ -60,11 +60,11 @@ are:
 .PD 0
 .TP
 .B MPI_MODE_NOCHECK 
-- no other process holds, or will attempt to acquire a 
-conflicting lock, while the caller holds the window lock. This is useful 
-when mutual exclusion is achieved by other means, but the coherence 
-operations that may be attached to the lock and unlock calls are still 
-required. 
+- no other process holds, or will attempt to acquire a
+conflicting lock, while the caller holds the window lock. This is useful
+when mutual exclusion is achieved by other means, but the coherence
+operations that may be attached to the lock and unlock calls are still
+required.
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_lock_all.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_lock_all.3
index 9c2180e1..9b9ffe7d 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_lock_all.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_lock_all.3
@@ -1,4 +1,4 @@
-.TH MPI_Win_lock_all 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_lock_all 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_lock_all \-  Begin an RMA access epoch at all processes on the given window. 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_post.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_post.3
index 14de915e..93181250 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_post.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_post.3
@@ -1,4 +1,4 @@
-.TH MPI_Win_post 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_post 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_post \-  Start an RMA exposure epoch 
 .SH SYNOPSIS
@@ -9,18 +9,18 @@ int MPI_Win_post(MPI_Group group, int assert, MPI_Win win)
 .PD 0
 .TP
 .B group 
-- group of origin processes (handle) 
+- group of origin processes (handle)
 .PD 1
 .PD 0
 .TP
 .B assert 
 - Used to optimize this call; zero may be used as a default.
-See notes. (integer) 
+See notes. (integer)
 .PD 1
 .PD 0
 .TP
 .B win 
-- window object (handle) 
+- window object (handle)
 .PD 1
 
 .SH NOTES
@@ -39,26 +39,26 @@ are:
 .B MPI_MODE_NOCHECK 
 - the matching calls to 
 .I MPI_WIN_START
-have not yet 
+have not yet
 occurred on any origin processes when the call to 
 .I MPI_WIN_POST
-is made. 
-The nocheck option can be specified by a post call if and only if it is 
-specified by each matching start call. 
+is made.
+The nocheck option can be specified by a post call if and only if it is
+specified by each matching start call.
 .PD 1
 .PD 0
 .TP
 .B MPI_MODE_NOSTORE 
-- the local window was not updated by local stores (or 
-local get or receive calls) since last synchronization. This may avoid 
-the need for cache synchronization at the post call. 
+- the local window was not updated by local stores (or
+local get or receive calls) since last synchronization. This may avoid
+the need for cache synchronization at the post call.
 .PD 1
 .PD 0
 .TP
 .B MPI_MODE_NOPUT 
-- the local window will not be updated by put or accumulate 
-calls after the post call, until the ensuing (wait) synchronization. This 
-may avoid the need for cache synchronization at the wait call. 
+- the local window will not be updated by put or accumulate
+calls after the post call, until the ensuing (wait) synchronization. This
+may avoid the need for cache synchronization at the wait call.
 .PD 1
 
 .SH NOTES FOR FORTRAN
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_set_attr.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_set_attr.3
index fdae6ec0..b62700de 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_set_attr.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_set_attr.3
@@ -1,4 +1,4 @@
-.TH MPI_Win_set_attr 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_set_attr 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_set_attr \-  Stores attribute value associated with a key 
 .SH SYNOPSIS
@@ -9,7 +9,7 @@ int MPI_Win_set_attr(MPI_Win win, int win_keyval, void *attribute_val)
 .PD 0
 .TP
 .B win 
-- MPI window object to which attribute will be attached (handle) 
+- MPI window object to which attribute will be attached (handle)
 .PD 1
 .PD 0
 .TP
@@ -21,7 +21,7 @@ int MPI_Win_set_attr(MPI_Win win, int win_keyval, void *attribute_val)
 .PD 0
 .TP
 .B attribute_val 
-- attribute value 
+- attribute value
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_set_errhandler.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_set_errhandler.3
index ec4abd38..607054fd 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_set_errhandler.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_set_errhandler.3
@@ -1,4 +1,4 @@
-.TH MPI_Win_set_errhandler 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_set_errhandler 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_set_errhandler \-  Set window error handler 
 .SH SYNOPSIS
@@ -9,12 +9,12 @@ int MPI_Win_set_errhandler(MPI_Win win, MPI_Errhandler errhandler)
 .PD 0
 .TP
 .B win 
-- window (handle) 
+- window (handle)
 .PD 1
 .PD 0
 .TP
 .B errhandler 
-- new error handler for window (handle) 
+- new error handler for window (handle)
 .PD 1
 
 
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_set_info.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_set_info.3
index a26dfbe7..708254bc 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_set_info.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_set_info.3
@@ -1,4 +1,4 @@
-.TH MPI_Win_set_info 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_set_info 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_set_info \-  Set new values for the hints of the window associated with win. 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_set_name.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_set_name.3
index 0e840883..5cf8fd63 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_set_name.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_set_name.3
@@ -1,4 +1,4 @@
-.TH MPI_Win_set_name 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_set_name 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_set_name \-  Set the print name for an MPI RMA window 
 .SH SYNOPSIS
@@ -9,12 +9,12 @@ int MPI_Win_set_name(MPI_Win win, const char *win_name)
 .PD 0
 .TP
 .B win 
-- window whose identifier is to be set (handle) 
+- window whose identifier is to be set (handle)
 .PD 1
 .PD 0
 .TP
 .B win_name 
-- the character string which is remembered as the name (string) 
+- the character string which is remembered as the name (string)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_shared_query.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_shared_query.3
index 4803289c..615cd35e 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_shared_query.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_shared_query.3
@@ -1,9 +1,9 @@
-.TH MPI_Win_shared_query 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_shared_query 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_shared_query \-  Query the size and base pointer for a patch of a shared memory window. 
 .SH SYNOPSIS
 .nf
-int MPI_Win_shared_query(MPI_Win win, int rank, MPI_Aint *size, int *disp_unit, void *baseptr)
+int MPI_Win_shared_query(MPI_Win win, int rank, MPI_Aint * size, int *disp_unit, void *baseptr)
 .fi
 
 This function queries the process-local address for remote memory segments
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_start.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_start.3
index f933f45a..2a08e523 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_start.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_start.3
@@ -1,4 +1,4 @@
-.TH MPI_Win_start 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_start 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_start \-  Start an RMA access epoch for MPI 
 .SH SYNOPSIS
@@ -9,18 +9,18 @@ int MPI_Win_start(MPI_Group group, int assert, MPI_Win win)
 .PD 0
 .TP
 .B group 
-- group of target processes (handle) 
+- group of target processes (handle)
 .PD 1
 .PD 0
 .TP
 .B assert 
 - Used to optimize this call; zero may be used as a default.
-See notes. (integer) 
+See notes. (integer)
 .PD 1
 .PD 0
 .TP
 .B win 
-- window object (handle) 
+- window object (handle)
 .PD 1
 
 .SH NOTES
@@ -39,15 +39,15 @@ are:
 .B MPI_MODE_NOCHECK 
 - the matching calls to 
 .I MPI_WIN_POST
-have already 
+have already
 completed on all target processes when the call to 
 .I MPI_WIN_START
-is made. 
-The nocheck option can be specified in a start call if and only if it is 
-specified in each matching post call. This is similar to the optimization 
-of ready-send that may save a handshake when the handshake is implicit in 
-the code. (However, ready-send is matched by a regular receive, whereas 
-both start and post must specify the nocheck option.) 
+is made.
+The nocheck option can be specified in a start call if and only if it is
+specified in each matching post call. This is similar to the optimization
+of ready-send that may save a handshake when the handshake is implicit in
+the code. (However, ready-send is matched by a regular receive, whereas
+both start and post must specify the nocheck option.)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_sync.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_sync.3
index 02576943..a594f681 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_sync.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_sync.3
@@ -1,4 +1,4 @@
-.TH MPI_Win_sync 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_sync 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_sync \-  Synchronize public and private copies of the given window. 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_test.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_test.3
index ffb8d598..895177d0 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_test.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_test.3
@@ -1,4 +1,4 @@
-.TH MPI_Win_test 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_test 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_test \-  Test whether an RMA exposure epoch has completed 
 .SH SYNOPSIS
@@ -9,14 +9,14 @@ int MPI_Win_test(MPI_Win win, int *flag)
 .PD 0
 .TP
 .B win 
-- window object (handle) 
+- window object (handle)
 .PD 1
 
 .SH OUTPUT PARAMETERS
 .PD 0
 .TP
 .B flag 
-- success flag (logical) 
+- success flag (logical)
 .PD 1
 
 .SH NOTES
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_unlock.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_unlock.3
index 6f0b6e1e..7347767d 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_unlock.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_unlock.3
@@ -1,4 +1,4 @@
-.TH MPI_Win_unlock 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_unlock 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_unlock \-  Completes an RMA access epoch at the target process 
 .SH SYNOPSIS
@@ -9,12 +9,12 @@ int MPI_Win_unlock(int rank, MPI_Win win)
 .PD 0
 .TP
 .B rank 
-- rank of window (nonnegative integer) 
+- rank of window (nonnegative integer)
 .PD 1
 .PD 0
 .TP
 .B win 
-- window object (handle) 
+- window object (handle)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_unlock_all.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_unlock_all.3
index b0f0afc8..aa6ccf74 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_unlock_all.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_unlock_all.3
@@ -1,4 +1,4 @@
-.TH MPI_Win_unlock_all 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_unlock_all 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_unlock_all \-  Completes an RMA access epoch at all processes on the given window. 
 .SH SYNOPSIS
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Win_wait.3 b/linx64/mpi/mpich/share/man/man3/MPI_Win_wait.3
index b4406df9..058b0274 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Win_wait.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Win_wait.3
@@ -1,4 +1,4 @@
-.TH MPI_Win_wait 3 "11/10/2017" " " "MPI"
+.TH MPI_Win_wait 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Win_wait \-  Completes an RMA exposure epoch begun with MPI_Win_post 
 .SH SYNOPSIS
@@ -9,7 +9,7 @@ int MPI_Win_wait(MPI_Win win)
 .PD 0
 .TP
 .B win 
-- window object (handle) 
+- window object (handle)
 .PD 1
 
 .SH THREAD AND INTERRUPT SAFETY
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Wtick.3 b/linx64/mpi/mpich/share/man/man3/MPI_Wtick.3
index 44641e07..84c52947 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Wtick.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Wtick.3
@@ -1,9 +1,9 @@
-.TH MPI_Wtick 3 "11/10/2017" " " "MPI"
+.TH MPI_Wtick 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Wtick \-  Returns the resolution of MPI_Wtime 
 .SH SYNOPSIS
 .nf
-double MPI_Wtick( void )
+double MPI_Wtick(void)
 .fi
 .SH RETURN VALUE
 Time in seconds of resolution of MPI_Wtime
diff --git a/linx64/mpi/mpich/share/man/man3/MPI_Wtime.3 b/linx64/mpi/mpich/share/man/man3/MPI_Wtime.3
index d9583e54..cb810be3 100644
--- a/linx64/mpi/mpich/share/man/man3/MPI_Wtime.3
+++ b/linx64/mpi/mpich/share/man/man3/MPI_Wtime.3
@@ -1,9 +1,9 @@
-.TH MPI_Wtime 3 "11/10/2017" " " "MPI"
+.TH MPI_Wtime 3 "6/5/2019" " " "MPI"
 .SH NAME
 MPI_Wtime \-  Returns an elapsed time on the calling processor 
 .SH SYNOPSIS
 .nf
-double MPI_Wtime( void )
+double MPI_Wtime(void)
 .fi
 .SH RETURN VALUE
 Time in seconds since an arbitrary time in the past.