INSTLGD3.PDF the Cohort V3 installation guide with complete instructions for installing the Cohort suite of products. The guide also includes a sample VDM installation. The manual is in the Adobe Acrobat Public Document Format; most browsers can read these files and free viewers for many platforms are available from www.adobe.com; no official .pdf viewer is available for OpenVMS, however, we do plan to publish our documentation to .html as well for the final Cohort V3 release. It is possible to print documentation from within the Acrobat reader.

A 30 day demo license is available for VDM or Cohort by contacting Saiga Systems directly. Current users should note that the license key used for previous version(s) of VDM or Cohort will need to be replaced by a current license which must be loaded before running VDM V7.0; your existing license will not work. Please contact us directly to obtain a license for this version if you do not already have one. However, this license will not interfere with existing license(s) if you plan to run a mixture of Cohort V2 and Cohort V3 modules.

1	A new user detail report that has a separate page for each user showing their storage usage for every disk they have files on and the total space used.
2	A new file selection criteria has been added so that interactive reports, such as the size report, can be generated for specific files, file types or directories. Any portions of the file specification not given will be completed from the default specification of [...].;
3	A new unauthorized files report shows all the files on a disk that belong to a UIC that is not currently in the UAF file. With this report you can quickly find files that should be deleted or reset to belong to a valid user.
4	VDM currently uses the system service $getdvi to obtain information on disk devices. When obtaining the name for the disk the item “DEVNAM” is used. In sites with HSC devices this DEVNAME changes when the HSC node is changed so that VDM current and capacity reports can no longer access historical information for that disk. A new logical name “VDM$USE_DISK_NAME” has been added; if it is defined, in the system table, to be FULLDEVNAM: $ define /system VDM$USE_DISK_NAME FULLDEVNAM that item will be used instead. This generates more consistent results at sites using HSC devices. For a typical nonHSC disk in a cluster the two device items would return devices names of: DEVNAM node1$dka100: FULLDEVNAM $1$dka100: Switching from the current method to the new “FULLDEVNAM” item, at sites that are currently running VDM, will leave historical information unavailable because of the disk name change. A command procedure, VDM_COM:CONVERT_OLD_DATA has been added to read an existing data file and convert all the disk references from the DEVNAM format to the FULLDEVNAM format. As long as a disk has not been moved since the older data was created this will successfully make older data available. The procedure requires the date from the data file name as a parameter; to convert data from October 13, 1999, for example: $ @VDM_COM:CONVERT_OLD_DATA 19991013
5	VDM V6 had an error in the command definition file that made it difficult to change the default mail recipient for the monitor. This problem has been fixed. To change the default mail recipient enter: $ vdm /monitor /mail=username
6	The current and capacity directory reports can now be generated to any level, how-ever, during reporting any directory string that is too long is truncated.

The following patch files were released on December 19, 2001. They can be applied to any installation of Version 7.0 of VDM. The zip file of the patches includes detailed instructions on how to apply the patches; please copy the zip file to your VAX or AXP, unzip it under OpenVMS and then follows the instructions in the patches.txt file. If you downloaded Version 7.0 after January 2, 2002, it is not necessary to apply the patches after installation - they are included in the standard distribution.