VDM V7 - Saigasaiga.com/ftp/saiga/cohort30/vdm70u.pdf · 2012-03-26 · VDM V7.0 OpenVMS Disk Manager by Saiga Systems Quick Links New Features of Version 7 9 Common Uses of VDM 21

VDM V7.0OpenVMS Disk Manager

by Saiga Systems

Quick LinksNew Features of Version 7 9Common Uses of VDM 21Qualifier Summary 82

Current Report 77Capacity Report 76Interactive Reports 80

Monitor Reference 29GO, An OpenVMS Directory Utility 179Index 184

The information in this document is subject to change without notice and should not be construedas a commitment by Saiga Systems Software Inc. Saiga Systems Software Inc. assumes noresponsibility for any errors or omissions that may appear in this document.

The software described in this document is furnished under a license and may be used or copied onlyin accordance with the terms of such license.

Copyright © 1999 by Saiga Systems Software Inc.All rights reserved

DECNET, VAX, OpenVMS, Alpha AXP and VAXCLUSTER are trademarks of Compaq.

Saiga Systems

#215, 801 - 6th Street SWCalgary, Alberta, Canada

T2P 3V8

Voice: 1-800-561-8876

Fax (403) 263-0744Telephone (403) 263-1151Internet [email protected]

[email protected] http://www.saiga.com/FTP ftp.saiga.comListserver [email protected]

December 1999

Table of Contents

New with Version 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Overview of VDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Verify that VDM logicals are defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Verify that your account has the necessary privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Verify that command definitions are installed and compatible . . . . . . . . . . . . . . . . . . . . . 18Ensure VDM has file access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Ensure there is adequate disk space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Ensure there are adequate resources for sorting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Ensure resource quotas are adequate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Handling system crashes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Calling Saiga Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Common Uses of VDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Defining thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Setting up VDM to monitor files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Defining cleanup procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Recording activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Sending Warning Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Collecting information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Handling error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Hints for running VDM/MONITOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Stopping and re-starting VDM/MONITOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Forecasting future requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Adding new accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Removing accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Listing accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Adding new owners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Removing owners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Listing owners . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58VDM directory structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65SYSUAF.DAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Data files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Usage by UIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Usage by DIRECTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66DISKNAMES.DAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66VDM_PLA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67VDM_PERM_DATA.DAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Work files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Data file removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Data logical name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Sort work files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Command syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Abbreviating commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Editing command lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Qualifiers Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84/ACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84/ACTIVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86/ALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87/ALLOCATED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88/BACKUP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89/BEFORE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90/BROADCAST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91/CONSOLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92/CONVERT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93/CREATED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94/CURRENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95/DATA_FILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96/DCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97/DIR_COLLECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98/DIR_FILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99/DISK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100/EVENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102/EXPIRED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106/FRAGMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109/INDENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110/INTERVAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111/LARGE_CHANGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112/LEVEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113/LIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114/LOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115/MAIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116/MATCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117/MAXIMUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118/MINIMUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119/MODIFIED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120/MONITOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121/NEAR_QUOTA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122/OUTPUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125/OWNER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126/PANIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127/PERIOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129/PREVIOUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130/PROTECTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

/QUOTA_COLLECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133/RATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134/REPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135/RESET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137/SEQUENCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138/SHOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139/SINCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140/SIZE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141/SORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142/START . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143/STATISTICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144/STATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145/STOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146/SUMMARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147/TYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149/UIC_COLLECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150/UIC_FILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151/UNUSED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152/USAGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153/USED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154/VALUE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155/VERSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156/WORRY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Verify that VDM logicals are defined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Verify that your account has the necessary privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . 160Verify that command definitions are installed and compatible . . . . . . . . . . . . . . . . . . . . 160Ensure VDM has file access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Ensure there is adequate disk space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Ensure there are adequate resources for sorting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Ensure resource quotas are adequate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Handling system crashes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Calling Saiga Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Appendix G - GO, an OpenVMS directory utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Going to a new directory or sub-directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Going to a sub-directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Going up one level in your current directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Going to the top of your current directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Going to your home directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Returning to a previous directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Going to a new drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Displaying your current directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Displaying directory trees . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Displaying the entire directory tree for the drive . . . . . . . . . . . . . . . . . . . . . . . . 181Displaying a list of sub-directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Controlling the current directory message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Controlling the prompt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181GO qualifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182GO symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182GO logicals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183GO versus the SET/SHOW DEFAULT COMMANDS . . . . . . . . . . . . . . . . . . . . . . . . . . 183Directory access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Overview of VDM

Using VDM to manage your disk drivesThis chapter shows you how VDM (OpenVMS Disk Monitor) can give you greater control over yourfile system and help you:

recover wasted disk spaceimprove system performancepinpoint problem filestighten file security

by analyzing your disks. VDM helps you do your job better and makes your life easier.

VDM helps you analyze disk allocation and file usage on your Alpha AXP and VAX systems. Itdetects users who are gobbling up disk space or are near their quota and projects future growth basedon observed increases in usage. VDM can help you:

identify wasted spacelocate inactive or expired fileslocate wasted space hidden in over-allocated fileslocate large files created recentlyanalyze disk usage by user, UIC, directory, account and owner

pinpoint security problemslocate files with unusual access such as WORLD:READlist files with a specified ACL

uncover performance problemslocate fragmented files

locate problem fileslocate files needing backup or flagged NOBACKUPlocate files with bad blockslocate zero-length space

project future demandby user, UIC or directoryusing observed rates of increasebased on actual, average or maximum allocations

generate dozens of precise, informative reportsbased on selection criteria you specifysorted on the fields you specify

VDM allows you to generate exception reports which show only the users or files that meet thecriteria you specify.

VDM can be run interactively or submitted to batch. In batch VDM allows simple unattended datacollection and analysis.

VDM handles files owned by UICs and identifier. And, it displays UICs in either numeric oralphanumeric format.

VDM runs on all members of the Alpha AXP and VAX family including VAXCLUSTER systems.It handles multi-drive volume sets as well as HSC disks.

Easy to useVDM is easy to set up and use. It comes with a tutorial, on-line HELP, extensive error messages anda comprehensive user guide and reference manual.

Field-provenVDM is highlighting problems at hundreds of sites in North America. It's solidly engineered,rigorously tested and fully field-proven by system managers like yourself.

Fully supportedWith an annual support agreement, you'll always have someone to call if you have any problems withVDM. For a single low annual fee, you get unlimited TOLL-FREE telephone support, access to ourVDM list-server where you can post questions about how to better use VDM and free updates asthey become available. Our support lines are open Monday to Friday from 8 a.m. to 5 p.m. MountainTime except holidays.

Saiga Systems Software#215, 801 Sixth Street SWCalgary, Alberta CanadaT2P 3V8

(800) 561-8876(403) 263-1151 (International)(403) 263-0744 (fax)

WWW: http://www.saiga.com/FTP: ftp.saiga.com (anonymous ftp supported)E-MAIL: [email protected]

[email protected] [email protected]

New with Version 7

VDM Version 7 incorporates many of the most requested enhancements to VDM. These include:

1 A new user detail report that has a separate page for each user showing their storageusage 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 sizereport, can be generated for specific files, file types or directories. Any portions of thefile 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 thatis not currently in the UAF file. With this report you can quickly find files that shouldbe 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 withHSC devices this DEVNAME changes when the HSC node is changed so that VDMcurrent 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, inthe system table, to be FULLDEVNAM:$ define /system VDM$USE_DISK_NAME FULLDEVNAMthat item will be used instead. This generates more consistent results at sites usingHSC devices. For a typical nonHSC disk in a cluster the two device items wouldreturn devices names of:

DEVNAM node1$dka100:FULLDEVNAM $1$dka100:

Switching from the current method to the new “FULLDEVNAM” item, at sites thatare currently running VDM, will leave historical information unavailable because ofthe disk name change. A command procedure,VDM_COM:CONVERT_OLD_DATA has been added to read an existing data fileand convert all the disk references from the DEVNAM format to the FULLDEVNAMformat. As long as a disk has not been moved since the older data was created this willsuccessfully make older data available. The procedure requires the date from the datafile 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 changethe default mail recipient for the monitor. This problem has been fixed. To change thedefault 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.

Installing VDM

VDM is easy to install on your Alpha AXP or VAX system using the Digital supplied VMSINSTALprocedure. It only takes a few minutes and can be safely done while there are users on the system.For the complete installation instructions refer to the VDM section of the Cohort V3 ProductInstallation Guide.

Overview of VDM

VDM ComponentsVDM has four main features.

1. An on-line report generator which creates reports directly from the INDEXF.SYS file;this makes it significantly faster than the DIRECTORY command when searching forfiles across an entire disk. Features include:a. a report showing the 50 largest files on a diskb. the ability to find files using a variety of selection criteria including size (used,

allocated or unused), protection, organization (indexed, sequential, direct), etc.c. V7 adds the ability to find files based on a file specification which can include

wildcards (/file qualifier)

2. A report generator that creates reports from previously collected data. This data can becollected daily or weekly and from it reports can be generated:a. showing total usage by user or UIC on a disk or group of disksb. showing projected disk usage for capacity planningc. V7 adds the ability to report usage by user across all disks that VDM collects data

on (/sequence=detail)

3. A detached process that can be configured to send mail, send console messages and/orsubmit batch jobs when:a. disks are filling past user defined thresholdsb. disks have experienced an errorc. a particular file has been changedd. a particular file is found or has been deletede. a particular file has grown/shrunk beyond a specified size

4. GO; a utility that works much like set default but is more flexible. Go allows the user tochange their DCL prompt automatically to reflect their current working directory, omitthe square brackets from directory specifications and go back to your last workingdirectory automatically.

Getting Started

This chapter shows you how to get started after you have installed VDM.

From the command line interface you can initiate data collection and generate reports. Somereports require that data collection has run; others can be run immediately. For furtherinformation on commands, refer to the chapter "VDM Commands". Here are some examples ofDCL commands:

To show the directory structure on a disk drive, type:

$ VDM /REPORT=TREE /DISK=disk-name

To display which version of VDM you are running, type:

$ VDM /VERSION

Here is a procedure to generate sample reports from the DCL interface.

1. Enable the VDM command verb if necessary.

$ SET COMMAND VDM_CDU:VDM_COMMANDS

2. Specify a report; in this case a size report for all files with 5000 or more blocks ofdisk space allocated

$ VDM /REPORT=SIZE /DISK=disk /ALLOCATED=5000: /OUTPUT

3. Print the report.

$ PRINT VDM.LIS

Data CollectionTo generate usage analysis or capacity projections, you must first run data collection.We recommend you do the following to get started:

Run ANALYZE/DISK/REPAIR on your drivesIf you haven't run the OpenVMS ANALYZE/DISK utility on your drives within the last twoweeks, please run it before you run data collection. If it finds errors in your disk structure youmay wish to run it again with the /REPAIR option. This will clean up any errors in file headersand pointers and prevent problems during data collection runs.

Review the data collection procedureThe directory [VDM.COM] contains the data collection procedure COLLECT.COM. It reads theDISKNAMES.DAT file and does the data collection on the specified drives. You may want toconfirm that this file exists and contains an appropriate list of disk drives. If this file does notexist it should be created using the VDM_COM:CREATE_DISK_FILE.COM procedure. Theonly modification that you may want to make to the data collection procedure would be toremove collection for directories if it is unlikely that you will generate current usage or capacityreports summarized by directory. Some sites like to modify this file to collect data only 1 or 2days a week; this is particularly appropriate at sites where large changes in disk usage are notlikely to occur from day to day or that have a large number of disks and wish to avoid theoverhead of collecting data on these disks every day. To change the time, frequency or queuewith which collect.com is run edit the procedure vdm_com:resubmit.com.

Submit the data collection procedure to batchBecause the data collection procedure imposes a load on the system, we do not recommend thatdata collection be done on-line. Submit it to batch queue that will run at a lower priority or, evenbetter, submit it to run at night during a low usage period.

Wait until the data collection procedure runsCheck the batch log to verify that the procedure executed correctly. It can be found in the defaultlogin directory of the account the batch procedure was submitted from. Once the data collectionprocedure has been executed, it will automatically be requeued to SYS$BATCH to run at afuture date - you can specify the date by modifying the resubmit.com command file. The log filewill be in the VDM_DAT directory.

Generate an analysis reportThe directory [VDM.COM] contains three sample data analysis procedures,ANALYSIS_1.COM, ANALYSIS_2.COM and ANALYSIS_3.COM. Look at them, select theone that is closest to your needs and customize it. You can run the data analysis proceduresinteractively.

Update the collection procedureWhen you've established which drives you want to monitor, you can modify theDISKNAMES.DAT file to your needs or run the vdm_com:create_disk_file.com procedure torecreate this file at anytime.

Using VDM on a VAXCLUSTER

This chapter shows you how to use VDM on VAXCLUSTER systems. VDM can be run onclusters that are mixed VAX andAXP architectures, however, it must be installed on at least onenode of each type, and, if you are running with multiple major versions of the operating system(ie: 6.2 and 7.0); it should be installed under each version once. It can be installed in a commondirectory; in cases of multiple major version of OpenVMS there should be a separate exedirectory for each version; define the logical VDM_EXE to point to the correct area for eachnode.

If you install VDM on a common disk, you need not install it on each node. However, there are acouple of things you have to do to make it available to all nodes of the cluster:

you must define the logical names VDM_EXE and VDM_DAT on each node, preferablyby executing the VDM_STARTUP procedure on each node

if you are using node specific DCLTABLES.EXE files, you will have to add the VDMcommand verb to each of the tables, or add the command verb to your process commandtable when you want it to be available - see the preceding section.

If you don't install VDM on a common disk, then you must install it on each node for it to beavailable on all nodes of the cluster.

Data collectionWhen you run VDM on a cluster, you should have the data files on a disk that is accessible fromall nodes in the cluster. This way, you can generate the reports from any node in the cluster. Thecollection procedures can be run from any node in the cluster. Because of the way VDM iswritten, you can run multiple collections from different machines. However, only one processcan access the VDM data files at one time. When you are running multiple collections, makesure that they are running at different times.

Common SYSUAF.DATIf you have a common SYSUAF.DAT for your cluster, you can use VDM as if you were on asingle Alpha AXP and VAX. VDM will automatically find your SYSUAF.DAT using theOpenVMS-supplied logical "SYSUAF".

Multiple SYSUAF.DAT filesOn the other hand, if your cluster has a separate SYSUAF.DAT for each node, you will have todirect VDM to use the SYSUAF.DAT on a different node. To do this, define the logical sysuafin your process logical name table. For example:

$ DEFINE /PROCESS SYSUAF - NODE2::$4$DUA0:[SYS0.SYSCOMMON.SYSEXE]SYSUAF.DAT

$ VDM /REPORT=PROTECTION /OUTPUT=NODE2_PROTECTION

to create a file protection report for the users on NODE2 by running VDM on a SYSUAF on adifferent node. Be sure to define SYSUAF in your process table; this will prevent the systemfrom trying to use that UAF when other users log in.

If you don't have a logical defined for SYSUAF, VDM will use the SYSUAF.DAT on yourcurrent node.

STARTUP command procedureThe VDM installation procedure creates a file, VDM_STARTUP.COM and copies it to theSYS$MANAGER directory. This command procedure defines the system logicals VDMrequires to run and must be executed on every node that you wish to run VDM data collection orreports on.

VDM/MONITOR on VAXCLUSTERThis section describes VDM/MONITOR processing on VAXcluster systems.

VDM/MONITOR will run on a cluster. However, you should only run VDM/MONITOR on anode which has access to all the disks that you want to check. If you have disks that are onlyaccessible from one machine, you will have to run VDM/MONITOR on that machine, in order tocheck and cleanup those disks.

Permanent data fileYou should not have the permanent data file shared across the cluster, because you could create asituation where two separate machines submit jobs at the same time to clean up a disk. Eachrunning copy of VDM/MONITOR should have its own permanent data file, with only the disksthat it is checking in the file.

Error and output logThese files are created by the detached process if an error occurs. The error text will be placed inthese files. The errors from the detached process will also be signalled on the console, so it is notreally necessary to give these files special consideration.

HITMAN free disk events and VDM/MONITORIf you are using the product HITMAN from Saiga Systems to monitor free space or errors onyour disks we suggest you move this functionality to VDM at your convenience. VDM allowsyou to customize how often your disks are checked, by disk, and provides two thresholds (worryand panic) with separate actions for each making it more flexible than the corresponding freespace HITMAN event.

VDM and RAWith Version 6 of RA it is now possible to collect data for both RA and VDM in a single RAdata collection pass. Cohort V3 users will find that this decreases the data collection overhead by

nearly 50%. To set this up a new command procedure has been included with RA calledCOMBINED_AUTOSUBMIT.COM. If VDM and RA data collections are running normallysimply run this command procedure to submit SAIGA_DISK_COLLECTION_node.COM andremove the individual data collections from the queues. We do suggest having data collectionsworking normally before making this change. Since RA’s data collection is significantly moreinvolved than VDM’s the common collection is run during the RA data collection.

Solving VDM problems

This chapter shows you how to resolve problems with VDM.

If you have a problem running VDM, please do the following:

Verify that VDM logicals are definedVerify that your process has the necessary privilegesVerify that the command definition is installed and compatibleVerify that the license has been installedCall Technical Support at Saiga Systems

Verify that VDM logicals are definedVDM uses five logicals to access data files and executables. Normally, these logicals are definedas part of the system startup. However, to ensure the logicals are defined, type the followingcommand:

$ @SYS$MANAGER:VDM_SYSTEM_LOGICALS.COM

This procedure is created as part of the VDM installation procedure. If the logicals were alreadydefined, you will see the following message:

%DCL-I-SUPERSEDE, previous value of {logical_name} has been superseded

repeated five times.

To verify that the VDM logicals are defined, type the following command:

$ SHOW LOGICAL VDM*

You should see output similar to the following:

(LNM$PROCESS_TABLE)

(LNM$JOB_xxxxxx)

(LNM$GROUP_xxxxxx)

(LNM$SYSTEM_TABLE)

"VDM_CDU" = "ddcu:[VDM.CDU]" "VDM_COM" = "ddcu:[VDM.COM]" "VDM_DAT" = "ddcu:[VDM.DAT]" "VDM_DOC" = "ddcu:[VDM.DOC]" "VDM_EXE" = "ddcu:[VDM.EXE.VAX]" or "ddcu:[VDM.EXE.AXP]"

where "ddcu:" is the disk drive on which VDM is installed. This output indicates that the VDMlogicals are properly defined in the SYSTEM table.

Verify that your account has the necessary privilegesVDM data collection requires OpenVMS privileges such as SYSPRV to run. Ensure that youhave sufficient privileges in your account.

To ensure your process has all the necessary privileges, type the following command:

$ @VDM_COM:SET_PRV.COM

If you see the following message:

%SYSTEM-W-NOTALLPRIV, not all requested privileges authorized

the account you are logged into does not have all the privileges necessary to run VDM. Youmust log into an account which does have all the privileges. Normally, the SYSTEM accountwill have (or be able to acquire) all the necessary privileges to run VDM.

If your process does not have all the necessary privileges, VDM will list the additionalprivilege(s) you need when you enter a command.

To find out what privileges your process has, type the command:

$ SHOW PROCESS /PRIVILEGES

To give your process specific privileges, type the command:

$ SET PROCESS /PRIVILEGES=privilege_name

Verify that command definitions are installed and compatible.If you receive either of the following messages when you type a command:

%DCL-W-IVVERB, unrecognized command verb - check validity and spelling \VDM\

%CLI-F-SYNTAX, error parsing 'qualifier_name'-CLI-F-ENTNF, specified entity not found in command tables

where "qualifier_name" is one of the VDM qualifiers, VDM's command definition has not beeninstalled in the system or process table or the command definition version you are using is notcompatible with the VDM executable version.

To add the command definition to your process table, type the following command:

$ @VDM_COM:INSTALL_CDU.COM

Ensure VDM has file accessVDM requires authorized access to all disk drives. It must be run out of a privileged account orbe given privilege when it is installed. Refer to the chapter "Privileges You Need to Use VDM"for more complete information.

Ensure there is adequate disk spaceVDM creates a number of work files and three permanent files each time data is collected. Ifyour system is very low on disk, you may have problems with insufficient space. The chapter onVDM data files contains more complete information on VDM's disk requirements.

Ensure there are adequate resources for sortingDuring the collection phase and to generate some of the reports, VDM uses the OpenVMS SORTutility. Because the OpenVMS sort uses a large amount of virtual memory during its operation,the command may abort with the error message INSUFFICIENT VIRTUAL MEMORY. Thereare several reasons why this might happen:

The sysgen parameter VIRTUALPAGECNT is too lowThe UAF parameter PGFLQUOTA is too lowThe UAF parameter WSQUOTA is too lowThe paging and/or swapping files are too small

If this error occurs during the execution of the collection procedure, it may leave the current datafile corrupt. If a data file was generated for the date when you had this error, delete that data file,adjust the quotas, and try the command again.

Ensure resource quotas are adequate

When running the collection procedure, VDM may abort with the error INSUFFICIENTVIRTUAL MEMORY while running the analyze/disk portion. This error can be caused by thefollowing:


Adjust the quotas appropriately, and run the collection procedure again.

Handling system crashesIf your system crashes or is restarted, you may have to resubmit the data collection and dataanalysis procedures.

Verifying that the License has been InstalledTo verify that the license has been installed enter:

$ show logical pkms*

there should be a translation for one of the following logicals:PKMS$VDM-VAXPKMS$VDM-AXPPKMS$COHORT-VAXPKMS$COHORT-AXP

If one of these logicals is not defined look for a pkms startup command procedure insys$manager and execute it. If the logical is defined enter:

$ vdm/versionwhich will tell you whether or not the license has expired.

Calling Saiga SystemsIf you try the above suggestions and still continue to have problems, please contact SaigaSystems Technical Support at 1-800-561-8876. Technical support is provided between 8:00 a.m.and 5:00 p.m. Mountain Time.

When you call 1-800-561-8876, please have the following information available:

Alpha AXP or VAX ModelOpenVMS versionCompany NameVDM version (from VDM/VERSION output)

The operator will:

1) verify that you have a support agreement2) transfer your call to the Technical Support group.

You may also obtain technical support by:FAX (403) 263-0744E-MAIL [email protected] http://www.saiga.com/

Common Uses of VDM

Locating wasted space and inactive or fragmented files

This chapter shows you how to find wasted space, inactive files, fragmented files, etc. on yoursystem using VDM's new SIZE report and the interactive reporting facility. Often disk space istied up unnecessarily within files which have been allocated more space than they really requireor are not being used. Waste occurs when the number of blocks allocated to a file is significantlylarger than the number of blocks used. To generate the size report you specify /REPORT=SIZE.

Report informationThe report displays the disk it is searching then the directory name. This identifying informationis preceded by blank lines. Then it displays the following information for each selected file:

NoBackup flag (files marked with an asterisk are set NoBackup)file name.type;versionblocks allocatedblocks usedblocks unused (allocated - unused)date createddate modifieddate backed upexpiration dateACL countFragment count

Block fields are shown as 7 digit numbers without commas or signs and are automaticallytotalled as 8 digit fields. Dates are shown in the format: dd-mmm-yy (note the 2 digit year). ACLand fragmentation counts are shown as 4 digit numbers without commas or signs. For all reportnumeric fields, if the actual number is larger than the maximum, it is displayed as all 9's.

For your convenience, VDM automatically totals all columns containing numbers of blocks aswell as showing the total allocated, used and unused figures for the entire drive.

Report sequenceThe report is produced in the file-spec sequence.

Associated QualifiersYou can use the following qualifiers when creating a size report:

/ALLOCATED /FILE /OUTPUT/BEFORE /OWNER /USED/DCL /SINCE/FLAGS /STATISTICS/FRAGMENTS /UNUSED/MODIFIED or /EXPIRED or /BACKUP or /CREATED

Use the command VDM/REPORT=SIZE/UNUSED=n: (note the ":" after the number) togenerate a report showing files with n or more unused blocks.

Use the command VDM/REPORT=SIZE/ALLOCATED=n: (note the ":" after the number) togenerate a report showing files with n or more allocated blocks.

Use the command VDM/REPORT=SIZE/ALLOCATED=0 to generate a report showing thezero-length files on a drive.

Use the command VDM/REPORT=SIZE/MODIFIED/BEFORE=date to generate a reportshowing the files on a drive which haven't been written to or modified since the specified date.

Use the command VDM/REPORT=SIZE/EXPIRED/BEFORE=TODAY to generate a reportshowing files on a drive which are expired. These files haven't been read or written to in the timelimit you set with the OpenVMS commands SET VOLUME/RETENTION and SETFILE/EXPIRATION.

Use the command VDM/REPORT=SIZE/FRAGMENTS=n: (note the ":" after the number) togenerate a report showing files on a drive which have n or more fragments.

Use the command VDM/REPORT=SIZE/FLAGS=NOBACKUP to generate a report showingfiles on a drive which will not be backed up regardless of activity.

Use the command VDM/REPORT=SIZE/BACKUP/BEFORE=date to generate a report showingfiles on a drive which haven't been backup up since the specified date. This report will also showfiles that have never been backed up (the backup date is none). To limit this report to only filesthat have been backed up prior to today use a combination of /BEFORE and /SINCE;VDM/REPORT=SIZE/BACKUP/BEFORE=date/SINCE=01-JAN-1900.

Use the command VDM/REPORT=SIZE/FILE=*.zip to generate a report showing all the zipfiles on a drive. Since no /disk has been specified VDM will default to the current disk.

Use the command VDM /REPORT=LARGE_FILES /NUM_FILES=50 /FILE=*.DAT/DISK=DKB300: to generate a large files report showing the 50 largest dat files on dkb300.

Displaying file protection information

This chapter shows you how to locate files with unusual (and possibly dangerous) access bygenerating reports showing file protection information.

Use the VDM/REPORT=PROTECTION/PROTECTION=protection_code command to generatethe file protection report. The protection report shows you protection for the files which matchthe criteria you've specified.

Use this report to locate files with potentially troublesome protection such as files which:

have excessive access such as:WORLD write or delete access, /PROTECTION=WORLD:WD GROUP write or delete access, /PROTECTION=GROUP:WD

do not have sufficient access such as:lack full SYSTEM access, /PROTECTION=("-",SYSTEM:RWED)lack any OWNER access, /PROTECTION=("-",OWNER:RWED)

Specifying selection criteriaYou can select one or more files to appear on the report by specifying selection criteria. If youdon't specify any selection criteria, all files will appear on the report. Normally, you wouldspecify /PROTECTION to search for specific file protection. You can also specify additionalcriteria such as /OWNER or /ACE. For more information on selection criteria, refer to thechapter "Specifying selection criteria".

The protection report will find any file that matches any of the protections you have specified. Bydefault the protection report takes the /MATCH=OR action. For instance/PROTECTION=(WORLD:WD) will find files with world write OR delete or both protection. Ifyou want to find files that match the specified access exactly you need to specify/MATCH=AND. For instance /PROTECTION=(WORLD:WD)/MATCH=AND will find onlyfiles with both world write AND delete access.

Report informationThe report displays the disk it is searching then the directory name. The directory information ispreceded by blank lines to provide visual separation between each directory Then it displays thefollowing information for each file:

owner (UIC, identifier or username)file name.type;versionprotection (graphic display of file protection)Number of ACE's in ACL (999, blank if zero)

=================================================================Report Name

Owner File-spec Protection ACLDisk: x-disk-x

Directory: [x-directory-x]x-owner-x x-filename.type;version-x x-protection-x n-ACL-nx-owner-x x-filename.type;version-x x-protection-x n-ACL-n

Directory: [x-directory-x]x-owner-x x-filename.type;version-x x-protection-x n-ACL-n=================================================================

For readability, file protection is shown in following graphic format:

SYSTEM OWNER GROUP WORLDRWED RWED R-E- R---

