Name of the file currently being used to identify critical disk space and operations per second trap thresholds for individual disks. This file contains: disk name (required) percent full or number of free blocks (optional) operations per second (optional) The disk name may take the form of a physical disk name (including the leading underscore (_) and trailing colon (:)), a logical volume name, or, for shadowed disks, the name of the virtual unit. If two entries specify the same disk (one by physical name and the other by logical volume name), only the entry for the physcial disk name will be used for that disk. Once the disk usage exceeds the specified percent full or the number of free blocks drops below the specified free disk blocks, disk full (sDskFull) traps will begin to be sent. Disk busy (sDskOpSec) traps are sent if the number of operations per second exceeds the limit specified for this disk. The following are valid entries in the critical disk file: _ALPHA$DKA0:,blocks=652829 disk$alphasys,percent=99,ops=120 _DSA1:,ops=300 This file is associated with the system logical name COMTEK$SYSMGR_CRITDSK. Changing this variable redefines the COMTEK$SYSMGR_CRITDSK logical name. NM*SysMgr must be reinitialized (by setting the variable sCfgReinitSubagent to true) before a new critical disk file is used. If a set-request is performed on this variable and the specified file name does not exist, is not accessible by the subagent, or contains invalid data, the file name is not changed, an error is returned, and a sSwErr trap is generated describing the error. Set-requests: Take effect only after reinitialization (sCfgReinitSubagent) NOTE: To make changes to this value permanent across system reboots, the definition of this logical name must also be changed in the system startup procedures.