FLOW - Fortran Structure Analysers
==================================

This file describes how to install Flow on VMS, Unix
and IBM/VM/CMS machines. 

Please read the COPYRIGHT file.

The posting includes a new version of the user guide for
Floppy and Flow. This contains a detailed description of
the various possibilities. The help files for the various
systems (flow.hlp, flow.helpcms, and flow.l) should, however,
be adequate for most uses.

Note that this version of Flow is ICOMPATIBLE with the previous
version of Floppy (called ffccc in Volume 12 of comp.sources.misc).
So you MUST install the latest version of Floppy before you can
use this version of Flow.

1) Unix Installation

   To use Flow, you will need to already have installed Floppy.

   How to procede
   ==============
   (Please read the Floppy README file, which contains details for
   HP-UX machines relevant also for Flow.)
   Put all the distribution files in a subdirectory called
   flow. Type make. This should generate a flow executable.
   If your Fortran 77 compiler is not invoked by "f77" then
   you will have to edit the makefile and change it accordingly.
   (E.g. if you are building Flow in AIX, then the xlf compiler
   may not allow .for suffixes. There is a suggested mod in
   the makefile which takes care of this.) Take care if you
   do modify the makefile that you remember the tab characters ...
   Make is very picky about tabs, apparently.
   
   To test Flow, generate an input file for it using Floppy.
   For example, using a source Fortran file called myfile.f :

   floppy -t -cn myfile.f

   flow -q myfile.f.floptre

   If you are satisfied, move the man page flow.l to the right 
   place on your system, and put flow in the appropriate place too.

2) VMS Installation   

   To use Flow, you will need to already have installed Floppy.

   How to procede
   ==============
   Put all the distribution files in a subdirectory called
   [.FLOW]. Set default to that directory, and type @MAKE_VMS.
   This should generate a flow excutable, and a flow library.

   To add the command for testing, edit the file FLOW.CLD.
   Change the filename of the FLOW.EXE image so that it
   corresponds to where FLOW.EXE actually is on your machine.
   Exit the editor. Type SET COMMAND FLOW.

   To test Flow, generate an input file for it using Floppy.
   For example, using a source Fortran file called MYFILE.FOR :

   FLOPPY /TREE /NOCHECKS MYFILE

   FLOW /QUERY MYFILE

   If you are satisfied, then add the command to the system
   DCLTABLES (this requires privilege), by using the commands
   SET COMM/TABLE=SYS$COMMON:[SYSLIB]DCLTABLES -
       /OUT=SYS$COMMON:[SYSLIB]DCLTABLES FLOW
   INSTALL REPLACE SYS$LIBRARY:DCLTABLES

   This makes the command available for all newly logging in
   users. Then add the FLOW.HLP to your user help library, using
   a command of the form LIBRARY/INS SYS$HELP:USER.HLB FLOW.HLP

3) VM/CMS Installation

   To use Flow, you will need to already have installed Floppy.

   How to procede
   ==============
   The Flow source makes use of INCLUDE directives; the filename
   format of the target files is not compatible with the form
   required for a GLOBAL MACLIB. This means that you will have to
   expand the include files in all the modules. A procedure for
   doing this (on a VMS machine!) is included in the posting as
   MAKE_CMS.COM. This generates one large file called CMSFLOW FORTRAN
   which should be then moved to the VM/CMS environment and compiled.
   
   The FLOW EXEC Rexx file is intended to be used either in line mode,
   or via an IOS3270 panel. The panel for the latter option is
   included as FLOW PANEL in the posting. But you don't need IOS3270
   to run FLOW.

   Once the CMSFLOW FORTRAN has been compiled, you should have a
   CMSFLOW TEXT file. This is the program that will be loaded by
   FLOW EXEC. Note that you will need a virtual machine of at least
   12 MBytes to run FLOW. 

   To test FLOW, generate an input file for it using FLOPPY. For
   example, type:

   FLOPPY myfile (NOCHECKS TREE
   FLOW myfile (QUERY

4) Problems and Bugs

   If you find bugs in Flow, or have installation problems on a
   specific machine, I would like to hear about them, although
   I cannot guarantee to be able to help. Please mail
   julian@vxcern.cern.ch.
   