R indicates READ accessW indicates WRITE accessE indicates EXECUTE accessD indicates DELETE access- indicates the absence of that class of protection

Report sequenceThe report is produced in the file-spec sequence.

Associated QualifiersYou can use the following qualifiers with this command:

/ACE/ALLOCATED/DCL/FILE/MATCH/OUTPUT/OWNER/PROTECTION/STATISTICS/TYPE/UNUSED/USED

Locating files with a particular ACE

This chapter shows you how to find files which have one or more specified access control entries(ACE) in their access control list (ACL). OpenVMS provides two methods of access to a file:the traditional UIC/file protection and the more powerful and flexible ACL. Unfortunately, it isdifficult to determine which files have a particular ACE. The ACE report allows you to quicklydetermine which files have one or more specified ACE in their ACL.

Use the command:

VDM/REPORT=ACE/ACE=(IDENTIFIER=identifier,ACCESS=access)

to generate a report showing all files which have one or more specified ACEs. The ACL reportshows you all files on the disk drives you've specified with ACE entries for the identifier youspecified. Use additional qualifiers such as /OWNER or /MATCH to tailor the report to findspecific files which need further analysis.

The access portion of the ACE qualifier is specified in the standard OpenVMS way. Forexample, ACCESS="READ+WRITE+DELETE+EXECUTE" will find any files that give read,write, delete or execute access to the specified identifier. Specifying /MATCH=AND will findonly files with read, write, delete and execute access. You may specify NONE or "" to find fileswhich the identifier is denied any access to.

Report informationThe report displays the disk it is searching then the directory name. This identifying informationis preceded by blank lines. Then it displays the following information for each selected file:

owner (UIC, identifier or username)file name.type;versionprotection (graphic display of file protection)Number of ACE's in ACL (999, blank if zero)ACL (there is one line for each ace)

Report sequenceThe report is produced in file-spec sequence.


/ACE/ALLOCATED/BACKUP or /CREATED or /EXPIRED or /MODIFIED/BEFORE or /SINCE/DCL/DISK (one only)/FILE/FLAGS/FRAGMENTS/MATCH/OUTPUT/OWNER/PROTECTION/STATISTICS/TYPE/UNUSED/USED/WIDTH

Generating & deleting directory trees

This chapter shows you how to use VDM to produce reports showing the directory structure (a"directory tree"). OpenVMS allows directories within directories up to eight deep. Too manylevels of sub-directories can degrade system performance. With the VDM tree report, you canquickly see how many levels there are on each disk. It provides a clear overview of directoriesand sub-directories on each disk; an excellent "structure chart" of the disk layout.

Use the DCL procedure VDM_COM:DELTREE to remove an entire directory tree from yoursystem.

Use the command VDM/REPORT=TREE/DISK=(...) to generate a report showing directorytrees for one or more drives. If you enter more than one drive, each starts on a new page. Usethe /LEVEL qualifier to control how many levels of sub-directory are displayed (the default isall). Use the /INDENT qualifier to control how many spaces each sub-directory is indented.

Report informationThe report display the disk it is working on then the root directory "[000000]". Then it displaysall the remaining directories on the disk, indenting each directory so the structure is clearlyvisible. Here is a sample directory tree:

000000 (device name)CLIFFORDA

EXEMRKTNG

GILBERTSHITMAN

V52V60

RARASSMUSSONA

CURRHITMANVDM

PERS

Report sequenceThe report is produced in the following sequence:

disk drive (in the order specified by the /DISK qualifier)directory


/DISK/INDENT/LEVEL/OUTPUT

Monitoring free disk space, detecting errors and monitoring files

This chapter shows you how to use VDM to check for and report low free space, errors on yourdisk drives and changes to critical files automatically. With it, you can eliminate productionproblems and database inconsistencies caused by system hangs resulting from lack of free space.

VDM/MONITOR guards free spac, checks for errors on your disk drives and checks critical filesfor changes in size or content. At intervals you set (from 1 to 60 minutes), it checks how manyblocks are free on each disk drive and whether any errors have occurred. If any drive has lessthan the minimum free blocks you've set, it sends an alarm and recovers space by submitting abatch procedure to purge multiple file versions and delete temporary files. Two different freespace thresholds can be set for each drive with a batch procedure for each threshold. You canuse the standard cleanup procedures supplied with the package or create your own. If any errorshave occurred during the specified interval, VDM/MONITOR sounds an alarm and, optionally,sends mail to the user(s) you specify. If VDM detects changes in a file, according to criteria youspecify, it will take any combination of actions you specify; sending console messages, sendingmail and submitting a correction procedure to batch.

To invoke VDM's disk monitoring function, type "VDM/MONITOR" at the command levelalong with the desired qualifiers. This creates a detached process which monitors your diskdrives and files. Various /monitor qualifiers allow you to add, remove and change entries inVDM’s permanent data file which contains all the details on what the monitor is watching for.You can enter "HELP VDM Monitor_disk" at the command level to obtain information aboutdisk monitoring.

Getting StartedWe recommend you do the following to get started:

1. Create the permanent data fileDo this by typing any VDM/MONITOR command that changes the permanent data file, such asVDM/MONITOR/NOACTIVE:

$ VDM/MONITOR/NOACTIVE%VDM-W-ERROPEPERM, Error opening permanent data file%RMS-E-FNF, file not found%SYSTEM-W-NOSUCHFILE, no such fileCannot open the permanent data fileWould you like to create a new one(y/n) [Y]? y%VDM-E-NOTRUN, VDM/MONITOR is not running

VDM/MONITOR responds by telling you that it can't open the permanent data file, because thefile was not found. It then asks you if you want to create a new one. When you say yes, it createsthe new data file and fills it with the defaults for all parameters. It also gives you the error

message that VDM/MONITOR is not running, because the detached process has not been started. You can ignore that error for now.

2. List the permanent data fileYou can see what the defaults are for the permanent file, by doing a list:

$ VDM/MONITOR/LISTLogging to the operators console is enabled..

The list shows which defaults VDM/MONITOR will use for each disk you add to the monitorlist. You may override many of these defaults on a disk by disk basis.

NOTE: VDM's disk monitor will not check for free space thresholds or errors on anydevice unless you add that device to the permanent data file.

3. Change parametersYou will probably want to change some of the defaults. You can do that now. For example, todisable the log file, you would enter the command:

$ VDM /MONITOR /NOLOG%VDM-E-NOTRUN, VDM/MONITOR is not running

No messages will be written to the log file until a /LOG command is entered.

Here is another example to mail a message to the user SYSTEM when low free space is detected:

$ VDM/MONITOR/MAIL=(USER=SYSTEM,QUEUE=SYS$BATCH)%VDM-E-NOTRUN, VDM/MONITOR is not running

Here is another example, to add DRA1: to the list of drives to be checked using the defaultthresholds:

$ VDM/MONITOR/DISK=DRA1:%VDM-E-NOTRUN, VDM/MONITOR is not running

NOTE: When you change a parameter, VDM/MONITOR tells the detached process toread the parameter file. Since the detached process doesn't exist at this point, you get the"VDM/MONITOR is not running" message. This can be ignored.

4. List the changed parametersWhen you have modified the setup to your needs, check the permanent data file to ensure that allparameters are as you want them:

$ VDM/MONITOR/LISTLogging to the operators console is disabled..

5. Start the detached processWhen the defaults are satisfactory, start the detached process:

$ VDM/MONITOR/START%VDM-S-PROCID, Identification of created process is 00000AFB

The above command starts the detached process, with a system assigned process ID of00000AFB. The process name is "VDM_MONITOR".

NOTE: To limit the possibility of problems with the detached process and batch jobs itsubmits, we suggest you issue the VDM/MONITOR/START command while logged inas SYSTEM. If you add this command to your system startup file the monitor willautomatically be started under the SYSTEM account.

6. Define cleanup proceduresThere are standard cleanup procedures supplied with the distribution kit. Their names areWORRY and PANIC. Once you see from the console log and the VDM/MONITOR log file howthe parameters you have set up are working and are satisfied that this is the correct behaviour,you can start running VDM/MONITOR live:

$ VDM /MONITOR /ACTIVE

Now VDM/MONITOR will monitor free space and activate cleanup procedures.

Once you have the permanent data file set up, it is not necessary to change it again. To start upVDM/MONITOR automatically, add the command VDM/MONITOR/START to the systemspecific startup file SYS$MANAGER:SYSTARTUP.COM. The command should be insertedafter the part in the command procedure that defines all the logical names. Whenever the systemstarts up, VDM/MONITOR will be started. You should also add the commandVDM/MONITOR/STOP to the system specific shutdown command procedureSYS$MANAGER:SYSHUTDWN.COM. This will terminate the VDM/MONITOR detachedprocess and close the log file.

Defining thresholdsVDM/MONITOR has two free space thresholds called WORRY and PANIC. Use WORRY andPANIC threshold clauses to define free space thresholds and actions on a device.

Threshold clauseA threshold clause consists of the following two items:

• A threshold level. A threshold is the free space point below which action should be taken. Youcan specify a threshold as a percentage of the disk, using the PERCENT=n clause, or an exactnumber of blocks, using the BLOCKS=n clause.

• The name of the command procedure that you wish to run when the threshold is reached.

For example, DUA1: is an RA81 disk drive. The RA81 has a total of approximately 800,000blocks. We want to purge the disk if we have less than 10 percent of the disk free, and we wantto clean up temporary files if we have less than 10,000 blocks. Thus we have the followingVDM/MONITOR command.

$ VDM /MONITOR /DISK=DUA1: /WORRY=(PERCENT=10)/PANIC=(BLOCKS=10000)

WORRYUse the /WORRY=(...) threshold_clause to indicate what the first free space threshold is. Thedefault is /WORRY=(PERCENT=15).

You can also specify a specific number of blocks as the threshold using the BLOCKS=nthreshold clause.

PANICUse the /PANIC=(...) threshold_clause to indicate what the second free space threshold is. Thedefault is /PANIC=(PERCENT=5).

You can also specify a specific number of blocks as the threshold using the BLOCKS=nthreshold clause.

For a more detailed explanation of thresholds, please see the section of the manual that describesthe /WORRY and /PANIC qualifiers.

Setting up VDM to monitor filesNew with Version 6 of VDM is the ability to set up VDM to monitor files. Files can be monitorfor any of the following event types:

- a file exists a file with a specific name has been created- a file does not exist a file with a specific name cannot be found any longer- a file has changed a check of certain VMS file attributes indicates that this file

has been modified since the last time it was checked- a file has grown a file has become larger than a threshold number of blocks- a file has shrunk a file has become smaller than a threshold number of

blockswith each of these event types it is possible to configure VDM to send console messages, sendmail and/or submit a batch procedure when the event is detected. The procedures for setting upand taking advantage of file monitor events are very similar to those for disks. The /file and/event qualifiers are used in conjunction with the /monitor qualifier to add file events to themonitor’s permanent data file. The file size events can be configured to check against disk blocks

used, allocated or unused; since OpenVMS often allocates blocks long before it marks them asused this can be particularily useful for catching problems with files that are growing beyondreasonable size.

These events can be configured to detect a number of possible problems before they becomeserious and allow you to correct the problem, often automatically using a batch job. Thefollowing examples should help to illustrate the usefulness of these events.

1. This event will submit a job to automatically reset the OpenVMS accounting file when itexceeds 15,000 blocks used. The correction procedure used simply does a SETACCOUNTING/NEW command and then purges the system accounting file keeping 3versions. Mail will also be sent to the SYSOP and a console message broadcast.

$ VDM /MONITOR /FILE=SYS$SYSTEM:ACCOUNTNG.DAT -/EVENT=(NODE=THISND, TYPE=SIZE, BLOCKS=15000, SIZE=USED, -COMMAND=SYS$MANAGER:RESET_SYSTEM_ACCOUNTING.COM,-QUEUE=THISND$BATCH) /MAIL=SYSOP /CONSOLE

2. This command will submit a job that performs a comparison and mails the results to thesystem operator everytime the OpenVMS system startup file gets changed on THISND.Mail is also being sent to the system operator directly by VDM so that the operator willbe aware if the comparison job fails for any reason. Setting up this event and keeping acopy of the system startup file in another directory will allow the operator responsible forthis file to quickly determine if an unauthorized change has been made to the systemstartup file.

$ VDM /MONITOR /FILE=SYS$SYSTEM:SYSTARTUP_VMS.COM -/EVENT=(TYPE=CHANGE, NODE=THISND, QUEUE=THISND$BATCH, -COMMAND=SYS$MANAGER:COMPARE_STARTUP.COM) /MAIL=SYSOP

To remove a file event from the VDM Monitor permanent data file simply enter:

$ VDM /MONITOR /NOFILE=filename

using the exact same filename that the event was added with. The event will be deleted from thepermanent data file and VDM will stop monitoring that file.

Defining cleanup proceduresA batch procedure can be submitted when you reach either of the WORRY or PANIC thresholds. You define the contents of the procedure.

Writing cleanup proceduresWhen a threshold is crossed, VDM/MONITOR executes a cleanup procedure by submitting acommand file to run on a specified batch queue. The purpose of this procedure is to free disk

space by eliminating unnecessary files. Two possible cleanup procedures may be executed - theworry command procedure or the panic command procedure. Remember, you define thecontents of these procedures.

The command procedure for the first threshold level (WORRY level) should purge multipleversions of files. Two parameters, P1 and P2, are passed to the worry command procedure. P1 isthe device name. P2 is the worry threshold level. P2 can be used to give you more control overthe cleanup procedure. For example, you can check the number of free blocks on the disk againstP2 to see if you have passed the threshold level yet. The command procedure can then executethe commands PURGE/KEEP=3 or PURGE/KEEP=2, depending on this check.

The command procedure for the second threshold level (PANIC level) should delete temporaryfiles. It should also execute at a higher priority, ie., priority 5 either by running in a separatequeue or containing a SET PROCESS/PRIORITY command in the procedure. Two parameters,P1 and P2, are passed to the panic command procedure. P1 is the device name. P2 is the panicthreshold level. P2 can be used in the panic command procedure similar to P2 in the worrycommand procedure.

Purging multiple versions of a fileAs files are modified, OpenVMS creates new versions of files and retains the previous version. This is a great convenience but can consume a lot of space. Purging multiple versions of a filefrees up space without eliminating the most current version. You can specify how many versionsof the file are to be kept and specify which directories are to be purged. Within OpenVMS, youcan automatically restrict the number of versions of a file in a directory. You can set versionslimits on a directory, or on a specific file. The DCL commands to do this are:

$ SET DIRECTORY /VERSION_LIMIT=n directory-name$ SET FILE /VERSION_LIMIT=n file-name

where n is the number of versions of the file(s) you want to keep. For example, if you set theversion limit to 3, then when the fourth version of a file is created, the first version isautomatically deleted. If you are already using version limits on files and directories, thenpurging the disk will have a lesser effect on the free space than if you were not using them. Ifyou set these limits, they will not be in effect on a file until it has been purged to the number ofversion you specified (or less). For further information on setting version limits on directoriesand files, see the OpenVMS manual, DCL DICTIONARY.

Deleting temporary filesIn the course of operation, many programs create temporary files which aren't always deletedafter completion. Any file that can be easily regenerated can also be considered a temporary file. For example, the listing and object files generated from a FORTRAN compile can be easilyrecreated, by simply recompiling the FORTRAN source. RUNOFF output files, such asfile.MEM, file.BRN, etc can be recreated if you have the original RUNOFF document. It isimportant to remember that this type of file should only be considered temporary if the file that itwas generated from is readily available, and the procedure for creating the output files does not

involve a significant amount of work.

Truncating filesUse the OpenVMS command SET FILE/TRUNCATE file-spec to truncate files to the number ofblocks they are using as opposed to the number they have allocated.

Recording activityVDM/MONITOR can record every action it makes. This record can be logged to a file. It canalso be sent to the operator console if you wish.

Log informationThe following information is contained in each log record:

• Date • Threshold• Time • Cleanup Procedure name• Drive number

System console logUse the /CONSOLE qualifier to tell VDM/MONITOR to send a message to all operators enabledas a CENTRAL operator when a cleanup procedure is activated. Use the /NOCONSOLEqualifier to suppress messages to these operators. The default is /CONSOLE.

Log fileVDM/MONITOR automatically logs all activity to a file. Use the /LOG qualifier to tellVDM/MONITOR to close the existing file and start a new one with the same name and a higherversion number. This allows you to look at the log file.

The log file is, by default, called VDM_DAT:VDM_LOG_FILE.LOG. To change its name,define the system logical name VDM_LOG_FILE to be the file name you want. For example:

$ DEFINE /SYSTEM VDM_LOG_FILE DUA1:[FRED]DISK_LOG.DAT

will cause the new log file to be opened as "DUA1:[FRED]DISK_LOG.DAT". Use the/NOLOG qualifier to close the current log file and not to open a new file. No messages will belogged to the log file, until a new file is opened with the /LOG qualifier.

Sending Warning MessagesIn addition to submitting cleanup procedures, VDM/MONITOR can send alarm messages when athreshold is crossed.

BroadcastVDM/MONITOR has the ability to send a warning message to user terminals when disk spacegets low. This allows the users to cleanup their own accounts if they have space allocated totemporary files or multiple versions.

Use the /BROADCAST qualifier to indicate that a message is to be sent. Use the/NOBROADCAST qualifier to eliminate warnings. The default is /BROADCAST.

If broadcast is turned on, it will send a message to all terminals, telling them that the panic stagehas been reached. If the free space on a disk gets below 100 blocks, VDM/MONITOR willbroadcast a message to all terminals regardless of what the broadcast switch is set to. It willbroadcast this message every time it checks the disk space, and finds it below 100 blocks. If auser does not want to receive these messages, execute the command:

$ SET BROADCAST=NOGENERAL

This will still allow the user to receive messages from DCL (spawn and CTRL/T messages),mail, phone, etc, but they will not receive the VDM/MONITOR messages. If the user has histerminal set /NOBROADCAST or has typed CTRL/S, the warning message will not bedisplayed.

MailVDM/MONITOR can send a mail message to a user or group of users. If the mail qualifier isused, it will send this mail message to the specified users when the panic stage is reached. Formore information on how the mail qualifier works, see the command qualifiers section of themanual.

Collecting informationVDM/MONITOR can collect information about free space without activating any cleanupprocedures or generating any alarms. VDM/MONITOR has the ability to monitor the drives andrecord when thresholds were crossed and cleanup procedures would have been activated. Thisfunction is used to collect information about the activity on your system before turningVDM/MONITOR loose.

Use the /NOACTIVE qualifier to prevent procedures from being activated. The default is/ACTIVE. /NOACTIVE disables the activation of procedures and warning of terminals but thelog file, console and mail functions continue to operate.

NOTE: We recommend that you collect information for a few days before you startactivating cleanup procedures.

Here are some sample VDM/MONITOR console messages:

This message is created when VDM/MONITOR starts up, or from VDM/MONITOR/LOG %%%%%%%%%%% OPCOM 7-JUL-1999 16:48:44.03 %%%%%%%%%%%Message from user SYSTEM7-JUL-1999 16:48:43.77 VDM/MONITOR - New log file created

This is the message when VDM/MONITOR submits the WORRY procedure%%%%%%%%%%% OPCOM 7-JUL-1999 17:00:32.17 %%%%%%%%%%%Message from user SYSTEM

7-JUL-1999 17:00:31.11 VDM/MONITOR - 23,900 free blocks on _DRA0:, Worry Batch Procedure submitted

This is the message when VDM/MONITOR submits the PANIC procedure%%%%%%%%%%% OPCOM 7-JUL-1999 17:01:25.97 %%%%%%%%%%%Message from user SYSTEM7-JUL-1999 17:01:24.17 VDM/MONITOR - 11,900 free blocks on _DRA0:, Panic Batch Procedure submitted

This is the message when someone modifies the permanent data file%%%%%%%%%%% OPCOM 7-JUL-1999 17:02:45.51 %%%%%%%%%%%Message from user SYSTEM7-JUL-1999 17:02:45.37 VDM/MONITOR - Permanent data file modified

This is the time stamp%%%%%%%%%%% OPCOM 7-JUL-1999 17:00:32.17 %%%%%%%%%%%Message from user SYSTEMThis is VDM/MONITOR, see you in an hour

This is the message from VDM/MONITOR/STOP%%%%%%%%%%% OPCOM 7-JUL-1999 17:22:59.59 %%%%%%%%%%%Message from user SYSTEMVDM/MONITOR shutting down

Handling error messagesBecause the VDM/MONITOR process is detached, i.e. not connected to a terminal, it sends allerror messages to the console.

There will be one or more messages. The first will give the error for what happened (i.e. unableto open log file). The next error message will give the reasons (i.e. insufficient quota.)

All errors from the detached process are signalled on the operators console regardless of thesetting of the console logging switch. This is to ensure that you will know as soon as possiblewhen the VDM/MONITOR detached process stops running.

Signalling these errors is done by establishing an error handler which sends the error to theconsole, then continues with the error handling. All errors pass through the error handler and itdecides whether the error comes from the detached process and has to be signalled.

Here are some sample VDM/MONITOR error messages:

This is an error message from the detached process.

%%%%%%%%%%% OPCOM 7-JUL-1999 19:24:04.00 %%%%%%%%%%%Message from user SYSTEM%VDM-W-ERRCREMBX, Error creating mailbox

%%%%%%%%%%% OPCOM 7-JUL-1999 19:24:05.36 %%%%%%%%%%%Message from user SYSTEM%SYSTEM-F-NOPRIV, no privilege for attempted operation

Hints for running VDM/MONITORThis section describes some hints and explanations that you might need for runningVDM/MONITOR.

