Selects or rejects records for interactive sessions at the specified terminals.
/TERMINAL= ([-]terminal_name[,...])
The /TERMINAL qualifier uses the value of the terminal name field to select records for processing. This field is present in all records except file backward link and file forward link records. For records that contain information about interactive sessions, this field contains the name of the terminal associated with the session.The /TERMINAL qualifier selects only records that have the specified values in the terminal name field. If you precede the values with a minus sign, it selects all records except those with the specified values.
Give the terminal name as the standard device name and include the colon (:).
Example
$ ACCOUNTING /TERMINAL=TTB3:
This example processes the file SYS$MANAGER:ACCOUNTNG.DAT. It produces a brief report of all records for interactive sessions at the terminal TTB3.
Specifies the title shown on the first line of a summary report.
/TITLE= title
The /TITLE qualifier specifies the title shown in the center of the first line of summary reports. The title is truncated if it is too long. For reports displayed on your screen, the title is truncated if it is longer than (W--56) characters, where W is the width (in characters) of your screen.
Example
$ ACCOUNTING /SUMMARY=IMAGE /TITLE="June Accounting Report"
This example processes the file SYS$MANAGER:ACCOUNTNG.DAT. It produces a summary report that shows the number of times each image was executed. The title "June Accounting Report" appears at the top of the report.
Selects or rejects the specified types of record.
/TYPE= ([-]record_type[,...])
record_type[,...]
Specifies the types of record that you want to select or reject. Table 2-5 shows the keywords available.
Table 2-5 Types of Record in an Accounting File Keyword Type of Record Description of Record FILE FILE_BL File backward link. This is the first record in the accounting file. It is logged when the file is created, and contains the name of the previous accounting file. FILE_FL File forward link. This is the last record in the file. It is logged when the file is closed, and contains the name of the next accounting file. IMAGE IMAGE Image termination. It contains details of the resources used by the image. LOGFAIL LOGFAIL Failed attempt to log in. It contains details of the resources used by the login attempt. Print job termination. It contains details of the resources used by the print job. PROCESS PROCESS Process termination. It contains details of the resources used by the process. Note that this includes the resources used by the images executed by that process. SYSINIT SYSINIT System booted. It contains details of resources used to boot the system. UNKNOWN Record not recognized as one of the other types in this table. USER USER Record logged by a program calling the $SNDJBC system service to send an accounting message.
All records in an accounting file contain a type field that contains the type of the record.The /TYPE qualifier selects the specified types of record. If you precede the list with a minus sign, it selects all records except those specified.
See also the /PROCESS qualifier, which selects or rejects records for particular types of process.
$ ACCOUNTING /TYPE=PRINT
$ ACCOUNTING /TYPE=-PRINT
Selects or rejects records for the specified UICs.
/UIC= ([-]uic[,...])
The /UIC qualifier uses the value of the UIC field to select records for processing. This field is present in all records except file backward link and file forward link records. It contains the value [SYSTEM] for login failure records where the user did not give a valid user name.The /UIC qualifier selects only records that have the specified values in the UIC field. If you precede the values with a minus sign, it selects all records except those with the specified values.
You can specify the UIC in numeric or alphanumeric format, and can use the asterisk (*) wildcard character.
Example
$ ACCOUNTING /UIC=([360,*],[ADMIN,COTTON])
This example processes the file SYS$MANAGER:ACCOUNTNG.DAT. It produces a brief report of all records for users in group number 360 or users whose UIC is [ADMIN,COTTON].
Selects or rejects records for the specified user names.
/USER= ([-]user name[,...])
The /USER qualifier uses the value of the user name field to select records for processing. This field is present in all records except file backward link and file forward link records. It contains the value <login> for login failure records where the user did not give a valid user name.The /USER qualifier selects only records that have the specified values in the user name field. If you precede the values with a minus sign, it selects all records except those with the specified values.
Examples
$ ACCOUNTING /USER=SMITH
$ ACCOUNTING /USER=(-SMITH,JONES)
By using ANALYZE/DISK_STRUCTURE to identify and delete lost files and files marked for deletion, you can reclaim disk space.
ANALYZE/DISK_STRUCTURE performs the verification of a volume or volume set in eight distinct stages. During these stages, ANALYZE/DISK_STRUCTURE collects information used in reporting errors or performing repairs. However, ANALYZE/DISK_STRUCTURE repairs volumes only when you specify the /REPAIR qualifier. For a complete description of each of the eight stages, and an annotated example of an ANALYZE/DISK_STRUCTURE session, refer to Appendix D.
You can invoke the Analyze/Disk_Structure utility to operate in any of the following three modes:
By default, ANALYZE/DISK_STRUCTURE reports errors, but does not make repairs. For example, use the following command to report all errors on device DBA1:
$ ANALYZE/DISK_STRUCTURE DBA1:
When you issue this command, ANALYZE/DISK_STRUCTURE runs through eight stages of data collection, then, by default, prints a list of all errors and lost files to your terminal. One type of problem that ANALYZE/DISK_STRUCTURE locates is an invalid directory backlink; a backlink is a pointer to the directory in which a file resides. If your disk has a file with an invalid directory backlink, ANALYZE/DISK_STRUCTURE displays the following message and the file specification to which the error applies:
%VERIFY-I-BACKLINK, incorrect directory back link [SYSEXE]SYSBOOT.EXE;1
To instruct ANALYZE/DISK_STRUCTURE to repair the errors that it detects, use the /REPAIR qualifier. For example, the following command reports and repairs all errors on the DBA1 device:
$ ANALYZE/DISK_STRUCTURE DBA1:/REPAIR
To select which errors ANALYZE/DISK_STRUCTURE repairs, use both the /REPAIR and /CONFIRM qualifiers:
$ ANALYZE/DISK_STRUCTURE DBA1:/REPAIR/CONFIRM
When you issue this command, ANALYZE/DISK_STRUCTURE displays a description of each error and prompts you for confirmation before making a repair. For example, the previous command might produce the following messages and prompts:
%VERIFY-I-BACKLINK, incorrect directory back link [SYS0]SYSMAINT.DIR;1
Repair this error? (Y or N): Y
%VERIFY-I-BACKLINK, incorrect directory back link [SYSEXE]SYSBOOT.EXE;1]
Repair this error? (Y or N): N
Consider running ANALYZE/DISK_STRUCTURE twice for each volume. First, invoke the utility to report all errors. Evaluate the errors and decide on an appropriate action. Then invoke the utility again with the /REPAIR qualifier to repair all errors, or with the /REPAIR and /CONFIRM qualifiers to repair selected errors.
For message descriptions, use the online Help Message (MSGHLP) utility or refer to the OpenVMS system messages documentation.
A lost file is a file that is not linked to a directory. Under normal circumstances, files do not become lost. However, files occasionally become lost because of disk corruption, hardware problems, or user error. For example, in cleaning up files and directories, you might inadvertently delete directories that still point to files. When you delete a directory file (a file with the file type .DIR) without first deleting its subordinate files, the files referred to by that directory become lost files. Though lost, these files remain on the disk and consume space.
When you run ANALYZE/DISK_STRUCTURE specifying the /REPAIR qualifier, the utility places lost files in SYSLOST.DIR.
For example, to report and repair all errors and lost files found on the device DDA0, issue the following command:
$ ANALYZE/DISK_STRUCTURE/REPAIR/CONFIRM DDA0:
If it discovers lost files on your disk, ANALYZE/DISK_STRUCTURE issues messages similar to those that follow:
%VERIFY-W-LOSTHEADER, file (16,1,1) []X.X;1 not found in a directory %VERIFY-W-LOSTHEADER, file (17,1,1) []Y.Y;1 not found in a directory %VERIFY-W-LOSTHEADER, file (18,1,1) []Z.Z;1 not found in a directory %VERIFY-W-LOSTHEADER, file (19,1,1) []X.X;2 not found in a directory %VERIFY-W-LOSTHEADER, file (20,1,1) []Y.Y;2 not found in a directory %VERIFY-W-LOSTHEADER, file (21,1,1) []Z.;1 not found in a directory %VERIFY-W-LOSTHEADER, file (22,1,1) []Z.;2 not found in a directory %VERIFY-W-LOSTHEADER, file (23,1,1) LOGIN.COM;163 not found in a directory %VERIFY-W-LOSTHEADER, file (24,1,1) MANYACL.COM;1 not found in a directory
All lost files in this example are automatically moved to SYSLOST.DIR.
When you initialize a volume, the initialize operation might not erase old home blocks. These are blocks that were created by previous initialize operations. If a volume that has old home blocks is damaged, you may not be able to recover the volume without erasing the blocks.
You can erase old home blocks manually by using the /HOMEBLOCKS qualifier on the ANALYZE/DISK_STRUCTURE command as follows:
$ ANALYZE/DISK_STRUCTURE/REPAIR/HOMEBLOCKS
Note that this operation can take up to 30 minutes to complete.
By default, the Analyze/Disk_Structure utility directs all output to your terminal. If you prefer, you can use the /LIST qualifier to generate a file containing the following information for each file on the disk:
To generate a disk usage accounting file, use the /USAGE qualifier. The first record of the file, called the identification record, contains a summary of disk and volume characteristics. The identification record is followed by a series of summary records; one summary record is created for each file on the disk. A summary record contains the owner, size, and name of the file.
For more information on the disk usage accounting file, see Appendix E.
The Analyze/Disk_Structure utility checks the readability and validity of Files--11 Structure Level 1 and Structure Level 2 disk volumes, and reports errors and inconsistencies.You can detect most classes of errors by invoking the utility once and using its defaults.
ANALYZE/DISK_STRUCTURE device-name:[/qualifier]
device-name
Specifies the disk volume or volume set to be verified. If you specify a volume set, all volumes of the volume set must be mounted as Files--11 volumes. For information on the Mount utility, refer to the MOUNT documentation in this manual.
Use the following command to invoke the utility:ANALYZE/DISK_STRUCTURE device-name: /qualifiersTo terminate an ANALYZE/DISK_STRUCTURE session, press Ctrl/C or Ctrl/Y while the utility executes. You cannot resume a session by using the DCL command CONTINUE.
By default, ANALYZE/DISK_STRUCTURE directs all output to your terminal. Use the /USAGE or /LIST qualifiers to direct output to a file.
To repair a disk effectively, you must have read, write, and delete access to all files on the disk. To effectively scan a disk (/NOREPAIR), you must have read access to all files on the disk.
For a complete explanation of file access, see the OpenVMS Guide to System Security.
You can safely use ANALYZE/DISK_STRUCTURE on a disk that is concurrently being used for other file operations. If you specify /REPAIR, the utility locks the volume before performing any operations; this blocks volume modification. Because other users cannot create, delete, extend, or truncate files, repair operations are unimpeded and the volume is left in a consistent state.
If you specify /NOREPAIR, the volume is not locked; the utility does not attempt to write to the disk. However, if users perform file operations while you run the utility, you may receive error messages that incorrectly indicate file damage. To avoid this problem, Digital recommends that you run ANALYZE/DISK_STRUCTURE when the disk is in a quiescent state.
Qualifier | Description |
---|---|
/CONFIRM | Determines whether ANALYZE/DISK_STRUCTURE prompts you to confirm each repair |
/HOMEBLOCKS | Erases damaged home blocks on an initialized volume. |
/LIST[=filespec] | Determines whether ANALYZE/DISK_STRUCTURE produces a listing of the index file |
/OUTPUT[=filespec] | Specifies the output file to which ANALYZE/DISK_STRUCTURE writes the disk structure errors |
/READ_CHECK | Determines whether ANALYZE/DISK_STRUCTURE performs a read check of all allocated blocks on the specified disk |
/RECORD_ATTRIBUTES | Determines whether ANALYZE/DISK_STRUCTURE repairs files containing erroneous settings in the record attributes section of their associated file attribute block (FAT) |
/REPAIR | Determines whether ANALYZE/DISK_STRUCTURE repairs errors that are detected in the file structure of the specified device |
/USAGE[=filespec] | Specifies that a disk usage accounting file should be produced, in addition to the other specified functions of ANALYZE/DISK_STRUCTURE |
Determines whether the Analyze/Disk_Structure utility prompts you to confirm each repair. If you respond with Y or YES, the utility performs the repair. Otherwise, the repair is not performed.
/CONFIRM
/NOCONFIRM
You can only use the /CONFIRM qualifier with the /REPAIR qualifier. The default is /NOCONFIRM.
Example
$ ANALYZE/DISK_STRUCTURE DBA0:/REPAIR/CONFIRM %VERIFY-I-BACKLINK, incorrect directory back link [SYS0]SYSMAINT.DIR;1 Repair this error? (Y or N): Y %VERIFY-I-BACKLINK, incorrect directory back link [SYSEXE]SYSBOOT.EXE;1 Repair this error? (Y or N): N
The command in this example causes the Analyze/Disk_Structure utility to prompt you for confirmation before performing the indicated repair operation.
Erases home blocks from a volume whose home blocks were not deleted during previous initialization operations.
/HOMEBLOCKS
You can only use the /HOMEBLOCKS qualifier with the /REPAIR qualifier. The operation can take 30 minutes to complete.
$ ANALYZE/DISK_STRUCTURE DBA0:/REPAIR/HOMEBLOCKS
The command in this example causes the Analyze/Disk_Structure utility to erase home blocks on DBA0.
Determines whether the Analyze/Disk_Structure utility produces a listing of the index file.
/LIST
[=filespec]/NOLIST
If you specify /LIST, the utility produces a file that contains a listing of all file identifications (FIDs), file names, and file owners. If you omit the file specification, the default is SYS$OUTPUT. If you include a file specification without a file type, the default type is .LIS. You cannot use wildcard characters in the file specification.The default is /NOLIST.
$ ANALYZE/DISK_STRUCTURE DLA2:/LIST=INDEX $ TYPE INDEX Listing of index file on DLA2: 31-DEC-1995 20:54:42.22 (00000001,00001,001) INDEXF.SYS;1 [1,1] (00000002,00002,001) BITMAP.SYS;1 [1,1] (00000003,00003,001) BADBLK.SYS;1 [1,1] (00000004,00004,001) 000000.DIR;1 [1,1] (00000005,00005,001) CORIMG.SYS;1 [1,1] . . . $
In this example, ANALYZE/DISK_STRUCTURE did not find errors on the device DLA2. Because the file INDEX was specified without a file type, the system assumes a default file type of .LIS. The subsequent TYPE command displays the contents of the file INDEX.LIS.
Specifies the output file to which the Analyze/Disk_Structure utility is to write the disk structure errors.
/OUTPUT[=filespec]
/[NO]OUTPUT[=filespec]
Specifies the output file for the disk structure errors. If you omit the /OUTPUT file specification, output is directed to SYS$OUTPUT. If /NOOUTPUT is specified, no disk structure errors are displayed. If the /CONFIRM qualifier is specified, output is forced to SYS$OUTPUT regardless of whether this qualifier is used.
Determines whether the Analyze/Disk_Structure utility performs a read check of all allocated blocks on the specified disk. When the Analyze/Disk_Structure utility performs a read check, it reads the disk twice; this ensures that it reads the disk correctly. The default is /NOREAD_CHECK.
/READ_CHECK
/NOREAD_CHECK
$ ANALYZE/DISK_STRUCTURE DMA1:/READ_CHECK
The command in this example directs ANALYZE/DISK_STRUCTURE to perform a read check on all allocated blocks on the device DMA1.
Determines whether the Analyze/Disk_Structure utility repairs files containing erroneous settings in the record attributes section of their associated file attribute block (FAT).
/RECORD_ATTRIBUTES
The /RECORD_ATTRIBUTES qualifier may be used with the /REPAIR qualifier. If attribute repair is enabled during the repair phase, erroneous bits will be cleared from a file's record attributes. This action may not correctly set a file's record attributes as it is beyond the scope of this utility to determine their correct values.It is recommended that system managers do not perform an attribute repair; instead they should notify the owners of the files about the inconsistencies and have the owners reset the files' attributes using the SET FILE/RECORD_ATTRIBUTES=({record-attributes}) command.
$ ANALYZE/DISK_SYS$SYSDEVICE: %ANALDISK-I-BAD_RECATTR, file (2930,1,1) [USER]ATTRIBUTES.DAT;13 file record format: Variable inconsistent file attributes: Bit 5 %ANALDISK-I-BAD_RECATTR, file (2931,1,1) [USER]ATTRIBUTES.DAT;14 file record format: Variable inconsistent file attributes: FORTRAN carriage control, Bit 5 %ANALDISK-I-BAD_RECATTR, file (2932,1,1) [USER]ATTRIBUTES.DAT;15 file record format: Variable inconsistent file attributes: Implied carriage control, Bit 5 %ANALDISK-I-BAD_RECATTR, file (2933,1,1) [USER]ATTRIBUTES.DAT;16 file record format: Variable inconsistent file attributes: Non-spanned, Bit 5 %ANALDISK-I-BAD_RECATTR, file (2934,1,1) [USER]ATTRIBUTES.DAT;17 file record format: Variable inconsistent file attributes: FORTRAN carriage control, Non-spanned, Bit 5
6048P004.HTM OSSG Documentation 26-NOV-1996 12:42:22.12
Copyright © Digital Equipment Corporation 1996. All Rights Reserved.