| Qualifiers |
| Depending on the qualifier, "x" can be an alphanumeric value, a numeric value, a file name, a device, a directory, a date or a specially formatted clause such as an access control entry. |
| /FILE Specify a file to be monitored |
| /FILE Specify a file selection criteria for reports |
| /NUM_FILES Specify how many files to include in the largest_files report |
| Specifies the ACE used to select files. The ACE matches the ACE specified in the file ACL. |
| When you specify this qualifier, specify at least one ACE entry. You can specify up to 64 ACE entries. If you specify an ACE more than once, VDM counts and uses only the first reference. If you specify more than one value, separate them with commas, and enclose the list in parentheses. |
| IDENTIFIER=identifier (required) |
| Specifies the identifier in the ACE used to select files. You can select alphanumeric characters or binary formats. You cannot select using wildcard characters. |
| When you specify this clause, specify one and only one identifier. |
| Specifies the access in the ACE used to select files. Use one or more of the following keywords: |
| READ the ACE allows the user to read the file |
| WRITE the ACE allows the user to write the file |
| EXECUTE the ACE allows the user to execute the file |
| DELETE the ACE allows the user to delete the file |
| CONTROL the ACE allows the user to change the file access |
| NONE, "" 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 up to 5 access types. If you specify an access more than once, VDM counts and uses only the first reference. If you specify more than one value, separate them with "+" and enclose the list in double quotes ("). VDM will select the record if the identifier has one or more of the access codes specified. You cannot specify NONE in conjunction with any other type of access. When you specify a list, the file will be selected if it matches one or more of the elements in the list based on the setting of the /MATCH qualifier. |
| Generate a report for files with the ACE ENGR and Read or Write access in their ACL. |
| Generate a report for all files with the ACE "ACC" that users with that identifier are denied access to. |
| /MONITOR/ACTIVE |
| None |
| Stop submission of procedures. The monitor will continue to run normally. |
| "-" |
| 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 blocks specifies the number of blocks allocated to the file. Specify the allocated blocks as an integer. An allocated value of 0 indicates the file contains no data. The allocated blocks matches the allocated blocks specified in the file header. |
| Specify n:m to select an inclusive range of allocated blocks using the relationship (i>=n AND i<=m). Specify n to select a specific number of allocated blocks. Specify n: to select a number of allocated blocks and all higher values. Specify :m to select a number of allocated blocks and all lower values. |
| This is not a list; you must specify one and only one of the selections. |
| Generate a report for all files with 5,000 or more allocated blocks. |
| Generate a report for zero-length files. |
| Generate a report of all files which not been backed up since February 25, 1994, or have never been backed up. |
| Generate a report for all files which have been backed up today. |
| date |
| Specifies the date for file selection. Enter the date in the format "15_JUN_94". |
| TODAY |
| Specifies today's date. |
| YESTERDAY |
| Specifies yesterday's date. |
| TOMORROW |
| Specifies tomorrow's date. |
| Generate a report of all files which have expired before February 25, 1994. |
| Generate a report of all files which not been backed today or have never been backed up. |
| /MONITOR/BROADCAST |
| None |
| Stop broadcasting messages to users when the panic threshold is exceeded on a disk. |
| /MONITOR/CONSOLE |
| None |
| Stop the monitor's actions from being logged to the system console. |
| /CONVERT |
| None |
| Converts all VDM data files from V4.0 or V5.0 to V6.0. If you have already done V6.0 data collections be sure and answer "NO" when prompted if files from those data collections should be converted. |
| Generate a report of all files which have been created since February 25, 1994 |
| Generate a report for all files which were created today. |
| date |
| Specifies the date of the current column on the report. Enter the date in the format "15_JUN_94". |
| Generate a current report using July 4th as the current date. |
| Generate a capacity report in UIC sequence using the most recent data collection date (normally yesterday) as the current date. |
| UIC |
| Specifies that the UIC file is to have a value reset. |
| DIR |
| Specifies 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. |
| Reset the average value in the UIC file only. |
| Reset the average value in the both the UIC file and the directory file. |
| File-spec |
| Specifies the name of the file in which selected filenames are recorded. If you omit the file-spec entirely, VDM will use the file specification "FILE_LIST.DAT" in your current directory. You cannot specify a node name. If you omit the device, VDM will default to your current device. If you omit the directory, VDM will default to your current directory. If you omit a file name, VDM will default to the file name "FILE_LIST". If you omit a file extension, VDM will default to ".DAT". If you want to store the file in the VDM directory, specify the logical "VDM_DAT: in front of the filename. If VDM can't create the file, it will report an error. |
| Generate a report showing all files with the ACE "ENGR" in their ACL and write their names in the file FILE_LIST.DAT in the VDM directory. |
| Generate a report showing all files with any protection through WORLD and write their names in the file PROTECTION_CHK.DAT in your current directory. |
| /DIR_COLLECT |
| None |
| Collect directory information for disk DRA1:. |
| DEFAULT |
| Specifies 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 alphanumeric characters. 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 size reports, VDM will search your current default disk. You can specify up to 200 disk names. If you specify a disk name more than once, VDM counts and uses only the first reference. If you specify a logical name, VDM will translate it to a physical disk name but 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 checks all devices and will not collect data on secondary volume devices. |
| Generate a first level directory report for disk DUA1: and USER$DISK2: |
| Generate a report of all files with 5,000 or more allocated blocks on the disk DUA0:. |
| Generate a report of all files with 5 or less allocated blocks on the disk with the logical name SYS$SYSDEVICE. |
| Generate a capacity report for all disks that data has been collected on. |
| /MONITOR/EVENT=event_clause |
| The event clause consists of any valid combination of the following keywords and values. |
| When adding events TYPE must be specified. It defines the event type being added and controls which additional keywords are appropriate. The valid event types are: |
| Use BLOCKS to specify the number of disk blocks for a file size event. This keyword is only valid with TYPE=SIZE. If BLOCKS is omitted a file size event will added with the number of blocks specified in the default file event record. |
| COMMAND=file |
| Used COMMAND to specify the command procedure that should be submitted when a VDM monitor EVENT is true. This keyword can be used with all 4 event types. It must point to a valid DCL command procedure. Use QUEUE to specify which 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. |
| Use COMPARE when adding file size events to specify the type of compare that should be made. The event will then make that type of comparison for the file against the number of BLOCKS specified and take action when the condition is true. Valid comparisons are: |
| LESS take action when FILE is LESS than x BLOCKS in size |
| Use SIZE to control whether VDM is checking against the number of blocks allocated, used or unused by FILE. |
| Use messages to control how many times VDMs monitor will signal an event as true and submit the action procedure. MESSAGES can be specified with all four file event types. Each subsequent time that VDM checks a file event and determines it to be true VDM will take the appropriate action until it has reached MESSAGES=nn times. If MESSAGES is omitted the value from the default file event record will be used. |
| NODE=node name |
| Use NODE when running VDM in a cluster to control which node VDM actually checks for a file event on. If your cluster is sharing a common VDM monitor data file specifying a NODE will prevent an event from being signalled on every node in the cluster when it becomes true. If you omit node the value from the default file event record will be used. |
| QUEUE=queue name |
| Use QUEUE to specify which queue a file event should submit its COMMAND procedure to. Be sure to specify a valid queue that will execute on an appropriate node. If you omit QUEUE the value from the default file event record will be used. |
| SIZE=size type |
| Use SIZE to control which value VDM COMPAREs BLOCKS against. Valid choices for size type are: |
| To delete a file event from the VDM monitor database use /NOFILE=filename and /EVENT=(TYPE=filetype). |
| Remove the file changed event for the specified file. Any other events for this file such as size or absent file are not affected. |
| On node1 anytime HITMANs log file exceeds 4000 blocks used submit a command procedure to node1$batch that resets the log file. |
| Generate a current report that shows only the users with a change in usage greater that 24 percent or that are near their quota if disk quota information is being used. |
| Generate a report of all files which have expired since February 25, 1994, or are not yet expired. |
| Generate a report for all files which expire today or are not yet expired. |
| Generate a report for all files which will expire between today and December 31, 1994. |
| /FILE=disk:[directory]filename.type file event usage |
| /FILE=[directory]filename.type selection criteria usage |
| This command creates a VDM event that will send mail to SYSOP anytime VDM detects that the system startup file has been modified. |
| This event monitors HITMANs log file and any time it has allocated more than 2500 blocks, submits a batch job that resets and purges the log file. |
| This command will generate a file protection report for all the subdirectories and files under the account directory. /output has been added to direct the report to a file. |
| "-" |
| Specifies that all files are selected except those matching any specified flags. This operator applies to the entire list, not just to the first element. Files with no flags will be included (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 match the 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. If you specify more than one flag, separate them with commas, and enclose the list in parentheses. When you specify a list, the account will be selected if it matches one or more of the elements in the list. |
| Generate a report of all files which will not be backed up regardless of activity. |
| "-" |
| 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 the number of separate extents assigned to the file. Specify the file fragmentation as an integer. 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>=n AND i<=m). Specify n to select a specific file fragmentation. Specify n: to select a number of file fragments and all higher values. Specify :m to select a number of file fragments and all lower values. |
| This is not a list; you must specify one and only one of the selections. |
| Generate a report of all files with 5 or more fragments. |
| Generate a tree report indenting each sub-directory 8 characters. |
| number-of-minutes |
| Specifies the number of minutes between checks for free space and disk errors. |
| Specifies that drives DISK1$ and DISK2$ are to be checked every two minutes. |
| Generate a current report for all users with a 5% or greater increase in their usage are flagged. |
| Generate a current report showing only users with at least a 20% increase in their usage or that are near their quota. |
| Generate a current directory report for users showing the top two levels of directories. |
| Generate a current directory report for users showing the only the top 2 levels of directories on disk DUA0:. |
| Generate a directory tree showing five levels of directories for disk DUA0. |
| /MONITOR/LIST[=file-name] |
| "file-name" |
| The name of the file to write the output to. If it is omitted, "SYS$OUTPUT" is assumed. |
| username |
| Specifies the name of the user to receive the mail message. |
| distribution-list |
| Specifies the name of a text file containing the names of the users to receive the mail message. The filename must be preceded by the "@" character and the entire string enclosed in double quotes ("). The distribution file must conform to the rules for distribution files outlined in the OpenVMS Mail utility manual. |
| Send a mail message to user SYSTEM when the PANIC threshold is reached. |
| Send mail messages to all users in the file OPER.DIS when the PANIC threshold is reached. |
| OR (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. |
| AND |
| Specifies that the logical operation "AND" is to used when more than one entry is specified. 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 protection class is specified, an AND relationship is assumed. |
| Generate a report of files whose owners have either Read or Write access using default /MATCH value of "OR". |
| Generate a report of files where system has both Read and Write access. |
| Generate a report showing files which the ENGR identifier provides read, write and delete access to. |
| Generate a capacity report with a maximum growth rate of 5%. |
| Generate a capacity report with a default maximum growth rate of 25%. |
| Generate a capacity report with a minimum growth rate of 5% and a maximum of 8%. |
| Generate a capacity report with a minimum growth rate of -25%. |
| Generate a report of all files which have been modified since February 25, 1994 |
| Generate a report for all files which have been modified today. |
| Generate a report for all files which have not been modified this year (1994). |
| /MONITOR |
| None |