Owner's Manual

30 Using Dell Online Diagnostics
Aborting Online Diagnostics in CLI Mode Using <Ctrl><C>
Using <Ctrl><C> to abort with the --show command does not cause the
action to abort. When running tests, you may use <Ctrl><C> at any point
of time during the execution sequence to stop the test. No output may be
available and the test may exit with a blank message. This may occur if the
execution of the pediags command is interrupted even before the
diagnostic test has started. If you abort a test that has already started, the test
may abort with a Test was aborted by the user result event if the
Abort feature is supported by the particular test. For multiple passes, even if
the test supports Abort, the test may not abort with the Test was aborted
by the user result event. This might occur because the multiple pass test
may have been aborted during the transition from one pass to another.
Tests that do not support the Abort feature always run to completion.
Scripting With the CLI
The Online Diagnostics CLI allows administrators to write batch programs or
execute scripts using the operating system.
Scripting enables the user to automate the schedule diagnostic of a systems
health.
In many cases, the CLI allows a user with a very well-defined task in mind
to retrieve information about the system rapidly. You can redirect the
diagnostic output to a file using the operating system’s redirection feature.
You can also use the exit codes explained in the following table when
writing scripts.
Exit codes 0, 1, and 2 are applicable for only test execution (irrespective of
multiple or single pass). The exit code is the aggregate status of all the tests
executed. For example, out of 20 tests, if there is one test with a warning
0 The test has a passed result.
1 The test has a warning result.
2 The test has a failed result.
3 The application failed because of dependency issues or runtime issues.