HP OpenVMS Systems Documentation

HP OpenVMS System Management Utilities Reference Manual

Table 7-5 shows BACKUP command formats for copy operations, including some of the qualifiers you can use with a copy operation.

Table 7-6 shows BACKUP command formats for compare operations, including some of the qualifiers you can use with a compare operation.

Table 7-7 shows BACKUP command formats for a list operation, including some of the qualifiers you can use with a list operation.

On VAX systems, you can use the Crash Log Utility Extractor (CLUE) to display the contents of a crash history file. The crash history file, which is created and updated by CLUE, contains key parameters from crash dump files. Unlike crash dumps, which are overwritten with each system failure (crash) and are therefore typically available only for the most recent failure, the crash history file is a permanent record of system failures. By examining the contents of the crash history file with the CLUE/DISPLAY command, you can understand and resolve the issues responsible for some crashes and you can also obtain other useful data.

On Alpha and I64 systems, CLUE features are provided through System Dump Analyzer (SDA) utility commands. For more information, see the OpenVMS Alpha System Dump Analyzer Utility Manual.

8.2 CLUE Usage Summary (VAX Only)

When a system fails, physical memory is copied to the crash dump file, and CLUE automatically appends the relevant parameters to a file named CLUE$OUTPUT:CLUE$HISTORY.DATA. You can use CLUE to display and examine the data in this file.

Format

CLUE /DISPLAY

Parameters

None.

Description

Before you run CLUE, define the CLUE command (either interactively or in a procedure such as a login command procedure), as follows:

$ CLUE :== $CLUE

To invoke CLUE, enter the CLUE/DISPLAY command. To terminate CLUE, enter the EXIT command at the CLUE_DISPLAY> prompt or press Ctrl/Z.

Note that you can also issue CLUE/DISPLAY commands directly from DCL, as in the following example:

$ CLUE/DISPLAY = DIR/TYPE=INVEXCEPTN/SINCE=21-NOV-2002/OUT=CLUE.LIS

This section describes and provides examples of the CLUE /DISPLAY commands. You can abbreviate any command, keyword, or qualifier as long as the abbreviation is not ambiguous. The asterisk and the percent sign can be used as wildcard characters in the specification of user names, node names, and UICs.

The following table lists the commands described in this section:

Deletes an entry from the list and writes the remaining entries to a binary file.

Format

DELETE n

Parameter

n

The number of the entry that you want to delete from the crash history file. The number of the entry corresponds to the entry number shown by the DIRECTORY command.

Description

Entries in the CLUE.BIN file can be permanently removed using the DELETE command. This command deletes the specified entry and writes the remaining entries to an output file. When an entry is deleted from the crash history file, a new history file (with a higher version number) is created.

Example

CLUE_DISPLAY> DELETE 4

      

Deletes the fourth entry in the list.

Displays a brief summary of each entry in the crash history file.

Format

DIRECTORY

Qualifiers

/MODULE=

Lists all failures that correspond to the specified module (that is, failures that start with the specified string).

/OFFSET=

Lists all failures that correspond to the specified offset (that is, failures that start with the specified string).

/SINCE=

Lists all failures that have occurred since the specified date. If the /SINCE qualifier is used and no date is specified, all failures that have occurred on the current day are listed.

/TYPE=

Lists all failures that correspond to the specified type (that is, failures that start with the specified string).

Description

The DIRECTORY command lists the record entries in the crash history file, beginning with the most recent entry. Six headings are displayed for each entry:

• Entry number
• Date and time of crash
• Type
• Process
• Module
• Offset

You can use one or more qualifiers for the DIRECTORY command to limit the crash entries that are displayed. You can also use more than one qualifier in the same command line. For example, the command DIRECTORY/SINCE=18-APR-2002/MODULE=NETACP lists only those crash entries that have taken place since April 18, 2002, and for which the module is NETACP.

Examples

CLUE_DISPLAY> DIRECTORY





  

    

      

      




#  Time                      Type         Process name   Module   Offset
   ====                      ==========   ============   ======   ======
1  11-JUL-2002 09:07:45.78  INVEXCEPTN   batman         NETACP   14B9
2  01-JAN-2002 11:32:55.23  SSRVEXCEPT   startrek       SYSLOA   10A8
3  15-MAY-2002 07:26:12.34  BADFID       evolushun      NONE     NONE
4  22-APR-2002 10:45:20.60  INVEXCEPTN   aprocess       IOBUF    015D





      

This example lists all entries in the crash history file.

CLUE_DISPLAY> DIRECTORY /MODULE=SYSLOA






  

    

      

      




#  Time                      Type         Process name   Module   Offset
   ====                      ==========   ============   ======   ======