Resource quotasSince VDM/MONITOR uses asynchronous system traps (AST'S) to time when to check disks,and to be notified when batch jobs complete, you may have to increase the UAF parameterASTLM. The process AST limit is the number of AST's that a process can have outstanding atone time. The detached processes AST limit defaults to the limit specified for the account thatstarted the detached process. If you see the detached process go intoRWAST (resource wait for AST) state, you may want to increase this parameter.

Stopping and re-starting VDM/MONITORIf the system is heavily loaded, and you issue the command VDM/MONITOR/STOPimmediately followed by the command VDM/MONITOR/START, you may receive the errormessage "VDM/MONITOR is already running". This is because the detached process may nothave actually stopped running yet. If this happens, execute the commandVDM/MONITOR/START again.

ClustersWhen running VDM/MONITOR on a cluster, you should only need to have one copy runningacross the cluster. VDM/MONITOR should be executed on a machine that has access to all thedisks in the cluster. If you have disks that are only accessible from one machine, you should runa copy of VDM/MONITOR on that machine, and that copy should have its own permanent datafile. This copy of the data file should contain the disks that are accessible from only thatmachine.

Disk quotasIf you have disk quotas enabled, the VDM/MONITOR detached process may not be able tocreate its log files. This will occur if VDM/MONITOR is started from an account without theEXQUOTA (exceed quota) privilege and the account has exceeded its quota.

If this is the problem, every time VDM/MONITOR's detached process is started, the PID numberis displayed (of the created process) but if a $ SHOW SYSTEM command is issued, the detachedprocess is not found.

To find out if the account has exceeded its disk quota, execute the DISKQUOTA Utility and lookat the username. If the permanent quota is less than the usage, increase the quota so it is largerthan the usage. You may increase the quota to 2 times the usage to be safe. The SYSTEMaccount has the EXQUOTA privilege so the quota does not restrict it.

NOTE: To limit the possibility of problems with the detached process and any batch jobsit submits we suggest you issue the VDM/MONITOR/START command while logged inas SYSTEM. If you add this command to your system startup file the monitor willautomatically be started under the SYSTEM account.

Debugging the VDM MonitorIf, at any time, the VDM monitor does not appear to be working use the VDM /MONITOR/STATUS command. This will generate a screen showing whether or not the monitor is runningas well as listing every disk and file being monitored and the current state of the event. For diskspace events this state will be Okay, Worry or Panic; for file events the state will be either true, ifthe event has already been detected, or false.

Correcting problems detected by VDM

This section shows you how to correct problems you locate using VDM.

For many VDM operations, you can generate a list of file names in your current directory usingthe /DCL qualifier. This allows you to make a list of the files which meet the criteria you'vespecified.

The [VDM.COM] directory contains a DCL shell procedure named PROCESS_FILE.COMwhich accepts a parameter specifying a file containing filenames, reads the file and does anoperation on each file. Use this procedure with the output from /DCL to perform "corrective"surgery on files with problems after editing it to include the operator you want to perform oneach file.

Collecting data

This chapter discusses how VDM collects data for subsequent analysis in usage, capacity anddirectory reports. Data collection must be done before usage, directory and capacity reports canbe generated. Cohort users can take advantage of the new common data collection procedure inRA Version 6 or 7; with this procedure disk information for RA and VDM is collected in onepass, reducing data collection overhead by nearly 50 percent. Refer to the section on VDM andRA in the RA user manual for more information; since RA’s data collection is more involvedthan VDM’s the procedures were added to RA.

Process DescriptionThe data collection process performs the following operations on every disk drive you'vespecified in DISKNAMES.DAT:

1. Generate usage dataRun the OpenVMS utility ANALYZE/DISK with the /USAGE qualifier on the drive. Thiscreates a temporary file containing usage by file, one entry per file, and can exceed 5,000 blocksin size. VDM deletes them as soon as it has summarized them.

2. Create VDM data filesRead the temporary usage files for the usage information and create the VDM data files whichare later used to create VDM reports. This is divided into four phases:

2.1 Determine usage by disk drive2.2 Create usage by UIC/identifier2.3 Create usage by directory (Optional)2.4 Run the special FILES report which shows a breakdown of files by size, the

largest 50 files and files that may need to be purged. (Optional)

3. Get quota data (Optional)Enable quotas (if they are not enabled), rebuild the quota file, extract quota information into atemporary file and disable quotas (if they were disabled originally). This part of collection isoptional. If it is not performed, quotas will be displayed as zero on all reports.

System ImpactAlthough data collection can be run while there are other users on the system, it is best to run itwhen there is no activity since it uses the OpenVMS ANALYZE/DISK and DISK QUOTAutilities which freeze volume activity momentarily and produce a sizable load on the drive forseveral minutes. Refer to the chapters on ANALYZE/DISK and DISK QUOTA for more details.

Conflict with BACKUPIf you run BACKUP at night, be sure that the run time does not conflict with the data collectionrun. No problems will occur, but data collection will take much longer if BACKUP is alsorunning. The same could be said for any other site specific jobs that run off-line at night. VDMdata collection is best performed on a lightly loaded system.

Automatic submissionOnce the data collection procedure is set up, it will normally run without further interaction fromyou. However, if your system goes down while a data collection is running, you may have toresubmit the batch job.

Time requiredVDM requires approximately 2 minutes per disk drive for data collection and consolidation on aMicroVAX 3100. The exact time is dependent on the type of disk drive, the number of files, thenumber of UICs, the amount of activity on the system and the processor type. You will have tomake sample runs to determine the time more exactly on your system.

Collecting quota informationVDM allows you to collect UIC quota information using the OpenVMS DISKQUOTA utility. By default, VDM will collect quota information. If the quota information is not important to you,you can remove the call to COLLECT_QUOTA in the collection procedure. Avoiding thecollection of quota information will decrease the data collection time.

Collecting directory informationBy default, VDM collects directory information. VDM allows you to exclude data collection fordirectories. Removing directory collection will reduce data collection time. If you do not want togenerate current or capacity reports in directory sequence, remove the VDM/DIR_COLLECTcommand from the data collection procedure. Disabling directory collection will also decreasethe amount of disk space consumed by the VDM data files substantially.

Specifying disk drivesVDM uses a file DISKNAMES.DAT in the [VDM.DAT] directory to determine which files tocollect data on. Modify this file to fit your needs. If you maintain scratch drives which do notcontain permanent data, they would normally be excluded from the data collection process. Themaximum number of drives that VDM can handle in a single pass is 200.

Specifying collection timeBy default, VDM starts collecting data at 10 p.m. This is normally a period of low activity so thatdata collection won't impact other processes. If you want to collect data at some other time,modify the COLLECT.COM command procedure. Remember to consider other off-lineprocedures such as BACKUP.

Generating file size reportsBy default, VDM generates a file size report. You can omit this report if you wish. For moreinformation, refer to the chapter "Generating File Size Reports".

Specifying the location of the batch logVDM will put the batch log from data collection in the VDM_DAT directory. If /LOG_FILE isleft out of the SUBMIT call, the default directory for the log file is SYS$LOGIN.

Side benefits

VDM data collection has two side benefits you may be interested in. The first is thatANALYZE/DISK is run on your disk drives on a regular basis as part of the data collectionprocess. This may enable you to detect errors on a drive earlier than you normally would. Thesecond benefit is that the disk quota information is rebuilt each data collection if you choose tocollect quota information. This means that the information in the quota file will be moreaccurate.

Generating usage reports

This chapter shows you how to use VDM to generate current usage reports.

Usage reports show the number of disk blocks each user currently has allocated, contrasts it withthe allocation on some previous date and flags possible problems. Use usage reports to detectlarge increases in accounts and users who are nearing their quota. Usage reports allow you tomanage disk resources by highlighting change.

Department & project analysisVDM allows you to analyze usage by owner or account as well as username. This gives youthree independent ways to summarize individual user disk allocations. If you set up yourSYSUAF carefully, you can get useful department and project reporting with minimal cost andeffort.

Selecting and summarizing disk drivesYou can select one or more disk drives using the /DISK qualifier. If you specify the/SUMMARY qualifier, the drives will be summarized into a single report. Otherwise, each diskwill be presented in a separate report.

Sorting criteriaYou can generate usage reports in several sequences. You select a sequence using the/SEQUENCE qualifier.

/SEQUENCE=USERNAME shows disk allocations by username. Username is an OpenVMScode consisting of 1 to 12 alphanumeric characters assigned by systems managers to identifyusers. A sample username might be "GEORGE".

/SEQUENCE=UIC shows disk allocations by UIC. UIC is an OpenVMS code consisting of agroup and member number separated by a comma and enclosed in brackets. It is assigned bysystems managers to group users together. A sample UIC might be "[1,4]" or "[88,21]". Thiscriteria can be used to generate project or department summaries from the VDM data. VDMallows you to display UICs in alphanumeric form such as "[ENG,ANN]". If the UIC does nothave a corresponding record in the UAF, it is flagged with an "*".

/SEQUENCE=GROUP summarizes the data by group as opposed to the entire UIC.

/SEQUENCE=ACCOUNT shows disk allocations by account. Account is a 1 to 8 alphanumericcharacter description field in the UAF. It is assigned by systems managers to group userstogether. A sample account string might be "Project9". It can be used to group users togetherindependently of UIC or username. Thus, it can be used to generate project or departmentsummaries from the disk usage data.

/SEQUENCE=OWNER shows disk allocations by owner. Owner is a 1 to 31 alphanumericcharacter description field in the UAF. It is assigned by systems managers to group users

together. A sample account string might be "Accounts Payable Dept". It can be used to groupusers together independently of UIC, username or account. It also can be used to generate projector department summaries from the VDM data.

/SEQUENCE=DIRECTORY shows disk allocations by directory. VDM truncates the directoryto 50 characters for reporting purposes. Refer to the chapter "Generating directory reports" inthis manual for more information.

/SEQUENCE=DISK shows disk allocations by disk. This is a summary report by disk; each diskoccupies one line on the report. Use it to get a one-page overview of your disk status.

Selecting only large accountsUse the /SIZE qualifier to select accounts with a minimum disk usage. Use this qualifier to limitthe report to the major accounts where problems are most frequent. Detecting accounts with large increasesVDM flags users whose accounts are increasing rapidly in size. You specify a percentageincrease using the /LARGE_CHANGE qualifier and VDM flags current usage lines with "*" iftheir percentage change exceeds the amount you've specified. The default for large change is20%.

Detecting users nearing their quotaVDM flags users whose allocations are close to their quota. You specify a percentage using the/NEAR_QUOTA qualifier and VDM flags the percent quota field with "*" if their percentagequota exceeds the amount you've specified. The default for near quota is 80%.

Reporting only exceptionsUse the /EXCEPTION qualifier to display the users who are flagged for "large change" or "nearquota". This will allow you to see the potential "problem" users in the report rather then allusers. On a large system with many users, this can be a great convenience.

Setting quotasOne of the problems with establishing quotas on OpenVMS is deciding on their initial size andadjusting them as the needs of the users change. VDM provides an easy way to determine quotavalues since it maintains both an average and a maximum value for each account. Based onthose numbers, you can establish a quota which controls users without constraining themunnecessarily.

Report headingsThe current usage report headings contain the following information:

• Report name • Run date and time • Node name • Selected disk drive(s)

• Near Quota threshold • Large Change threshold

These heading fields record all the options you entered on your VDM/REPORT command. Thecurrent and previous dates are displayed over the appropriate column headings.

Report fieldsThe current usage report contains the following fields:

Key - contains the username, account, owner, UIC, directory or disk depending on the/SEQUENCE qualifier. There is one line on the report for each entity which has disk blocksallocated.

Previous usage - contains the number of disk blocks the user had allocated on some previousdate. You specify the date using the /PREVIOUS qualifier.

Current usage - contains the current number of disk blocks the user (account, owner, etc.) hasallocated. You specify the date using the /CURRENT qualifier.

Percentage of blocks allocated - indicates what percentage of the total disk blocks this user has. It is calculated using the formula:

(Current / Total Allocated) X 100

Percentage change from previous - indicates by what percentage the account has changed sincethe previous run. It is calculated using the formula:

((Current - Previous) / Previous) X 100

The report contains a warning "*" after this field if it exceeds a percentage you indicate with the/LARGE_CHANGE qualifier. If /EXCEPTION has been specified, the "*" is omitted.

Disk quota - contains the maximum number of blocks the user is allowed to have allocated. Ifquotas are not active during VDM data collection, the quota field will contain zero. If quotas areactive during VDM data collection but not enabled, the quota field will contain the default quota. On summary reports, the individual quotas are added together and theirtotal is shown.

Percentage of quota - indicates what percentage of their account quota this user has used up. Itis calculated using the formula:

(Current / Quota) X 100

The report contains a warning "*" after this field if it exceeds a percentage you indicate with the/NEAR_QUOTA qualifier. If /EXCEPTION has been specified, the "*" is omitted.

Average usage - contains the average number of blocks the user has had allocated since the lastreset. This number is updated after the data collection run. Refer to the chapter "ResettingAverages" for an explanation of how the average is calculated.

Maximum usage - contains the maximum number of blocks the user has allocated since the lastreset. This number is updated (if necessary) after the data collection run.

Percentages and roundingThe current usage reports contain several percentages. To present a concise, readable report,these percentages are all rounded, on the report, to ONE decimal place. (ie 23.42 becomes 23.4and 56.87 becomes 56.9). This means the individual percentages may not always total 100exactly.

Overflow, underflow and undefined numbersIf an observed value is too large to be shown in a report field, it is replaced by "999M". If anobserved value is too small to be shown in a report field, it is replaced by "-999M". If acalculated value involving a previous number is undefined because there is no previous number,it is shown as "0" and flagged as undefined. Non-labelled UICs and identifiersUICs and identifiers which do not have a corresponding record in the SYSUAF or the RIGHTSlist are listed at the end of the report. You should check these UICs and identifiers to see if thereis a problem. In /SEQUENCE=UIC reports these records are included in the body of the report;to help differentiate them from valid UICs they are flagged with an "*".

Examples

$ VDM /REPORT=CURRENT /PREVIOUS=01-NOV-96 /SEQUENCE=USERNAME -/SUMMARY /NEAR_QUOTA=90

Produce a current usage report by username for all disk drives using November 1st, 1993 for theprevious numbers. Any user with 90% or more of their quota allocated will be flagged.

$ VDM /REPORT=CURRENT /SEQUENCE=UIC /LARGE_CHANGE=15 -/DISK=(DRA1:,DRA2) /EXCEPTION

Produce a current usage report by UIC for the disk DRA1: and DRA2. Only the UICs whichhave changed by more than 15% will be printed in the report.

$ VDM /Report=current /seqeunce=username /size=5000 /current=15-dec-99Produce a current usage report by username for all disks using December 15th as the date for thecurrent numbers. Only users which have 5,000 or more blocks allocated will be printed in thereport. The date used for PREVIOUS will be determined by VDM and will be earlier thanCURRENT.

$ VDM/report=current/sequence=owner/summary/current=15-dec-99Produce a current usage report by owner for all disks using December 15th as the date for thecurrent numbers. Since /LARGE_CHANGE and /NEAR_QUOTA were not specified, VDMwill use default values of 20 and 80 percent to flag lines in the reports. The date used forPREVIOUS will be determined by VDM and will be earlier than CURRENT.

$ VDM /report=current /sequence=detail /current=30-nov-1999 Generate the new detail report showing disk usage as of November 30, 1999, for each user. Aseparate page is generated for each user showing all the disks that user has files on and the totalusage. This report is new with Version 7 of VDM and is an ideal tool for providing backup to RAdisk billing values or for cleaning up disks.

Forecasting future requirements

This chapter shows you how to use VDM to do capacity planning. Capacity planning is theprocess of projecting growth in resource usage to determine if new equipment has to be ordered. To generate a capacity planning report, VDM needs four pieces of information:

1. Current usage VDM gets the current usage from its own data files. You can select ACTUAL(allocated) usage, AVERAGE usage, MAXIMUM usage, or USED usage using the /USAGEqualifier. /USAGE=AVERAGE normally provides the best basis for projection and is the default.

2. Period length By default, the projection period length is 3 months. Use the /PERIODqualifier to specify a large or smaller number of months.

3. Rate of increase VDM uses as the projected rate of increase either:

3.1 A user-supplied percentage You can specify a rate of increase using the /RATE=nqualifier where n is a per interval percentage increase. It can be positive or negative andcan include fractions (ie 2.4%)

3.2 The observed increase If you don't specify a rate, VDM uses the percentage changebetween current usage and usage on some previous date to determine the rate of increase. You specify the previous date using the /PREVIOUS qualifier. Be sure to allow areasonable length of time (a couple of months) between current and previous. Adifference of only a week will likely cause inaccurate projections. VDM assumes that theobserved rate of change applies to one projection interval, therefore you should specify acurrent and previous date which represents the number of months you have chosen foryour projection interval.

4. The date used for the previous values If you don't specify a previous date VDM willdetermine the number of days in the period and check for data from that long ago. If a data file isnot found for that date VDM will decrement the number of days by 1 and check again. Itcontinues this way until it finds a data file. In this way VDM finds the oldest data file from thelast period to use in its' calculations.

To present a concise, readable report, the rate of increase is truncated on the report to twodecimal place (ie 23.423 becomes 23.42 and 56.878 becomes 56.87). Internally, VDM carriesthe rate of increase to much more precision. This means the projected increases may not appearto be consistent with hand calculations.

Projection calculationVDM shows your current usage and project usage for five periods into the future. It uses asimple (as opposed to compound) rate of growth when it is projecting growth. Projections aretruncated to the nearest block.

You can specify a sequence using the /SEQUENCE qualifier, summarize the data using the/SUMMARY qualifier and select disk drives using the /DISK qualifier. Refer to the previouschapter "Generating Usage Reports" for more information on these qualifiers.

Examples

$ VDM /REPORT=CAPACITY /PREVIOUS=01-NOV-96 /SEQUENCE=USERNAME -/SUMMARY

Produce a capacity planning report by username for all disk drives using the observed differencebetween current usage and November 1st, 1993 as the projected rate of increase. Since type ofusage is not specified, average usage is used. The default interval of 3 months is used.

$ VDM /REPORT=CAPACITY /DISK=(DRA1:) /RATE=2 /SEQUENCE=UIC - /PERIOD=4

Produce a capacity planning report by UIC for DRA1: using a specified rate of increase of 2%per interval, using a 4 month interval. Since type of usage is not specified, average usage isassumed.

$ VDM /REPORT=CAPACITY /USAGE=ACTUAL /SEQUENCE=OWNER -/SUMMARY /RATE=1.6

Produce a capacity planning report by owner for all disk drives at a rate of 1.6 percent. Since/PREVIOUS was not specified VDM will find the oldest data file that is one period old or morerecent.

Generating directory reports

This chapter shows you how to use VDM to generate directory reports. Directory reports showhow blocks are allocated by directory and how directories have increased or decreased in size.

The directory report analyzes directories. It does not show the size of individual files in adirectory. Use other VDM reports to obtain information about individual files.

Directory StructureVDM uses the current directory structure as the standard. If the previous directory included sub-directories which have subsequently been deleted, the blocks in those directories are not includedin the previous totals.

Directory sizesThe number of blocks shown for each directory is the number of blocks allocated to the files inthat directory plus the number of blocks that contain file headers used by the files in thatdirectory. If your disks are relatively contiguous, the number of file headers will be equal to thenumber of files in that directory.

Summary dataThe blocks in each directory are reported (for example "[ENG]") as well as the TOTAL blocks inthe directory and all sub-directories (for example "[ENG...]"). Level 1 "directory" reports showonly the total blocks for each directory (for example "[ENG...]" unless no sub directories exist inthe level 1 directory.

LevelsNormally, the directory report displays only the top level directories (ie those immediately below[000000]) and 1 level of subdirectories (/LEVEL=2). However, the directory report can alsodisplay an additional level of sub-directories. You specify the number of levels of directory toshow using the /LEVEL qualifier. If you specify /LEVEL=4 or higher, VDM assumes/LEVEL=3.

Levels and directoriesThe following pages show examples of how the /LEVEL qualifier can be used to summarizedirectories using a sample directory structure of:

000000

ENG ENG.MOE ENG.MOE.SRC ENG.MOE.EXE ENG.CURLY ENG.CURLY.SRC ENG.CURLY.EXE

PROD PROD.EXE PROD.COM PROD.DOC

If /LEVEL=1 is entered, the report will contain the lines:

000000

ENG

PROD

If no level qualifier is entered, /LEVEL=2 is assumed and the report will contain the lines:

000000

ENG ENG.MOE (total for this directory and all sub-directories) ENG.CURLY


And finally, if /LEVEL=3 is entered, the report will contain the lines:

000000

ENG ENG.MOE ENG.MOE.SRC ENG.MOE.EXE ENG.CURLY ENG.CURLY.SRC ENG.CURLY.EXE


Examples

$ VDM /REPORT=CURRENT /SEQUENCE=DIRECTORY /PREVIOUS=01-NOV-96Produce a current report by directory for all disk drives showing current usage and usage as ofNovember 1st, 1993. Since the number of levels is not specified, VDM assumes /LEVEL=2.

$ VDM /REPORT=CAPACITY /SEQUENCE=DIRECTORY /LEVEL=3Produce a capacity report by directory for all disk drives showing current usage and previoususage using the oldest data from no more than 3 months ago (the default). Since three levels ofdirectory have been specified, a total for each top level directory will be presented along with atotal for all sub-directories down two levels. If the directory structure is deeper than three, thelower level will be summarized. If the directory structure has only one level, it will be presented.

Generating file size reports

This chapter shows you how to use VDM to generate file size reports during data collection. Thefile size report summarizes the number of files by size and lists the names of the 50 largest filesin descending order of size. It is an optional report that can only be generated at collection timefor each disk that is in the DISKNAMES.DAT file. It cannot be generated on-line, though someof the information it contains is reported in the /REPORT=SIZE on-line report. It contains threesections:

Interval files reportThis section of the report summarizes files by size. Files with sizes for 0 - 49 blocks aresummarized in increments of 10. Files with sizes from 50 - 999 blocks are summarized inincrements of 50. Files with sizes of 1000 blocks and over are summarized in increments of1000. For each category, the report shows:

• number of files in the category • total allocated blocks in the category • percent of total allocated blocks • total used blocks in the category • percent of total used blocks

Large files reportThis section of the report lists the 50 largest files on that disk in descending order of size. It islocated on the right hand side of the page. The report shows the filename (up to 50 characters) aswell as blocks allocated and blocks used.

File versions reportOn the second page of the file size report VDM displays files with multiple versions indescending order by the number of copies of each file on disk. It displays the filename, numberof versions, total blocks used and total blocks allocated. In conjunction with the purge commandthis report helps keep multiple versions of files from using a large amount of disk space.

Finding files that no longer belong to an authorized user

Frequently in OpenVMS when an account is deleted from the System Authorization File(SYSUAF) files remain on the system that have that particular user as their owner. These filesare then included in disk accounting reports and the VDM reports as unauthorized usage. VDMVersion 7 now includes a report that will scan a disk for all the files that do not belong to a validSYSUAF account and report them. These files can then be set to belong to a valid user or deletedfrom the system.

The report includes the directory, filename, used, allocated and unused blocks, the creation dateand the owner UIC.

Note: It is normal for there to be a number of system files in the master ([000000]) directory ofevery disk that belong to [1,1] however user files should not be set to belong to this system UIC.

Note: In a cluster without a common SYSUAF file you should note that unless users areauthorized on all nodes they maybe reported as unauthorized when this report is run on aparticular node and yet be valid. VDM cannot compare the ownership of the file to mutlipleSYSUAF files; it is important that you run the report on the node with the most authorized usersand verify the results by checking for the unauthorized UICs in the other SYSUAF files, in thecluster, before deleting or changing the ownership of any files!

Example

$ vdm /report=unauthorized /disk=$1$dka100: /output=dka100_orphans.rptThis report will scan the files on disk $1$dka100: and create a report showing all the files that donot belong to an authorized user.

Generating reports off-line

This chapter shows you how to use VDM to generate reports off-line after data collection hascompleted.

Most VDM users run a regular set of reports after data collection. This is the "standard"information they wish to receive each morning.

Sample data analysis proceduresThe distribution kit contains the COM files ANALYSIS_1, ANALYSIS_2 and ANALYSIS_3containing various report requests which can be customized to your needs.

On-going interactionThe data analysis procedure would normally run immediately after the data collection run. Oncethe procedure is set up, it will normally run without further interaction with you. However, ifyour system goes down, you may have to resubmit the batch job.

We strongly recommend that you set up a standard set of reports and review your disk usage atleast weekly. Disk management is not complex or time-consuming but it does require regularattention.

VDM and the user authorization file (SYSUAF.DAT)

This chapter discusses the SYSUAF.DAT and its relationship with VDM.

The User Authorization File (SYSUAF.DAT) is an OpenVMS system file containing importantinformation on every user who is authorized to gain access to the system. Each SYSUAF.DATrecord contains the username, password, UIC, privileges and additional information.

It is normally maintained by the OpenVMS utility AUTHORIZE.

It can be read in either user name or UIC sequence.

Typically, there is one record in the UAF for each user that can access the system. There is arecord with the user name "DEFAULT" which contains default values used during the creation ofnew accounts. There are special accounts such as SYSTEST, SYSTEST_CLIG and FIELD foruse by Digital personnel.

VDM uses four fields in the UAF:

• Username • UIC • Account • Owner

SYSUAF.DAT accessVDM needs read-only access to the file.

The section in this manual on using VDM in a cluster outlines how you can use the logicalSYSUAF to instruct VDM which user authorization file to use when creating reports. This can beuseful if you wish to run reports on a node other than the one that data collection is run on. If youhave a cluster common authorization file, VDM will use it automatically.

For more complete information about the User Authorization file refer to the OpenVMSAUTHORIZE manual.

Updating account names

This chapter shows you how to modify account names in the UAF. Account is part of the UAFrecord and is updated by the OpenVMS AUTHORIZE utility. It is a user-assigned code used togroup users together independently of UIC or username. It can be used to generate project ordepartment summaries from the disk usage data.

NOTE: In the following text, we have assumed that the UAF record for the user has already beencreated.

For more data on the UAF and the functions you can perform on it, refer to the OpenVMSAUTHORIZE manual.

Adding new accountsTo add new accounts to the UAF record, use the following command:

RUN AUTHORIZE UAF>MODIFY username/ACCOUNT=account-name

where "username" is the username you want to change and "account-name" is the new accountfor that user.

Removing accountsTo remove accounts from the UAF record, use the following command:

RUN AUTHORIZE UAF>MODIFY username/ACCOUNT=""

where "username" is the username you want to change and there is no account name.

Listing accountsTo list the accounts in the table, use the following command:

RUN AUTHORIZE UAF>LIST

This command will list ALL fields in the records in the UAF file to a default file SYSUAF.LISon the current drive. Output can be directed to the printer or a file using the /OUTPUT qualifier.

The FULL OpenVMS AUTHORIZE list is comprehensive but not very readable. For a morereadable report, use the following command:

RUN AUTHORIZE UAF>LIST/BRIEF

Updating owner names

This chapter shows you how to modify owner names in the UAF. Owner is part of the UAFrecord and is updated by the OpenVMS AUTHORIZE utility. It is a user-assigned code used togroup users together independently of UIC or username. It can be used to generate project ordepartment summaries from the disk usage data.

NOTE: In the following text, we have assumed that the UAF record for the user has already beencreated.

For more data on the UAF and the functions you can perform on it, refer to the OpenVMSAUTHORIZE manual.

Adding new ownersTo add a new owner to the UAF record, use the following command:

RUN AUTHORIZE UAF>MODIFY username/OWNER=owner-name

where "username" is the username you want to change and "owner-name" is the new owner forthat user.

Removing ownersTo remove the owner from the UAF record, use the following command:

RUN AUTHORIZE UAF>MODIFY username/OWNER=""

where "username" is the username you want to change and there is no owner name.

Listing ownersTo list the owners in the table, use the following command:

RUN AUTHORIZE UAF>LIST

This command will list all fields in the records in the UAF file to a default file SYSUAF.LIS onthe current drive. Output can be directed to the printer or a file using the /OUTPUT qualifier.

The full OpenVMS AUTHORIZE list is comprehensive but not very readable. For a morereadable report, use the following command:

RUN AUTHORIZE UAF>LIST/BRIEF

Resetting averages

This chapter shows you how to use VDM to reset allocation averages.

VDM calculates the average number of blocks allocated to each user. The average is updatedeach time data collection is done. If this is done weekly, it is not as representative of the "true"average as daily updates would be but it is normally good enough for disk management purposes.

Use the command VDM/RESET/VALUE=AVERAGE to reset the average.

NOTE: The average will get increasingly insensitive to current information as the amount ofhistorical information grows. We recommend that you reset the average at least once everythree months. Resetting the average does NOT affect the maximum.

AveragesVDM incorporates historical data into the average calculation so that extremes in usage do notaffect the average as strongly as they normally would.

Every data collection, VDM performs the following calculations:

Total-to-date = Total-to-date + Current-usageNumber-of-observations = Number-of-observations + 1

To calculate an average, VDM uses the formula:

Total-to-dateAverage = ---------------------- Number-of-observations

The reset function sets:

Total-to-date = AverageNumber-of-observations = 1

Resetting maximums

This chapter shows you how to use VDM to reset allocation maximums.

VDM maintains a record of the maximum number of blocks allocated to each user. Themaximum is checked and updated if necessary each time data collection is done.

Use the command VDM/RESET/VALUE=MAXIMUM to reset the maximum.

After the reset command, the maximum will be equal to the current usage.

NOTE: Since the maximum is a "high water mark", it may get increasingly unrealistic comparedto current information as the time from the last reset grows. We recommend that you reset themaximum at least once every three months. Resetting the maximum does NOT affect theaverage.

VDM and disk quotas

This chapter discusses disk quotas and their relationship with VDM.

Many sites do not use disk quotas. This is unfortunate since quotas are a valuable tool for diskmanagement. The common complaint that users have is that quotas prevent them from gettingtheir work done. However, with sensible quotas which are reviewed regularly, users will notcomplain about being hampered and you will be able to support more users with the sameamount of disk. VDM provides you with the numbers to create satisfactoryPERMANENT and OVERDRAFT limits for your users.

NOTE: VDM will work whether you have quotas enabled or disabled.

If you wish to collect quota information with VDM and a quota file does not exist on the volume,you must CREATE one using the DISKQUOTA section of the SYSMAN utility.

If quotas are NOT enabled on the volume, data collection will ENABLE them, REBUILD thequota file and DISABLE them.

If quotas ARE enabled, data collection will REBUILD the quota file, and leave the quotasENABLED.

In all cases, VDM's processing will not affect the rest of your operation.

NOTE: If you don't use quotas, you must disable them when you MOUNT the disk volume sincethe default is to enable the disk quotas when the volume is mounted. To disable thequotas when mounting the disk, use the /NOQUOTA qualifieron the mount command.

Creating and optionally enabling quota filesTo create a quota file:

1. Wait until you are alone on the system and invoke the SYSMAN utility $ MCR SYSMAN2. CREATE the quota file SYSMAN> DISKQUOTA CREATE /DEVICE=diskname3. MODIFY [0,0] which sets the default values for the initial build SYSMAN> DISKQUOTA MODIFY [0,0]/DEVICE=diskname/PERM=10000004. REBUILD the quota file to create quota entries for every UIC currently on the

disk SYSMAN> DISKQUOTA REBUILD /DEVICE=diskname5. ENABLE disk quota checking (optional) SYSMAN> DISKQUOTA ENABLE /DEVICE=diskname

6. Exit the SYSMAN utility SYSMAN> EXIT

If you are not using quotas, the above procedure prevents problems with users exceeding theirquotas. It allows any user to allocate essentially unlimited space (up to 1,000,000 blocks) on thevolume. If an account creates files on the volume then the account UIC is added to the quota file(REBUILD does this), their default quota will be the value stored in [0,0]. At some later date,when you have decided on reasonable quotas, you can adjust the values in [0,0] and theindividual UICs.

For more information about disk quotas and disk management, refer to the OpenVMS SYSMANmanual and the OpenVMS System Manager's Guide.

VDM and the OpenVMS ANALYZE/DISK utility

This chapter discusses the OpenVMS utility ANALYZE/DISK and its relationship with VDM.

ANALYZE/DISK is a utility supplied by Digital to verify the contents of a disk pack. It verifiesthat blocks are not doubly allocated, that file headers are accurate and that file pointers are valid. This requires a considerable amount of I/O activity.

/USAGEVDM runs VERIFY with the /USAGE option to collect data on disk allocation by file and UIC. This is the primary reason VDM runs VERIFY.

/READ_CHECKVDM runs VERIFY with the /NOREAD_CHECK option. READ_CHECK performs additionalverification of the disk but at the cost of increased I/O activity. Data collection will run muchslower if you substitute /READ_CHECK but it will do a better job of verifying your disks.

/REPAIRVDM runs VERIFY with the /NOREPAIR option. We do not recommend using /REPAIRduring VDM data collection runs.

NOTE: If you have not been running ANALYZE/DISK regularly, you may have problems on thefirst VDM data collection run because of the number of errors or inconsistencies theANALYZE/DISK utility locates. You may need to run /REPAIR manually to clean up these errorand inconsistencies.

For more complete information, refer to the OpenVMS VERIFY manual.

Handling volume and shadow sets

This chapter shows you how VDM handles volume and shadow sets.

Volume setsA volume set is a logical volume which includes two or more physical volumes.

VDM will work on volume sets. When you specify the disk names for the collection procedure,you should specify only the first disk of the volume set. All the data that VDM needs iscontained on that first volume. If by accident a secondary volume disk is specified VDM willautomatically ignore it.

When using VDM's monitor to check free space on volume sets, use the /DISK=device_name toadd a disk record to the permanent data file. The device name of any volume in the set may bespecified to add and/or change the free space thresholds for the volume set. However, when theparameters of the database are listed, the device name shown will be the device name of the rootvolume.

Shadow setsA shadow set is a duplicate disk to which a write is made every time a write is made to thevolume being shadowed.

Enter the shadow set name into the DISKNAMES.DAT file and VDM will collect data on it.

Files you need to use VDM

This chapter shows you how VDM and OpenVMS files are used by VDM and the amount of diskspace they require.

VDM directory structureThe VDM directory contains all executables, objects, documentation and command procedures. Here is its structure:

[VDM.CDU] Command Definition.COM] DCL Command Procedures.DAT] Data Files.DEF] Include Files, SOURCE licenses only

