Sophos Anti-Virus for OpenVMS installation notes ------------------------------------------------ www.sophos.com Contents -------- General notes Installing VSWEEP from files copied via Pathworks/Advanced Server Installing directly to OpenVMS from the CD-ROM Installing using VSWEEP.ZIP Making LIBSAVI available for use Running VSWEEP General notes ------------- VSWEEP consists of the following components: LIBSAVI_AXP/VAX/I64.EXE - virus detection engine shareable image VSWEEP_AXP/VAX/I64.EXE - command-line interface image VDL.DAT, *.VDB - virus definition files Each image filename indicates the target hardware platform as follows: *_AXP - Alpha platforms *_VAX - VAX platforms *_I64 - Itanium platforms The virus definition files must be kept in the same directory as VSWEEP_AXP/VAX/I64.EXE. These files and additional supporting files are included on the CD as an OpenVMS saveset and as a Zip file. Both installing and updating VSWEEP use the same procedure. This involves transferring and unpacking the VSWEEP update files from CD or Zip file to a directory on the OpenVMS server. It may also be necessary to copy or move LIBSAVI_AXP/VAX/I64.EXE to complete the installation. See the subsection "Making LIBSAVI available for use" for more details. The VSWEEP CD-ROM installation files comprise: READVMS.TXT README INSTVMS.TXT installation notes VSWEEP.BCK save set containing the VSWEEP update files VSWREST.CMD command procedure to restore VSWEEP update files from the save set VSWEEP.ZIP Zip file with the same contents as VSWEEP.BCK, provided as an alternative means of installing VSWEEP. Installation may be done either by using the CD-ROM drive of a Pathworks/ Advanced Server connected PC and copying VSWEEP.BCK and VSWREST.CMD to the server over the network and then unpacking them, or if the OpenVMS system supports ISO 9660 format CD-ROMs, by using the CD-ROM drive of an OpenVMS machine and unpacking the files directly. Both methods are described below. Installing VSWEEP from files copied via Pathworks/Advanced Server ----------------------------------------------------------------- 1. Copy the CD-ROM installation files (VSWEEP.BCK and VSWREST.CMD) from a Pathworks/Advanced server client to a dedicated directory on the OpenVMS server. 2. Within OpenVMS, run VSWREST.CMD with the appropriate parameter (see below). VSWREST.CMD extracts the VSWEEP update files from VSWEEP.BCK. (The extension CMD is used in preference to COM to prevent users inadvertently running the file as an executable file on DOS or related platforms). If VSWREST.CMD is run with no parameters the save set VSWEEP.BCK must be in the current OpenVMS default directory. The VSWEEP update files are then unpacked to the current default directory. If VSWREST.CMD is run with the parameter "-M" (i.e. @VSWREST.CMD -M) then the user is prompted for installation options before extracting the files. The settings entered are saved in a configuration file (VSWREST.CFG). These values may be used for future updates without user input if the parameter "-A" is used (i.e. @VSWREST.CMD -A). Installing directly to OpenVMS from the CD-ROM ---------------------------------------------- 1. Load the CD-ROM into the drive and mount the CD-ROM using the command: $ MOUNT /MEDIA=CD /OVER=IDENT /UNDEFINED=(STREAM:132) 2. Ensure that the current default directory is either the directory to install to, or the directory containing VSWREST.CFG (if VSWREST.CMD is run with -A). 3. Run the installation command procedure VSWREST.CMD, for example: $ @DKA400:[OPENVMS]VSWREST.CMD (to install to the current directory) or $ @DKA400:[OPENVMS]VSWREST.CMD -M (to customize installation settings) or $ @DKA400:[OPENVMS]VSWREST.CMD -A (to install using customized settings) NOTE: Do not SET DEFAULT to the CD-ROM device before running VSWREST.CMD. Installing using VSWEEP.ZIP --------------------------- If you install using VSWEEP.ZIP instead of the saveset VSWEEP.BCK, unzip VSWEEP.ZIP into the directory you wish to use, replacing any existing files there. VSWEEP.ZIP may be unzipped from the CD after the CD has been mounted on the OpenVMS system, or it may be copied from a PC via Pathworks/Advanced Server before unzipping. Then follow the instructions in the subsection entitled "Making LIBSAVI available for use". We recommend that VSWEEP.ZIP is unzipped on an OpenVMS system. An OpenVMS unzip utility is available from Info-ZIP (www.info-zip.org). Making LIBSAVI available for use -------------------------------- Once the update files have been transferred to the OpenVMS system, the LIBSAVI shareable image must be made available for use by the VSWEEP image. This is achieved EITHER by copying LIBSAVI_AXP/VAX/I64.EXE to SYS$COMMON:[SYSLIB] OR by referring to the LIBSAVI image by logical name: * LIBSAVI_AXP/VAX/I64.EXE copied to SYS$COMMON:[SYSLIB] Copy the LIBSAVI shareable image file to SYS$COMMON:[SYSLIB] (which is referenced by the logical name SYS$SHARE) replacing any earlier version of this file. The file ownership should then be set to SYSTEM and the protection set to (S:RWED,O:RWED,G:RWED,W:RE). The installation command procedure VSWREST.CMD can be configured to perform this step automatically if run with the option -M to set the option, and then with -A for subsequent updates. To install this way requires SYSTEM privileges for the user carrying out the installation. * LIBSAVI_AXP/VAX/I64.EXE referenced by logical name If you do not wish to copy the LIBSAVI shareable image to SYS$SHARE during installation (for example if installation/updating is to be carried out without SYSTEM privileges), the file can be left in the directory to which it was installed. However, it is then necessary to define the SYSTEM logical name LIBSAVI_AXP, LIBSAVI_VAX or LIBSAVI_I64 as appropriate. This logical name must translate to the full specification of the LIBSAVI image, for example: $ DEFINE/SYSTEM LIBSAVI_AXP MYDEV:[MYEXES.VSWEEP]LIBSAVI_AXP.EXE or $ DEFINE/SYSTEM LIBSAVI_VAX MYDEV:[MYEXES.VSWEEP]LIBSAVI_VAX.EXE or $ DEFINE/SYSTEM LIBSAVI_I64 MYDEV:[MYEXES.VSWEEP]LIBSAVI_I64.EXE as appropriate for the platform. This command may be included in the site-specific startup procedure to ensure that it is defined after a re-boot. Alternatively, if VSWEEP is to be run only from within a command procedure, the logical name may be defined within that procedure, for example where the foreign symbol VSWEEP is defined. If the logical name is not defined, or defined incorrectly, an error message of the following form will be generated: %DCL-W-ACTIMAGE, error activating image LIBSAVI_AXP -CLI-E-IMAGEFNF, image file not found AXP1$DKA0:[SYS0.SYSCOMMON.][SYSLIB]LIBSAVI_AXP.EXE; Running VSWEEP -------------- Before VSWEEP can be run from the command-line or command-procedure, it is necessary to define the foreign command symbol VSWEEP, for example: $ VSWEEP :== $MYDEV:[MYEXES.VSWEEP]VSWEEP_I64.EXE See the Sophos Anti-Virus for OpenVMS manual for further details.