"Out-of-the-box" the package executes using DEC TCP/IP Services or other UCX compatible emulation (e.g. TCPware) under VMS 6.0, 6.1, 6.2 and 7.1 It will also execute with other TCP/IP packages supported by MadGoat NETLIB (see WASD HTTPd Has Spread It's Wings!).
The software was originally written in a VAX C (v3.2) and
later DEC C (v5.n) environments, under VMS 6.n. No
consideration has been given to any other environments. The DEC C run-time
environment is prefered to the VAX C run-time environment because the former's
greater integrity and improved performance over the latter.
NO EXECUTABLES
Previous releases of the package provided executables. In an effort to make the package more universal and easier to distribute and maintain only object code is now provided. To ease installation and updates relevant procedures
HT_ROOT:[000000]INSTALL.COM
HT_ROOT:[000000]UPDATE.COMare provided. After the package is unzipped the appropriate procedure must be run to create the required executables. See the Technical Overview for the detail.
For VAX systems there may be an incompatibility for VMS versions prior to 6.2, as noted in the Open VMS Version 6.2 Release Notes:
4.5.2.2 DECC$SHR.EXE (VAX Only) V6.2 A new package of internationalization routines has been added to the DEC C RTL (see Section 4.5.1.3) and the trans- fer vector has been extended, necessitating an increase in the minor ident (GSMATCH) of the image. Because of this, pro- grams using the DEC C RTL (DECC$SHR.EXE) linked on OpenVMS VAX Version 6.2 systems will not run on prior versions of OpenVMS VAX.
If your VAX site does not support the DEC C compiler or run-time environment (check here for the run-time, shareable image: SYS$COMMON:[SYSLIB]DECC$SHR.EXE ), the run-time components alone can be installed and used without additional licensing. This is a simple and short duration exercise. The DEC C/C++ Run-Time Components kit is available on the Digital consolidated distribution CD-ROM. See comments in the [.AACRT060] directory.
- NOTE -
Needless-to-say (but I will anyway), the server requires a privileged environment (either account or image) in which to execute.
NETLIB must be installed separately. The package may be obtained from:
http://www.madgoat.com/netlib.html
As the software has been written to the requirements of DEC C (in an uncritical, VAXC-backward-compatible compilation mode, i.e. /STANDARD=VAXC (when moving from VAXC C to DEC C the author discovered he wasn't the rigorous software engineer he had hoped he was :^)) its build and run-time behaviour in other compiler environments is unpredictable.
All applications are linked against the DEC C DECC$SHR.EXE RTL. The DEC C run-time environment is prefered to the VAX C run-time environment because the former's greater integrity and improved performance over the latter.
Brute-force build procedures are provided in each software application source directory. They are named "BUILD_whatever.COM". All package applications may be build or linked using the procedures HT_ROOT:[SRC]BUILD_ALL.COM and HT_ROOT:[SRC]LINK_ALL.COM,