Update INSTALL and INSTALL_parallel files to remove references to

ancient systems and add generic steps for building HDF5 on HPC clusters.

2 files changed, 14 insertions, 19 deletions

diff --git a/release_docs/INSTALL b/release_docs/INSTALL
index 124dba9..f84ddc2 100644
--- a/release_docs/INSTALL
+++ b/release_docs/INSTALL
@@ -14,7 +14,6 @@ CONTENTS
 
         2. Quick installation
         2.1. Windows and Cygwin
-        2.2. RedStorm (Cray XT3)
 
         3. HDF5 dependencies
         3.1. Make
@@ -97,13 +96,6 @@ CONTENTS
         Users of Microsoft Windows should see the INSTALL_Windows files for
         detailed instructions.  INSTALL_Cygwin also exists for those platforms.
 
-2.2. RedStorm (Cray XT3)
-        Users of the Red Storm machine, after reading this file, should read
-        the Red Storm section in the INSTALL_parallel file for specific
-        instructions for the Red Storm machine.  The same instructions would
-        probably work for other Cray XT3 systems, but they have not been
-        verified.
-
 
 3. HDF5 dependencies
 3.1. Make
diff --git a/release_docs/INSTALL_parallel b/release_docs/INSTALL_parallel
index bf14b2e..23dc2a0 100644
--- a/release_docs/INSTALL_parallel
+++ b/release_docs/INSTALL_parallel
@@ -82,19 +82,22 @@ This allows for >2GB sized files on Linux systems and is only available with
 Linux kernels 2.4 and greater.
 
 
-2.3. Hopper (Cray XE6) (for v1.8 and later)
+2.3. Unix HPC Clusters (for v1.8 and later)
 -------------------------
 
-The following steps are for building HDF5 for the Hopper compute
-nodes.  They would probably work for other Cray systems but have
-not been verified.
+The following steps are generic instructions for building HDF5 on 
+several current HPC systems.  The exact commands and scripts to use
+will vary according to the scheduling software on the individual 
+system.  Consult the system documentation to determine the details.
 
 Obtain the HDF5 source code:
     https://portal.hdfgroup.org/display/support/Downloads
 
-The entire build process should be done on a MOM node in an interactive allocation and on a file system accessible by all compute nodes.
-Request an interactive allocation with qsub:
-qsub -I -q debug -l mppwidth=8
+In general HDF5 can be built on a login/front-end node provided it is 
+installed on a file system accessible by all compute nodes.  If parallel
+tests run by "make check" or "make check-p" will be run on compute 
+nodes in a batch job, the HDF5 build directory should also exist on a 
+file system accessible by all compute nodes.
 
 - create a build directory build-hdf5:
   mkdir build-hdf5; cd build-hdf5/
@@ -102,12 +105,12 @@ qsub -I -q debug -l mppwidth=8
 - configure HDF5:
   RUNSERIAL="aprun -q -n 1" RUNPARALLEL="aprun -q -n 6" FC=ftn CC=cc /path/to/source/configure --enable-fortran --enable-parallel --disable-shared
 
-  RUNSERIAL and RUNPARALLEL tells the library how it should launch programs that are part of the build procedure.
+  RUNSERIAL and RUNPARALLEL tells the library how it should launch programs that are part of the build procedure. Note that the command names and the specific options will vary according to the batch system.
 
 - Compile HDF5: 
   gmake
 
-- Check HDF5
+- Check HDF5:  on most systems this should be run as a batch job on compute nodes.
   gmake check
 
 - Install HDF5
@@ -117,8 +120,8 @@ The build will be in build-hdf5/hdf5/ (or whatever you specify in --prefix).
 To compile other HDF5 applications use the wrappers created by the build (build-hdf5/hdf5/bin/h5pcc or h5fc)
 
 
-3. Detail explanation
----------------------
+3. Detailed explanation
+-----------------------
 
 3.1. Installation steps (Uni/Multiple processes modes)
 -----------------------