.VAX] VAX OpenVMS

.AXP] Alpha AXP OpenVMS.DOC] Documentation and HELP text.EXE Executables

.VAX] VAX OpenVMS

.AXP] Alpha AXP OpenVMS.LIS] Compile Listing Files, SOURCE licenses only.MAP] Compile Map Files, SOURCE licenses only.MSG] Error Message text and object.OBJ] Object Library

.VAX] VAX OpenVMS

.AXP] Alpha AXP OpenVMS.SRC] FORTRAN Source, SOURCE licenses only

.VAX] VAX OpenVMS

.AXP] Alpha AXP OpenVMS

VDM requires 1,800 blocks for the VAX/OpenVMS version or 2,700 blocks on the AXP (4,000blocks if they are both installed in the same directory structure). If you have source, thosedirectories requires an additional 1,900 blocks.

SYSUAF.DATVDM reads information from the OpenVMS System User Authorization File. Refer to thechapter "VDM and the OpenVMS user authorization file (SYSUAF.DAT)" for moreinformation.

Data filesVDM has five permanent data file types:

• USAGE by UIC, filename VDM_UIC_date.DAT, for each data collection • USAGE by Directory, filename VDM_DIR_date.DAT, one for each data collection

• DISKNAMES.DAT, one on each node that data is collecting data • VDM_PLA.DAT, one on each node that is collecting data • VDM_PERM_DATA.DAT, one on each node that VDM/MONITOR is running on

Usage by UICThese files contain disk allocation data used to generate analysis reports for username, UIC,account, and owner. The files are named VDM_UIC_date.DAT. It is an indexed file keyed onUIC and disk volume name. There is a record in the file for each UIC and disk (ie if the UIC hasblocks on three disk drives, there are three records). Each record contains the fields:

• Disk name • UIC Group • UIC Member • UIC • Current allocated blocks • Current used blocks • Average allocated blocks • Average weight • Maximum allocated blocks • Quota

Username, account and owner are obtained from the UAF file directly, during report generation,rather than being stored in the usage record.

The FORTRAN structure describing the record is stored in VDM_UIC_RECORD.TXT in thetext library VDM_TEXT.TLB in [VDM.DEF.VAX] or [VDM.DEF.AXP].

Usage by DIRECTORYThese files contain directory data used to generate directory analysis reports. It is an indexed filekeyed on disk volume name and directory. The files are named VDM_DIR_date.DAT. Eachrecord contains the fields:

• Disk name • Directory • Current allocated blocks • Current used blocks • Average allocated blocks • Average weight • Maximum allocated blocks

The FORTRAN structure describing the record is stored in VDM_DIR_RECORD.TXT in thetext library VDM_TEST.TLB in [VDM.DEF.VAX] or [VDM.DEF.AXP].

DISKNAMES.DATThis file contains the disknames you wish VDM to collect information for. It also tells VDM

whether or not to update quotas for that disk, and to leave them enabled or disabled. This file iscreated during the installation procedure and can be recreated by executingCREATE_DISK_FILE.COM in the [VDM.COM] directory. It can also be modified using a texteditor such as EVE (TPU) or EDT.

VDM_PLAThis file is used by VDM for reporting purposes. It is an indexed file keyed on disk name and isrecreated every data collection. There is a record in the file for each disk that VDM collects dataon. Each record contains:

• Disk name • Total allocation • Total used • Maximum blocks • Quota

The FORTRAN structure describing the record is stored in VDM_PLA_RECORD.TXT in thetext library VDM_TEXT.TLB in [VDM.DEF.VAX] or [VDM.DEF.AXP].

VDM_PERM_DATA.DATThis file is used and maintained by VDM's monitor. It contains the Defaults and values for alldisks which VDM has been configured to monitor.

Work filesVDM creates two temporary data files during data collection. The size of these temporary filesdepends on the number of disks you are collecting data for. VDM requires approximately 400blocks for these files for every five disks being included in the data collection. They are deletedat the end of the data collection procedure.

Data file removalVDM does not delete any data files. You must purge the data files you do not want.

You must decide how many sets of data files you wish to keep and establish some procedure toremove old files.

Data logical nameAll permanent VDM data files are stored in the directory pointed to by the logical VDM_DAT:. Temporary files are created in SYS$SCRATCH:.

Sort work filesSorts can put a large I/O load on the system. To spread out the I/O load, the sort work files canbe assigned to different devices. Use the statement

$ ASSIGN device: SORTWORKn

where n is the number of the work file (number from 0 to 9). This will split the I/O load over thedrives specified. You can add these assign statements to the data collection procedure(COLLECT.COM) to balance the I/O load during data collection.

Logicals you need to use VDM

This chapter shows you the logicals that VDM uses and how to define them. To use VDM, youmust define several logicals. Here is a description of each logical that may be defined on yoursystem.

VDM$NOCONVERT - Disables conversion of logical disk names to their physical equivalent.

VDM_CDU - This logical points to the [VDM.CDU] directory. It is used to access the VDMcommand definition table. VDM_CDU is optional.

VDM_COM - This logical points to the [VDM.COM] directory. It is used to access VDM DCLcommand procedures. VDM_COM is optional.

VDM_DAT - This logical points to the [VDM.DAT] directory. It is used to access the data files. It must be defined in the system logical table. VDM_DAT is required.

VDM_DOC - This logical points to the [VDM.DOC] directory. It is used to access the screeninterface help files. It must be defined in the system logical table. VDM_DOC is required.

VDM_EXE - This logical points to the [VDM.EXE.VAX] or [VDM.EXE.AXP] directory. It isused to access the VDM executables. It must be defined in the system logical table. VDM_EXEis required.

VDM_LOG_FILE - This logical defines the location and name of the log file if you want it tobe different from the default location and name.

VDM_PERM_DATA - This logical defines the location and name of the permanent data file ifyou want it to be different from the default location and name.

GO_DEVICE - This logical is used to control the default directory when the drive is changed. Itis normally defined in your process logical table by an entry in your LOGIN.COM. If you wishto modify the default value of this logical, you should define it in your LOGIN.COM file. Thelogical has only two valid values: "ON" and "OFF".

GO_DISPLAY - This logical is used to control the display of the current directory message. Itis normally defined in your process logical table by an entry in your LOGIN.COM. If you wishto modify the default value of this logical, you should define it in your LOGIN.COM file. Thelogical has only two valid values: "ON" and "OFF".

GO_NODE - This logical is used to control the display of the current directory message. It isnormally defined in your process logical table by an entry in your LOGIN.COM. If you wish tomodify the default value of this logical, you should define it in your LOGIN.COM file. Thelogical has only two valid values: "ON" and "OFF".

GO_PROMPT - This logical is used to control prompt redefinition. It is normally defined inyour process logical table by an entry in your LOGIN.COM. If you wish to modify the defaultvalue of this logical, you should define it in your LOGIN.COM file. The logical has only thefollowing valid values: "ON", "OFF", "1", "2" or "3".

You can define the standard VDM logicals by typing:


SYSUAF - This logical points to the UAF file. The default definition is"SYS$SYSTEM:SYSUAF.DAT"; the system will use this file specification of SYSUAF is notdefined. Note that this is a logical defined by OpenVMS rather than a VDM logical.

VDM$SHOW_COMMAND - If this logical is defined VDM will include the DCL commandused to generate a report at the bottom of the report.

VDM$KEEP - If this logical is defined VDM will submit all action procedure jobs from themonitor with /keep set so the logs are not deleted when the job completes.

VDM$USE_DISK_NAME - VDM uses the $GETDVI item DEVNAM to determine a disksname during data collection and for subsequent reporting. If VDM$USE_DISK_NAME isdefined, in the system table, to be FULLDEVNAM VDM will use that item to determine thedevice name instead. This is primarily useful at sites using HSC controllers that move disksperiodically since the DEVNAM will change but FULLDEVNAM normally doesn’t.

VDM$ERROR_HANDLER - By default the Monitor detached process traps severe errors andcontinues to prevent an error from stopping the monitor. Defining this logical to anything butitself will instruct the VDM monitor to stop running when it detects a severe error.

The command procedure SYS$MANAGER:VDM_SITE_LOGICALS.COM is new with Version6 of VDM. All logicals expect VDM_COM, VDM_DAT, VDM_DOC, VDM_CDU andVDM_EXE that are defined should be added to this procedure which is executed during systemstartup. This procedure will not be replaced during subsequent upgrades and will, therefore,preserve your site specific logical names and their values.

Privileges you need to use VDM

This chapter shows you the privileges needed to do various VDM operations.

VDM requires the following privileges to run:• SYSPRV• TMPMBX• NETMBX

Data collectionFor ANALYZE/DISK operations, VDM does not require the BYPASS and EXQUOTAprivileges, but we recommend the process have those privileges. For more details, see theOpenVMS VERIFY manual.

For QUOTA operations, VDM requires one of the following:- SYSPRV- a system UIC- ownership of the volume

For more details, see the OpenVMS DISK QUOTA UTILITY manual or the SYSMANUTILITY manual.

Data analysisFor data analysis (generating reports), VDM requires READ, WRITE and DELETE access to theVDM data files and READ access to the system UAF file.

VDM/MONITORVDM/MONITOR requires the following privileges to run.

• DETACH• OPER• PRMMBX• SYSNAM• SYSPRV• WORLD

NOTE: If you want to start the detached process with a base priority of 10 (a higher priorityensures more precise data collection) you require ALTPRI privilege. Otherwise, thebase priority of the creator process will be used.

You can acquire all the necessary privileges by typing:


Resources you need to use VDM

This chapter shows you the resource quotas and limits you need to do various VDM operations.

VDM may abort with the error INSUFFICIENT VIRTUAL MEMORY when running theANALYZE/DISK portion of the data collection procedure. This error can be caused by thefollowing reasons:

• The sysgen parameter VIRTUALPAGECNT is too low

• The UAF parameter PGFLQUOTA is too low

• The UAF parameter WSQUOTA is too low

• The paging and/or swapping files are too small

VDM Commands

This chapter shows you the purpose of each VDM command and lists the qualifiers that are validto use with it. Then it lists all the qualifiers in alphabetical order and describes each qualifier indetail.

It provides a complete command reference "manual" for a VDM user.

Command syntaxVDM commands look and act like DCL commands. The commands conform to normalOpenVMS DCL command syntax.

VDM commands have the format:

$ VDM[/qualifier...]

VDM is the name of the command and /qualifier is the name of a command qualifier. Lowercaseand uppercase characters in command and qualifier names are equivalent. As in DCL, '/', servesas a delimiter and command lines can be continued on to another line by terminating the line witha hyphen, pressing <RETURN> and typing the rest of the command on the next line.

Abbreviating commandsAs with DCL, many VDM commands can be truncated to a unique string, for example,"OUTPUT" can be truncated to "OUT". This provides compact command entry for experiencedusers. In command procedures, it is best to avoid abbreviating command names and qualifiers. Please refer to the OpenVMS DCL manual for more details.

The maximum length of a DCL command is 256 characters. This may be a problem when youare entering long file names and several sets of selection criteria.

Editing command linesAs with DCL, VDM commands and qualifiers can be edited using terminal keys. Command-lineediting is most useful for modifying long command lines.

VDM command line overview

Use VDM/REPORT to produce reports.

Use the following commands to collect data for current, capacity and directory reports:

VDM/UIC_COLLECTVDM/DIR_COLLECTVDM/QUOTA_COLLECT

Use VDM/MONITOR to monitor your system for low disk space and device errors.

Use VDM/RESET to reset averages and maximums in VDM data files.

Here are examples of VDM commands:

$ VDM /Report=current /Sequence=owner /summary /current=15-jun-1999

$ VDM /RESET /DATA_FILE=BOTH /VALUE=MAXIMUM

$ VDM /MONITOR /STATUS

The first command creates a summary report showing usage by owner using data from June 15 asthe previous usage.

The second command resets the maximum values in the current UIC and directory data files.

The third command generates a status report for the VDM monitor which can be configured tomonitor your system for low free space, disk errors and changes to critical files.

This chapter describes the purpose of each VDM command and lists the qualifiers that are validto use with it. Then it lists all the qualifiers in alphabetical order and describes each qualifier indetail.

HELPThe HELP command provides access to VDM's on-line HELP text.

VDM's HELP text can be installed into the system help library or into a user help library.

To access VDM's help, you enter:

$ HELP VDM

VDM DATA COLLECTION

Use these commands to collect data for later analysis. They are normally included in a batchprocedure which runs at night.

Format:

VDM/UIC_COLLECTVDM/DIR_COLLECTVDM/QUOTA_COLLECT

The command can have the qualifier:

/DISK=()

EXAMPLE:

VDM /UIC_COLLECT /DISK=(DRA1:)

This runs the VDM_UIC collection procedure to read the output from the ANALYZE/DISK/USAGE command and summarizes it by UIC. For more details on the datacollection qualifiers, see the chapter on DATA COLLECTION.

VDM calculates and records some historic information during its data collection. Overtime thevalues for average and maximum use may become unrepresentative. Use the VDM/RESETcommand to reset these values in the UIC and/or directory historic files.

Format:VDM /RESET /VALUE=[AVERAGE|MAXIMUM|BOTH] /DATA_FILE=[UIC|DIR|BOTH]

Use this command to reset the disk average usage, maximum usage or both fields. Averages arekept in the VDM_UIC and VDM_DIR data files, specify which file you wish to reset using the/DATA_FILE qualifier or BOTH to reset both files.

EXAMPLE:VDM /RESET /DATA_FILE=UIC /VALUE=AVERAGE

This will reset the average values for the VDM_UIC file to the current values.

VDM /RESET /VALUE=MAXIMUM /DATA_FILE=BOTHUse this command to reset the disk maximum fields in both the VDM_UIC andVDM_DIR files.

VDM/REPORT=CAPACITYUse this command to generate a capacity report using current disk usage and projected rates ofincrease.

Format:

VDM/REPORT=CAPACITY

The command can have the qualifiers:

/CURRENT=current_date /DISK=() /LEVEL=n /OUTPUT=file_specification /PERIOD=number_of_months /PREVIOUS=previous_date /RATE=n /SEQUENCE=key /SIZE=n /SUMMARY /USAGE=x

EXAMPLE:

$ VDM/REPORT=CAPACITY

VDM/REPORT=CURRENT

Use this command to generate a current usage report.

Format:

VDM/REPORT=CURRENT


/CURRENT=current_date /DISK=() /EXCEPTION /LARGE_CHANGE=n /LEVEL=n /NEAR_QUOTA=n /OUTPUT=file_specification /PREVIOUS=previous_date /SEQUENCE=key /SIZE=n /SUMMARY

EXAMPLE:

VDM/REPORT=CURRENT

VDM/RESET

VDM/RESET/VALUE=AVERAGE

Use this command to reset the disk average fields. Averages are kept in the VDM_UIC andVDM_DIR data files, you must specify which file you wish to reset using the /DATA_FILEqualifier. You can specify UIC, DIR, or BOTH.

Format:

VDM/RESET/DATA_FILE=UIC/VALUE=AVERAGE

EXAMPLE:

VDM/RESET/DATA_FILE=UIC/VALUE=AVERAGE

This will reset the average values for the VDM_UIC file to the current values.

VDM/RESET/VALUE=MAXIMUM

Use this command to reset the disk maximum fields. Maximums are kept in the VDM_UIC andVDM_DIR data files, you must specify which file you wish to reset using the /DATA_FILEqualifier. You can specify UIC, DIR, or BOTH.

Format:

VDM/RESET/DATA_FILE=DIR/VALUE=MAXIMUM

EXAMPLE:

VDM/RESET/DATA_FILE=DIR/VALUE=MAXIMUM

This will reset the maximum values for the VDM_DIR file to the current values.

VDM/MONITOR

Use this command to monitor your disk drives for limited free space and errors.

Format:

VDM/MONITOR


/ACTIVE/BROADCAST/CONSOLE/DISK/INTERVAL/LOG/LIST/MAIL/PANIC/START/STATUS/STOP/WORRY

EXAMPLE:

VDM/MONITOR/START

This command starts the VDM Monitor detached process which monitors the free space level onthe disks you have specified. The VDM Monitor notifies you if thresholds are exceeded or iferrors have occurred on the disk since the last time the monitor checked it.

VDM Interactive Reports

These commands allow you to generate a variety of reports. Unlike the current and capacityreports they do not depend on previously collected data so they can be run at anytime. A numberof qualifiers are available so that reports can be generated including only files that match avariety of selection criteria.

The interactive report types are: /report=ACE Shows files and their access control entries /report=Large_files Shows the largest files on a disk /report=Protection Shows files and their protection settings /report=Size Shows files and their used, allocated and unused block sizes /report=Tree Shows the directory tree structure of a disk or the current directory /report=Unauthorized Shows files that do not belong to an authorized (SYSUAF) UIC

(all commands begin with VDM and are issued at the DCL level).

The following qualifiers can be used to control which files are included in these reports. Not allselection types are available for all reports; the most common usage for the qualifiers is noted.

/ace=(identifier=value, To find files that have a specific ACE Aaccess=value)

/allocated=value or range To find files by number of blocks allocated A,L,P,S /backup To find files by their backup date A,L,P,S /before=date or range Combine with any of the date related qualifiers A,L,P,S

to specify the date /created To find files by their creation date A,L,P,S /expired To find files by their expiration date A,L,P,S /flags=flag To find files by various file flags A,L,P,S /fragments=value or range To find files by the number of fragments S /match=and|or To control how protections are matched P /modified To find files by their modification date A,L,P,S /num_files=value To specify how many files to include in the L

size report /organization=type To find files by their organization (indexed, A,L,P,S

relative or sequential) /owner=owner To find files by their owner A,L,P,S /protection=protection To find files by their protection settings P /since=date or range Combine with any of the date related qualifiers A,L,P,S

to specify the date /title=value Include the specified title in the report A,L,P,S,U /unused=value or range To find files by blocks of unused disk space L,S /used=value or range To find files by blocks of used disk space L,S

Qualifiers

This section describes the purpose of each VDM qualifier. Then it lists all the qualifiers inalphabetical order and describes each qualifier in detail.

Qualifier syntaxVDM qualifiers look and act like DCL qualifiers. They conform to normal OpenVMS DCLcommand qualifier syntax.

A qualifier consists of a keyword, or a keyword followed by a value. The keyword starts with aslash. All qualifiers apply to the entire command. VDM qualifiers have one of the followingformats:

VDM/qualifier

VDM/qualifier=x

Depending on the qualifier, "x" can be an alphanumeric value, a numeric value, a filename, a device, a directory, a date or a specially formatted clause such as an accesscontrol entry.

Most of the qualifiers have defaults.

VDM qualifier listThis page contains a complete list of all VDM qualifiers. Subsequent pages contain detaileddescriptions of each qualifier.

/ACE Specify selection criteria/ACTIVE Submit cleanup procedures/ALL Used with /REPORT=TRACE/ALLOCATED Specify selection criteria/BACKUP Select files based on their backup date/BEFORE Select all dates before the specified date/BROADCAST Send message to users/CONSOLE Log activities to security operators/CONVERT Convert data files from a previous version/CREATED Select files based on their creation date/CURRENT Specify date of current data/DATA_FILE Specify data file to reset/DATE Specify date of files to convert (obsolete)/DCL Specify a filename for selected files/DIR_COLLECT Used in batch procedures to collect data/DIR_FILE Used with /REPORT=TRACE/DISK Specify selection criteria/EXCEPTION Enable exception reporting/EXPIRED Select files based on their expiry date/EVENT Specify file monitoring event details/FILE Specify a file to be monitored/FILE Specify a file selection criteria for reports/FLAGS Select files based on their flag settings/FRAGMENTS Select files based on their fragmentation/INDENT Set the amount of indentation in tree reports/INTERVAL Set interval between free space checks/LARGE_CHANGE Specify threshold for flagging large changes/LEVEL Specify number of directory levels/LIST Specify a list of report fields/LOG Close log file and start a new one/MAIL Define users to receive mail messages/MATCH Specify logical operation for protection/MAXIMUM Specify maximum rate of change percentage/MINIMUM Specify minimum rate of change percentage/MODIFIED Select files based on their modification date/MONITOR Used to monitor disk free space and errors/NEAR_QUOTA Specify threshold for flagging quotas/NUM_FILES Specify how many files to include in the

largest_files report/ORGANIZATION Specify files based on their organization/OUTPUT Specify the destination of output

/OWNER Specify selection criteria/PANIC Define second free space threshold/PERIOD Specify interval projection time in months/PREVIOUS Specify date of previous data/PROTECTION Specify selection criteria/QUOTA_COLLECT Used in batch procedures to collect data/RATE Specify projected capacity planning growth/REPORT Specify a report to be generated/RESET Reset averages and/or maximums in data files/SEQUENCE Specify the sequence of a report/SHOW Specify blocks or files on reports/SINCE Select all dates since the specified date/SIZE Enable size checking for analysis reports/SORT Specify the sequence of a report/START Start the VDM/MONITOR process/STATISTICS Specify file statistics during operations/STATUS Show VDM/MONITOR status/STOP Stop the VDM/MONITOR process/SUMMARY Summarize all disks specified/TITLE Specify a user title to appear on the report/TYPE Specify UIC format/UIC_COLLECT Used in batch procedures to collect data/UIC_FILE Used with /REPORT=TRACE/UNUSED Specify selection criteria/USAGE Specify data type used in capacity planning/USED Specify selection criteria/VALUE Specify type of value to reset/VERSION Display VDM version/WORRY Define first free space threshold

Qualifiers Reference

/ACE

Use this qualifier to ensure that only those files including the specified ACE in their ACL areselected. If you omit the qualifier, ACE's are not used to select files.

FORMAT/REPORT=rpt_type/ACE=(IDENTIFIER=identifier,ACCESS=access)

KEYWORDSACE=(...)Specifies the ACE used to select files. The ACE matches the ACE specified in the fileACL.

When you specify this qualifier, specify at least one ACE entry. You can specify up to 64ACE entries. If you specify an ACE more than once, VDM counts and uses only the firstreference. If you specify more than one value, separate them with commas, and enclosethe list in parentheses.

IDENTIFIER=identifier (required)Specifies the identifier in the ACE used to select files. You can select alphanumericcharacters or binary formats. You cannot select using wildcard characters.

When you specify this clause, specify one and only one identifier.

ACCESS=access (required)Specifies the access in the ACE used to select files. Use one or more of the followingkeywords:

READ the ACE allows the user to read the fileWRITE the ACE allows the user to write the fileEXECUTE the ACE allows the user to execute the fileDELETE the ACE allows the user to delete the fileCONTROL the ACE allows the user to change the file accessNONE, "" the ACE doesn't allow the user to access the file

