Site powered by WASD and VMS   Welcome to  WASD VMS Web Services  version 12.2
Copyright © 1996-2024 Mark G. Daniel, licenced under the Apache License, Version 2.0

Thanks to Jeremy Begg of VSM Software Services Pty Ltd for the generous support in providing this demonstration server via his company's systems.

New to WASD?  Start here!  After that there is Installation Configuration Features Environment Scripting documentation.  There is also a consolidated list of the resources available in the WASD environment.  Note: Links with a trailing open in a new page.

Of course you may just wish to browse the directory tree.

When upgrading, consult the list of significant changes in the server, its configuration or environment.

This site is currently using the v12.2.0 package, hosted on an HP rx2660 running VSI OpenVMS V8.4-2L3 and Process Software Multinet V5.6 Rev A-X. 

 Demonstration

Server Basics   Directory listing & tree, SSI, TLS, server administration, log statistics.
Scripting Support   CGI & CGIplus, WebSocket & "Raw"Socket, DECnet & OSU, ISAPI, Java.
VMS Scripts   Help & text libraries, BNU & Bookreader, document search, system performance, SHOW system.
Miscellanea   WOTSUP, scréper, fetch, formwork, tmailer, utilities.
Other   WASD related resources, mailing list, PowerPoint presentations.
Support   Community, commercial, development, casual.
x86-64  WASD's Own x86-64 Porting Effort

 Download

Primary distribution site for full packages, new versions, updates, bugfixes, other support packages, etc.

The site also provides technical articles, the info-WASD mailing list and archive, along with other resources.

 Mark G. Daniel
 Mark.Daniel@wasd.vsm.com.au
 A pox on the houses of all spammers. Make that two poxes.
 Trouble contactingme?
 Last revised January 2024

www wasd.vsm.com.au
 * This is the default page for the WASD package.
The above contact is almost certainly not the administrator of this site.
** This package does not use or store cookies for any purpose.
Nor does it collect or store personal information.
Contact the local administrator for any site-specific detail.