Review the original installation instructions to refresh the various
Some insurance on the directory tree is recommended in case
the update should fail or otherwise be unusable or problematic (of course, this
is good advice whenever about to make major changes to anything!) This may be
in the format of a regular site backup, special pre-update backup, or special
pre-update ZIP archive of the directory tree. The latter two could be
accomplished using commands similar to the following:
$ BACKUP WASD_ROOT:[000000...] location:WASDROOT.BCK/SAVE/VERIFY
$ ZIP "-V" location:WASDROOT.ZIP device:[WASD_ROOT...]*.*
$ ZIP "-T" location:WASDROOT.ZIP
If using ZIP then ensure that a previous version of the target ZIP file
does not already exist. If it does then that version is updated, a new
version is not created.
For existing files a new version is created (the first time this is about
to occur the UNZIPper requests permission – either "A" for all, or
"y" or "n" or a per-file basis).
It is possible to selectively extract portions of a tree if
something has become damaged. This would be accomplished by specifying what
needs to be extracted from the archive (instead of the default
all), as illustrated by the following example where only the Alpha
object modules are extracted.
$ SET DEFAULT device:
$ UNZIP device:[dir]archive-AXP.ZIP ht_root/src/httpd/obj_axp/*.*
Updating a package follows a similar process to installation.
The ZIP archive will contain brief installation instructions. Use the
following command to read this and any other information provided.
$ UNZIP -z device:[dir]archive.ZIP
It is recommended to check the integrity of, then list the contents of, the
archive before UNZIPing.
The archive contains the complete directory tree. Hence it is necessary
to SET DEFAULT into the parent directory of the WASD_ROOT logical name, as with
the following example.
$ SHOW LOGICAL WASD_ROOT
"WASD_ROOT" = "DKA100:[WASD_ROOT.]" (LNM$SYSTEM_TABLE)
$ SET DEFAULT DKA100:
$ UNZIP device:[dir]archive.ZIP
Updating From v9.3 or Earlier
Before UNZIPing the v11 package and when updating an existing v9.3 or
earlier installation the root directory must be renamed from HT_ROOT.DIR to
WASD_ROOT.DIR. The v10 and later packages use [WASD_ROOT] as the top-level
directory in line with other naming schema changes employing "WASD". Remember
to modify local startup procedures in-line with this new top-level directory
name. Also note that the v11 package is not suitable for updating from
existing v8.0 or earlier installation.
Source Archive, Object Module Archives
If a complete build is planned then only the main archive is required. If
a link-only build then an additional archive for each architecture must be
Expat is an XML parser required for WASD WebDAV. From WASD v11.5.0 the Expat
library uses 64 bit data types unavailable to the 32 bit VAX CPU. WASD v11.5.0
and later on VAX requires the replacement of the 64 bit Expat directory with
the earlier 32 bit Expat release. The WASD download page notes this and
provides an archive of the 32 bit release. After download, UNZIP, and before
building, the following additional step is required.
The UPDATE.COM procedure assists with subsequent updates of WASD.
It assumes a vanilla setup, using the standard directories and
account environment described in this document. All sections prompt before
performing any action and generally default to "no". Read the questions
Of course it is best (read mandatory) for the server to be shut down during
After UNZIPing the updated package do the following:
$ SET DEFAULT WASD_ROOT:
It provides the following functions:
Build Executables –
Either compile sources and link, or just link package object code to produce
images for the local version of VMS. If the system has a suitable SSL toolkit
the installer is requested whether an SSL enabled version be built.
Server Quick-Check –
Executes a procedure that runs up the HTTPd in demonstration mode. Allows
evaluation/checking of the basic package (2.10 Quick-Check).
Server Support/Configuration Files –
Copies changed example HTTP server configuration and support files from the
[EXAMPLE] directory to the [HTTP$SERVER], [LOCAL] and [STARTUP] directories.
Update Scripts –
Selectively copy groups of scripts from package build directories into the