When you specify this qualifier, specify at least one access keyword. You can specify upto 5 access types. If you specify an access more than once, VDM counts and uses onlythe first reference. If you specify more than one value, separate them with "+" andenclose the list in double quotes ("). VDM will select the record if the identifier has oneor more of the access codes specified. You cannot specify NONE in conjunction withany other type of access. When you specify a list, the file will be selected if it matchesone or more of the elements in the list based on the setting of the /MATCH qualifier.

EXAMPLES

$ VDM/REPORT=ACE/ACE=(IDENTIFIER=ENGR,ACCESS="READ+WRITE")Generate a report for files with the ACE ENGR and Read or Write access in their ACL.

$ VDM/REPORT=ACE/ACE=(IDENTIFIER=ACC,ACCESS="")Generate a report for all files with the ACE "ACC" that users with that identifier aredenied access to.

/ACTIVE

Use this qualifier to enable or disable submission of batch procedures when thresholds areexceeded. Use it to test VDM/MONITOR on your system without altering any data. When/NOACTIVE is specified, VDM/MONITOR does everything except actually submit theWORRY or PANIC procedures. Log messages are written, mail messages are sent and theprogram performs exactly as if it is operating. The default is /ACTIVE. To disable proceduresubmission, use /NOACTIVE. You can only use this qualifier in conjunction with the/MONITOR qualifier.

FORMAT/MONITOR/ACTIVE/MONITOR/NOACTIVE

KEYWORDSNone

EXAMPLES

$ VDM/MONITOR/NOACTIVEStop submission of procedures. The monitor will continue to run normally.

/ALL

This qualifier is used with the /REPORT=TRACE qualifier. Saiga Systems uses the trace reportto diagnose problems. The report doesn't contain information useful to customers.

/ALLOCATED

Use this qualifier to ensure that only those files matching the specified number of allocatedblocks are selected. If you omit the qualifier, allocated blocks is not used to select files.

FORMAT/REPORT=report-type/ALLOCATED=[-] [n] [n:m] [n:] [:m]

KEYWORDS"-"Specifies that all files are selected except those matching the specified allocated blocks.

[n] [n:m] [n:] [:m]Specifies the number of allocated blocks used to select files. The allocated blocksspecifies the number of blocks allocated to the file. Specify the allocated blocks as aninteger. An allocated value of 0 indicates the file contains no data. The allocated blocksmatches the allocated blocks specified in the file header.

Specify n:m to select an inclusive range of allocated blocks using the relationship (i>=nAND i<=m). Specify n to select a specific number of allocated blocks. Specify n: toselect a number of allocated blocks and all higher values. Specify :m to select a numberof allocated blocks and all lower values.

This is not a list; you must specify one and only one of the selections.

EXAMPLES

$ VDM/REPORT=SIZE/ALLOCATED=5000:Generate a report for all files with 5,000 or more allocated blocks.

$ VDM/REPORT=SIZE/ALLOCATED=0Generate a report for zero-length files.

/BACKUP

Use this qualifier to select files based on the date of their most recent backup. If you omit thequalifier, backup date is not used to select files.

You can specify only one of the following qualifiers:

/BACKUP/CREATED/EXPIRED/MODIFIED

When you specify one of the above qualifiers, you must specify one or both of the followingqualifiers:

/BEFORE/SINCE

FORMAT/REPORT=report-type/BACKUP

EXAMPLES

$ VDM/REPORT=SIZE/BACKUP/BEFORE=25-FEB-1994Generate a report of all files which not been backed up since February 25, 1994, or havenever been backed up.

$ VDM/REPORT=SIZE/BACKUP/SINCEGenerate a report for all files which have been backed up today.

/BEFORE

Use this qualifier to select only those files before the specified date. If you omit the qualifier,date is not used to select files.

When you specify this qualifier, you must specify one of the following qualifiers:


You can specify one or both of the following qualifiers:

/BEFORE/SINCE

FORMAT/REPORT=report-type/BEFORE=[date | TODAY | YESTERDAY | TOMORROW]

KEYWORDSdateSpecifies the date for file selection. Enter the date in the format "15-JUN-94".

TODAYSpecifies today's date.

YESTERDAYSpecifies yesterday's date.

TOMORROWSpecifies tomorrow's date.

EXAMPLES

$ VDM/REPORT=SIZE/EXPIRED/BEFORE=25-FEB-1994Generate a report of all files which have expired before February 25, 1994.

$ VDM/REPORT=SIZE/BACKUP/BEFORE=TODAYGenerate a report of all files which not been backed today or have never been backed up.

/BROADCAST

Use this qualifier to broadcast messages to users when the second free space threshold (PANIClevel) is reached and the associated batch procedure is submitted. The default is /BROADCAST.To disable broadcast messages, use /NOBROADCAST. You can only use this qualifier inconjunction with the /MONITOR qualifier.

FORMAT/MONITOR/BROADCAST/MONITOR/NOBROADCAST

KEYWORDSNone

EXAMPLES

$ VDM/MONITOR/NOBROADCASTStop broadcasting messages to users when the panic threshold is exceeded on a disk.

/CONSOLE

Use this qualifier to ensure that actions are logged to the system console when free spacethresholds are reached and batch jobs are submitted. The default is /CONSOLE. To stop actionsfrom being logged, use /NOCONSOLE. The default is /CONSOLE. You can only use thisqualifier in conjunction with the /MONITOR qualifier.

FORMAT/MONITOR/CONSOLE/MONITOR/NOCONSOLE

KEYWORDSNone

EXAMPLES

$ VDM/MONITOR/NOCONSOLEStop the monitor's actions from being logged to the system console.

/CONVERT

Use this qualifier to convert VDM V4.0 or V5.0 data files to V6.0 format when you upgrade toVDM V6.0. The program allows you to convert all the data files in the [VDM.DAT] directory.There were no changes to these files made with V7.0 so V4 or V5 files can be converted directlyto the new format without an intermediate upgrade to V6.

FORMAT/CONVERT

KEYWORDSNone

EXAMPLES

$ VDM/CONVERTConverts all VDM data files from V4.0 or V5.0 to V6.0. If you have already done V6.0data collections be sure and answer "NO" when prompted if files from those datacollections should be converted.

/CREATED

Use this qualifier to select files based on their creation date. If you omit the qualifier, creationdate is not used to select files.




/BEFORE/SINCE

FORMAT/REPORT=report-type/CREATED

EXAMPLES

$ VDM/REPORT=SIZE/CREATED/SINCE=25-FEB-1994Generate a report of all files which have been created since February 25, 1994

$ VDM/REPORT=SIZE/CREATED/SINCEGenerate a report for all files which were created today.

/CURRENT

Use this qualifier to specify which file to access for the current column on the report. If thisqualifier is omitted, the date of the most recent run is used.

FORMAT/REPORT=report-type/CURRENT=date

KEYWORDSdateSpecifies the date of the current column on the report. Enter the date in the format"15-JUN-94".

EXAMPLES

$ VDM/REPORT=CURRENT/CURRENT="04-JUL-94"Generate a current report using July 4th as the current date.

$ VDM/REPORT=CAPACITY/SORT=UICGenerate a capacity report in UIC sequence using the most recent data collection date(normally yesterday) as the current date.

/DATA_FILE

Use this qualifier in conjunction with the /RESET and /VALUE qualifiers to ensure that to resetvalues in the UIC, DIR, or BOTH data files. If you omit the qualifier, BOTH is assumed

FORMAT/DATA_FILE=[UIC | DIR | BOTH]

KEYWORDSUICSpecifies that the UIC file is to have a value reset.

DIRSpecifies that the directory file is to have a value reset.

BOTH (default)Specifies that both the UIC and directory files are to have a value reset.

EXAMPLES

$ VDM/RESET/DATA_FILE=UIC/VALUE=AVERAGEReset the average value in the UIC file only.

$ VDM/RESET/VALUE=AVERAGEReset the average value in the both the UIC file and the directory file.

/DCL

Use this qualifier to specify a file to hold a list of files selected during a VDM operation. Use thefile in conjunction with a DCL procedure to correct the problem you located using the VDMoperation. If you omit the qualifier, a file containing the names of selected files is not generated. You can only use this qualifier in conjunction with /REPORT=PROTECTION, /REPORT=ACEand /REPORT=SIZE. The file is generated in your current directory.

Each record in the generated file contains the following information:

node::device:[directory]name.type;version

in the normal OpenVMS file-spec format.

FORMAT/REPORT=report-type/DCL=file-spec

KEYWORDSFile-specSpecifies the name of the file in which selected filenames are recorded. If you omit thefile-spec entirely, VDM will use the file specification "FILE_LIST.DAT" in your currentdirectory. You cannot specify a node name. If you omit the device, VDM will default toyour current device. If you omit the directory, VDM will default to your currentdirectory. If you omit a file name, VDM will default to the file name "FILE_LIST". Ifyou omit a file extension, VDM will default to ".DAT". If you want to store the file inthe VDM directory, specify the logical "VDM_DAT: in front of the filename. If VDMcan't create the file, it will report an error.

EXAMPLES

$ VDM/REPORT=ACE/ACE=(IDENTIFIER=ENGR,ACCESS=READ)/DCLGenerate a report showing all files with the ACE "ENGR" in their ACL and write theirnames in the file FILE_LIST.DAT in the VDM directory.

$ VDM/REPORT=PROTECTION/DCL=PROTECTION_CHK/PROTECTION=W:RWEDGenerate a report showing all files with any protection through WORLD and write theirnames in the file PROTECTION_CHK.DAT in your current directory.

/DIR_COLLECT

Use this qualifier to collect usage information by directory. This qualifier is used in a batchprocedure which collects directory, UIC and quota information.

FORMAT/DIR_COLLECT

KEYWORDSNone

EXAMPLES

$ VDM/DIR_COLLECT/DISK=DRA1:Collect directory information for disk DRA1:.

/DIR_FILE


/DISK

Use this qualifier to ensure that only those files on the specified disks are selected. If you omitthe qualifier, disk is not used to select files and all disks in the VDM data files are included forcurrent or capacity reports; for ACE, protection and size reports only your current default diskwill be reported. If you specify a device which is not a disk, VDM will reject it with an errormessage.

FORMAT/MONITOR/DISK=DEFAULT/DISK=(disk-name[,...]) for Current or Capacity reports/DISK=disk-name for ACE, Protection or size reports/MONITOR/DISK=disk-name

KEYWORDS

DEFAULTSpecifies default /WORRY and /PANIC thresholds and procedures be set or updated.

disk-name[,...]Specifies the disk name used to select files. The disk name is 1 through 31 alphanumericcharacters. If you omit the ":" character at the end, VDM will insert it automatically.

If you specify the qualifier without a value or omit it entirely for ACE, protection or sizereports, VDM will search your current default disk. You can specify up to 200 disknames. If you specify a disk name more than once, VDM counts and uses only the firstreference. If you specify a logical name, VDM will translate it to a physical disk namebut display the logical name you entered. If you specify more than one disk name,separate them with commas, and enclose the list in parentheses. When you specify a list,the disk will be selected if it matches any of the elements in the list.

When you specify volume sets, specify only the first drive of the volume. VDM checksall devices and will not collect data on secondary volume devices.

EXAMPLES$VDM/REPORT=CURRENT/SEQUENCE=DIRECTORY/DISK=(DRA1:,USER$DISK2:)

Generate a first level directory report for disk DUA1: and USER$DISK2:

$ VDM/REPORT=SIZE/DISK=DUA0:/ALLOCATED=5000:Generate a report of all files with 5,000 or more allocated blocks on the disk DUA0:.

$ VDM/REPORT=SIZE/DISK=SYS$SYSDEVICE:/ALLOCATED=:5Generate a report of all files with 5 or less allocated blocks on the disk with the logicalname SYS$SYSDEVICE.

$ VDM/REPORT=CAPACITYGenerate a capacity report for all disks that data has been collected on.

/EVENT

Use this qualifier to add or delete events from VDM’s monitor. The /EVENT qualifier requiresan event clause. You can only use this qualifier in conjunction with the /MONITOR qualifier.

FORMAT/MONITOR/EVENT=event_clause/MONITOR/NOEVENT=event_id

EVENT_CLAUSEThe event clause consists of any valid combination of the following keywords and values.

TYPE=event typeWhen adding events TYPE must be specified. It defines the event type being added andcontrols which additional keywords are appropriate. The valid event types are:

ABSENT to check to see if a file has been deletedPRESENT to check to see if a file existsSIZE to monitor a files sizeCHANGE to monitor a file and take action if it has been changed

BLOCKS=valueUse BLOCKS to specify the number of disk blocks for a file size event. This keyword isonly valid with TYPE=SIZE. If BLOCKS is omitted a file size event will added with thenumber of blocks specified in the default file event record.

COMMAND=fileUsed COMMAND to specify the command procedure that should be submittedwhen a VDM monitor EVENT is true. This keyword can be used with all 4 eventtypes. It must point to a valid DCL command procedure. Use QUEUE to specifywhich queue this job should be submitted to. If you specify COMMAND without a procedure name the procedure from the default file event record will be used.

COMPARE=comparison_typeUse COMPARE when adding file size events to specify the type of compare thatshould be made. The event will then make that type of comparison for the fileagainst the number of BLOCKS specified and take action when the condition istrue. Valid comparisons are:

GREATER take action when FILE is GREATER than x BLOCKS in sizeLESS take action when FILE is LESS than x BLOCKS in sizeEQUAL take action when FILE is x BLOCKS in size

Use SIZE to control whether VDM is checking against the number of blocksallocated, used or unused by FILE.

MESSAGES=valueUse messages to control how many times VDM’s monitor will signal an event as true

and submit the action procedure. MESSAGES can be specified with all four fileevent types. Each subsequent time that VDM checks a file event and determines it tobe true VDM will take the appropriate action until it has reached MESSAGES=nntimes. If MESSAGES is omitted the value from the default file event record will beused.

NODE=node nameUse NODE when running VDM in a cluster to control which node VDM actuallychecks for a file event on. If your cluster is sharing a common VDM monitor datafile specifying a NODE will prevent an event from being signalled on every node inthe cluster when it becomes true. If you omit node the value from the default fileevent record will be used.

QUEUE=queue nameUse QUEUE to specify which queue a file event should submit it’s COMMANDprocedure to. Be sure to specify a valid queue that will execute on an appropriatenode. If you omit QUEUE the value from the default file event record will be used.

SIZE=size typeUse SIZE to control which value VDM COMPAREs BLOCKS against. Validchoices for size type are:

ALLOCATED total blocks allocated by a fileUSED number of blocks used by a fileUNUSED the number of blocks allocated but not yet used by a file

If you omit SIZE the size type from the default file event record will be used.

To delete a file event from the VDM monitor database use /NOFILE=filename and/EVENT=(TYPE=filetype).

EXAMPLES

$ VDM/NOFILE=DISK1:[DIR1]TMP.FIL/EVENT=(TYPE=CHANGED)Remove the file changed event for the specified file. Any other events for this file such assize or absent file are not affected.

$ VDM /FILE=HITMAN_DAT:HITMAN_LOG_FILE.NODE1 /EVENT=(TYPE=SIZE, -BLOCKS=4000, SIZE=USED, COMPARE=GREATER,

QUEUE=NODE1$BATCH, -COMMAND=HITMAN_COM:RESET_HITMAN_LOG.COM)On node1 anytime HITMAN’s log file exceeds 4000 blocks used submit a commandprocedure to node1$batch that resets the log file.

$ VDM /MONITOR /FILE=SYS$MANAGER:SYSTARTUP_VMS.COM -

/EVENT=(TYPE=CHANGED)The VDM monitor will take it’s normal default actions for sending mail and console messagesanytime it detects a change to the system startup file.

$ VDM /MONITOR /FILE=DISK1:[DIR1]FILE.DAT -/EVENT=(TYPE=ABSENT, MESSAGES=10, -QUEUE=NODE1$BATCH, NODE=NODE1, -COMMAND=VDM_COM:RECREATE_FILE.COM)

If DISK1:[DIR1]FILE.DAT ever gets deleted VDM’s monitor will submit a job that can recreatethe file. The check is made on only node1 and if the file is not successfully created VDM will tryagain for up to 9 more times since subsequent checks would still show the file absent.

/EXCEPTION

Use this qualifier to specify that the report created will be an exception report. This means thatonly the users flagged as exceptions will be printed in the report. There are three criteria bywhich a user can be flagged as an exception: SIZE, NEAR_QUOTA, LARGE_CHANGE. Forinformation on how to specify these criteria, see the information on the above qualifiers. If youomit the qualifier, all records matching the other criteria will be printed.

FORMAT/REPORT=report-type/EXCEPTION

KEYWORDSNone

EXAMPLES

$ VDM/REPORT=CURRENT/LARGE_CHANGE=24/EXCEPTIONGenerate a current report that shows only the users with a change in usage greater that 24percent or that are near their quota if disk quota information is being used.

/EXPIRED

Use this qualifier to select files based on the expiration date. If you omit the qualifier, expirationdate is not used to select files. The expiration date is set with the OpenVMS commands SETFILE/EXPIRATION_DATE and SET VOLUME/RETENTION.




/BEFORE/SINCE

FORMAT/REPORT=report-type/EXPIRED

EXAMPLES

$ VDM/REPORT=SIZE/EXPIRED/SINCE=25-FEB-1994Generate a report of all files which have expired since February 25, 1994, or are not yetexpired.

$ VDM/REPORT=SIZE/EXPIRED/SINCEGenerate a report for all files which expire today or are not yet expired.

$ VDM/REPORT=SIZE/EXPIRED/SINCE/BEFORE=31-DEC-1994Generate a report for all files which will expire between today and December 31, 1994.

/FILE

Use this qualifier to specify the file for VDM’s file events OR to specify a file selection criteriawhen running interactive reports. For file events you must specify a valid file specification thatcontains no wildcards; as a selection criteria wildcards are fine and the portions of thespecification not included will be defaulted from [*...]*.*;*.

FORMAT/FILE=disk:[directory]filename.type file event usage/FILE=[directory]filename.type selection criteria usage

KEYWORDSThis qualifier has no keywords. Enter a valid OpenVMS file specification or wildcarded filespecification when used as a selection criteria.

EXAMPLES$ VDM /MONITOR /FILE=SYS$SYSTEM:SYSTARTUP_VMS.COM -/EVENT=(TYPE=CHANGE, NODE=THISND, MESSAGES=1, MAIL=SYSOP)This command creates a VDM event that will send mail to SYSOP anytime VDM detectsthat the system startup file has been modified.

$ VDM /MONITOR /FILE=HITMAN_DAT:HITMAN_LOG_FILE.THISND -/EVENT=(TYPE=SIZE, COMPARE=GREATER, BLOCKS=2500, -SIZE=ALLOCATED, COMMAND=HITMAN_COM:RESET_LOG.COM,-QUEUE=THISND$BATCH, NODE=THISND)This event monitors HITMAN’s log file and any time it has allocated more than 2500blocks, submits a batch job that resets and purges the log file.

$ VDM /REPORT=SIZE /FILE=*.LOG /DISK=DKA400:This command will generate a file size report for all the log files on disk dka400.

$ VDM /REPORT=PROTECTION /FILE=[ACCOUNT...]*.*;* -/OUTPUT=ACC.LIS

This command will generate a file protection report for all the subdirectories and filesunder the account directory. /output has been added to direct the report to a file.

/FLAGS

Use this qualifier to ensure that only those files matching the specified flags are selected. If youomit the qualifier, flags are not used to select files.

FORMAT/REPORT=report-type/FLAGS=(["-",] [NO]flag[,...])

KEYWORDS"-"Specifies that all files are selected except those matching any specified flags. Thisoperator applies to the entire list, not just to the first element. Files with no flags will beincluded (see /ALL).

flags[,...]Specifies the flags used to select files. A list of valid flags is contained in Appendix G. Specify the absence of a flag by placing "NO" in front of the flag name. The flags matchthe flags specified in the user authorization file.

When you specify this qualifier, specify at least one flag. You can specify up to 18 flags. If you specify a flag more than once, VDM counts and uses only the first reference. Ifyou specify more than one flag, separate them with commas, and enclose the list inparentheses. When you specify a list, the account will be selected if it matches one ormore of the elements in the list.

Use /NOALL if you want to exclude files with no flags from a negated list.

EXAMPLES

$ VDM/REPORT=SIZE/FLAGS=NOBACKUPGenerate a report of all files which will not be backed up regardless of activity.

/FRAGMENTS

Use this qualifier to ensure that only those files matching the specified number of fragments areselected. If you omit the qualifier, file fragmentation is not used to select files.

FORMAT/REPORT=report-type/FRAGMENTS=[-] [n] [n:m] [n:] [:m]

KEYWORDS"-"Specifies that all files are selected except those matching the specified file fragmentation. This operator applies to the entire list, not just to the first element.

[n] [n:m] [n:] [:m]Specifies the number of fragments used to select files. The file fragmentation is thenumber of separate extents assigned to the file. Specify the file fragmentation as aninteger. The fragmentation matches the file fragmentation specified in the INDEXF.SYS.

Specify n:m to select an inclusive range of file fragmentation using the relationship (i>=nAND i<=m). Specify n to select a specific file fragmentation. Specify n: to select anumber of file fragments and all higher values. Specify :m to select a number of filefragments and all lower values.


EXAMPLES

$ VDM/REPORT=SIZE/FRAGMENTS=5:Generate a report of all files with 5 or more fragments.

/INDENT

Use this qualifier with the /REPORT=TREE qualifier to specify how many characters to indenteach directory level when creating a tree. "4" is the default. The maximum value is 40. The treereport shows up to 8 levels of directory. If you omit the qualifier, /INDENT=4 is assumed.

FORMAT/INDENT=n

EXAMPLES

$ VDM/REPORT=TREE/INDENT=8Generate a tree report indenting each sub-directory 8 characters.

/INTERVAL

Use this qualifier to specify the time interval between free space and error checks for the diskdrives listed. A valid time interval is between 1 minute and 60 minutes. You can only use thisqualifier in conjunction with the /MONITOR qualifier. You may, using this qualifier, setdifferent intervals for different drives.

FORMAT/MONITOR/INTERVAL=number-of-minutes

KEYWORDSnumber-of-minutesSpecifies the number of minutes between checks for free space and disk errors.

EXAMPLES

$ VDM/MONITOR/INTERVAL=2/DISK=(DISK1$,DISK2$)Specifies that drives DISK1$ and DISK2$ are to be checked every two minutes.

/LARGE_CHANGE

Use this qualifier to specify the percentage increase at which accounts will be flagged as having a"large change" from the previous total. The default percentage is 20 percent. Valid values are inthe range 1 to 100. If /EXCEPTION is specified with /LARGE_CHANGE then the report willcontain only the users that are flagged for LARGE_CHANGE or NEAR_QUOTA. If you omitthe qualifier, 20 percent is assumed.

FORMAT/REPORT=CURRENT/LARGE_CHANGE=n

EXAMPLES

$ VDM/REPORT=CURRENT/DISK=DUA0:/LARGE_CHANGE=5Generate a current report for all users with a 5% or greater increase in their usage areflagged.

$ VDM/REPORT=CURRENT/DISK=DUA0:/EXCEPTIONGenerate a current report showing only users with at least a 20% increase in their usage orthat are near their quota.

/LEVEL

Use this qualifier with the /SEQUENCE=DIRECTORY or /REPORT=TREE qualifier to specifyhow many levels of directory to print when creating a tree report. "2" is the default for reportsgenerated in directory sequence and means only the top directories and 1 level of sub-directorieswill be printed. The default for the tree report is to show all levels; below the current directory if/DISK is not specified or for the entire disk if you specify /DISK. The disk usage for each level"2" directory is the same as the block usage returned by the DCL command DIR/SIZE=ALL[level_1_directory...]. The directory sequence current or capacity reports can produce a reportshowing up to three directory levels. The tree report shows up to 8 levels of directory. If youomit the qualifier, /LEVEL=8 is assumed. When you use this qualifier with the/SEQUENCE=DIRECTORY qualifier, values above 4 are assumed to be 3.

FORMAT/LEVEL=n

EXAMPLES

$ VDM/REPORT=CURRENT/SEQUENCE=DIRECTORY/LEVEL=2Generate a current directory report for users showing the top two levels of directories.

$ VDM/REPORT=CURRENT/DISK=DUA0:/SEQUENCE=DIRECTORYGenerate a current directory report for users showing the only the top 2 levels ofdirectories on disk DUA0:.

$ VDM/REPORT=TREE/DISK=DUA0:/LEVEL=5Generate a directory tree showing five levels of directories for disk DUA0.

/LIST

Use this qualifier to list the parameters in the VDM/MONITOR database. This allows you toverify that the commands you have typed are being used, and find out what parametersVDM/MONITOR is actually using. If you omit the filename, the list is sent to the screen,pausing after each disk until you press the enter key.

FORMAT/MONITOR/LIST[=file-name]

KEYWORDS"file-name"The name of the file to write the output to. If it is omitted, "SYS$OUTPUT" is assumed.

EXAMPLES

$ VDM/MONITOR/LIST=P.LISList the VDM/MONITOR parameters in the file P.LIS.

/LOG

Use this qualifier to close the VDM monitor's current log file and ensure that a new log file isopened. Actions are logged to the log file when free space thresholds are reached and batch jobsare submitted. The log file is, by default, called VDM_DAT:VDM_LOG_FILE.LOG. To changethe log file name, define the system logical name VDM_LOG_FILE to be the file name you wantthe log file to be. For example:

$ DEFINE/SYSTEM VDM_LOG_FILE DUA1:[FRED]PURGE_LOG.DAT

will cause the log file to be "dua1:[fred]purge_log.dat".

The /LOG qualifier closes the current log file and opens a new one. The operator can thenexamine the contents of the previous log file.

The /NOLOG qualifier closes the current log file but does not open a new one. Hence, nomessages are recorded until the operator opens another log file.

There is no default for this qualifier, a new log file will be opened by VDM only if explicitlyrequested or each time VDM starts.

You can only use this qualifier in conjunction with the /MONITOR qualifier.

FORMAT/MONITOR/LOG/MONITOR/NOLOG

EXAMPLES

$ VDM/MONITOR/NOLOGStop actions from being logged to the log file.

/MAIL

Use this qualifier to ensure that users will be notified of impending problems using theOpenVMS MAIL utility when the monitor detects that the second threshold (PANIC) has beenreached.

FORMAT/MONITOR/MAIL=username/MONITOR/MAIL=distribution-list/MONITOR/NOMAIL

KEYWORDSusernameSpecifies the name of the user to receive the mail message.

distribution-listSpecifies the name of a text file containing the names of the users to receive the mailmessage. The filename must be preceded by the "@" character and the entire stringenclosed in double quotes ("). The distribution file must conform to the rules fordistribution files outlined in the OpenVMS Mail utility manual.

EXAMPLES

$ VDM/MONITOR/MAIL=SYSTEMSend a mail message to user SYSTEM when the PANIC threshold is reached.

$ VDM/MONITOR/MAIL="@OPER.DIS"Send mail messages to all users in the file OPER.DIS when the PANIC threshold isreached.

/MATCH

Use this qualifier to specify the logical operation to be used when more than one entry isspecified in a list of selection criteria. Use this qualifier in conjunction with /PROTECTION or/ACE. The normal AND relationship still applies between multiple qualifiers.

FORMAT/PROTECTION=(...)/MATCH=[OR | AND]

KEYWORDSOR (Default)Specifies that the logical operation "OR" is to used when more than one entry is specified. If any of the entries are present, the file will be selected.

ANDSpecifies that the logical operation "AND" is to used when more than one entry isspecified. All of the entries must be present for the file to be selected.

For protection, this qualifier applies within a protection class. If more than one protectionclass is specified, an AND relationship is assumed.

If you specify OR, you cannot specify AND and vice-versa. EXAMPLES

$ VDM/REPORT=PROTECTION/PROTECTION=OWNER:RWGenerate a report of files whose owners have either Read or Write access using default/MATCH value of "OR".

$ VDM/REPORT=PROTECTION/PROTECTION=SYSTEM:RW/MATCH=ANDGenerate a report of files where system has both Read and Write access.

$ VDM /REPORT=ACE /ACE=(IDENT=ENGR,ACCESS="READ+WRITE+DELETE") - /MATCH=AND

Generate a report showing files which the ENGR identifier provides read, write anddelete access to.

/MAXIMUM

Use this qualifier with the /REPORT=CAPACITY qualifier to specify a maximum value for therate of change if you request a report where it is automatically calculated. The default is +25 ifyou omit the qualifier. Valid values are in the range of -99999.9 and +99999.9. This qualifiercannot be used with the /RATE qualifier.

FORMAT/REPORT=CAPACITY/MAXIMUM=n

EXAMPLES

$ VDM/REPORT=CAPACITY/PREVIOUS=28-FEB-94/MAXIMUM=5Generate a capacity report with a maximum growth rate of 5%.

$ VDM/REPORT=CAPACITY/PREVIOUS=28-FEB-94Generate a capacity report with a default maximum growth rate of 25%.

/MINIMUM

Use this qualifier with the /REPORT=CAPACITY qualifier to specify a minimum value for therate of change if you request a report where it is automatically calculated. The default is -25 ifyou omit the qualifier. Valid values are in the range of -99999.9 and +99999.9. This qualifiercannot be used with the /RATE qualifier.

FORMAT/REPORT=CAPACITY/MINIMUM=n

EXAMPLES

$ VDM/REPORT=CAPACITY/PREVIOUS=28-FEB-94/MAXIMUM=8/MINIMUM=5Generate a capacity report with a minimum growth rate of 5% and a maximum of 8%.

$ VDM/REPORT=CAPACITY/PREVIOUS=28-FEB-94Generate a capacity report with a minimum growth rate of -25%.

/MODIFIED

Use this qualifier to select files based on their modification date. If you omit the qualifier,modification date is not used to select files.




/BEFORE/SINCE

FORMAT/REPORT=report-type/MODIFIED

EXAMPLES

$ VDM/REPORT=SIZE/MODIFIED/SINCE=25-FEB-1994Generate a report of all files which have been modified since February 25, 1994

$ VDM/REPORT=SIZE/MODIFIED/SINCEGenerate a report for all files which have been modified today.

$ VDM/REPORT=SIZE/MODIFIED/BEFORE=1-JAN-94Generate a report for all files which have not been modified this year (1994).

/MONITOR

Use this qualifier to monitor your disk for low free space and device errors.

This qualifier should always be used with one or more of the qualifiers for using and maintainingVDM's monitor.

/ACTIVE/BROADCAST/CONSOLE/DISK/EVENT/FILE/INTERVAL/LOG/LIST/MAIL/PANIC/START/STATUS/STOP/WORRY

FORMAT/MONITOR

KEYWORDSNone

EXAMPLES

$ VDM/MONITOR/STARTEnable monitoring of low disk space and device errors.

/NEAR_QUOTA

Use this qualifier to specify the percentage increase at which accounts will be flagged as beingnear their quota. The default percentage is 80 percent. Valid values are in the range 1 to 100. If/EXCEPTION is specified with /NEAR_QUOTA, the report will contain only the users that areflagged for LARGE_CHANGE or NEAR_QUOTA. If you omit the qualifier,/NEAR_QUOTA=80 is assumed.

FORMAT/REPORT=CURRENT/NEAR_QUOTA=n

EXAMPLES

$ VDM/REPORT=CURRENT/DISK=DUA0:/NEAR_QUOTA=66Generate a current report for users and flag all users who have allocated 66% or more oftheir quota.

$ VDM/REPORT=CURRENT/DISK=DUA0:Generate a current report that flags users who have allocated 80% or more of their quota.

$ VDM/REPORT=CURRENT/NEAR_QUOTA=90/EXCEPTIONGenerate a current report for all disks that shows only users who have allocated 90% ormore of their quota or whose usage has increased or decreased by more than 20% sincethe previous data collection.

/NUM_FILES

Use this qualifier when generating VDM’s large files report to specify how many files should bereported. By default VDM will show the 50 largest files; use /NUM_FILES if you want toinclude more or less than this amount.

FORMAT/REPORT=LARGE_FILES/NUM_FILES=nnn

KEYWORDSnnnSpecifies the number of files that the report is to contain. If you omit the value or thisqualifier, VDM will use 50.

NOTEThe large files report must sort a table of all files that meet its initial criteria to find thelargest ones. To significanlty improve performance we suggest adding at least oneselection criteria such as /USED or /CREATED.

EXAMPLES$ VDM/REPORT=LARGE_FILES/NUM_FILES=75/DISK=DISK1:

Generate a large files report to show the 75 largest files on disk DISK1:. Since no/OUPUT file has been specified the report will be displayed on the users terminal.

$ VDM/REPORT=LARGE_FILES/NUM_FILES=75/DISK=DISK1:/USED=250:This generates the same report as the previous example, however, the report has beenlimited to files that use at least 250 blocks. This report will be generated significantlyfaster than the previous example because all files less than 250 blocks will be omittedfrom the sort that orders the files in decending order by size.

/ORGANIZATION

Use the /ORGANIZATION qualifier when creating interactive reports to control which files areincluded in the reports.

FORMAT

/ORGANIZATION=([INDEXED,][RELATIVE,][SEQUENTIAL])

EXAMPLES

$ VDM /REPORT=SIZE /ORGANIZATION=INDEXED /DCLThis command generates a size report showing all the indexed files on the current defaultdisk and create a text file with the filenames of all matching files, one per line.

/OUTPUT

Use this qualifier to direct VDM output. If you omit the qualifier, reports are output toSYS$OUTPUT.

FORMAT/REPORT=report-type/OUTPUT=[file-spec]

KEYWORDSfile-specSpecifies the name of the file that is to contain the requested report. If you omit the filename, the file name "VDM.LIS" is used. If you omit a node, VDM will default to yourcurrent node. If you omit a device, VDM will default to your current device. If you omita directory, VDM will default to your current directory. If you omit a file extension,VDM will default to ".LIS". When creating current or capacity reports if you omit thefile-spec output will be directed to SYS$OUTPUT.

EXAMPLES

$ VDM/REPORT=SIZE/UNUSED=50:/OUTPUT=RGenerate a size report. The report goes to R.LIS.

$ VDM/REPORT=SIZE/UNUSED=50:/OUTPUT=SYS$MANAGER:Generate a report and direct the output to SYS$MANAGER:VDM.LIS

/OWNER

Use this qualifier to ensure that only those files matching the specified UIC or identifier areselected. This qualifier can also be used to find files belonging to UICs that the current orcapacity reports say are unauthorized. A username may be specified because OpenVMSmaintains usernames as identifiers in the RIGHTSLIST.DAT file. If you omit the qualifier,owner is not used to select files.

FORMAT/REPORT=report-type/OWNER=(["-",]owner[,...])

KEYWORDS"-"Specifies that all files are selected except those matching any specified owner UIC oridentifier. This operator applies to the entire list, not just to the first element.

owner[,...]Owner consists of either identifier or UIC.

identifierSpecifies the identifier used to select files. You can specify the identifier as a number oruse the identifier name. The identifier matches the identifier specified in theRIGHTSLIST.DAT file.

uicSpecifies the UIC used to select files. The UIC value, specified in octal, is a group andmember number separated by a comma and enclosed in brackets. The UIC value matchesthe UIC specified in the user authorization file.

When you specify this qualifier, specify at least one owner UIC or identifier. You canspecify up to 64 owner UICs or identifiers. If you specify an owner UIC or identifiermore than once, VDM counts and uses only the first reference. If you specify more thanone owner UIC or identifier, separate them with commas, and enclose the list inparentheses. You can use the wildcard characters "*" and "%" in owner UICs. Youcannot use wildcard characters in owner identifiers. When you specify a list, the file willbe selected if it matches one or more of the elements in the list.

EXAMPLES$ VDM/REPORT=SIZE/OWNER=%X80081080

Generate a report for files owned by the specified identifier.

$ VDM/REPORT=SIZE/OWNER=([77,*],ENG)Generate a report for files owned by anyone in the UIC [77,] group or the identifier ENG.

/PANIC

Use this qualifier to specify the second free space threshold and associated batch procedure. You can specify the threshold as a number of disk blocks or as a percentage of the total availableblocks on the drive. You can only use this qualifier in conjunction with the /MONITORqualifier. You must specify /DISK with this qualifier; specify /DISK=DEFAULT if you wish tomodify the default panic threshold parameters.

FORMAT/MONITOR/PANIC=([[BLOCKS=number-of-blocks] or [PERCENT=percentage]]-

[,COMMAND=procedure-name][,NODE=nodename][,MESSAGES=number-of-messages][,QUEUE=batch-queue])

KEYWORDSBLOCKS=number-of-blocksSpecifies the minimum number of free blocks. If you omit blocks or percentage thevalues assigned to the DEFAULT disk will be used.

PERCENT=percentageSpecifies the minimum percentage of free space. If you omit blocks or percentage thevalues assigned to the DEFAULT disk will be used.

COMMAND=procedure-nameSpecifies the procedure to be executed when the /PANIC threshold is crossed. Theprocedure is assumed to be in the [VDM.DAT] directory. If you omit a file type, "COM"is assumed. If you omit COMMAND the procedure name assigned to the DEFAULT diskwill be used.

NODE=nodenameSpecifies the node that should detect the panic condition and take the appropriate action.Use this qualifier in a cluster environment to limit detection to the Node that the disk isnormally served to the cluster by otherwise you may have the command proceduresubmitted to run on multiple nodes. If you omit NODE the node name assigned to theDEFAULT disk will be used.

MESSAGES=number-of-messagesSpecifies the number of times the console panic message and/or mail should be sent whenthe disk drops below the panic threshold. The COMMAND procedure is only submittedonce, regardless of the value specified for MESSAGES. If you omit MESSAGES thenumber of messages assigned to the DEFAULT disk will be used.

QUEUE=batch-queueSpecifies the batch queue that the COMMAND procedure will be submitted to. Thedefault, if batch-queue is not specified, is SYS$BATCH. If you omit QUEUE the queueassigned to the DEFAULT disk will be used.

EXAMPLES

$ VDM/MONITOR/PANIC=(PERCENT=5,COMMAND=PANIC05.COM)/DISK=DUA0:Submit the procedure when the free space percentage falls below 5% on disk DUA0:.Copy the values for node, messages and queue from the DEFAULT disk record.

$VDM/MONITOR/PANIC=(BLOCKS=500,COMMAND=PANIC_PRIME)/DISK=DEFAULT

Set the default values to be 500 blocks and the procedure to PANIC_PRIME for any disksadded to the monitor with a panic qualifier that has not specified them.

$ VDM /MONITOR /PANIC=(PERCENT=7, NODE=MVAXI, QUEUE=MVAXI$BATCH, -MESSAGES=99) /DISK=DUB0:Add disk DUB0 to the monitor with a panic threshold of 7%. When the monitor runningon node MVAXI detects that the threshold has been crossed it will submit the defaultpanic procedure to queue MVAXI$BATCH and signal the panic condition every intervaluntil it has been resolved and free space is above the threshold.

/PERIOD

Use this qualifier when running capacity reports to specify the monthly interval to calculateprojection periods for. If you specify /PERIOD=5, VDM will show projections for every fivemonths. If you omit the qualifier, VDM assumes a value of 3. The capacity report will try tofind a data file which is period months old to use for the previous values. If it cannot, it will findthe oldest file less than period months old and use it.

FORMAT/REPORT=CAPACITY/PERIOD=n

KEYWORDSnSpecifies the number of months in each interval.

EXAMPLES

$ VDM/REPORT=CAPACITY/PERIOD=2Generate a capacity report with a two month interval for projections.

$ VDM/REPORT=CAPACITYGenerate a capacity report with a three month interval for projections.

/PREVIOUS

Use this qualifier to specify which file to access for the previous column on the report. If thisqualifier is omitted, the date of the most recent run prior to the latest data collection is used. Capacity reports use a different set of rules. Please refer to the /PERIOD documentation formore details.

FORMAT/REPORT=report-type/PREVIOUS=date

KEYWORDSdateSpecifies the date of the previous column on the report. Enter the date in the format"15-JUN-94".

EXAMPLES

$ VDM/REPORT=CURRENT/PREVIOUS=04-JUL-94Generate a current report using July 4th as the previous date.

$ VDM/REPORT=CURRENT/SORT=UICGenerate a current report in UIC sequence using today's date as the current date and thedate of the previous data collection as the previous date.

$ VDM/REPORT=CAPACITY/SORT=UIC/PERIOD=2Generate a capacity report in UIC sequence using today's date as the current date and aprevious file from two months ago as the previous date.

/PROTECTIONUse this qualifier to ensure that only those files including the specified file protection are selected. Ifyou omit the qualifier, protection is not used to select files.

FORMAT/REPORT=report-type/PROTECTION=(["-",]WORLD:[access...],

GROUP:[access...],OWNER:[access...],SYSTEM:[access...])

KEYWORDS"-"Specifies that all files are selected except those matching any specified file protection. Thisoperator applies to the entire list, not just to the first element.

WORLDSpecifies the world protection.

OWNERSpecifies the owner file protection.

GROUPSpecifies the owner's group protection.

SYSTEMSpecifies the system file protection.

accessSpecifies the protection used to select files. The protection matches the protection specifiedin the file header. Use the following codes to indicate types of access:

R ReadW WriteE ExecuteD Delete

When you specify this qualifier, specify at least one protection class. If you specify morethan one protection class, separate them with commas, and enclose the list in parentheses. By default, if you specify more than one access code for a protection class, the file will beselected if it has one or more of the codes for that class. See the /MATCH qualifier for moredetails. If you specify the protection class but omit the access type, VDM assumes "RWED"(Note that this is different from the OpenVMS convention). You can check for the presenceof access types or you can check for the absence of access types (using the "-" operator) butyou cannot check for the presence of some and the absence of others in the same report.

EXAMPLES

$ VDM/REPORT=PROTECTION/PROTECTION=WORLDGenerate a report for all files which have any WORLD access.

$ VDM/REPORT=PROTECTION/PROTECTION=GROUP:WDGenerate a report for all files which have GROUP write or delete access.

$ VDM/REPORT=PROTECTION/PROTECTION=("-",OWNER:D)Generate a report for all files which the owner cannot delete.

$ VDM/REPORT=PROTECTION/PROTECTION=("-",SYSTEM)Generate a report for all files for which system lacks any access.

$ VDM/REPORT=PROTECTION/PROTECTION=W:RE/MATCH=ANDGenerate a report for all files which have both WORLD Read and Execute access.

$ VDM/REPORT=PROTECTION/PROTECTION=("-",O:D,G:D,S:D,W:D)Generate a report for all files which cannot be deleted under any access category.

/QUOTA_COLLECT

Use this qualifier to collect quota usage information and update the current data to reflect thesevalues. This qualifier is used in a batch procedure which collects directory, UIC and quotainformation.

FORMAT/QUOTA_COLLECT

KEYWORDSNone

EXAMPLES

$ VDM/QUOTA_COLLECT/DISK=DRA1:Collect quota information for disk DRA1:.

/RATE

Use this qualifier when running capacity planning reports to specify the percentageincrease/decrease. This allows you to test various rates of growth. Normally the capacity reportuses the percentage change between the previous and current periods as a projected periodpercentage increase. You can override that with this qualifier. There is no default. Valid valuesare in the range-99999.9 to +99999.9.

FORMAT/REPORT=CAPACITY/RATE=n

EXAMPLES

$ VDM/REPORT=CAPACITY/RATE=5Generate a capacity report for users using a growth rate of 5%.

$ VDM/REPORT=CAPACITYGenerate a capacity report for users using a growth rate calculated from the allocations 3months ago and current allocations.

/REPORT

Use this qualifier to specify the type of report VDM is to generate.

You can specify the /SORT or /SEQUENCE qualifiers with the /REPORT qualifier for current andcapacity reports.

FORMAT/REPORT= [ACL | CAPACITY| CURRENT | FILES | LARGE_FILES

| PROTECTION | SIZE | TRACE | TREE | UNAUTHORIZED]

KEYWORDS"ACL"Specifies that the pre-formatted ACL report should be generated.

"CAPACITY"Specifies that the pre-formatted capacity report projecting future demand should be generated.

"CURRENT"Specifies that the pre-formatted current usage report should be generated.

"FILES"Specifies that the pre-formatted files report should be generated. This must be done during datacollection or by running the new FILE_REPORT.COM procedure.

"LARGE_FILES"Specifies that the pre-formatted large files report should be generated. Unlike the “FILES” reportthis report can be run at anytime.

"PROTECTION"Specifies that the pre-formatted protection report should be generated.

"SIZE"Specifies that the pre-formatted size report showing blocks allocated, used and unused should begenerated.

"TRACE"Saiga Systems uses the trace report to diagnose problems. The report doesn't contain informationuseful to customers.

"TREE"Specifies that the pre-formatted tree report showing directory structure should be generated.

"UNAUTHORIZED"Specifies that the pre-formatted unauthorized files showing all the files on a disk that belong to aUIC that is no longer in the SYSUAF file be generated.

EXAMPLES

$ VDM/REPORT=SIZE/ALLOCATED=500:Generate a report for all files with allocated blocks of 500 or more.

$ VDM/REPORT=SIZE/OUTPUT/ALLOCATED=0List zero-length files. The report goes to the file VDM.LIS.

/RESET

Use this qualifier in conjunction with the /VALUE qualifier to reset average and/or maximumfields in the data files.

FORMAT/RESET/VALUE=field-type

KEYWORDSNone

EXAMPLES

$ VDM/RESET/VALUE=AVERAGEReset the average field in the data file to the current allocation.

/SEQUENCE

Use this qualifier in conjunction with the /REPORT qualifier to specify the sequence of reportsspecified with the /REPORT qualifier. This qualifier is functionally equivalent to the /SORTqualifier.

FORMAT/REPORT=report-type/SEQUENCE=[ACCOUNT | DETAIL | DIRECTORY |

DISK | GROUP | OWNER | UIC | USER]

KEYWORDSYou can only specify one of these items.

ACCOUNTSpecifies that reports are to be produced in UAF account sequence and summarized byaccount.

DIRECTORYSpecifies that reports are to be produced in directory sequence and summarized bydirectory to the number of levels specified.

DISKSpecifies that reports are to be produced in disk sequence and summarized by disk.

GROUPSpecifies that reports are to be produced in group sequence and summarized by UICgroup.

OWNERSpecifies that reports are to be produced in UAF owner sequence and summarized byowner.

UICSpecifies that reports are to be produced in UIC sequence and summarized by UIC.

USER (Default)Specifies that reports are to be produced in username sequence and summarized byusername.

EXAMPLES

$ VDM/REPORT=CURRENT/SEQUENCE=UICGenerate a current report of all disks in UIC sequence.

/SHOW

Use this qualifier to specify whether number of blocks or files appear on reports specified by/REPORT. Use this qualifier in conjunction with the /REPORT=CURRENT and/REPORT=CAPACITY qualifier. If you omit /SHOW with the current or capacity reports thedefault action will be /SHOW=BLOCKS.

FORMAT/REPORT=report-type/SHOW=[BLOCKS] [FILES]

KEYWORDSBLOCKSSpecifies that the report is to be produced showing blocks.

FILESSpecifies that the report is to be produced showing number of files.

EXAMPLES

$ VDM/REPORT=CURRENT/SHOW=FILESGenerate a current report showing number of files rather than allocated blocks.

$ VDM/REPORT=CAPACITYGenerate a capacity report showing blocks on the report.

/SINCE

Use this qualifier to select only those files dated after the specified date. If you omit thequalifier, date is not used to select files.

When you specify this qualifier, you must specify one of the following qualifiers:


You can specify one or both of the following qualifiers:

/BEFORE/SINCE

FORMAT/REPORT=report-type/SINCE=date [TODAY] [YESTERDAY] [TOMORROW]

KEYWORDSdateSpecifies the date for file selection. Enter the date in the format "15-JUN-1994".

TODAYSpecifies today's date.

YESTERDAYSpecifies yesterday's date.

TOMORROWSpecifies tomorrow's date.

EXAMPLES$ VDM/REPORT=SIZE/EXPIRED/SINCE=25-FEB-1994

Generate a report of all files which have expired since February 25, 1994, or will expirein the future.

$ VDM/REPORT=SIZE/BACKUP/SINCE=YESTERDAYGenerate a report of all files which have been backed up since yesterday.

$ VDM/REPORT=SIZE/EXPIRED/SINCE=25-FEB-1994/BEFORE=TODAYGenerate a report of all files which have expired since February 25, 1994.

/SIZE

Use this qualifier to ensure that only those users matching the specified minimum number ofblocks are selected. If you omit the qualifier, blocks allocated is not used to limit the number ofitems reported in a current or capacity report.

FORMAT/REPORT=report-type/SIZE=n

KEYWORDSnSpecifies the number of allocated blocks used to select users, UICs, directories, etc. Theblocks specifies the number of blocks allocated to the user. Specify the blocks as aninteger. The blocks matches the allocated blocks for the user.

Specify n to select a number of allocated blocks and all higher values.

EXAMPLES

$ VDM/REPORT=CURRENT/SIZE=5000/SEQUENCE=ACCOUNTGenerate a report for all accounts with 5,000 or more allocated blocks.

/SORT

This qualifier is functionally equivalent to the /SEQUENCE qualifier. It is maintained forcompatibility with previous versions of VDM. All procedures which use this qualifier should bemodified to use /SEQUENCE at your convenience.

/START

Use this qualifier to start the VDM/MONITOR function. If there is already a monitor processrunning, the command will return an error. You can only use this qualifier in conjunction withthe /MONITOR qualifier.

FORMAT/MONITOR/START

EXAMPLES

$ VDM/MONITOR/STARTStart monitoring for free space and disk errors.

/STATISTICS

Use this qualifier to display file statistics such as files read during VDM operations.

For the protection report, size and ACE reports, /STATISTICS shows the files checked and thefiles selected.

FORMAT/REPORT=report-type/STATISTICS

KEYWORDSNone

EXAMPLES

$ VDM/REPORT=SIZE/STATISTICS/BACKUP/SINCEGenerates a size report showing files backed up today. At the end of the report filestatistics showing number of files checked and number of files selected will be displayed.

/STATUS

Use this qualifier to see a brief display of what VDM/MONITOR is currently doing. Use thisqualifier to check that VDM is running, what permanent data file it is using, and what version ofVDM you have. This will also show you all disks being monitored and their current status(OKAY, WORRY or PANIC).

FORMAT/MONITOR/STATUS

KEYWORDSNone

EXAMPLES

$ VDM/MONITOR/STATUSShow the current VDM status for the monitor and all disks being monitored.

/STOP

Use this qualifier to stop the VDM/MONITOR detached process. If the monitor isn't running,the command will return an error. You can only use this qualifier in conjunction with the/MONITOR qualifier.

FORMAT/MONITOR/STOP

EXAMPLES

$ VDM/MONITOR/STOPStop monitoring for free space and disk errors.

/SUMMARY

Use this qualifier in conjunction with the /REPORT qualifier to summarize all the disks specifiedinto one report rather than creating a separate report for each disk. If you omit the qualifier, eachdisk starts on a new page.

FORMAT/REPORT=report-type/SUMMARY

EXAMPLES

$ VDM/REPORT=CURRENT/SORT=GROUP/SUMMARYGenerate a current report which shows each group's usage regardless of the number ofdrives on which they own files. All disks on which data is collected will be summarizedinto one current report.

/TITLE

Use the /title qualifier to specify a title that will be included in the report headings.

FORMAT:

/TITLE=”text title”

If you specify the /title qualifier you must include a text title; this qualifier does not have adefault value.

EXAMPLES:

$ VDM /REPORT=LARGEST_FILES /CREATE /SINCE=-7-00:00 -/TITLE=”Largest files created this week”This command will create a largest files report for the current disk showing the 50 largestfiles created in the past week. A title “Largest files created this week” will appear at thetop of each page of the report. Limiting the possible files, in the case by date, will greatlyreduce the amount of time it takes VDM to create this report. /num_files could also beused with this command to specify how many files should be included.

/TYPE

Use this qualifier to specify the format of the UIC's on reports.

FORMAT/REPORT=report-type/TYPE=[NUMERIC | ASCII]

KEYWORDSNUMERICSpecifies that UIC's are to be formatted in the form [n,m] where n and m are octalnumbers.

ASCII (Default)Specifies that UIC's are to be formatted in the form [account,username] where accountand username are text strings.

If you specify NUMERIC, you cannot specify ASCII and vice-versa. EXAMPLES

$ VDM/REPORT=PROTECTION/TYPE=ASCIIFormat UIC's using the alphanumeric format.

/UIC_COLLECT

Use this qualifier to collect usage information by directory. This qualifier is used in a batchprocedure which collects directory, UIC and quota information.

FORMAT/UIC_COLLECT

KEYWORDSNone

EXAMPLES

$ VDM/UIC_COLLECT/DISK=DRA1:Collect UIC ownership information for disk DRA1:.

/UIC_FILE


/UNUSED

Use this qualifier to ensure that only those files matching the specified number of unused blocksare selected. If you omit the qualifier, unused blocks are not used to select files.

OpenVMS does not store the value of the unused blocks in the file header. VDM calculates theunused value by subtracting used blocks from allocated blocks.

FORMAT/REPORT=report-type/UNUSED=[-] [n] [n:m] [n:] [:m]

KEYWORDS"-"Specifies that all files are selected except those matching the specified unused blocks.

[n] [n:m] [n:] [:m]Specifies the number of unused blocks used to select files. The unused blocks specifiesthe number of blocks allocated but not used by the file. Specify the unused blocks as aninteger. An unused value of 0 indicates the file contains no wasted space.

Specify n:m to select an inclusive range of unused blocks using the relationship (i>=nAND i<=m). Specify n to select a specific number of unused blocks. Specify n: to selecta number of unused blocks and all higher values. Specify :m to select a number ofunused blocks and all lower values. Specifying a value less than the disk's cluster sizemay produce a large report.


EXAMPLES

$ VDM/REPORT=SIZE/UNUSED=5000:Generate a report for all files with 5,000 or more unused blocks


/USAGE

Use this qualifier in conjunction with the /REPORT=CAPACITY qualifier to specify whether touse ACTUAL, AVERAGE, MAXIMUM or USED as the current usage in a VDM capacityreport. The default is ACTUAL. This qualifier may also be used in conjunction with/REPORT=CURRENT to control whether ACTUAL or disk USED blocks are reported; you maynot specify AVERAGE or MAXIMUM for the CURRENT report.

FORMAT/REPORT=CAPACITY/USAGE=[ACTUAL | AVERAGE | MAXIMUM | USED]

KEYWORDSYou can only specify one of the following options.

ACTUAL (Default)Specifies that actual allocated values are to be used when generating capacity or currentreports.

AVERAGESpecifies that average values are to be used when generating capacity reports.

MAXIMUMSpecifies that maximum values are to be used when generating capacity reports.

USEDSpecifies that used (as opposed to allocated) values are to be used when generatingcapacity or current reports.

EXAMPLES

$ VDM/REPORT=CAPACITY/USAGE=AVERAGEUse average number as the current usage to calculate growth rates in capacity reports.

$ VDM/REPORT=CURRENT/USAGE=USEDReport blocks used instead of blocks allocated for the usage values in a current report.

/USED

Use this qualifier to ensure that only those files matching the specified number of used (asopposed to allocated) blocks are selected. If you omit the qualifier, used blocks is not used toselect files.

FORMAT/REPORT=report-type/USED=[-] [n] [n:m] [n:] [:m]

KEYWORDS"-"Specifies that all files are selected except those matching the specified used blocks.

[n] [n:m] [n:] [:m]Specifies the number of used (as opposed to allocated) blocks be used to select files. Theused blocks specifies the number of blocks used by the file. Specify the used blocks as aninteger. An used value of 0 indicates the file contains no data. The used blocks matchesthe used blocks specified in the file header.

Specify n:m to select an inclusive range of used blocks using the relationship (i>=n ANDi<=m). Specify n to select a specific number of used blocks. Specify n: to select anumber of used blocks and all higher values. Specify :m to select a number of usedblocks and all lower values.


EXAMPLES

$ VDM/REPORT=SIZE/USED=5000:Generate a report for all files with 5,000 or more used blocks


/VALUE

Use this qualifier in conjunction with the /RESET qualifier to specify whether to resetAVERAGE, MAXIMUM or BOTH values in the specified data file. The default is BOTH.

FORMAT/RESET/VALUE=[AVERAGE | MAXIMUM | BOTH]

KEYWORDSYou can only specify one of the following options.

AVERAGESpecifies that average values are to be reset to the number of blocks currently allocated.

MAXIMUMSpecifies that maximum values are to be reset to the number of blocks currently allocated.

BOTHSpecifies that both average and maximum values are to be reset to the number of blockscurrently allocated.

EXAMPLES

$ VDM/RESET/VALUE=AVERAGE/DATA_FILE=UICReset the average number in the specified data file.

/VERSION

Use this qualifier to check the version of VDM you are running. The VERSION qualifier mustbe submitted as a separate command.

FORMAT/VERSION

KEYWORDSNone

EXAMPLES

$ VDM/VERSIONDisplay the current version of VDM you are running in the message:

%VDM-I-VERSION, this is VDM 6.0

Some additional information will follow including license and system information.

/WORRY

Use this qualifier to specify the first free space threshold and associated batch procedure. Youcan specify the threshold as a number of disk blocks or as a percentage of the total availableblocks on the drive. You can only use this qualifier in conjunction with the /MONITORqualifier.

FORMAT/MONITOR/WORRY=([[BLOCKS=number-of-blocks] or

[PERCENT=percentage]][,COMMAND=procedure-name][,NODE=nodename][,MESSAGES=number-of-messages][,QUEUE=batch-queue])

KEYWORDSBLOCKS=number-of-blocksSpecifies the minimum number of free blocks. If you omit blocks or percentage thevalues assigned to the DEFAULT disk will be used.

PERCENT=percentageSpecifies the minimum percentage of free space. If you omit blocks or percentage thevalues assigned to the DEFAULT disk will be used.

COMMAND=procedure-nameSpecifies the procedure to be executed when the /WORRY threshold is crossed. Theprocedure is assumed to be in the [VDM.DAT] directory. If you omit a file type, "COM"is assumed. If you omit COMMAND the procedure name assigned to the DEFAULT diskwill be used.

NODE=nodenameSpecifies the node that should detect the worry condition and take the appropriate action.Use this qualifier in a cluster environment to limit detection to the Node that the disk isnormally served to the cluster by otherwise you may have the command proceduresubmitted to run on multiple nodes. If you omit NODE the node name assigned to theDEFAULT disk will be used.

MESSAGES=number-of-messagesSpecifies the number of times the console worry message and/or mail should be sentwhen the disk drops below the worry threshold. The COMMAND procedure is onlysubmitted once, regardless of the value specified for MESSAGES. If you omitMESSAGES the number of messages assigned to the DEFAULT disk will be used.

QUEUE=batch-queue

Specifies the batch queue that the COMMAND procedure will be submitted to. Thedefault, if batch-queue is not specified, is SYS$BATCH. If you omit QUEUE the queueassigned to the DEFAULT disk will be used.

EXAMPLES

$ VDM /MONITOR /WORRY=(PERCENT=16, COMMAND=WORRY_16.COM) -/DISK=DUA0:Submit the procedure when the free space percentage falls below 16% on disk DUA0:.Copy the values for node, messages and queue from the DEFAULT disk record.

$ VDM /MONITOR /WORRY=(BLOCKS=5000,COMMAND=WORRY_PRIME) -/DISK=DUB0:Submit the default WORRY procedure when the free block count falls below 5,000 freeblocks on disk DUB0:. Copy the values for node, messages and queue from theDEFAULT disk record.

$ VDM /MONITOR /WORRY=(BLOCKS=5000,COMMAND=WORRY_PRIME) -/DISK=DEFAULTSet the default values to be 5000 blocks and the procedure to WORRY_PRIME for anydisks added to the monitor with a worry qualifier that has not specified them.

$ VDM /MONITOR /WORRY=(PERCENT=17, NODE=MVAXI, -QUEUE=MVAXI$BATCH, /MESSAGES=4)/DISK=DUB0:Add disk DUB0 to the monitor with a worry threshold of 17%. When the monitor runningon node MVAXI detects that the threshold has been crossed it will submit the defaultworry procedure to queue MVAXI$BATCH and signal the worry condition for fourintervals or until it has been resolved and free space is above the worry threshold.

Troubleshooting

This section shows you how to resolve problems with VDM.

If you have a problem running VDM, please do the following:

Verify that VDM logicals are definedVerify that your process has the necessary privilegesVerify that the command definition is installed and compatibleVerify that the license has been installedCall Technical Support at Saiga Systems

Verify that VDM logicals are definedVDM uses five logicals to access data files and executables. Normally, these logicals are definedas part of the system startup. However, to ensure the logicals are defined, type the followingcommand:


This procedure is created as part of the VDM installation procedure. If the logicals were alreadydefined, you will see the following message:

%DCL-I-SUPERSEDE, previous value of {logical_name} has been superseded

repeated five times.

To verify that the VDM logicals are defined, type the following command:

$ SHOW LOGICAL VDM*

You should see output similar to the following:

(LNM$PROCESS_TABLE)

(LNM$JOB_xxxxxx)

(LNM$GROUP_xxxxxx)

(LNM$SYSTEM_TABLE)

"VDM_CDU" = "ddcu:[VDM.CDU]" "VDM_COM" = "ddcu:[VDM.COM]" "VDM_DAT" = "ddcu:[VDM.DAT]" "VDM_DOC" = "ddcu:[VDM.DOC]" "VDM_EXE" = "ddcu:[VDM.EXE.VAX]" or "ddcu:[VDM.EXE.AXP]"

where "ddcu:" is the disk drive on which VDM is installed. This output indicates that the VDMlogicals are properly defined in the SYSTEM table.

Verify that your account has the necessary privilegesVDM requires OpenVMS privileges such as SYSPRV to run. Ensure that privileges in youraccount.

To ensure your process has all the necessary privileges, type the following command:


If you see the following message:

%SYSTEM-W-NOTALLPRIV, not all requested privileges authorized

the account you are logged into does not have all the privileges necessary to run VDM. Youmust log into an account which does have all the privileges. Normally, the SYSTEM accountwill have (or be able to acquire) all the necessary privileges to run VDM.

If your process does not have all the necessary privileges, VDM will list the additionalprivilege(s) you need when you enter a command.

To find out what privileges your process has, type the command:

$ SHOW PROCESS /PRIVILEGES

To give your process specific privileges, type the command:

$ SET PROCESS /PRIVILEGES=privilege_name

Verify that command definitions are installed and compatible.If you receive either of the following messages when you type a command:

%DCL-W-IVVERB, unrecognized command verb - check validity and spelling \VDM\

%CLI-F-SYNTAX, error parsing 'qualifier_name'-CLI-F-ENTNF, specified entity not found in command tables

where "qualifier_name" is one of the VDM qualifiers, VDM's command definition has not beeninstalled in the system or process table or the command definition version you are using is notcompatible with the VDM executable version.

To add the command definition to your process table, type the following command:


Ensure VDM has file accessVDM requires authorized access to all disk drives. It must be run out of a privileged account orbe given privilege when it is installed. Refer to the chapter "Privileges You Need to Use VDM"for more complete information.

Ensure there is adequate disk spaceVDM creates a number of work files and three permanent files each time data is collected. Ifyour system is very low on disk, you may have problems with insufficient space. The chapter onVDM data files contains more complete information on VDM's disk requirements.

Ensure there are adequate resources for sortingDuring the collection phase and to generate some of the reports, VDM uses the OpenVMS SORTutility. Because the OpenVMS sort uses a large amount of virtual memory during its operation,the command may abort with the message INSUFFICIENT VIRTUAL MEMORY. There areseveral reasons why this might happen:


If this error occurs during the execution of the collection procedure, it may leave the current datafile corrupt. If a data file was generated for the date when you had this error, delete that data file,adjust the quotas, and try the command again.

Ensure resource quotas are adequateWhen running the collection procedure, VDM may abort with the error INSUFFICIENTVIRTUAL MEMORY while running the analyze/disk portion. This error can be caused by thefollowing:


Adjust the quotas appropriately, and run the collection procedure again.

Handling system crashesIf your system crashes or is restarted, you may have to resubmit the data collection and dataanalysis procedures.

Verifying that the License has been Installed

To verify that the license has been installed enter:$ show logical pkms*

there should be a translation for one of the following logicals:PKMS$VDM70VAXPKMS$VDM70AXPPKMS$COHORT3VAXPKMS$COHORT3AXP

If one of these logicals is not defined look for a pkms startup command procedure insys$manager and execute it. If the logical is defined enter:

$ vdm/versionwhich will tell you whether or not the license has expired.

Calling Saiga SystemsIf you try the above suggestions and still continue to have problems, please contact SaigaSystems Technical Support at 1-800-561-8876. Technical support is provided between 8:00 a.m.and 5:00 p.m. Mountain Time.

When you call 1-800-561-8876, please have the following information available:Alpha AXP or VAX ModelOpenVMS versionCompany NameVDM version (from VDM/VERSION output)

The operator will:1) verify that you have a support agreement2) transfer your call to the Technical Support group.

