1  CLUE_Extension
   The SDA CLUE command invokes the Crash Log Utility Extractor,
   which captures specific crash dump information and, upon system
   reboot, preserves it in a file with the following naming scheme:

        CLUE$nodename_ddmmyy_hhmm.LIS

   You enter CLUE extension commands at the SDA prompt. For example:

        SDA> CLUE CONFIG

   You can get full help on CLUE by entering HELP CLUE at the SDA>
   prompt.
 

2  Overview
   SDA CLUE (Crash Log Utility Extractor) commands automate the
   analysis of crash dumps and maintain a history of all fatal
   bugchecks on either a standalone or cluster system. You can use
   SDA CLUE commands in conjunction with SDA to collect and decode
   additional dump file information not readily accessible through
   standard SDA commands. SDA CLUE extension commands can summarize
   information provided by certain standard SDA commands and provide
   additional detail for some SDA commands. For example, SDA CLUE
   extension commands can quickly provide detailed extended QIO
   processor (XQP) summaries. You can also use SDA CLUE commands
   interactively on a running system to help identify performance
   problems.

   You can use all CLUE commands when analyzing crash dumps; the
   only CLUE commands that are not allowed when analyzing a running
   system are CLUE CRASH, CLUE ERRLOG, CLUE HISTORY, and CLUE STACK.

   When you reboot the system after a system failure, you
   automatically invoke SDA by default. To facilitate better crash
   dump analysis, SDA CLUE commands automatically capture and
   archive summary dump file information in a CLUE listing file.

   A startup command procedure initiates commands that do the
   following:

   o  Invoke SDA

   o  Issue an SDA CLUE HISTORY command

   o  Create a listing file called CLUE$nodename_ddmmyy_hhmm.LIS

   The CLUE HISTORY command adds a one-line summary entry to a
   history file and saves the following output from SDA CLUE
   commands in the listing file:

   o  Crash dump summary information

   o  System configuration

   o  Stack decoder

   o  Page and swap files

   o  Memory management statistics

   o  Process DCL recall buffer

   o  Active XQP processes

   o  XQP cache header

   The contents of this CLUE list file can help you analyze a system
   failure. If these files accumulate more space than the threshold
   allows (default is 5000 blocks), the oldest files are deleted
   until the threshold limit is reached. You can also customize this
   threshold using the CLUE$MAX_BLOCKS logical name.

   It is important to remember that CLUE$nodename_ddmmyy_hhmm.LIS
   contains only an overview of the crash dump and does not always
   contain enough information to determine the cause of the crash.

   To inhibit the running of CLUE at system startup, define the
   logical CLUE$INHIBIT in the SYLOGICALS.COM file as /SYS TRUE.