From: ftp-bimas.cit.nih.gov                    Last update: October 9, 1997

                 Portability Information for VMS

FASTLINK can be ported to VMS, although it takes some effort to get
things set up. At this time, checkpointing and crash-recovery do not
work in all cases, but they do not interfere with runs that do not
crash.

There are two significant variants of VMS in existence. One is VMS for
VAXen and the other is OpenVMS for Alphas. The FASTLINK distribution
includes separate instructions for these two versions. The availability of
these instructions is largely due to the super effort of four
adventuresome FASTLINK users, Steve Roberts in the United Kingdom, Kimmo
Kallio in Finland, Anita Destefano in the U.S., Don Plugge in the U.S
and to Shriram Krishnamurthi, a student at Rice. Steve provided 
instructions for VAXen and Kimmo for Alphas. Don updated both the MMS
file and the Make tool for FASTLINK 4.0P and tested them on
several systems. All four users did extensive testing and
troubleshooting.  Thanks to Steve, Kimmo, Anita, Don, and Shriram!

You can find the top level instructions for VAX/VMS in README.VAX and they
refer to some files in fastlink/4.0P/vaxvms, where fastlink is the top
level directory created when you untar FASTLINK. Caution: I am using UNIX
syntax for subdirectories here; you need to adapt this to VMS syntax.  You
can find the top level instructions for OpenVMS in README.ALPHAVMS and they
refer to some files in fastlink/4.0P/alphavms. One way of
compilation that may work on either type of system is MMS.
A suitable MMS file can be found in the fastlink/4.0P/vaxvms directory.
It may require small modifications to be ported to different VMS
computers.

More user input on simplifying the FASTLINK port to VMS, making it work
with more compilers, and testing checkpointing would be very much
appreciated.