You may also obtain technical support by:FAX (403) 263-0744E-MAIL [email protected] http://www.saiga.com/Listserver [email protected]

Appendix A, Error messages

VDM uses OpenVMS-style error messages. The chapter lists every VDM error message inalphabetical order along with an explanation and recommended actions.

Error messages in VDM, like OpenVMS messages, are categorized as:

• Informational - %VDM-I-• Warning - %VDM-W-• Error - %VDM-E-• Success - %VDM-S-

to help you determine if action is required on your part.

The rest of the appendix lists error messages and recommended action.

BADINTERVAL, Interval must be between 1 min and 60 minYou specified an invalid time interval for free space checks. The time intervalmust be between 1 minute and 60 minutes.

CANTOPENIN, Can't open input fileThere was an error opening the file. Check the logical VDM_DAT, and that the VDM data files are accessible in that directory.

DEFDISK, Defaulted to SYS$SYSDEVICE:VDM was unable to determine what disk you are on from SYS$DISK so it has defaultedto SYS$SYSDEVICE:

DEVNOTMOUNT. <device> is not mounted, please mount device and re-enter commandYou tried to add a disk that was not mounted. Since VDM needs to determine themaximum block count for the disk it could not add it. Mount the disk and re-enter thecommand.

DISKNOTFOUND, Disk(s) not found in current dataThere is no data for the specified disk. Respecify the command with a diskparameter that exists in the data file. If you are unsure of what disks you have inthe file, do not specify the disk, and the reports generated will tell you which disksyou have.

