ignored when used with /INTERACTIVE. /OUTPUT /OUTPUT=filesspec /NOOUTPUT Identifies the destination file for the results of the analysis. The /NOOUTPUT qualifier specifies that no output file is to be created. In all cases, the Analyze/RMS_File utility displays a message indicating whether the data file has errors. /CHECK Places the integrity report in the output file. The default file type is .ANL, and the default file name is ANALYZE. If you omit the output- filespec parameter, output is written to the current SYS$OUTPUT device, which is generally your terminal. /FDL Places the resulting FDL specification in the output file. The default file type is .FDL, and the default file name is that of the input file. /INTERACTIVE Places a transcript of the interactive session in the output file. The default file type is .ANL, and the default file name is ANALYZE. If you omit the output-filespec parameter, no transcript of your interactive session is produced. /RU_JOURNAL Places the recovery-unit journal information in the output file. The default file type is .ANL, and the default file name is ANALYZE. If you omit the output-filespec parameter, output is written to the current SYS$OUTPUT device, which is generally your terminal. /STATISTICS Places the statistics report in the output file. The default file type is .ANL, and the default file name is ANALYZE. If you omit the output- filespec parameter, output is written to the current SYS$OUTPUT device, which is generally your terminal. /SUMMARY Places the summary report in the output file. The default file type is .ANL, and the default file name is ANALYZE. If you omit the output- filespec parameter, output is written to the current SYS$OUTPUT device, which is generally your terminal. /RU_JOURNAL Provides information about recovery-unit journaling where applicable. You can use the /RU_JOURNAL qualifier on any file, but it is inoperative on files not marked for recovery-unit journaling. This qualifier provides the only way of accessing a file that would otherwise be inaccessible because of unresolved recovery units. This situation might be the result of an unavailable recovery-unit journal file or of unavailable data files that were included in the recovery unit. To use the /RU_JOURNAL qualifier, your process must have both CMEXEC privilege and access to the [SYSJNL] directory (either SYSPRV privilege or access for UIC [1,4]). This qualifier is compatible with all of the ANALYZE/RMS_FILE qualifiers, and you can use it with wildcards and multiple file specifications. When you specify the /RU_JOURNAL qualifier, the Analyze/RMS_File utility provides you with the following data for each active recovery unit: o The journal file specification and the journal creation date o The recovery-unit identification, recovery-unit start time, cluster system identification number (CSID), and process identification (PID) o Information about the files involved in the recovery unit, including the file specification, the name of the volume where the file resides, the file identification, the date and time the file was created, and the current status of the file o The state of the recovery unit - active, none, started, committed, or not available (for more information, see the RMS Journaling for OpenVMS Manual) o An error statement /STATISTICS Specifies that a report is to be produced containing statistics about the file. The /STATISTICS qualifier is used mainly on indexed files. By default, if you do not specify an output file with the /OUTPUT qualifier, the statistics report is written to the current SYS$OUTPUT device, which is generally your terminal. The /STATISTICS qualifier is not compatible with the /CHECK qualifier, the /FDL qualifier, the /INTERACTIVE qualifier, or the /SUMMARY qualifier. If /STATISTICS is used with any other qualifiers, /FDL takes precedence, and then /INTERACTIVE. All other qualifiers are ignored. The /STATISTICS qualifier does an implicit check. /SUMMARY Specifies that a summary report is to be produced containing information about the file's structure and use. The /SUMMARY qualifier generates a summary report containing information about the file's structure and use. If the file has no errors, the output generated from the /SUMMARY qualifier is identical to that produced by the /CHECK qualifier. Unlike the /CHECK qualifier, however, the /SUMMARY qualifier does not check the structure of your file, so output is generated more quickly. Do not use this qualifier with the /CHECK qualifier, the /FDL qualifier, the /INTERACTIVE qualifier, the /STATISTICS qualifier, or the /UPDATE_HEADER qualifier. If /SUMMARY is used with any other qualifiers, /FDL takes precedence, next is /INTERACTIVE, and then /STATISTICS. /UPDATE_HEADER Attempts to update the following attributes in the header of the file: longest record length (LRL) and/or file length hint attribute. You must use this qualifier in combination with either /STATISTICS or /CHECK (the default). This qualifier only applies to sequential file organizations and is ignored for any other file organization. The /UPDATE_HEADER qualifier attempts to update the LRL and/or file hint attribute in the file header if the calculated value(s) differ from the current value(s) in the file header. The /UPDATE_HEADER qualifier applies to: o An LRL request - if the file is sequential and has a record format other than undefined (UDF). o A HINT request - if the file is sequential, the record format is either variable (VAR) or variable with fixed control (VFC), and the file is located on an ODS-5 disk device. It is not supported for remote accesses; requests are ignored. The /UPDATE_HEADER qualifier requires either the STATISTICS or CHECK (default) functions since calculating new values for the LRL and/or file length hint presumes that all the records in the sequential file are processed. It is not compatible with the /FDL qualifier, the /INTERACTIVE qualifier, or the /SUMMARY qualifier. Any errors returned by the file system when an attempt to update the file header fails are ignored. If the update succeeds, the updated values are displayed at the end of the report. 3 EXAMPLES 1.$ ANALYZE/RMS_FILE/CHECK CUSTFILE This command checks the file CUSTFILE.DAT for errors and displays the report 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 DENVER::DB1:[PROD]RUN.DAT This command analyzes the structure of the file RUN.DAT residing at remote node DENVER. 4.$ANALYZE/RMS_FILE/UPDATE_HEADER=HINT A.A FILE HEADER File Spec: DISK$REGRES:[REGRES]A.A;3 ... RMS FILE ATTRIBUTES File Organization: sequential Record Format: variable Record Attributes: carriage-return Maximum Record Size: 0 Longest Record: 52 Blocks Allocated: 4, Default Extend Size: 0 End-of-File VBN: 1, Offset: %X'008E' File Monitoring: disabled File Length Hint (Record Count): 6 (invalid) File Length Hint (Data Byte Count): 42 (invalid) Global Buffer Count: 0 The analysis uncovered NO errors. UPDATED File Length Hint (Record Count) to: 10 UPDATED File Length Hint (Data Byte Count) to: 118 ANALYZE/RMS_FILE/UPDATE_HEADER=HINT A.A 2 /SSLOG Valid for Alpha and I64 systems only. Displays the collected data. Format: ANALYZE/SSLOG [/BRIEF | /FULL | /NORMAL | /STATISTICS] [/OUTPUT=filename] [/SELECT=(option[,...])] [/WIDE] [filespec] filespec Optional name of the log file to be analyzed. The default filename is SSLOG.DAT. 3 Qualifiers /BRIEF Displays abbreviated logged information. /FULL Displays logged information, error status messages and sequence numbers. /NORMAL /NORMAL (Default) Displays basic logged information. /STATISTICS /STATISTICS[=BY_STATUS] Displays statistics on system services usage; accepts BY_ STATUS keyword. Outputs a summary of the services logged with a breakdown by access mode. Output is ordered with the most frequently requested services first. If BY_STATUS is included, the summary is further separated by completion status. Output is displayed up to 132 columns wide. /OUTPUT /OUTPUT=filename Identifies the output file for storing the results of the log analysis. An asterisk (*) and percent sign (%) are not allowed as wildcards in the file specification. There is no default file type or filename. If you omit the qualifier, results are output to the current SYS$OUTPUT device. /SELECT /SELECT=([option[,...]]) Selects entries based on your choice of options. You must specify at least one of the following: Keyword Meaning ACCESS_MODE=mode Selects data by access mode. IMAGE=image-name Selects data by image name. STATUS[=n] Selects data by status. n is optional. /SELECT=STATUS displays all entries that have an error status. SYSSER=service-name Selects data by service name. /WIDE Provides for a display of logged information up to 132 columns wide. 3 Description The ANALYZE/SSLOG command displays the collected logged data. Note that a system service log must be analyzed on the same platform type as the one on which it was created; for example, a log created on an OpenVMS Alpha system must be analyzed on an OpenVMS Alpha system. For examples with explanations, see the System Service Logging chapter of the VSI OpenVMS System Analysis Tools Manual. 2 /SYSTEM Invokes the System Dump Analyzer utility, which analyzes a running system. The /SYSTEM qualifier is required. Requires CMKRNL (change-mode-to-kernel) privilege. Also requires PFNMAP (map-by-PFN) privilege to access memory by physical address. For more information about the System Dump Analyzer utility on Alpha and Integrity server systems, see the VSI OpenVMS System Analysis Tools Manual or online help. Format: ANALYZE/SYSTEM 3 /SYMBOL Specifies an alternate system symbol table for SDA to use. Format: ANALYZE/SYSTEM/SYMBOL=system-symbol-table system-symbol-table The file specification of the SDA system symbol table required by SDA to analyze a running system. The specified system-symbol-table must contain those symbols required by SDA to find certain locations in the executive image. On Alpha and I64 systems, if you do not specify the /SYMBOL qualifier, SDA uses SDA$READ_DIR:SYS$BASE_IMAGE.EXE to load system symbols into the SDA symbol table. On VAX systems, if you do not specify the /SYMBOL qualifier, SDA uses SYS$SYSTEM:SYS.STB by default. When you specify the /SYMBOL qualifier, SDA assumes the default disk and directory to be SYS$DISK and [default-dir]; that is, the disk and directory specified in your last SET DEFAULT command. If no device and directory are given in the file name and the file is not found in the current default directory, SDA attempts to open the file SDA$READ_DIR:filename.type. If no type has been given in the file name, SDA assumes .EXE. If you specify a file for this parameter that is not a system symbol table, SDA halts with a fatal error. 3 Examples 1. $ ANALYZE/SYSTEM OpenVMS (TM) system analyzer SDA> This command invokes SDA to analyze the running system. 2. On Alpha and I64 systems: $ ANALYZE/SYSTEM/SYMBOL=SDA$READ_DIR:SYS$BASE_IMAGE.EXE SYS$SYSTEM This command invokes SDA to analyze the running system, using the base image in SDA$READ_DIR. 3. On VAX systems: $ ANALYZE/SYSTEM/SYMBOL=SYS$CRASH:SYS.STB SYS$SYSTEM This command invokes SDA to analyze the running system, using the system symbol table at SYS$CRASH:SYS.STB.