Requirements

WASD VMS Hypertext Services ... read this first

[next] [previous][contents]

4 - Requirements

``Out-of-the-box'' the package executes using DEC TCP/IP Services on both AXP and VAX platforms. The VMD HTTPd server itself is specifically tailored to DEC TCP/IP Services for OpenVMS (v4.0, a.k.a. UCX), particularly its QIO interface.

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.

Executables

The executables provided with the package have been compiled using DEC C v5.0 and linked against the VMS v6.2 DECC$SHR.EXE RTL, with the following implications:

Needless-to-say (but I will anyway), the server requires a privileged environment (either account or image) in which to execute.

- NOTE -

1996 NOTE: To give this software an opportunity to be useful to a larger number of sites I ported it to TGV MultiNet TCP/IP (v3.4) over New Year 95-96. This has been tested under VMS VAX 6.2 and seems to work OK. It is basically the DEC TCP/IP QIO adapted to MultiNet's QIO interface. It is not as exhaustively tested as the DEC TCP/IP version. I have not compiled or tested it using MultiNet on AXP, we have only the one VAX architecture system using TGV's product, other VAX and AXP systems use bundled DEC TCP/IP. Just to emphasize once again, WASD does not need a MultiNet version, so this is strictly a bonus. I would appreciate (but may not end up implementing) any suggestions on improving the networking code.

1997 NOTE: TGV MultiNet support is tenuous. WASD no longer has a MultiNet system to develop or test on.


[next] [previous][contents]