DUPDISKNAM, Duplicate diskname, data ignoredThe diskname specified already exists in data collection. Remove the duplicate

Error Messages

diskname from data collection.

ERRCLOLIS, Error closing list fileAn error occurred while closing the listing file. The error messages that followthis error message will further explain the problem.

ERRCLOLOG, Error closing log fileAn error occurred while closing the log file. The error messages that follow thiserror message will further explain the problem.

ERRCLOMAI, Error closing mail text fileAn error occurred while closing the mail text file. The error messages that followthis error message will further explain the problem.

ERRCLOPERM, Error closing permanent data fileAn error occurred while closing the permanent data file. The error messages thatfollow this error message will further explain the problem.

ERRGETDISK, <disk> - Error getting disk infoYou can only specify one disk in this case. Please re-enter the command with only onedisk.

ERRINQUAL, Error in processing the qualifier qualifierVDM encountered an error while processing a command. The error message(s)that follow will explain the problem.

ERROPELIS, Error opening list fileAn error occurred while opening the listing file. The error messages that followthis error message will further explain the problem.

ERROPELOG, Error opening log fileAn error occurred while opening the log file. The error messages that follow thiserror message will further explain the problem.

ERROPEMAI, Error opening mail text fileAn error occurred while opening the mail text file. The error messages that followthis error message will further explain the problem.

ERROPENFILE, Error opening file filenameAn error occurred while opening the specified file. The error message(s) that follow willexplain the problem.

ERROPENOUT, Error opening "filename" for output

Error Messages

There was an error opening a file for output. Check if you have sufficient diskquota, and that you have write access to the directory that you are trying to writeto.

ERROPEPERM, Error opening permanent data fileAn error occurred while opening the permanent data file. The error messages thatfollow this error message will further explain the problem.

ERROPPLA, Error opening VDM_PLA fileThere was an error opening the file. Check the logical VDM_DAT, and that the VDM data files are accessible in that directory.

ERRREADFILE, Error reading file filenameAn error occurred while reading the specified file. The error message(s) that follow willexplain the problem.

ERRSETAST, Error setting up mailbox ASTAn error occurred while setting up the write attention AST on the mailbox. Theerror messages that follow will further explain the problem.

ERRSTRTDET, Error starting detached processAn error occurred while starting the detached process. The error messages thatfollow will further explain the problem.

ERRSUBMIT, Error submitting <job> to batchThe VDM monitor process encountered an error submitting the corrective panic or worryprocedure. The following error messages should provide additional information.

ERRWRITLIS, Error writing list fileAn error occurred while writing to the listing file. The error messages that followthis error message will further explain the problem.

ERRWRITMAI, Error writing mail text fileAn error occurred while writing the mail text file. The error messages that followthis error message will further explain the problem.

ERRWRITPERM, Error writing permanent data fileAn error occurred while writing the permanent data file. The error messages thatfollow this error message will further explain the problem.

FILENOTFOUND, File specified was not foundThe file you specified when removing a file event record was not found. Please checkspelling and re-enter command.

Error Messages

FNF, The file <file> was not foundThe file was not found. Please check spelling, verify the files location and re-enter thecommand.

INCORFORMAT, Incorrect format for date specifiedThe date that you specified in an incorrect format. Check for spelling errors andretry using the format DD-MMM-YY. (ie. 28-FEB-90)

INTTOOHIGH, The integer <number> specified with the qualifier <string> is too high,maximum

is <number>You have specified an integer value that exceeds the maximum allowed value. Re-enterthe command with a lower value.

INTTOOLOW, The integer <number> specified with the qualifier <string> is too low,minimum

is <number>You have specified an integer value that below the minimum allowed value. Re-enter thecommand with a higher value.

INVACCESS, <code> is an invalid access code, please re-enterYou have specified an incorrect access code. Check spelling and verify the access code.Re-enter the command.

INVACE, Invalid access control entry, please re-enterYou have specified an invalid access control entry. Checking spelling and verify that theaccess code is valid. Re-enter the command.

INVDATE, string is not a valid date for the qualifier qualifierThe date you specified using the specified qualifier is invalid. The syntax may bewrong or you may have specified a time as well as a date. Please check for typingmistakes, check the qualifier documentation and re-enter the command with avalid OpenVMS date.

INVFLAG, <string> is an invalid flag, please re-enterYou have specified an incorrect flag. Check spelling and verify the flag. Re-enter thecommand.

INVPROTCLASS, <string> is an invalid protection classYou have specified an incorrect protection code. Check spelling and verify the protectioncode. Re-enter the command.

INVLRECHNG, Invalid number specified for large change

Error Messages

A number outside the valid range was specified for the parameter. Check thedocumentation, and respecify with the parameter in the correct range.

INVUICFORMAT, string is not a valid format for a UIC, check bracketsThe UIC you specified using the qualifier is invalid. The syntax may be wrong, thegroup or member may be too large or small. Please check for typing mistakes, check thequalifier documentation and re-enter the command with a valid UIC.

ITEMREQ, You must enter a value for the qualifier qualifierYou must specify an item when you specify this qualifier. Check for typingerrors, check the qualifier documentation and re-enter the command.

LOGNTDFND, VDM_DAT not definedThe logical VDM_DAT is not defined. Define in the system process table thelogicals VDM_DAT and VDM_EXE.

LOSTHEAD, Lost file header for: <file>You have a file specification of [] which will not sort correctly.

MINGTMAX, Minimum value is greater than Maximum value, please respecifyYou have specified a minimum value which is greater than the maximum value. Checkyour command and re-enter it; perhaps switching the two values.

MUSTSPEC, Must specify either /RATE or /PREVIOUS, both cannot be excludedYou must specify /RATE or /PREVIOUS in order for VDM to calculate the future value.

NONEXPR, Failure starting VDM MONITOR, check console for errorsThere was a problem starting the VDM detached process. The console,VDM_DAT:VDM_ERROR.node file and the system accounting file may contain moreinformation.

NOFILE, No file specifiedVDM could not open one of the required data files. Check the logical nameVDM_DAT, and verify that the data files are accessible, and that the data files arenamed in the proper format.

NOFILEMATCH, No files matched the file selection criteriaVDM could not find any files that matched the value specified with the /file qualifier.Verify that the file specification was entered correctly, that the file exists and that the/disk qualifier was specified if the file is not on the current disk.

NORMAL, Normal successful completionThis is a normal completion message. No action is necessary.

Error Messages

NOSUCHIDENT, string is not an identifierThe string you specified is not an identifier. Please check for typing errors and re-enterthe command with a correct identifier.

NOTDET, Image must be run as a detached processThe image VDM_DETACHED.EXE must be run as a detached process. It cannotbe run interactively. To start the detached process, use $VDM/MONITOR/START.

NOTDISKCLASS, Disk specified is not disk classYou specified a device name not in the disk class in the "DISK=device name"command.

NOTFOUND, File not foundVDM could not open one of the required data files. Check the logical nameVDM_DAT, and verify that the data files are accessible, and that the data files arenamed in the proper format.

NOTROOTVOL, Disk is not a root volumeThe disk specified was not a root volume. VDM can only collect data on rootvolumes. Check that you have specified the disk correctly and retry.

NOTRUN, VDM/MONITOR is not runningThe detached process for VDM/MONITOR is not running. To start the process,use VDM/MONITOR/START.

PRCSSTRT, Starting VDM MONITOR, please wait ...An informational message indicating you are starting the detached process. No furtheraction is required.

PROCID, Identification of created process is nnnnnnnnThe process identification of the detached process is the number that wasdisplayed. This is displayed as a result of the VDM/MONITOR/STARTcommand.

REALTOOHIGH, The real <number> specified with the qualifier <qualifier> is too high,maximum is <number>

You have specified a value that is too high. Please re-enter with a value that is lower thanthe maximum.

REALTOOLOW, The real <number> specified with the qualifier <qualifier> is too low,minimum is <number>

You have specified a value that is too low. Please re-enter with a value that is higher than

Error Messages

the minimum.

REQDETACH, Operation requires DETACH privilegeVDM/MONITOR requires the privilege DETACH to be run. Make sure that youhave the appropriate privileges and try the command again.

REQOPER, Operation requires OPER privilegeVDM/MONITOR requires the privilege OPER to be run. Make sure that youhave the appropriate privileges and try the command again.

REQPRMMBX, Operation requires PRMMBX privilegeVDM/MONITOR requires the privilege PRMMBX to be run. Make sure that youhave the appropriate privileges and try the command again.

REQSYSNAM, Operation requires SYSNAM privilegeVDM/MONITOR requires the privilege SYSNAM to be run. Make sure that youhave the appropriate privileges and try the command again.

REQSYSPRV, Operation requires SYSPRV privilegeVDM/MONITOR requires the privilege SYSPRV to be run. Make sure that youhave the appropriate privileges and try the command again.

REQWORLD, Operation requires WORLD privilegeVDM/MONITOR requires the privilege WORLD to be run. Make sure that youhave the appropriate privileges and try the command again.

RESPECIFY, Please respecify with the correct parametersThe disk that was specified was not a disk device. Respecify the command withthe proper device name.

RUNNING, VDM/MONITOR is already runningYou specified VDM/MONITOR/START, and the detached process was alreadyrunning.

TOOMANYDISK, Too many disks specified ROUTINE - <string>You have tried to add too many disk records.

TOOMANYDISKS, Too many disks specifiedMore than the maximum number of disks were specified. Maximum number isthe parameter max_num_disks, currently 200. Please specify fewer disks.

TOOMANYFILES, Too many files specifiedYou have tried to add too many file records.

Error Messages

VALUETOOHIGH, The item i specified with the qualifier q is too high, maximum is nThe value you specified for the item is greater than the legal maximum. Check thequalifier documentation and re-enter the command with a value equal to or less than themaximum.

VALUETOOLOW, The item i specified with the qualifier q is too low, minimum is nThe value you specified for the item is less than the legal minimum. Check the qualifierdocumentation and re-enter the command with a value equal to or greater than theminimum.

VERSION, This is VDM 6.0 from Saiga SystemsThis is the VDM response to the command VDM/VERSION. It will be followed by somegeneral system and VDM license information.

WORLESSPAN, WORRY threshold is less than or equal to PANIC thresholdYou specified a WORRY threshold level, either number of blocks or percentageof total blocks available, that is less than or equal to the PANIC threshold level.

WRONGQUETYP, Wrong queue type, must be batch or genericYou have specified the wrong type of queue. Please re-enter with a queue of the correcttype.

Appendix B, Moving HELP text

This appendix shows you how to move VDM HELP screens between your system help libraryand private, user help library. You would do this if you had previously installed VDM help intothe system help library and did not want public access to the help screens.

Moving HELP from system to a user libraryTo move the VDM HELP screens from the system HELP library to a private, user help library:

1. Delete help text from the system help library:

$ LIBRARY/DELETE=VDM SYS$HELP:HELPLIB.HLB

2. Define a user help library logical.

2.1 Enter the command "$ SHOW LOGICAL HLP$*" to find a user library logical namethat has not previously been assigned (logical names may be HLP$LIBRARY,HLP$LIBRARY_1, HLP$LIBRARY_2, ... ,HLP$LIBRARY_n)

2.2 Assign the help logical as follows:

$ DEFINE/SYSTEM HLP$LIBRARY_n VDM_DOC:VDM.HLB

If you define the logical in the SYSTEM table, everyone will be able to access the HELP. If you define it in your PROCESS table, only you will be able to access the HELP. If youuse the SYSTEM table, you should add a line to the VDM system startup to define itevery time the system is booted. If you use the PROCESS table, you should add a line toyour LOGIN.COM.

Moving HELP from a user to the system libraryTo move the VDM HELP screens from a private, user help library to the system help library:

1. Find the logical pointing to the user help library for VDM and deassign it.

$ SHOW LOGICAL HLP$LIBRARY*$ DEASSIGN HLP$LIBRARY_n

2. Add the VDM help library to the system help library.

$ LIBRARY/REPLACE/HELP SYS$HELP:HELPLIB.HLB -_$ dev:[VDM.DOC]VDM.HLP

3. If the HLP$LIBRARY_n logical was not the last logical in the sequence of user help librarylogicals, you must assign something else to it. HELP stops translating HLP$LIBRARY_n

logicals when it encounters the first one which isn't defined.

Appendix C, Moving command definitions

This appendix shows you how to install the VDM command definition in your systemDCLTABLES, remove it from the DCLTABLES or access it from the VDM directory. Youwould remove the VDM command definition if you had previously installed the VDM commanddefinition in the system command definition library and did not want public access to thecommand definition.

To install the command definition in the system table:

1. Check which version of the table is installed

$ INSTALLINSTALL> LIST SYS$LIBRARY:DCLTABLES.EXEINSTALL> EXIT

2. Replace the VDM command definitions in the table:

$ SET COMMAND/TABLE=SYS$LIBRARY:DCLTABLES.EXE -_$ /OUTPUT=SYS$LIBRARY:DCLTABLES.EXE -_$ /REPLACE VDM_CDU:VDM

NOTE: Ensure the new DCLTABLES.EXE are in the same directory as the previous tables.

3. Install the new table:

$ INSTALLINSTALL> REPLACE SYS$LIBRARY:DCLTABLES.EXEINSTALL> EXIT

4. Log out and back in to get a copy of the new table.

To remove the command definition from the system table, type:

$ SET COMMAND/DELETE=VDM/TABLE=SYS$LIBRARY:-_$ DCLTABLES.EXE/OUTPUT=SYS$LIBRARY:DCLTABLES.EXE

To access the command definition from the VDM directory, type:


Appendix D, Removing VDM from your system

This appendix shows you how to remove VDM from your system if you received a demo,decided to return it and want to remove VDM from your system.

NOTE: There is a command procedure REMOVE_VDM.COM which you can adapt to performmany of these steps rather than keying the commands individually.

Delete directoriesTo remove the VDM directories from your system, type:

$ DELETE SYS$SYSDEVICE:[VDM...]*.*;*/EXCLUDE=(*.DIR)

This removes all non-directory files from the directory structure.

To delete the VDM directory file from your system, set the protection to allow delete and deletethe directory files. Type:

$ SET FILE/PROTECTION=S:RWED SYS$SYSDEVICE:[VDM...]*.DIR$ DELETE SYS$SYSDEVICE:[VDM...]*.*;*$ DELETE SYS$SYSDEVICE:[000000]VDM.DIR;*

Remove HELP screensIf help screens were added into the system help library, remove them by typing:

$ LIBRARY/DELETE=VDM SYS$HELP:HELPLIB.HLB

If help screens were added into a private, user help library, follow the procedure outlined inAppendix B to remove them.

Remove command definitionIf the VDM command verb was added to the DCLTABLES, remove it by typing:

$ SET COMMAND/DELETE=VDM/TABLE=SYS$LIBRARY:-_$ DCLTABLES.EXE/OUTPUT=SYS$LIBRARY:DCLTABLES.EXE

Note: Remember to remove the command:

@VDM_COM:INSTALL_CDU.COM

from your LOGIN.COM and any other command procedures.

Deassign system logical namesDeassign the system logicals required by VDM:

$ DEASSIGN/SYSTEM VDM_CDU

$ DEASSIGN/SYSTEM VDM_COM

$ DEASSIGN/SYSTEM VDM_DAT

$ DEASSIGN/SYSTEM VDM_DOC

$ DEASSIGN/SYSTEM VDM_EXE

Remove SYS$MANAGER filesDelete the files VDM_STARTUP.COM and VDM_SYSTEM_LOGICALS.COM created by theinstallation procedure from the SYS$MANAGER directory and remove the line that executesthis procedure from SYS$MANAGER:SYSTARTUP_V5.COM orSYS$MANAGER:SYSTARTUP_VMS.COM (OpenVMS 6.0).

Appendix E, Software licenses

This appendix describes the terms of the VDM software license. Customers may license VDMseparately or as part of the Cohort Version 2 suite of system management utilities.

VDM and Cohort are sold under the following types of licenses:

CPU LicenseA CPU license allows you to run on one CPU at a time. It does not matter what the AXP orVAX model is.

Site LicenseA Site License allows you to run on any number of AXP or VAX systems owned by yourcompany within one city. For a nominal amount a site license can be upgraded to include anynumber of VAX and AXP systems within one city.

Corporate LicenseA Corporate License allows you to run VDM on any number of AXP or VAX systems owned byyour company within one country. For a nominal amount a corporate license can be upgraded toinclude any number of VAX and AXP systems within one country.

Global LicenseA Global License allows you to run VDM on any number of AXP or VAX systems worldwide.For a nominal amount a global license can be upgraded to include any number of VAX and AXPsystems worldwide.

License ValidationYou do not have to sign the license and return it. It comes into effect when you make use of theproduct.

DIGITALNone of Saiga Systems products require any Digital licenses beyond that for OpenVMS. If youplan to make changes to the products, you must have a FORTRAN license or access to a systemthat has such a license.

Upgrading your licenseYou can upgrade from one license to another by paying the difference between the two.

Appendix F, File Flags

This appendix lists the keywords you can use with the /FLAGS qualifier.

BADACL File contains a bad ACL. ACL is not used for protection checking.BADBLOCK File contains a bad block.CONTIGB File is best-try contiguous.CONTIG File is contiguous.DIRECTORY File is a directory.ERASE File will be erased (overwritten) on delete.LOCKED File is locked.MARKDEL File is marked for deletion.NOBACKUP File will not be backed up.NOCHARGE File is not charged to owner.NOMOVE File cannot be moved.READCHECK File requires read check operations. All read operations are verified.SPOOL File is a temporary spool file.WRITCHECK File requires write check operations. All write operations are verified.WRITEBACK Write-back cache may be used.

Appendix G - GO, an OpenVMS directory utility

This chapter shows you how to use GO, an OpenVMS Directory Utility. GO is useful to users aswellãas system managers. We've included a separate, unbound set of GO documentation whichyou can photocopy and distribute to your users.

OverviewGO moves you around OpenVMS directories and sub-directories easily and quickly and re-defines your prompt to show where you are. It is simpler and more powerful than thecorresponding OpenVMS commands SET/SHOW DEFAULT. GO is easy to learn since it lookslike the DCL commands you use every day. To invoke GO, type "GO" along with the desiredparameter at the DCL prompt. GO automatically returns to the DCL command level after everycommand. You can enter "HELP GO" at the command level to obtain information about GO'soperations. See command procedures GO_1, GO_2, GO_3 in VDM_COM: for examples of GOusage.

Going to a new directory or sub-directoryType "GO directory_name" to move to a new directory or sub-directory. For example, thecommand:

$ GO larry.src.inc

sets your current directory to [LARRY.SRC.INC]. You do not have the enter "[" and "]" arounddirectory specifications. However, if you do, GO will still work correctly. GO uses thefollowing logic to decide what to do:

If directory_name starts with a periodgo to the specified sub-directory under the current directory if it exists

elseif directory_name is a top level directory,

go to the top level directoryelseif directory_name is a sub-directory under the current directory,

display "sub-directory assumed" messagego to the sub-directory

elsedisplay "invalid directory" messageleave the current default unchanged

You can specify a drive in the normal OpenVMS format when you specify a new directory. Ifthe drive or directory doesn't exist, GO displays a message and leaves your current defaultdirectory unchanged.

Going to a sub-directoryType "GO .sub_directory_name" to move to a sub-directory under your current directory. (Notethe period). For example "GO .products" set your current directory to the .PRODUCTS sub-directory. You do not have the enter "[" and "]" around directory specifications. If you do, GO

will still work correctly. GO uses the leading period to distinguish between a sub-directory and adirectory. If the sub-directory doesn't exist, GO displays a message and leaves your currentdirectory unchanged.

Going up one level in your current directoryType "UP" to move up one level from your current directory. GO sets your current directory upone level. For example, if your current default directory is [LARRY.SRC.INC] and you enterUP, GO will set your default directory to [LARRY.SRC]. If you are already at the top of yourdirectory, GO displays a message and leaves your current directory unchanged.

Going to the top of your current directoryType "TOP" to move to the top level of your current directory. GO sets your current directory tothe top of the current directory tree. For example, if your current default directory is[LARRY.SRC.INC] and you enter TOP, GO will set your default directory to [LARRY]. If youare already at the top of your directory, GO displays a message and leaves your current directoryunchanged.

Going to your home directoryType "HOME" to move to the default login directory pointed to by the logical SYS$LOGIN.

Returning to a previous directoryType "POP" to go back to your previous directory. GO stores your previous directory and returnsyou to it when you type "POP". A current directory message is always displayed even if youhave the message display turned off. If you have no previous directory, GO displays a messageand leaves your current directory unchanged. Here's an example showing you how the POPcommand works:

$ GO bigb%Default Directory EAGLE$DRA2:[BIGB]BIGB> GO products.watch%Default Directory EAGLE$DRA2:[PRODUCTS.WATCH]PRODUCTS.WATCH>POP%Default Directory EAGLE$DRA2:[BIGB]

Going to a new driveType "GO drive:" to move to a new disk drive. You can specify a directory if you wish. If youdon't and the logical GO_DEVICE is defined to "OFF" or undefined, your default directoryremains unchanged. If the logical GO_DEVICE is defined as "ON", your default directory is setto the top level directory [000000]. Like OpenVMS, GO uses the trailing colon to distinguish adrive name. If the directory doesn't exist on the drive, GO displays a message and leaves yourcurrent default directory unchanged.

Displaying your current directoryType "GO" without a parameter to see a "%Default directory" message showing your currentdirectory and a list of sub-directories in alphabetical order.

Displaying directory treesDisplaying the entire directory tree for the driveType "TREE" without a parameter to get a list of all directories and sub-directories on yourcurrent disk drive. GO displays a list of directories and sub-directories in alphabetical order. Ifthere are more than 20 directories, GO pauses when the screen is full. Enter <RETURN> tocontinue the listing.

Displaying a list of sub-directoriesType "GO" without a parameter to get a list of sub-directories below your current directory. GOdisplays a "%Default directory" message showing your current directory and a list ofsub-directories in alphabetical order. If there are more than 20 directories, GO pauses when thescreen is full. Enter <RETURN> to continue the listing. If there aren't any sub-directories, GOdisplays the message "%No sub-directories". Use the /LEVEL qualifier to control the number ofsub-directories displayed (The default is /LEVEL=1). Use the /INDENT qualifier to control theamount of indentation at each level of the tree (The default is /INDENT=4).

Controlling the current directory messageAs you move from one directory to another, GO displays a current directory message to keep youinformed of where you are. Here's an example:

