sting(1)

NAME
     sting - Compositor (CBOB) Diagnostic Software

SYNOPSIS
     sting [ options ...]

DESCRIPTION
     The sting program is the diagnostic software for Compositor (CBOB)
     manufacturing test, stress and burn-in, field service hardware diagnosis,
     and component fault isolation.

     Sting is an on-line diagnostic tool running under IRIX. It is driven
     purely via command-line options during invocation.

     The output of sting is in a standardized format to allow easy parsing of
     results.  See the OUTPUT section.

     IRIX must be running in order to run sting. The diagnostic works in two
     modes. When the X server is not running, only the subset of the tests
     that does not require the X server will be executed. When the X server is
     running, all tests can be executed.

     The user must have root privilege to run sting.  Stng cannot be run from
     the graphics displays that are driving the Compositor. It should be run
     from either a remote shell or the diagnostic terminal.

EXAMPLE
     To run all standard Compositor tests:

     sting

     To run only the CCX (Compositor Control) Xilinx tests:

     sting -ccx

     After running sting (assuming no hardware failures that would preclude
     the window system from running), X should keep running as before.

OPTIONS
     Sting options are selected with one of four syntaxes:  ``minus'' options
     select tests to execute and access to other common options (examples:  -
     video, -forever); ``equal'' options assign values to a sting parameter
     (example: IMAGE_TYPE=2); ``plus'' options which provide access to
     generally undocumented options; and ''minus minus'' options remove tests
     from the selected list of tests to execute.

     General options. These are some of the most frequently used options under
     sting. For more options use -help.

     -help           Comprehensive interactive help menu. Provides help on
                     test, system and user options.
     -continue       Continue testing when a failure occurs.  Normal behavior
                     is to stop on first failure.  The -cont and -c also work.

     -forever        Loop over the specified tests until interrupted by ctrl-C
                     or until a failure occurs (see -continue ).

     DEBUG=# or -debug #
                     Enable output of debug messages at less than or equal to
                     # (where # is between 0 and 9 inclusive).

     REPEAT=#        Number of repetitions through all selected tests.

     irsaudit -help

OUTPUT
     The output format is line based.  Lines are no more than 80 characters in
     length (customizable by cmd line opts).  Each line is tagged by one of
     the following four-character identifiers:

     TEST    Test start markers, generated at the beginning of a test.
             Indicates the test's symbolic name and description.  All
             following lines up to the next TEST line are associated with the
             named test.

             Columns  1- 4: "TEST"
             Columns  6-25: test symbolic name
             Columns 26-80: test description

     RSLT    Test result, generated at the end of a test.  Indicates the
             test's symbolic name and the test result.  The result will be one
             of pass, fail, unresolved, or untested.

             Columns  1- 4: "RSLT"
             Columns  6-25: test symbolic name
             Columns 26-30: "PASS" | "FAIL" | "UNRESOLVED" | "UNTESTED"
             Columns 41-80: optional short explanation

     ERROR   When an error occurs, it will be reported using the following
             format:  Columns  1- 9: "*** ERROR"
             Columns  10-25: error code (for database keying)
             Columns 26-80: test description

     INFO    Information which is useful to an advanced user of the
             diagnostic.  This can include test progress reports, exp/rcv
             pairs, etc.  INFO messages are enabled by the -info command line
             option.

             Columns  1- 4: "INFO"
             Columns 25-80: informational message

     DBUG    Debugging information, only generated when debugging output is
             turned on (not the default); not intended for field or
             manufacturing use but may be useful to diagnostic programmers.
             DBUG messages are enabled by the -debug command line option.

             Columns  1- 4: "DBUG"
             Column      6: debugging level, one through nine
             Columns 25-80: debugging message

     TIME    Time stamp, generated at important time boundaries such as the
             beginning and end of irsaudit.

             Columns  1- 4: "TIME"
             Columns  6-33: Unix style date

     META    Summarizes information over several tests.  A table is generated
             providing the pass and fail counts of each test (and totals over
             all tests) across multiple full test loops.

             Columns  1- 4: "META"
             Columns 25-80: summary statistics

     /usr/diags/compositor/bin/sting
                                   executable for Compositor (CBOB)
                                   diagnostics.
     /usr/diags/compositor/doc     the Compositor (CBOB) diagnostics user
                                   manual.

KNOWN BUGS