STM: Tutorial

When errors occur that prevent the UI from functioning correctly, look in the UI Activity Log:
File --> UI Activity Log
The UI Activity Log contains errors logged by the UI.
If diagmond does not start up, look in the Syslog:
File --> Administration --> Local UUT Logs --> syslog
The Syslog contains information and errors logged by a variety of HP-UX programs.
To check for hardware errors, especially when experiencing hardware-related problems, look in the OS
Error Logs:
Tools --> Utility --> Run…
Select logtool
The OS Error Logs contain information logged by I/O drivers and some other OS components.
STM Tutorial: Variations
STM is easy to use because each test is run under the same basic paradigm:
1. Select the devices to test.
2. Run a tool (test) on the devices.
3. Examine the results.
You can increase your control over the test process by making simple variations to this paradigm. For example:
Options, for example, to run tools in special modes or for certain lengths of time.
Remote operation
Commands to select classes of devices or all devices.
Interactive tools
To show how you might use STM's more advanced features, consider an example. Let's say your system has an
intermittent problem that seems to appear at random intervals in different parts of the system. To smoke out the
problem, you might want to run exercisers on all devices in the system for 20 hours:
You could select all the devices in the system map by clicking each one of them in turn. A faster way is to use the
"Select All" command:
xstm: Device | Select All
mstm: Device | Select | All
cstm:
selall