2  01-JAN-2002 11:32:55.23  SSRVEXCEPT   startrek       SYSLOA   10A8





      

This example lists only those entries for which the module is SYSLOA.

Exits from CLUE.

Format

EXIT

Description

This command exits from CLUE and returns you to the DCL level.

Example

CLUE_DISPLAY> EXIT
$
      

This example exits from CLUE.

Extracts all of the data from an entry in the crash history file to either an ASCII or a binary file.

Format

EXTRACT n

Parameter

n

The number of the entry that you want to extract to a file. The number of the entry corresponds to the entry number shown by the DIRECTORY command.

Qualifiers

/BINARY=filename.bin

The /BINARY qualifier writes the output to a binary file.

/OUTPUT=filename.txt

The /OUTPUT qualifier writes the output to an ASCII file. The /OUTPUT qualifier is the default.

Description

Use the EXTRACT command to save record entries from the crash history file to an ASCII or a binary file. If no qualifier is used, entry is written to a text file with the name CLUE$HISTORY.TXT.

Example

CLUE_DISPLAY> EXTRACT 3 /OUTPUT=15MAYCRASH.TXT

      

This command writes the data from entry number 3 in the crash history file to an ASCII file named 15MAYCRASH.TXT.

Provides online help for CLUE commands.

Format

HELP [command]

Parameter

command

The command for which you want help.

Example

CLUE_DISPLAY> HELP DIRECTORY

      

This command provides online help for the DIRECTORY command in CLUE.

Displays specific information for an entry in the crash history file.

Format

SHOW info_type n

Parameters

info_type

You must choose one of the following information types:

• CRASH---displays information similar to the SHOW CRASH command in the System Dump Analyzer (SDA) utility.
• STACK---displays information similar to the SHOW STACK command in SDA.
• EXEC---displays information similar to the SHOW EXEC and SHOW DEVICE commands in SDA.
• ISTREAM---displays the instruction stream around the failing PC.
• SUMMARY---displays the active processes on the system, similar to the SHOW SUMMARY/IMAGE command in SDA.
• ALL---displays all the information from the preceding types.

For more information about SDA commands, see the OpenVMS VAX System Dump Analyzer Utility Manual.

n

The number of the entry for which you want to display information. The number of the entry corresponds to the entry number shown by the DIRECTORY command.

Description

This command lets you see all the data associated with a particular failure. This information is split into several sections; you can choose to see either individual sections or all of the information.

If the crash number is not specified, information for the most recent entry in the crash history file is displayed. You must, however, specify one of the keywords for info_type.

If you request a specific entry from the crash history list (using the SHOW n command), the display will include some parameters that are useful only to HP service representatives.

Examples

CLUE_DISPLAY> SHOW ISTREAM 4





  

    

      

      





Instructions around the failing PC:

    80A9F841 RSB
    80A9F842 BUG_CHECK #019C
    80A9F846 BUG_CHECK #019C
    80A9F84A PUSHL   R4
    80A9F84C MOVL    R5,R4
    80A9F84F BEQL    00002C88

    80A9F851 JSB     @#-7FFFCC48
    80A9F857 MOVL    (SP)+,R4
    80A9F85A RSB
    80A9F85B BUG_CHECK #019C
PC->80A9F85F BUG_CHECK #019C  => CLUSTRLOA + 09B6F
    80A9F863 MOVL    #00,R1
    80A9F866 MOVB    #01,R0
    80A9F869 RSB
    80A9F86A INCL    00002301
    80A9F86E TSTW    000022FF
    80A9F872 BLSS    00002CA5




      

This example displays instruction stream information around the failing PC from the crash history file for entry number 4.

CLUE_DISPLAY> SHOW CRASH 4





  

    

      

      




Time of system crash:              21-MAR-2002 15:21:33.72
Version of system:                 VAX/VMS VERSION V7.3-1
System Version Major ID/Minor ID:  1/0
VAXcluster node:                   HERMES, a VAX 6000-420
Crash CPU ID/Primary CPU ID:       03/01
Bitmask of CPUs active/available:  0000000A/0000000A
CPU bugcheck codes:                CPU 03     INCONSTATE
                                  1 other    CPUEXIT
Current Process name:              OPCOM
Current IPL:                       8
CPU database address:              801AA000

General registers:

 R0  = 80A9F85B   R1  = 00000002   R2  = 80A15B08   R3  = 00010008
 R4  = 80A15AD0   R5  = 00000000   R6  = 00000001   R7  = 00000042
 R8  = 00022520   R9  = 00020F18   R10 = 00021000   R11 = 00020EC0
   .
   .
   .




      

This example displays information about the state of the system at the time of the failure. The actual output from this command may contain significantly more information than is shown in this example.