$ GO bigb%Default Directory EAGLE$DRA2:[BIGB]BIGB> GO .products.watch%Default Directory EAGLE$DRA2:[BIGB.PRODUCTS.WATCH]BIGB.PRODUCTS.WATCH>

If you don't want this message displayed, define the logical name GO_DISPLAY to "OFF" inyour LOGIN.COM file using the command:

$ DEFINE GO_DISPLAY "OFF"

VDM_COM: contains a procedure, GO_3.COM, which illustrates this.

Controlling the promptAs you move from one directory to another, GO redefines your prompt to keep you informed ofwhere you are. You can include the node name as well as up to three levels of directory. Bydefault, GO will not include the node name and will show only the lowest level of your currentdirectory. Here's an example:

$ GO bigb%Default Directory EAGLE$DRA2:[BIGB]BIGB> GO .products.watch%Default Directory EAGLE$DRA2:[BIGB.PRODUCTS.WATCH]WATCH>

Disabling prompt definitionIf you don't want your prompt defined, define the logical name GO_PROMPT to "OFF" in yourLOGIN.COM FILE. NOTE: When you change GO_PROMPT to OFF, the prompt is left as itcurrently exists, it is NOT redefined to "$". You must redefine the prompt using the SETPROMPT command manually.

Specifying the number of levelsBy default, GO shows only the lowest level of the directory in your prompt. If you want yourprompt to include more than one directory level, define the logical name GO_PROMPT to be "2"or "3" to show two or three levels of directory information above your current sub-directory.

Including the node nameIf you want to include the node name in the prompt, define the logical name GO_NODE to "ON"in your LOGIN.COM file.

OpenVMS imposes a limit of 32 characters on the prompt. GO truncates the prompt to amaximum of 30 characters.

VDM_COM: contains a procedure, GO_3.COM, which illustrates these options.

GO qualifiersGO uses the following qualifiers:

/DISK display a directory tree of entire disk/HOME go to SYS$LOGIN/INDENT=n specify amount of indentation in directory trees; default is /INDENT=4/LEVEL=n specify number of directory levels to show when /DISK is present;

default is /LEVEL=9, otherwise, default is /LEVEL=1/POP go back to previous directory/TOP go to the top level of current directory/UP go up a level in current directory

For more information on VDM qualifiers, refer to the chapter "VDM Commands".

GO symbolsTo make GO as easy as possible to use, GO uses the following symbols:

HOME :== "GO/HOME"POP :== "GO/POP"TOP :== "GO/TOP"TREE :== "GO/DISKUP :== "GO/UP"

GO logicalsGO uses the following logicals:

GO_DISPLAY enable/disable current directory messageOFF | ON

GO_PROMPT control prompt definitionOFF | ON | 1 | 2 | 3

GO_NODE include/exclude node name in promptOFF | ON

For more information on VDM logicals, refer to the chapter "Logicals you need to use VDM".

GO versus the SET/SHOW DEFAULT COMMANDSGO is designed to replace the SET DEFAULT and SHOW DEFAULT commands. However,you can intermix GO and SET/SHOW commands freely without error. If you do so, you shouldturn off the GO prompt redefinition and redefine the prompt to "$". Otherwise, the combinationof the two commands will be misleading since SET DEFAULT will not cause your prompt to beredefined and it may look as if you are in a directory you aren't.

Directory accessGO does not give you any additional access to directories. If you attempt to access directories towhich you lack access, you will get the same error message you normally would.

Index

ACEcontrolling matches for multiple

ACEs . . . . . . . . . . . . . . . 117Specifying . . . . . . . . . . . . . . . . . . . 84

Analyze /Disk . . . . . . . . . . . . . . . . . . . . . . 63Options . . . . . . . . . . . . . . . . . . . . . 63

Cleanup proceduresDefining . . . . . . . . . . . . . . . . . . . . 33Writing . . . . . . . . . . . . . . . . . . 33, 34

Cluster considerations . . . . . . . . . . . . . . . 14Common data collecction with RA

. . . . . . . . . . . . . . . . . . . . . 15Data collection in a . . . . . . . . . . . . 14Running monitor in . . . . . . . . . . . . 15Startup command procedure . . . . . 15SYSUAF . . . . . . . . . . . . . . . . . . . . 14

Command definition . . . . . . . . . . . . . . . . 160Configuration

Moving command definitions . . . 174Moving help text . . . . . . . . . . . . . 172Uninstalling VDM . . . . . . . . . . . . 175

Data Collection/dir_collect qualifier . . . . . . . . . . 98/quota_collect . . . . . . . . . . . . . . . 133/uic_collect . . . . . . . . . . . . . . . . . 150Automatic submission . . . . . . . . . . 41Benefits of regular . . . . . . . . . . . . 42Checking logs . . . . . . . . . . . . . . . . 13Collecting directory information . . 41Collecting quota information . . . . 41Common with RA . . . . . . . . . . . . . 15Conflict with backup . . . . . . . . . . . 40Converting V4 or V5 data so it can be

used by V7 . . . . . . . . . . . . 93Data files . . . . . . . . . . . . . . . . 65, 66Disk quotas and . . . . . . . . . . . 61, 62Disknames.dat and . . . . . . . . . . . . 13Generating file size reports during

. . . . . . . . . . . . . . . . . . . . . 41Location of batch log . . . . . . . . . . 41No differences between V6 and V7

data . . . . . . . . . . . . . . . . . . 93

Overview of . . . . . . . . . . . . . . . . . 13Privileges needed . . . . . . . . . . . . . 71Process described . . . . . . . . . . . . . 40Qualifiers . . . . . . . . . . . . . . . . . . . 75Reference section . . . . . . . . . . . . . 40resetting cumulative values . . . 59, 60,

78, 96, 137Sample report procedures . . . . . . . 13Sharing with RA . . . . . . . . . . . . . . 15Specifying disks . . . . . . . . . . . . . . 41Specifying start time . . . . . . . . . . . 41Specifying value to reset . . . . . . . 155Submitting . . . . . . . . . . . . . . . . . . . 13System impact . . . . . . . . . . . . . . . . 40Time required to complete . . . . . . 41

Disk quotasChanging using SYSMAN . . . . . . . 61VDM and . . . . . . . . . . . . . . . . . . . 61

disknames.dat . . . . . . . . . . . . . . . . . . . . . . 41File protections

controlling matches for multipleACEs . . . . . . . . . . . . . . . 117

FilesDirectory usage . . . . . . . . . . . . . . . 66disknames.dat . . . . . . . . . . . . . . . . 66monitor data file . . . . . . . . . . . . . . 67UIC data files . . . . . . . . . . . . . . . . 66vdm_perm_data.dat . . . . . . . . . . . 67vdm_pla . . . . . . . . . . . . . . . . . . . . 67

Finding filesBy access control entries . . . . . . . 84By ACE . . . . . . . . . . . . . . . . . . . . 84By backup date . . . . . . . . . . . . 22, 89By blocks allocated . . . . . . . . 22, 88By blocks unused . . . . . . . . . . . . . 22By blocks used . . . . . . . . . . . 22, 154By created date . . . . . . . . . . . . 22, 94By expiration date . . . . . . . . . 22, 106By file name . . . . . . . . . . . . . . . . . 22By file organization . . . . . . . . . . 124By file protection . . . . . . . . . 23, 131By filename . . . . . . . . . . . . . . . . . 107

By flags . . . . . . . . . . . . . . . . . 22, 108By flags, list of valid . . . . . . . . . 178By modification date . . . . . . . 22, 120by number of fragments . . . . . 22, 109By owner . . . . . . . . . . . . . . . . . . 126By size . . . . . . . . . . . . . . . . . . . . 141No longer authorized . . . . . . . . . . 54specifying a before date . . . . . . . . 90Specifying a since date . . . . . . . . 140the largest files on a disk . . . 22, 123using AND or OR for ACE or

Protections . . . . . . . . . . . 117with unused disk blocks . . . . . . . 152

Getting started . . . . . . . . . . . . . . . . . . . . . . 12Go

Changing directories using . . . . . 179Changing disks using . . . . . . . . . . 180Compared to Set Default . . . . . . . 183Configuring Go with logicals names

. . . . . . . . . . . . . . . . . . . . 183Customizing directory messages

. . . . . . . . . . . . . . . . . . . . 181Customizing your OpenVMS prompt

. . . . . . . . . . . . . . . . 181, 182Displaying directory trees . . . . . 181Displaying your current directory

. . . . . . . . . . . . . . . . . . . . 180Overview . . . . . . . . . . . . . . . . . . 179Qualifiers . . . . . . . . . . . . . . . . . . 182Using symbols for Go commands

. . . . . . . . . . . . . . . . . . . . 182GO_DEVICE . . . . . . . . . . . . . . . . . . . . . . 69GO_DISPLAY . . . . . . . . . . . . . . . . . . . . . 69GO_NODE . . . . . . . . . . . . . . . . . . . . . . . . 69GO_PROMPT . . . . . . . . . . . . . . . . . . . . . 70Installation . . . . . . . . . . . . . . . . . . . . . . . . 10

Disk blocks required . . . . . . . . . . 65Licensing . . . . . . . . . . . . . . . . . . . . . . . . 177Logical names

Reference . . . . . . . . . . . . . . . . . . . 69Verifying . . . . . . . . . . . . . . . . . . . 159

Monitor/broadcast qualifier . . . . . . . . . . . 91/console qualifier . . . . . . . . . . . . . 92Adding events . . . . . . . . . . . . . . . 102

broadcasting messages from . . . . . 91Cleanup procedures . . . . . . . . . . . 31Clusters . . . . . . . . . . . . . . . . . . . . . 38Controlling batch job submissions

. . . . . . . . . . . . . . . . . . . . . 86controlling console messages . . . . 92Creating a permanent data file . . . 29Debugging . . . . . . . . . . . . . . . . . . . 39Disk quotas and . . . . . . . . . . . . . . 38Error messages . . . . . . . . . . . . . . . 37File events explained . . . . . . . . . . 32Getting monitor status . . . . . . . . . 145Keeping action procedure logs . . . 70Listing permanent data file contents

. . . . . . . . . . . . . . . . . 30, 114Log file name and location . . . . . . 35Logging without acting on conditions

. . . . . . . . . . . . . . . . . . . . . 36Monitoring files . . . . . . . . . . . 32, 33opening a new log file . . . . . . . . 115Panic threshold clauses . . . . . . . . . 32Permanent data file . . . . . . . . . 29, 31Privileges needed . . . . . . . . . . . . . 71Qualifiers . . . . . . . . . . . . . . . 79, 121Reference section . . . . . . . . . . 29-39Removing file events . . . . . . . . . . 33Resources required . . . . . . . . . . . . 38Restarting the monitor process . . . 38Sending warning messages . . . . . . 35specify recipient for mail . . . . . . 116Specifying a mail recipient . . . . . . 36Specifying a message broadcast class

. . . . . . . . . . . . . . . . . . . . . 36Specifying critical files . . . . . . . 107specifying interval between checks

. . . . . . . . . . . . . . . . . . . . 111specifying panic threshold . . . . . 127Specifying worry thresholds . . . . 157Starting the monitor process . . . . . 31,

143Status of . . . . . . . . . . . . . . . . . . . . 39Stopping the monitor . . . . . . . . . . 146Threshold clauses . . . . . . . . . . . . . 31Troubleshooting . . . . . . . . . . . . . . 39turning off event logging . . . . . . . 115

Turning off logging . . . . . . . . . . . . 30Using /active to troubleshoot . . . . 86Worry threshold clauses . . . . . . . . 32

New Features in V7 . . . . . . . . . . . . . . . . . . 9Overview . . . . . . . . . . . . . . . . . . . . . 7, 8, 11Possible uses . . . . . . . . . . . . . . . . . . . . 7, 21

Locating fragmented files . . . . . . . 21Locating inactive files . . . . . . . . . 21Locating wasted space . . . . . . . . . 21

Privileges Required . . . . . . . . . . . . . . . . 160Qualifiers

/ace . . . . . . . . . . . . . . . . . . . . . . . . 84/active . . . . . . . . . . . . . . . . . . . . . . 86/all . . . . . . . . . . . . . . . . . . . . . . . . 87/allocated . . . . . . . . . . . . . . . . . . . 88/backup . . . . . . . . . . . . . . . . . . . . . 89/before . . . . . . . . . . . . . . . . . . . . . 90/broadcast . . . . . . . . . . . . . . . . . . . 91/console . . . . . . . . . . . . . . . . . . . . 92/convert . . . . . . . . . . . . . . . . . . . . . 93/created . . . . . . . . . . . . . . . . . . . . . 94/current . . . . . . . . . . . . . . . . . . . . . 95/data_file . . . . . . . . . . . . . . . . . . . 96/dcl . . . . . . . . . . . . . . . . . . . . . . . . 97/dir_collect . . . . . . . . . . . . . . . . . . 98/dir_file . . . . . . . . . . . . . . . . . . . . 99/disk . . . . . . . . . . . . . . . . . . . . . . 100/event . . . . . . . . . . . . . . . . . . . . . 102/exception . . . . . . . . . . . . . . . . . . 105/expired . . . . . . . . . . . . . . . . . . . 106/File . . . . . . . . . . . . . . . . . . . . . . 107/flags . . . . . . . . . . . . . . . . . . . . . . 108/fragments . . . . . . . . . . . . . . . . . . 109/indent . . . . . . . . . . . . . . . . . . . . . 110/interval . . . . . . . . . . . . . . . . . . . 111/large_change . . . . . . . . . . . . . . . 112/level . . . . . . . . . . . . . . . . . . . . . 113/list . . . . . . . . . . . . . . . . . . . . . . . 114/log . . . . . . . . . . . . . . . . . . . . . . . 115/mail . . . . . . . . . . . . . . . . . . . . . . 116/match . . . . . . . . . . . . . . . . . . . . . 117/maximum . . . . . . . . . . . . . . . . . . 118/minimum . . . . . . . . . . . . . . . . . . 119/modified . . . . . . . . . . . . . . . . . . 120/monitor . . . . . . . . . . . . . . . . . . . 121

/near_quota . . . . . . . . . . . . . . . . . 122/num_files . . . . . . . . . . . . . . . . . . 123/Organization . . . . . . . . . . . . . . . 124/output . . . . . . . . . . . . . . . . . . . . . 125/owner . . . . . . . . . . . . . . . . . . . . 126/panic . . . . . . . . . . . . . . . . . . . . . 127/period . . . . . . . . . . . . . . . . . . . . 129/previous . . . . . . . . . . . . . . . . . . . 130/protection . . . . . . . . . . . . . . . . . 131/quota_collect . . . . . . . . . . . . . . . 133/rate . . . . . . . . . . . . . . . . . . . . . . 134/report . . . . . . . . . . . . . . . . . . . . . 135/reset . . . . . . . . . . . . . . . . . . . . . . 137/sequence . . . . . . . . . . . . . . . . . . 138/show . . . . . . . . . . . . . . . . . . . . . 139/since . . . . . . . . . . . . . . . . . . . . . 140/size . . . . . . . . . . . . . . . . . . . . . . 141/sort . . . . . . . . . . . . . . . . . . . . . . 142/start . . . . . . . . . . . . . . . . . . . . . . 143/statistics . . . . . . . . . . . . . . . . . . . 144/status . . . . . . . . . . . . . . . . . . . . . 145/stop . . . . . . . . . . . . . . . . . . . . . . 146/summary . . . . . . . . . . . . . . . . . . 147/Title . . . . . . . . . . . . . . . . . . . . . . 148/type . . . . . . . . . . . . . . . . . . . . . . 149/uic_collect . . . . . . . . . . . . . . . . . 150/uic_file . . . . . . . . . . . . . . . . . . . 151/unused . . . . . . . . . . . . . . . . . . . . 152/usage . . . . . . . . . . . . . . . . . . . . . 153/used . . . . . . . . . . . . . . . . . . . . . . 154/value . . . . . . . . . . . . . . . . . . . . . 155/version . . . . . . . . . . . . . . . . . . . . 156/worry . . . . . . . . . . . . . . . . . . . . . 157command line overview . . . . . . . . 74for monitor commands . . . . . . . . . 79list of valid . . . . . . . . . . . . . . . 82, 83reference section . . . . . . . . . . . 73, 81Selection criteria for interactive

reports . . . . . . . . . . . . . . . 80syntax . . . . . . . . . . . . . . . . . . . . . . 81

RASharing Data Collection with . . . . 15

Recovering unused spaceUsing purge . . . . . . . . . . . . . . . . . . 34Using set file /truncate . . . . . . . . . 35

Using version limits . . . . . . . . . . . 34Release Notes . . . . . . . . . . . . . . . . . . . . . . . 9Report, size . . . . . . . . . . . . . . . . . . . . . . . . 21Report, tree

controlling indent . . . . . . . . . . . . 110Reports

Adding your own title . . . . . . . . . 148Directing report to a file . . . . . . . 125Finding files by file organization

. . . . . . . . . . . . . . . . . . . . 124Including DCL command used to

generate report . . . . . . . . . 70Providing your own title . . . . . . . 148Requesting statistics on report . . 144Resources needed to run . . . . . . . . 72specify large_change percentage

. . . . . . . . . . . . . . . . . . . . 112Specifying the sort order . . . . . . . 142specifying UIC format for reports

. . . . . . . . . . . . . . . . . . . . 149Reports, ACE . . . . . . . . . . . . . . . . . . . . . . 25

By access control entries . . . . . . . 25using AND or OR for ACE or

Protections . . . . . . . . . . . . 25Reports, Capacity

Controlling the type of usage reported. . . . . . . . . . . . . . . . . . . . 153

default shows all disks . . . . . . . . 100Qualifiers . . . . . . . . . . . . . . . . . . . 76reference section . . . . . . . . . . . 48, 49showing number of files . . . . . . . 139specify near_quota amount . . . . . 122Specifying change rate . . . . . . . . 134Specifying current date . . . . . . . . . 95specifying disk . . . . . . . . . . . . . . 100specifying levels for directory report

. . . . . . . . . . . . . . . . . . . . 113specifying maximum change rate

. . . . . . . . . . . . . . . . . . . . 118specifying minimum change rate

. . . . . . . . . . . . . . . . . . . . 119specifying previous date . . . . . . . 130specifying the period . . . . . . . . . 129Summarizing all disks into one report

. . . . . . . . . . . . . . . . . . . . 147

Reports, CurrentControlling the type of usage reported

. . . . . . . . . . . . . . . . . . . . 153default shows all disks . . . . . . . . 100Qualifiers . . . . . . . . . . . . . . . . . . . 77Reference section . . . . . . . . . . 43-47showing number of files . . . . . . . 139Showing only exceptional changes

. . . . . . . . . . . . . . . . . . . . 105specify near_quota amount . . . . . 122Specifying current date . . . . . . . . . 95specifying disk . . . . . . . . . . . . . . 100specifying levels for directory report

. . . . . . . . . . . . . . . . . . . . 113specifying previous date . . . . . . . 130Summarizing all disks into one report

. . . . . . . . . . . . . . . . . . . . 147Reports, Directory sequence

reference section . . . . . . . . . . . 50-52Reports, Large Files

Controlling number of files included. . . . . . . . . . . . . . . . . . . . 123

Reports, large_filesSpecifying how many files to include

. . . . . . . . . . . . . . . . . . . . 123Reports, Off-line

reference section . . . . . . . . . . . . . . 55Reports, On-line

generating list of files found . . . . . 97Interactive report types . . . . . . . . . 80Selection criteria . . . . . . . . . . . . . 80specifying disk . . . . . . . . . . . . . . 100

Reports, protection . . . . . . . . . . . . . . . . . . 23using AND or OR for ACE or

Protections . . . . . . . . . . . . 23Reports, Size

File versions report . . . . . . . . . . . 53Files report . . . . . . . . . . . . . . . . . . 53Large files report . . . . . . . . . . . . . 53reference section . . . . . . . . . . . . . . 53

Reports, trace . . . . . . . . . . . . . . . . . . . 87, 99Reports, tree

Explained . . . . . . . . . . . . . . . . . . . 27specifying levels to report . . . . . 113specifying UIC file . . . . . . . . . . . 151

Reports, UnauthorizedReference section . . . . . . . . . . . . . 54

Saiga SystemsContacting . . . . . . . . . . . . . . . . . . 162

Shadow sets . . . . . . . . . . . . . . . . . . . . . . . 64SYSUAF

Adding new accounts . . . . . . . . . . 57Logical name . . . . . . . . . . . . . . . . 70Updating account names . . . . . . . . 57Updating owner names . . . . . . . . . 58VDM and the . . . . . . . . . . . . . . . . . 56

Techical SupportContacting . . . . . . . . . . . . . . . . . . . 20

Technical Support . . . . . . . . . . . . . . . . 8, 162Troubleshooting . . . . . . . . . . . . . 17-20, 159

Account to run VDM under . . . . . 161Adequate resource quotas . . . . . . 161Adequate resources . . . . . . . . . . 161Checking your license . . . . . . . . . 162Command Definition . . . . . . . 18, 160Contacting Technical Support . . . 162Correcting problems found by VDM

. . . . . . . . . . . . . . . . . . . . . 39Disk space . . . . . . . . . . . . . . . . . . 19File access privileges . . . . . . . . . . 19Getting file read/reported information

. . . . . . . . . . . . . . . . . . . . 144Getting monitor status . . . . . . . . . 145License . . . . . . . . . . . . . . . . . . . . . 20Logicals names . . . . . . . . . . . . . . . 17Monitor . . . . . . . . . . . . . . . . . . . . . 39Privileges needed . . . . . . . . . . . . . 18Privileges Required . . . . . . . . . . 160Resources . . . . . . . . . . . . . . . . . . . 19Resources required by monitor . . . 38System crashes and VDM . . . . . . 161Verifying Logical Names . . . . . . 159

UIC formatspecifying for reports . . . . . . . . . 149

Uninstalling . . . . . . . . . . . . . . . . . . . . . . . 175VDM

uses Analyze /Disk . . . . . . . . . . . . 63VDM components

Go directory utility . . . . . . . . . . . . 11Monitor . . . . . . . . . . . . . . . . . . . . . 11

Off-line report generator . . . . . . . . 11On-line report generator . . . . . . . . 11

VDM$ERROR_HANDLER . . . . . . . . . . . 70VDM$KEEP . . . . . . . . . . . . . . . . . . . . . . . 70VDM$NOCONVERT . . . . . . . . . . . . . . . . 69VDM$SHOW_COMMAND . . . . . . . . . . . 70VDM$USE_DISK_NAME . . . . . . . . . . . . 70VDM_CDU . . . . . . . . . . . . . . . . . . . . . . . . 69VDM_COM . . . . . . . . . . . . . . . . . . . . . . . 69VDM_DAT . . . . . . . . . . . . . . . . . . . . . . . . 69VDM_DOC . . . . . . . . . . . . . . . . . . . . . . . . 69VDM_EXE . . . . . . . . . . . . . . . . . . . . . . . . 69VDM_LOG_FILE . . . . . . . . . . . . . . . . . . . 69VDM_PERM_DATA . . . . . . . . . . . . . . . . 69Version limits . . . . . . . . . . . . . . . . . . . . . . 34Version Number

Determining VDM . . . . . . . . . . . 156Volume sets . . . . . . . . . . . . . . . . . . . . . . . . 64

Command Summary

This page provide a quick reference guide to VDM commands that can be used at the DCLcommand level.

Commands used to collect/modify usage data

VDM/UIC_COLLECT Collect UIC data for later analysis/DISK=()

VDM/DIR_COLLECT Collect directory data for later analysis/DISK=()

VDM/QUOTA_COLLECT Update quotas for later analysis/DISK=()

VDM/RESET Reset minimum, maximum and/or average files in the specified data files/DATA_FILE=data_file_spec/VALUE=value_spec

VDM/REPORT=FILES Special files report that is generated during data collection or by usingthe special VDM_COM:FILE_REPORT.COM

Commands used to report previously collected data

VDM/REPORT=CAPACITY Generate capacity planning report/CURRENT=current_date/DISK=()/PERIOD=n/LEVEL=n/MAXIMUM=n/MINIMUM=n/OUTPUT=file_specification/PREVIOUS=previous_date/RATE=n/SIZE=n/SEQUENCE=(username|uic|account|owner|group|directory|disk)/SUMMARY/USAGE=x

VDM/REPORT=CURRENT Generate current usage report/CURRENT=current_date

/DISK=()/EXCEPTION/LARGE_CHANGE=n/LEVEL=n/NEAR_QUOTA=n/OUTPUT=file_specification/PREVIOUS=previous_date/SEQUENCE=(username|uic|account|owner|group|directory|disk|detail)/SIZE=n/SUMMARY/USAGE=x

VDM/REPORT=TREE/DISK=()/INDENT/LEVEL=n

Reports that do not depend on previously collected data

VDM/REPORT=(ACE|LARGE_FILES|PROTECTION|SIZE)/ACE=(Access Control Entry)/ALLOCATED=n|n:n|:n|n:/BACKUP /BEFORE=date_range OR /SINCE=date_range/CREATED /BEFORE=date_range OR /SINCE=date_range/DCL/DISK=()/EXPIRED /BEFORE=date_range OR /SINCE=date_range/FILE=filespec/FLAGS=flags/FRAGMENTS=n|n:n|:n|n:/MATCH=AND|OR/MODIFIED /BEFORE=date_range OR /SINCE=date_range/NUM_FILES=n/ORGANIZATION=SEQUENTIAL|INDEXED|RELATIVE/OUTPUT=filespec/OWNER=UIC/PROTECTION=(protection entry)/SIZE=n|n:n|:n|n:/STATISTICS/TITLE=”report title”/TYPE=ASCII|NUMERIC/UNUSED=n|n:n|:n|n:/USED=n|n:n|:n|n:

VDM/REPORT=UNAUTHORIZED/DISK=()/TITLE=”report title”/TYPE=ASCII|NUMERIC

No other qualifiers can be present.

HELP VDM Access VDM help if installed into system help library.

HELP @VDM Access VDM help if installed into user help library.

VDM/MONITOR commands

VDM/MONITOR/START Start the VDM/MONITOR program/START can only be issued once. If VDM/MONITOR is already running, /START results in anerror message. The other qualifiers can be issued at any time.

/ACTIVE Submit cleanup procedures/BROADCAST Send message to users/CONSOLE Log activities to central operator/DISK=DEFAULT Use to modify default disk record/DISK=(device_name[,...]) Specify disk drives/INTERVAL=minutes Set interval between free space checks/LIST=filename List VDM/MONITOR parameters/LOG Close log file and start a new one/MAIL=username/distribution list Define users to receive mail messages/PANIC=(threshold_clause) Define second free space threshold/WORRY=(threshold_clause) Define first free space threshold

/NOACTIVE Stop submission of procedures/NOBROADCAST Stop message broadcast to users/NOCONSOLE Stop logging activity to the console/NODISK=(device_name[,...]) Remove disk from list to be checked/NOLOG Stop logging activity to the log file/NOMAIL Don't send mail messages

VDM/MONITOR/STOP Stop the VDM/MONITOR program.

HELP VDM/MONITOR Access the on-line help information.

GO commands

GO Display a list of sub-directoriesGO directory_spec Change to a new directoryGO .directory_spec Change to a new sub-directoryGO disk_drive: Change to a new sub-directoryGO node_name:: Change to a new sub-directoryHELP GO Access the on-line help information

GO/HOME Go back to sys$login directory*GO/POP Go to previous directory*GO/TOP Go to highest directory level in current directory*GO/UP Go up one directory level*GO/DISK Display a directory tree for the current drive*

*Most Go users create one word symbols for these commands such as home, pop, top, up andtree. For examples see the commands procedures GO_1.COM, GO_2.COM and GO_3.COM inthe VDM_COM directory.

Documents

VDM V7 - Saigasaiga.com/ftp/saiga/cohort30/vdm70u.pdf · 2012-03-26 · VDM V7.0 OpenVMS Disk Manager by Saiga Systems Quick Links New Features of Version 7 9 Common Uses of VDM 21