HELP ANALYZE — VMS 5.5-2H4
The ANALYZE commands invoke utilities to examine various components
of the VMS system. They perform the following functions:
o Invoke the Audit Analysis Utility to extract selective information
from the system security audit journal (see /AUDIT).
o Invoke the System Dump Analyzer (SDA) to examine the specified
dump file (see /CRASH_DUMP).
o Invoke the Analyze/Disk_Structure Utility to examine disk volumes
(see /DISK_STRUCTURE).
o Invoke the Errorlog Report Formatter to selectively report the
contents of an error log file (see /ERROR_LOG).
o Describe the contents of an image file or shareable image file
(see /IMAGE).
o Invoke the Bad Utility to find disk blocks that cannot be used to
store data (see /MEDIA).
o Describe the contents of an object file (see /OBJECT).
o Invoke the VMS Debugger for analysis of a process dump file
(see /PROCESS_DUMP).
o Analyze the internal structure of a VAX RMS file (see
/RMS_FILE).
o Invoke the SDA to examine the running system (see /SYSTEM).
The default analyze function is to examine object modules
(ANALYZE/OBJECT).
Additional information available:
/AUDIT/CRASH_DUMP/DISK_STRUCTURE/ERROR_LOG
/IMAGE/MEDIA/OBJECT/PROCESS_DUMP/RMS_FILE/SYSTEM
/AUDIT
Invokes the Audit Analysis Utility (ANALYZE/AUDIT) to selectively
extract information from the system security audit log file. The
/AUDIT qualifier is required. For a complete description of the
Audit Analysis Utility, including more information about the
ANALYZE/AUDIT command and its qualifiers, see the VMS Audit
Analysis Utility Manual.
Format:
ANALYZE/AUDIT [filespec[,...]]
Additional information available:
Parameters
filespec[,...] Specifies one or more security audit log files as input to be processed by the Audit Analysis Utility. If you specify more than one file, separate them with commas. If your current directory is the system manager directory and you omit the filespec parameter, data is processed from the default system security audit log file, SYS$MANAGER:SECURITY_AUDIT.AUDIT$JOURNAL. Wildcard characters are allowed in the file specification.
QUALIFIERS
Additional information available:
/BEFORE/BINARY/BRIEF/EVENT_TYPE/FULL/IGNORE
/INTERACTIVE/OUTPUT/PAUSE/SELECT/SINCE/SUMMARY
/BEFORE
/BEFORE[=time] /NOBEFORE Controls whether only those records dated earlier than the specified time are selected. Specify the time as an absolute time, delta time, or a combination of the two. Observe the syntax rules for date and time as described in the VMS DCL Concepts Manual.
/BINARY
/BINARY /NOBINARY (default) Controls whether output is a binary file. When /BINARY is specified, the output file, specified with the /OUTPUT qualifier, contains image copies of the selected input records. If you specify /NOBINARY or omit the qualifier, the output file contains ASCII records.
/BRIEF
/BRIEF (default) /NOBRIEF Controls whether a brief (one line per record) format is used in ASCII displays. Specify /FULL to display the full contents of each selected audit event record.
/EVENT_TYPE
/EVENT_TYPE=event-type[,...]
Indicates the classes of events that are selected. If you omit the
qualifier or specify /EVENT_TYPE=ALL, all event classes are
selected.
Specify any of the following event classes:
[NO]ACCESS [NO]ALL [NO]AUDIT
[NO]BREAKIN [NO]INSTALL [NO]LOGFAIL
[NO]LOGIN [NO]LOGOUT [NO]MOUNT
[NO]NETUAF [NO]RIGHTSDB [NO]SYSUAF
Specifying the negated form of an event class (for example, NOLOGFAIL)
excludes the specified event class from the audit analysis report.
/FULL
/FULL /NOFULL (default) Controls whether a full format is used in ASCII displays. If you specify /NOFULL or omit the qualifier, records are displayed in the brief format (/BRIEF).
/IGNORE
/IGNORE=criteria[,...] Controls whether records matching the specified criteria are excluded. See the /SELECT qualifier description for a list of the possible criteria to use with the /IGNORE qualifier.
/INTERACTIVE
/INTERACTIVE (default) /NOINTERACTIVE Controls whether interactive command mode is enabled when the Audit Analysis Utility is invoked. To interrupt the current report being displayed and enter interactive mode commands, press CTRL/C. Enter the HELP command at the COMMAND> prompt to obtain information about using interactive mode commands. Enter the CONTINUE command to leave interactive command mode and continue the audit analysis report or EXIT to terminate the session.
/OUTPUT
/OUTPUT[=filespec] /NOOUTPUT Specifies where to direct output from the VMS Audit Analysis Utility. If you omit the qualifier, selected ASCII records are output to SYS$OUTPUT. If you omit the file name and type, the default file name AUDIT.LIS is used. If the output is binary (/BINARY) and you omit the /OUTPUT qualifier, the binary information is output to the file AUDIT.AUDIT$JOURNAL.
/PAUSE
/PAUSE=seconds The /PAUSE qualifier can only be used with full format displays (/FULL) to specify the duration for each record displayed. By default, each record is displayed for a period of three seconds. A value of 0 results in a continuous display of audit records.
/SELECT
/SELECT=criteria[,...]
/NOSELECT
Controls whether only those records matching the specified
criteria are selected. If you omit the /SELECT qualifier or
specify /NOSELECT, all event records are selected.
The possible list of criteria that you may specify in the keyword
list are as follows:
ACCESS=(type,...) Specifies the type of object access upon
which the selection is based. It may be
any of: READ, WRITE, EXECUTE, DELETE, or
CONTROL.
ACCOUNT=(name,...) Specifies the account name upon which
selection is based. Full wildcarding
of the account name is allowed.
ALARM_NAME=(name,...) Specifies the alarm name upon which
selection is based. Full wildcarding
of the alarm name is allowed.
AUDIT_NAME=(name,...) Specifies the audit journal name upon
which selection is based. Full wild-
carding of the audit journal name is
allowed.
DEVICE_NAME=(name,...) Specifies the name of the device to be
used in the selection of event records.
Full wildcarding of the device name is
allowed.
DISMOUNT_FLAGS=(name,...) Specifies the names of the volume
dismounting flags upon which selection
is based. The available names are:
ABORT, CLUSTER, NOUNLOAD, and UNIT.
HOLDER=(keyword,...) Specifies the characteristics of the
(identifier) holder to be used in
selecting event records.
NAME=name Specifies the name of the
holder. Full wildcarding of
the name is allowed.
OWNER=value Specifies the owner (UIC)
of the holder.
IDENTIFIER=(attr,...) Specifies that some attribute of an
identifier should be used in selecting
event records.
ATTRIBUTE=name Specifies the name of the
particular attribute. The
available names are:
RESOURCE, DYNAMIC.
NAME=name Specifies the original name
of the identifier. Full
wildcarding of the name is
allowed.
NEW_NAME=name Specifies the new name of
the identifier. Full wild-
carding is allowed.
VALUE=value Specifies the original
value of the identifier.
NEW_VALUE=value Specifies the new value
of the identifier.
IMAGE_NAME=(name,...) Specifies the name of the image to be
used when selecting event records. Full
wildcarding of the image name is allowed.
INSTALL=(type,...) Specifies the type of installation event
to be considered when selecting event
records.
FILE=name Specifies the name of the
installed file. Full wild-
carding is allowed.
FLAGS=name Specifies the names of the
flags which correspond to
the INSTALL qualifiers.
(For example, OPEN corre-
sponds to /OPEN.)
PRIVILEGES=name Specifies the name of the
privileges with which the
file was installed.
LOCAL=(list,...) Specifies the characteristics of the
local (proxy) account to be used when
selecting event records.
USERNAME=name Specifies the name of the
local account used. Full
wildcarding of the name
is allowed.
LOGICAL_NAME=(name,...) Specifies the logical name of the volume
mounted (or dismounted) upon which selec-
tion is based. Full wildcarding of the
logical name is allowed.
MOUNT_FLAGS=(name,...) Specifies the names of the volume mount-
ing flags upon which selection is based.
The available names are:
CACHE=(NONE,WRITETHROUGH),CLUSTER,
DATACHECK=(READ,WRITE),FOREIGN,GROUP,
INITIALIZATION=(ALLOCATE,CONTINUATION),
INTERCHANGE,MESSAGE,NOASSIST,NOAUTO,
NODISKQ,NOHDR3,NOLABEL,NOWRITE,
OVERRIDE=(options[,...]),
ACCESSIBILITY,EXPIRATION,
IDENTIFICATION,SETID,LOCK,
LOCK,OWNER_IDENTIFIER
SHARE,SYSTEM
OBJECT=(keyword,...) Specifies which characteristics of an
object should be used in selecting event
records.
IDENTIFICATION=value Specifies a unique
object-id for the
object (currently,
only file-id is
supported).
NAME=name Specifies the name of the
object. Full wildcarding of
the name is allowed.
OWNER=value Specifies the owner (identi-
fier value) of the object.
TYPE=name Specifies the general object
type. Specify one of the
following:
FILE,
SYSTEM_GLOBAL_SECTION,
GROUP_GLOBAL_SECTION
PARENT=(list,...) Specifies which characteristics of the
parent process (when a subprocess causes
an event record to be generated) are
used in selecting event records.
IDENTIFICATION=value Specifies the parent
process PID.
NAME=name Specifies the name of
the parent process.
Full wildcarding of
the name is allowed.
OWNER=value Specifies the owner
(identifier value) of
the parent process.
USERNAME=name Specifies the username
of the parent process.
Full wildcarding of
the name is allowed.
PRIVILEGES_USED=(privs,...) Specifies the privileges of the process
to be used when selecting event records.
Specify any of the following privileges:
SYSPRV, BYPASS, GRPPRV, and READALL.
PROCESS=(list,...) Specifies the characteristics of the
process to be used when selecting event
records.
IDENTIFICATION=value Specifies the
process-id (PID) of
the process.
NAME=name Specifies the name of
the process. Full
wildcarding of the
process name is
allowed.
REMOTE=(list,...) Specifies that some characteristic of
the network request is to be used in
selecting event records.
IDENTIFICATION=value Specifies the
DECnet address.
NODENAME=name Specifies the
DECnet node name.
Full wildcarding
of the node name
is allowed.
USERNAME=name Specifies the
remote user name.
Full wildcarding
of the remote user
name is allowed.
STATUS=type Specifies the type of success status to
be used in selecting event records.
SUCCESSFUL Specifies a generic success
class
FAILURE Specifies a generic failure
class
CODE=value Specifies a specific
completion status.
SYSTEM=(list,...) Specifies the characteristics of the
system to be used in selecting event
records.
IDENTIFICATION=value Specifies the
(numeric) identi-
fication of the
system.
NAME=name Specifies the name
of the system.
TERMINAL=(name,...) Specifies that the name of the terminal
is to be used when selecting event
records. Full wildcarding of the terminal
name is allowed.
USERNAME=(name,...) Specifies the user name is to be used
when selecting event records. Full wild-
carding of the user name is allowed.
VOLUME_NAME=(name,...) Specifies that the name of the mounted
(or dismounted) volume is to be used in
selecting event records. Full wildcarding
of the volume name is allowed.
/SINCE
/SINCE[=time] /NOSINCE Controls whether only those records dated the same or later than the specified time are selected. You can specify an absolute time, delta time, or a combination of the two. Observe the syntax rules for date and time described in the VMS DCL Concepts Manual. If you specify /SINCE without the time, midnight of the current day is used.
/SUMMARY
/SUMMARY /NOSUMMARY (default) Specifies that a summary of the selected records be produced after all records are processed.
Examples
1. $ ANALYZE/AUDIT SYS$MANAGER:SECURITY_AUDIT.AUDIT$JOURNAL
This command invokes the Audit Analysis Utility and displays a
brief format listing of all the events recorded in the system
security audit log file.
2. $ ANALYZE/AUDIT /EVENT_TYPE=LOGFAIL/IGNORE=USERNAME=IAMOK -
_$ SYS$MANAGER:SECURITY_AUDIT.AUDIT$JOURNAL
This command displays a brief format listing of all failed attempts
to log in to the system except those from user IAMOK.
3. $ ANALYZE/AUDIT/FULL/SINCE=TODAY/BEFORE=10:00/SELECT=USERNAME=BOB -
_$ SYS$MANAGER:SECURITY_AUDIT.AUDIT$JOURNAL
This command displays a full format listing of all the security
events generated by user BOB between the hours of midnight and 10
a.m. of the current day.
4. $ ANALYZE/AUDIT/FULL/EVENT_TYPE=(BREAKIN,LOGFAIL,RIGHTSDB) -
_$ SYS$MANAGER:SECURITY_AUDIT.AUDIT$JOURNAL
This command displays a full format listing of all security events
generated by attempts to break in to the system, failed login
attempts on the system, or modifications to the rights database.
/CRASH_DUMP
Invokes the System Dump Analyzer. The System Dump Analyzer is a
utility that you can use to help determine the causes of system
failures. This utility is also useful for examining the running
system.
Format
[ /CRASH_DUMP [/RELEASE] filespec ]
ANALYZE [ /SYSTEM ]
[ ]
/SYMBOL=system-symbol-table
Additional information available:
Command Parameter
filespec Name of the file that contains the dump you want to analyze. At least one field of the filespec is required, and it can be any field. The default filespec is the highest version of SYSDUMP.DMP in your default directory.
Examples
1. $ ANALYZE/CRASH_DUMP SYS$SYSTEM:SYSDUMP.DMP
$ ANALYZE/CRASH SYS$SYSTEM
These commands invoke SDA to analyze the crash dump stored in
SYS$SYSTEM:SYSDUMP.DMP.
2. $ ANALYZE/CRASH SYS$SYSTEM:PAGEFILE.SYS
This command invokes SDA to analyze a crash dump stored in the
system paging file.
/RELEASE
Invokes SDA to release those blocks in the specified system paging
file occupied by a crash dump.
Format
/RELEASE filespec
Additional information available:
Parameter
filespec
Name of the system page file (SYS$SYSTEM:PAGEFILE.SYS). The
default file specification is
SYS$DISK:[default-dir]SYSDUMP.DMP
SYS$DISK and [default-dir] represent the disk and directory
specified in your last SET DEFAULT command. If you do not specify
filespec, SDA prompts you for it.
Description
You use the /RELEASE qualifier to release from the system paging
file those blocks occupied by a crash dump. When invoked with
the /RELEASE qualifier, SDA immediately deletes the dump from the
paging file and allows no opportunity to analyze its contents.
When you specify the /RELEASE qualifier in the ANALYZE command,
you must also
1. Use the /CRASH_DUMP qualifier.
2. Include the name of the system paging file
(SYS$SYSTEM:PAGEFILE.SYS) as the filespec.
If you do not specify the system paging file or the specified
paging file does not contain a dump, SDA generates the following
messages:
%SDA-E-BLKSNRLSD, no dump blocks in page file to release, or not page file
%SDA-E-NOTPAGFIL, specified file is not the page file
Example
$ ANALYZE/CRASH_DUMP/RELEASE SYS$SYSTEM:PAGEFILE.SYS
$ ANALYZE/CRASH/RELEASE PAGEFILE.SYS
These commands invoke SDA to release to the paging file those
blocks in SYS$SYSTEM:PAGEFILE.SYS occupied by a crash dump.
/SYMBOL
Specifies a system symbol table for SDA to use in place of the
system symbol table it uses by default (SYS$SYSTEM:SYS.STB).
Format
/SYMBOL =system-symbol-table
Additional information available:
Parameter
system-symbol table File specification of the VMS SDA system symbol table needed to define symbols required by SDA to analyze a dump from a particular VMS system. The specified system-symbol-table must contain those symbols required by SDA to find certain locations in the executive image. If you do not specify the /SYMBOL qualifier, SDA uses SYS$SYSTEM:SYS.STB by default. When you do specify the /SYMBOL qualifier, SDA assumes the default disk and directory to be SYS$DISK: that is, the disk and directory specified in your last SET DEFAULT command. If SDA is given a file that is not a system symbol table in the /SYMBOL qualifier, it halts with a fatal error.
Description
The /SYMBOL qualifier allows you to specify a system symbol table, other than SYS$SYSTEM:SYS.STB, to load into the SDA symbol table. This may be necessary, for instance, in order to analyze a crash dump taken on a processor running a different version of VMS. You can use the /SYMBOL qualifier whether you are analyzing a system dump or a running system.
Example
$ ANALYZE/CRASH_DUMP/SYMBOL=SYS$CRASH:SYS.STB SYS$SYSTEM
This command invokes SDA to analyze the crash dump stored
in SYS$SYSTEM:SYSDUMP.DMP, using the system symbol table at
SYS$CRASH:SYS.STB.
/DISK_STRUCTURE
Invokes the Analyze/Disk_Structure Utility to do the following:
o Check the readability and validity of Files-11 Structure Level 1
and Files-11 Structure Level 2 disk volumes
o Report errors and inconsistencies
The /DISK_STRUCTURE qualifier is required. For a complete
description of the Analyze/Disk_Structure Utility, including
information about the DCL command ANALYZE/DISK_STRUCTURE and its
qualifiers, see the VMS Analyze/Disk_Structure Utility Manual.
Format:
ANALYZE/DISK_STRUCTURE device-name:
Additional information available:
ParametersCommand QualifiersExamples
Parameters
device-name Specifies the disk volume or volume set to be verified. A logical name may be used. If a volume set is specified, all volumes must be mounted.
Command Qualifiers
Additional information available:
/CONFIRM/LIST/READ_CHECK/REPAIR/USAGE
/CONFIRM
/CONFIRM /NOCONFIRM (default) Controls whether the Analyze/Disk_Structure Utility prompts you to confirm a repair operation. If the response to the prompt is Y (YES), the Analyze/Disk_Structure Utility performs a repair. Otherwise, the repair is not performed. A few repairs allow you to delete the file. In these cases, if the response is D (DELETE), the file is deleted. However, if the response is Y (YES), the default repair is performed.
/LIST
/LIST[=filespec] /NOLIST (default) Controls whether the Analyze/Disk_Structure Utility produces a list of the index file. If you specify /LIST, Analyze/DISK_STRUCTURE produces a list of the index file in file number order, containing the file identification, file name, and owner UIC of each file. The list is copied to the specified file. No wildcard characters are allowed in the file specification. If you omit filespec, the list is written to the current SYS$OUTPUT device. If you include a file specification that does not have a file type, the default file type is LIS.
/READ_CHECK
/READ_CHECK /NOREAD_CHECK (default) Controls whether the Analyze/Disk_Structure Utility performs a read check on all allocated blocks on the file structure.
/REPAIR
/REPAIR /NOREPAIR (default) Controls whether the Analyze/Disk_Structure Utility repairs errors that are detected in the file structure. The file structure is modified only if /REPAIR is specified. When /REPAIR is specified, the file structure is software write-locked during execution. By default, the Analyze/Disk_Structure Utility reports errors, but does not repair them.
/USAGE
/USAGE[=filespec] Specifies that a disk usage accounting file be produced. If you omit all or part of the filespec, defaults are applied using SYS$DISK:USAGE.DAT.
Examples
1. $ ANALYZE/DISK_STRUCTURE/LIST DBC5: This command invokes the Analyze/Disk_Structure Utility to check the readability and validity of disk DBC5. The /LIST qualifier displays a report of errors and a listing of DBC5's index file at the current SYS$OUTPUT device. 2. $ ANALYZE/DISK_STRUCTURE/REPAIR/CONFIRM DBC5: This command repairs errors that are detected in the file structure of disk DBC5, but prompts you to confirm the repair operations.
/ERROR_LOG
Invokes the Errorlog Report Formatter (ERF) to selectively report
the contents of an error log file. The /ERROR_LOG qualifier is
required. For a complete description of the VMS Analyze Error Log
Utility, including more information about the ANALYZE/ERROR_LOG
command and its qualifiers, see the VMS Error Log Utility Reference
Manual.
Format:
ANALYZE/ERROR_LOG [filespec[,...]]
Additional information available:
Parameters
filespec[,...] Specifies one or more files that contain binary error information to be interpreted for the error log report. If you omit the file specification, the default file is SYS$ERRORLOG:ERRLOG.SYS.
QUALIFIERS
Additional information available:
/BEFORE/BINARY/BRIEF/ENTRY/EXCLUDE/FULL/INCLUDE
/LOG/NODE/OUTPUT/REGISTER_DUMP/REJECTED
/SID_REGISTER/SINCE/STATISTICS/SUMMARY
/BEFORE
/BEFORE[=date-time] Specifies that only those entries dated earlier than the stated date-time be selected for the error report. You can specify an absolute time, a delta time, or a combination of absolute and delta times.
/BINARY
/BINARY[=filespec] /NOBINARY Controls whether the binary error log records are converted to ASCII text or copied to the specified output file. The output file will contain image copies of the binary input records (the records will not be translated to ASCII).
/BRIEF
/BRIEF Generates a brief report, which supplies minimal information for an error log entry.
/ENTRY
/ENTRY[=(start:decimal-value[,end:decimal-value])] Generates an error log report that covers the specified entry range or starts at the specified entry number. If you specify /ENTRY without the entry range or omit the qualifier, the entry range defaults to START:1,END:EOF.
/EXCLUDE
/EXCLUDE=(device or entry-type[,...])
Excludes errors generated by the specified devices and/or errorlog
entry types from the error log report.
You can specify one or more devices by device class or name. The
following keywords and name constructs are valid for specifying
devices:
Device Class Keywords
ADAPTER
BUSES
CACHE
DISKS
INFORMATIONAL
LINE_PRINTER
REALTIME
SYNC_COMMUNICATIONS
TAPES
VECTOR
WORKSTATION
Device Name Constructs
DB - group of devices
DBA1 - specific device/unit number
DBA1,HSC1$DUA1,DYA0 - list of devices
DB,DR,XF - list of device groups
You can specify one or more of the following keywords that identify
entry types:
ATTENTIONS Exclude device attention entries from
the output report.
BUGCHECKS Exclude all types of bugcheck entries
from the report.
CONFIGURATION Exclude entries that describe system
configuration from the report.
CONTROL_ENTRIES Exclude control entries from the
report.
CPU_ENTRIES Exclude CPU-related entries from the
report.
DEVICE_ERRORS Exclude device error entries from the
report.
ENVIRONMENTAL_ENTRIES Exclude environmental entries from the
report.
MACHINE_CHECKS Exclude machine check entries from the
report.
MEMORY Exclude memory errors from the report.
SNAPSHOT_ENTRIES Exclude shapshot entries from the
report.
SYNDROME Exclude from the report VAX 9000
console-generated entries that provide
encoded syndrome values used by Customer
Services personnel.
TIMEOUTS Exclude device timeout entries from
the report.
UNKNOWN_ENTRIES Exclude any entry that had either an
unknown entry type or an unknown
device type/class.
UNSOLICITED_MSCP Exclude unsolicited MSCP entries from
the output report.
VOLUME_CHANGES Exclude volume mount and dismount
entries from the report.
/FULL
/FULL /NOFULL Generates a full report, which provides all possible information available for an error log entry. This is the default report format.
/INCLUDE
/INCLUDE=(device or entry-type[,...])
Includes errors generated by the specified devices and/or errorlog
entry types in the error log report.
You can specify one or more devices by device class or name. The
following keywords and name constructs are valid for specifying
devices:
Device Class Keywords
ADAPTER
BUSES
CACHE
DISKS
INFORMATIONAL
LINE_PRINTER
REALTIME
SYNC_COMMUNICATIONS
TAPES
VECTOR
WORKSTATION
Device Name Constructs
DB - group of devices
DBA1 - specific device/unit number
DBA1,HSC1$DUA1,DYA0 - list of devices
DB,DR,XF - list of device groups
You can specify one or more of the following keywords that identify
entry types:
ATTENTIONS Include device attention entries in
the output report.
BUGCHECKS Include all types of bugcheck errors
in the report.
CONFIGURATION Include entries that describe system
configuration in the report.
CONTROL_ENTRIES Include control entries in the report.
CPU_ENTRIES Include CPU-related entries in the
report.
DEVICE_ERRORS Include device errors in the report.
ENVIRONMENTAL_ENTRIES Include environmental entries in the
report.
MACHINE_CHECKS Include machine check errors in the
report.
MEMORY Include memory errors in the report.
SNAPSHOT_ENTRIES Include shapshot entries in the
report.
SYNDROME Include in the report VAX 9000
console-generated entries that provide
encoded syndrome values used by
Customer Services personnel.
TIMEOUTS Include device timeout errors in the
report.
UNKNOWN_ENTRIES Include any entry that had either an
unknown entry type or an unknown
device type/class.
UNSOLICITED_MSCP Include unsolicited MSCP entries in
the output report.
VOLUME_CHANGES Include volume mount and dismount
entries in the report.
/LOG
/LOG /NOLOG Controls whether informational messages that specify the number of entries selected and rejected for each input file are sent to SYS$OUTPUT. By default, these messages are not displayed.
/NODE
/NODE =(node-name[,...]) Generates a report containing entries for the specified nodes in a VAXcluster. Node names may not exceed six characters. If you specify more than one node, you must specify a comma-separated list of node names enclosed in parentheses.
/OUTPUT
/OUTPUT[=filespec] Specifies the output file for the error log report. If you omit the /OUTPUT qualifier, output is directed to SYS$OUTPUT.
/REGISTER_DUMP
/REGISTER_DUMP Used in conjunction with the /INCLUDE qualifier to generate, in a hexadecimal longword format, a report that consists of device register information. Only for memory, device error, and device timeout entries. No translation of any of the device register information occurs.
/REJECTED
/REJECTED[=filespec] Allows the user to specify the name of a file that will contain binary records for rejected entries.
/SID_REGISTER
/SID_REGISTER[=(hexadecimal-value[,...])] Generates a report that consists of error log entries that occurred on the specified CPU. The unique hexadecimal value is obtained from the system ID register using the $GETSYI system service. In a VAXcluster environment, you may specify a hexadecimal value for each member. If you specify more than one hexadecimal value, you must specify a comma-separated list of values enclosed in parentheses.
/SINCE
/SINCE[=time] Specifies that only those entries dated later than the stated time be selected for the report. You can specify either an absolute time or a combination of absolute and delta times. You can also use the keywords TODAY, TOMORROW, and YESTERDAY.
/STATISTICS
/STATISTICS Generates a report that consists of the page faults, buffered I/O, direct I/O, and CPU time used in the execution of the ANALYZE/ERROR_LOG command.
/SUMMARY
/SUMMARY[=summary-type[,...]]
Generates an error log report that consists of a statistical
summary, using one or more of the following summary-type keywords:
Keyword Meaning
DEVICE Include the Device Rollup section in the report.
ENTRY Include the Summary of Entries Logged section in
the report.
HISTOGRAM Include the Processed Entries Hour of Day
Histogram in the report.
MEMORY Include the Summary of Memory Errors section in
the report.
VOLUME Include the Volume Label section in the report.
NOTE
If you specify /SUMMARY without a summary type, the
report contains all the summary types listed above.
If only a summary report is desired, the command
line must specify both the /NOFULL qualifier and the
/SUMMARY qualifier.
Examples
1. $ ANALYZE/ERROR_LOG All defaults occur as specified. 2. $ ANALYZE/ERROR_LOG/ENTRY=(START:1,END:18) ERRLOG.SYS The entry range for the error log report generated from the file ERRLOG.SYS is limited to entry numbers 1 through 18. 3. $ ANALYZE/ERROR_LOG/EXCLUDE=MTA0 ERRLOG.SYS The device MTA0 is excluded from the error log report for the file ERRLOG.SYS. 4. $ ANALYZE/ERROR_LOG/EXCLUDE=(MTA0,DRA5) ERRLOG.SYS The devices MTA0 and DRA5 are excluded from the error log report for the file ERRLOG.SYS. 5. $ ANALYZE/ERROR_LOG/EXCLUDE=(DISKS,BUGCHECKS) ERRLOG.SYS All disk devices and all bugcheck entries are excluded from the error log report for the file ERRLOG.SYS. 6. $ ANALYZE/ERROR_LOG/EXCLUDE=(DISK,VOLUME_CHANGES) Entries for disk volume information are excluded from the error log report for the file ERRLOG.SYS. 7. $ ANALYZE/ERROR_LOG/EXCLUDE=(DISK,VOLUME_CHANGES,DEVICE_ERROR) Entries for volume and device error information on disks are excluded from the error log report for the file ERRLOG.SYS. 8. $ ANALYZE/ERROR_LOG/INCLUDE=(DISK,VOLUME_CHANGES) The report will consist only of error log entries for disk volume information, which are in the default error log file ERRLOG.SYS. 10. $ ANALYZE/ERROR_LOG/INCLUDE=(DISK,VOLUME_CHANGES,DEVICE_ERROR) The report will consist only of error log entries for volume and device error information on disks, which are in the default error log file ERRLOG.SYS. 11. $ ANALYZE/ERROR_LOG/NODE=(ORANGE,NASSAU) ERRLOG.OLD;72 In this example, a VAXcluster includes members ORANGE, PUTNAM, and NASSAU. The output consists of only those entries that were logged for VAXcluster members ORANGE and NASSAU.
/IMAGE
Analyzes the contents of an executable image file or a shareable
image file and checks for obvious errors in the image file. The
/IMAGE qualifier is required. For general information about image
files, see the description of the linker in the VMS Linker Utility
Manual. (Use the ANALYZE/OBJECT command to analyze the contents of
an object file.)
Format
ANALYZE/IMAGE filespec[,...]
Additional information available:
PARAMETER
filespec[,...] Specifies the name of one or more image files that you want analyzed. You must specify at least one file name. If you specify more than one file, separate the file specifications with either commas (,) or plus signs (+). The default file type is EXE. Wildcard characters (* and %) are allowed in the file specification.
QUALIFIERS
Additional information available:
/FIXUP_SECTION/GST/HEADER/INTERACTIVE/OUTPUT
/PATCH_TEXT
/FIXUP_SECTION
Positional qualifier. Specifies that the analysis should include all information in the fixup section of the image. If you specify the /FIXUP_SECTION qualifier after the ANALYZE /IMAGE command, the fixup section of each image file in the parameter list is analyzed. If you specify the /FIXUP_SECTION qualifier after a file specification, only the information in the fixup section of that image file is analyzed.
/GST
Positional qualifier. Specifies that the analysis should include all global symbol table records. This qualifier is valid only for shareable images. If you specify the /GST qualifier after the ANALYZE/IMAGE command, the global symbol table records of each image file in the parameter list are analyzed. If you specify the /GST qualifier after a file specification, only the global symbol table records of that file are analyzed.
/HEADER
Positional qualifier. Specifies that the analysis should include all header items and image section descriptions. The image header items are analyzed always.
/INTERACTIVE
/INTERACTIVE
/NOINTERACTIVE (default)
Specifies whether the analysis is interactive. In interactive
mode, as each item is analyzed, the results are displayed on the
screen and you are asked whether you want to continue.
/OUTPUT
/OUTPUT=filespec
Identifies the output file for storing the results of the
image analysis. No wildcard characters are allowed in the file
specification. If you specify a file type and omit the file name,
the default file name ANALYZE is used. The default file type is
ANL. If you omit the qualifier, the results are output to the
current SYS$OUTPUT device.
/PATCH_TEXT
Positional qualifier. Specifies that the analysis include all patch text records. If you specify the /PATCH_TEXT qualifier after the ANALYZE/IMAGE command, the patch text records of each image file in the parameter list are analyzed. If you specify the /PATCH_TEXT qualifier after a file specification, only the patch text records of that file are analyzed.
Examples
1. $ ANALYZE/IMAGE LINEDT
The ANALYZE/IMAGE command in this example produces a
description and an error analysis of the image LINEDT.EXE.
Output is sent to the current SYS$OUTPUT device. By default,
the entire image is analyzed.
2.
$ ANALYZE/IMAGE/OUTPUT=LIALPHEX/FIXUP_SECTION/PATCH_TEXT LINEDT, ALPHA
The ANALYZE/IMAGE command in this example produces a
description and an error analysis of the fixup sections
and patch text records of LINEDT.EXE and ALPHA.EXE in file
LIALPHEX.ANL. Output is sent to the file LIALPHEX.ANL.
/MEDIA
Invokes the Bad Block Locator Utility (BAD), which analyzes
block-addressable devices and records the location of blocks that
cannot reliably store data. The /MEDIA qualifier is required. For
a complete description of BAD, including information about the
ANALYZE/MEDIA command and its qualifiers, see the VMS Bad Block
Locator Utility Manual.
Format:
ANALYZE/MEDIA device
Additional information available:
ParametersCommand QualifiersExamples
Parameters
device
Specifies the device that BAD will analyze. The device has the
form:
ddcu: or logical-name
Command Qualifiers
Additional information available:
/BAD_BLOCKS/EXERCISE/LOG/OUTPUT/RETRY/SHOW
/BAD_BLOCKS
/BAD_BLOCKS[=list]
Adds the specified bad blocks to the Detected Bad Block File
(DBBF). If the /BAD_BLOCK qualifier is specified along with the
/EXERCISE qualifier, the medium is tested once the bad blocks are
added to the DBBF.
If you do not specify a value for the /BAD_BLOCK qualifier, you are
prompted as follows:
BAD_BLOCKS =
In prompt mode, BAD reports any duplicate bad blocks.
Qualifier Value
list
Specifies the bad block locations to be added to the DBBF. Valid
codes for specifying bad block locations are:
Code Meaning
lbn Specifies the Logical Block Number (LBN)
of a single bad block.
lbn:count Specifies a range of contiguous bad
blocks starting at the Logical Block
Number (LBN) and continuing for "count"
blocks.
sec.trk.cyl Specifies the physical disk address
(sector, track, and cylinder) of a single
bad sector. This code is valid only for
last track devices.
sec.trk.cyl:count Specifies a range of bad sectors starting
at the specified physical disk address
(sector, track, and cylinder) and
continuing for "count" sectors. This
code is valid only for last track
devices.
You can specify these formats in any
integer combination or radix combination.
NOTE
The term "block" denotes a standard unit of 512
bytes, whereas the term "sector" denotes the
physical size of the device sector, which is not
always the same for all devices. For example, an
RL02 has a sector size of 256 bytes, while an RK07
has a standard sector size of 512 bytes.
/EXERCISE
/EXERCISE=(FULL,[NO]KEEP,PATTERN)
/NOEXERCISE (default)
Controls whether the media should actually be tested. You can
update the DBBF without erasing the contents of the volume by
using the /NOEXERCISE qualifier along with the /BAD_BLOCKS
qualifier.
Qualifier Keywords
FULL
Causes BAD to test the media using three test patterns (0's,
1's, and "worst case") instead of the default single "worst
case" pattern. The FULL keyword can be used only with
/EXERCISE. Note that the "worst case" test pattern always
remains on media tested with the /EXERCISE qualifier.
KEEP
Ensures the preservation of the current Software Detected Bad
Block File (SDBBF). The KEEP keyword is the default when
/NOEXERCISE is specified.
NOKEEP
Causes BAD to create a new SDBBF. The NOKEEP keyword is the
default when /EXERCISE is specified. This keyword cannot be
used with the /NOEXERCISE qualifier.
PATTERN=
Allows users to specify the value of a test pattern to be
used as "worst case". Up to an octaword of test pattern data
may be specified in decimal (%D), hexadecimal (%X), or
octal (%O) radixes. The default radix is decimal.
The pattern is specified in longwords. If two or more
longwords are specified, they must be enclosed in parentheses
and separated by commas.
/LOG
/LOG /NOLOG (default) Specifies whether a message is sent to the current SYS$OUTPUT device and SYS$ERROR, indicating the total number of bad blocks detected by BAD.
/OUTPUT
/OUTPUT[=filespec]
Specifies whether the contents of the DBBF are written to the
specified file. If you omit the /OUTPUT qualifier, no output is
generated.
If you specify /OUTPUT but omit the filespec, the contents of the
DBBF are written to the current SYS$OUTPUT device.
When you specify /OUTPUT, the /SHOW=AFTER qualifier is implied.
Qualifier Value
filespec
Identifies the output file for storing the results of
the medium analysis. If you specify a file type and omit the
file name, the default file name ANALYZE is used. The default
file type is ANL. If you omit the filespec, the results are
output to the current SYS$OUTPUT device.
No wildcard characters are allowed in the file specification.
/RETRY
/RETRY /NORETRY (default) Enables the device driver to retry soft errors.
/SHOW
/SHOW[=(keyword[,...])]
Lists the contents of the DBBF before or after (or both) the
medium is exercised or modified.
Qualifier Keywords
[NO]BEFORE,[NO]AFTER
Specifies whether the contents of the DBBF are listed before or
after (or both) the medium is exercised. AFTER is the default.
Examples
In examples 1 and 2, the contents of the data region on the medium
are not altered or destroyed; in examples 3, 4, and 5, all the data
on the medium is destroyed.
1. $ ANALYZE/MEDIA/BAD_BLOCKS=(4.4.4:3) DBA1:
The /BAD_BLOCKS qualifier in this example specifies a range of 3
bad blocks beginning at the physical disk address sector 4, track
4, cylinder 4. This range is added to the DBBF.
2. $ ANALYZE/MEDIA /LOG DBB1:
Device DBB1: contains a total of 340670 blocks; 11 defective
blocks detected.
The command in this example requests BAD to report the total
number of bad blocks recorded in DBBF's for the disk mounted on
DBB1:. The medium is not exercised or altered in any way.
3. $ ANALYZE/MEDIA/EXERCISE/BAD_BLOCKS=(2) DBB1:
The command in this example adds the bad block specification to
the DBBF and then tests the media. The bad block in this example
is located at logical block number (LBN) 2.
4. $ ANALYZE/MEDIA/EXERCISE=KEEP DBA1:
This command tests the media while preserving the current SDBBF.
5. $ ANALYZE/MEDIA/EXERCISE/RETRY DBB1:
The command in this example directs the device driver to retry soft
errors.
/OBJECT
Analyzes the contents of an object file and checks for any obvious
errors. The /OBJECT qualifier is required. (Use the ANALYZE/IMAGE
command to analyze the contents of an image file.)
Format
ANALYZE/OBJECT filespec[,...]
Additional information available:
PARAMETER
filespec[,...] Specifies the object files or object module libraries you want analyzed (the default file type is OBJ). Use commas (,) or plus signs (+) to separate file specifications. Wildcard characters (* and %) are allowed in the file specification.
QUALIFIERS
Additional information available:
/DBG/EOM/GSD/INCLUDE/INTERACTIVE/LNK
/MHD/OUTPUT/TBT/TIR
/DBG
/DBG Positional qualifier. Specifies that the analysis should include all debugger information records. If you want the analysis to include debugger information for all files in the parameter list, insert the /DBG qualifier immediately following the /OBJECT qualifier. If you want the analysis to include debugger information selectively, insert the /DBG qualifier immediately following each of the selected file specifications.
/EOM
/EOM
Positional qualifier.
Specifies that the analysis should be limited to MHD records, EOM
records, and records explicitly specified by the command. If you
want this to apply to all files in the parameter list, insert the
/EOM qualifier immediately following the /OBJECT qualifier.
To make the /EOM qualifier applicable selectively, insert it
immediately following each of the selected file specifications.
NOTE
End-of-module records may be EOM or EOMW records. See the
VMS Linker Utility Manual for more information.
/GSD
/GSD Positional qualifier. Specifies that the analysis should include all global symbol directory (GSD) records. If you want the analysis to include GSD records for each file in the parameter list, specify the /GSD qualifier immediately following the /OBJECT qualifier. If you want the analysis to include GSD records selectively, insert the /GSD qualifier immediately following each of the selected file specifications.
/INCLUDE
/INCLUDE[=(module[,...])] When the specified file is an object module library, use this qualifier to list selected object modules within the library for analysis. If you omit the list or specify an asterisk (*), all modules are analyzed. If you specify only one module, you can omit the parentheses.
/INTERACTIVE
/INTERACTIVE /NOINTERACTIVE (default) Controls whether the analysis occurs interactively. In interactive mode, as each record is analyzed, the results are displayed on the screen, and you are asked whether you want to continue.
/LNK
/LNK Positional qualifier. Specifies that the analysis should include all link option specification (LNK) records. If you want the analysis to include LNK records for each file in the parameter list, specify the /LNK qualifier immediately following the /OBJECT qualifier. If you want the analysis to include LNK records selectively, insert the /LNK qualifier immediately following each of the selected file specifications.
/MHD
/MHD Positional qualifier. Specifies that the analysis should be limited to MHD records, EOM records, and records explicitly specified by the command. If you want this analysis to apply to all files in the parameter list, insert the /MHD qualifier immediately following the /OBJECT qualifier. To make the /MHD qualifier applicable selectively, insert it immediately following each of the selected file specifications.
/OUTPUT
/OUTPUT[=filespec] Directs the output of the object analysis (the default is SYS$OUTPUT). If you specify a file type and omit the file name, the default file name ANALYZE is used. The default file type is ANL. No wildcard characters are allowed in the file specification.
/TBT
/TBT Positional qualifier. Specifies that the analysis should include all module traceback (TBT) records. If you want the analysis to include TBT records for each file in the parameter list, specify the /TBT qualifier immediately following the /OBJECT qualifier. If you want the analysis to include TBT records selectively, insert the /TBT qualifier immediately following each of the selected file specifications.
/TIR
/TIR Positional qualifier. Specifies that the analysis should include all text information and relocation (TIR) records. If you want the analysis to include TIR records for each file in the parameter list, specify the /TIR qualifier immediately following the /OBJECT qualifier. If you want the analysis to include TIR records selectively, insert the /TIR qualifier immediately following the selected file specifications.
Examples
1. $ ANALYZE/OBJECT/INTERACTIVE LINEDT
In this example, the ANALYZE/OBJECT command produces a
description and a partial error analysis of the object file
LINEDT.OBJ. By default, all types of records are analyzed.
Output is to the terminal, because the /INTERACTIVE qualifier
has been used. As each item is analyzed, the utility displays
the results on the screen and asks if you want to continue.
2. $ ANALYZE/OBJECT/OUTPUT=LIOBJ/DBG LINEDT
In this example, the ANALYZE/OBJECT command analyzes only the
debugger information records of the file LINEDT.OBJ. Output is
to the file LIOBJ.ANL.
/PROCESS_DUMP
Invokes the VMS Debugger to analyze a process dump file that was
created when an image failed during execution. (Use the /DUMP
qualifier with the RUN or the SET PROCESS command to generate a
dump file.) For a complete description of the debugger (including
information about the DEBUG command), see the VMS Debugger Manual.
Requires read (R) access to the dump file.
Format
ANALYZE/PROCESS_DUMP dump-file
Additional information available:
PARAMETER
dump-file Specifies the dump file to be analyzed with the debugger.
Qualifiers
Additional information available:
/FULL/IMAGE/INTERACTIVE/MISCELLANEOUS/OUTPUT
/RELOCATION
/FULL
Displays all known information about the failing process.
/IMAGE
/IMAGE=image-name
/NOIMAGE
Specifies the image whose symbols are to be used in analyzing the
dump. If you use the /NOIMAGE qualifier, no symbols are taken from
any image. By default, symbols are taken from the image with the
same name as the image that was running at the time of the dump.
/INTERACTIVE
/INTERACTIVE
/NOINTERACTIVE (default)
Causes the display of information to pause when your terminal
screen is filled. Press the Return key to display additional
information. By default, the display is continuous.
/MISCELLANEOUS
Displays all the miscellaneous information in the dump.
/OUTPUT
/OUTPUT=filespec
Writes the information to the specified file. By default, the
information is written to the current SYS$OUTPUT device. No
wildcard characters are allowed in the file specification.
/RELOCATION
Displays the addresses to which data structures saved in the dump are mapped in P0 space. (Examples of such data structures are the stacks.) The data structures in the dump must be mapped into P0 space so that the debugger can use those data structures in P1 space.
Example
$ ANALYZE/PROCESS/FULL ZIPLIST
R0 = 00018292 R1 = 8013DE20 R2 = 7FFE6A40 R3 = 7FFE6A98
R4 = 8013DE20 R5 = 00000000 R6 = 7FFE7B9A R7 = 0000F000
R8 = 00000000 R9 = 00000000 R10 = 00000000 R11 = 00000000
SP = 7FFAEF44 AP = 7FFAEF48 FP = 7FFAEF84
FREE_P0_VA 00001600 FREE_P1_VA 7FFAC600
Active ASTs 00 Enabled ASTs 0F
Current Privileges FFFFFF80 1010C100
Event Flags 00000000 E0000000
Buffered I/O count/limit 6/6
Direct I/O count/limit 6/6
File count/limit 27/30
Process count/limit 0/0
Timer queue count/limit 10/10
AST count/limit 6/6
Enqueue count/limit 30/30
Buffered I/O total 7 Direct I/O total 18
Link Date 27-DEC-1990 15:02:00.48 Patch Date 17-NOV-1990 00:01:53.71
ECO Level 0030008C 00540040 00000000 34303230
Kernel stack 00000000 pages at 00000000 moved to 00000000
Exec stack 00000000 pages at 00000000 moved to 00000000
Vector page 00000001 page at 7FFEFE00 moved to 00001600
PIO (RMS) area 00000005 pages at 7FFE1200 moved to 00001800
Image activator context 00000001 page at 7FFE3400 moved to 00002200
User writeable context 0000000A pages at 7FFE1C00 moved to 00002400
Creating a subprocess
VAX DEBUG Version 5.4
DBG>
This example shows the output of the ANALYZE/PROCESS command
when used with the /FULL qualifier. The file specified,
ZIPLIST, contains the dump of a process that encountered a
fatal error. The DBG> prompt indicates that the debugger is
ready to accept commands.
/RMS_FILE
Invokes the VMS Analyze/RMS_File Utility (ANALYZE/RMS_FILE) to
inspect and analyze the internal structure of a VAX RMS file. The
/RMS_FILE qualifier is required. For a complete description of the
Analyze/RMS_File Utility, including more information about the
ANALYZE/RMS_FILE command and its qualifiers, see the VMS
Analyze/RMS_File Utility Manual.
Format:
ANALYZE/RMS_FILE filespec[,...]
Additional information available:
Parameters
filespec[,...] Specifies the data file to be analyzed. You must specify at least one file name. If you specify more than one file, separate the specifications with either commas or plus signs. By default, the file type is assumed to be DAT. Multiple file specifications and wildcard characters are allowed except when /FDL or /INTERACTIVE is specified.
QUALIFIERS
Additional information available:
/CHECK/FDL/INTERACTIVE/OUTPUT/RU_JOURNAL
/STATISTICS/SUMMARY
/CHECK
/CHECK Requests a check of the file's integrity and generates a report of any errors in the file's structure. The report also includes a summary of the file's structure. By default, if no output file is specified, the report is written to the current SYS$OUTPUT device. Also, if /NOOUTPUT is specified, no report is generated. Rather, only the message telling whether or not the file has errors is displayed. This qualifier is the default unless /FDL, /INTERACTIVE, or /STATISTICS is specified. Do not use this qualifier with /FDL, /INTERACTIVE, /STATISTICS, or /SUMMARY; the functions of /CHECK and these qualifiers are mutually exclusive.
/FDL
/FDL Specifies that an FDL file is to be generated that describes the VAX RMS file being analyzed. When you use this qualifier, wildcard characters and multiple file specifications are not allowed. The default file name will have the same file name as the input file with the file type FDL. To assign a different file specification, use the /OUTPUT qualifier. Do not use this qualifier with /CHECK, /INTERACTIVE, /STATISTICS, or /SUMMARY; the functions of /FDL and these qualifiers are mutually exclusive.
/INTERACTIVE
/INTERACTIVE Specifies that the examination of the VAX RMS file is to be performed interactively. When you use this qualifier, wildcard characters and multiple file specifications are not allowed. Do not use this qualifier with /CHECK, /FDL, /STATISTICS, or /SUMMARY; the functions of /INTERACTIVE and these qualifiers are mutually exclusive.
/OUTPUT
/OUTPUT=filespec /NOOUTPUT Requests that the results of the analysis be output to the specified file. The use of this qualifier depends on which of the other qualifiers are specified. If /CHECK is specified, the integrity report is written to the output file. If you specify a file type and omit the file name, the default file name ANALYZE is used. The default file type is ANL. If /FDL is specified, the resulting FDL specification is placed in the output file. If you specify a file type but omit the file name, the file name of the input file is used. The default file type is FDL. If /INTERACTIVE is specified, a transcript of the interactive session is placed in the output file. If you specify a file type and omit the file name, the default file name ANALYZE is used. The default file type is ANL. If /STATISTICS or /SUMMARY is specified, the statistics or summary report is written to the output file. If you specify a file type and omit the file name, the default file name ANALYZE is used. The default file type is ANL. If you specify /NOOUTPUT, no output is produced. However, with the /CHECK qualifier, the message telling whether or not the file has errors is displayed. In other words, using the /NOOUTPUT qualifier with the /CHECK qualifier is a quick way to test the structure of your file. If you omit the /OUTPUT qualifier, output is written to the current SYS$OUTPUT device. However, the /INTERACTIVE qualifier produces no output, and the /FDL qualifier specifies that output is written to the FDL file.
/RU_JOURNAL
/RU_JOURNAL
Applicable only if you have the RMS Journaling option. See the VAX
RMS Journaling Manual.
Provides information about recovery unit journaling for the file that
you analyze. If a file is unavailable due to incomplete recovery
units that cannot be resolved at the time, the ANALYZE/RMS_FILE
/RU_JOURNAL command may be the only means of RMS access to the file
until the recovery unit issue is resolved. Your process must have
CMEXEC privilege to use the ANALYZE/RMS_FILE/RU_JOURNAL command.
The "Recovery Unit State:" field provides the primary information
about the status of recovery units and the possible reasons for the
unavailability of the file. The possible states are as follows:
Active - another process is accessing the recovery unit journal;
the file cannot be accessed until the recovery unit is complete.
Started - a recovery unit has begun, but no other process is
accessing the file.
Committed - all transactions in the current recovery unit were
completed but the updated records were not fully written; no
other process is accessing the file.
None - a recovery unit has begun, but no transactions have taken
place; no other process is accessing the file.
Not Available - an active recovery unit exists and RMS Journaling
cannot access the recovery unit journal for the file.
/STATISTICS
/STATISTICS Specifies that a report is to be produced containing VAX RMS file statistics. By default, if no output file is specified, the report is written to the current SYS$OUTPUT device. Do not use this qualifier with /CHECK, /FDL, /INTERACTIVE, or /SUMMARY; the functions of /STATISTICS and these qualifiers are mutually exclusive.
/SUMMARY
/SUMMARY Specifies that a summary report containing information about the file's structure and use is to be produced. If the file has no errors, the output generated from the /SUMMARY qualifier is identical to that produced by the /CHECK qualifier. However, output is generated more quickly because no checking is done. Do not use this qualifier with /CHECK, /FDL, /INTERACTIVE, or /STATISTICS. The functions of /SUMMARY and these qualifiers are mutually exclusive.
Examples
1. $ ANALYZE/RMS_FILE/CHECK CUSTFILE
This command performs a check on the file CUSTFILE.DAT. Output is a
check report that is displayed on the terminal.
2. $ ANALYZE/RMS_FILE/FDL ADDRFILE
This command generates an FDL file named ADDRFILE.FDL from the data
file ADDRFILE.DAT.
3. $ ANALYZE/RMS_FILE/FDL/OUTPUT=TEST.FDL
$_File(s): DENVER::DB1:[PROD]RUN.DAT
This command analyzes the structure of the file RUN.DAT at remote
node DENVER and generates the FDL file TEST.FDL at the local node.
/SYSTEM
Invokes the System Dump Analyzer (SDA) for analysis of the running
system. The /SYSTEM qualifier is required. For a complete
description of the System Dump Analyzer, including more information
about the ANALYZE/SYSTEM command and its qualifiers, see the VMS
System Dump Analyzer Manual.
Format:
$ ANALYZE/SYSTEM
Additional information available:
Example
$ ANALYZE/SYSTEM
This command invokes SDA to analyze the running system.