STM: Overview

map automatically by entering the command
mstm
at the MPE/iX prompt.
How do I get memory (or CPU or I/O) configuration if sysmap is gone?
In the SYSDIAG online diagnostic platform, you could get memory and CPU configuration information with the
memmap and
cpumap commands under sysmap.
Similar configuration information is available through STM. To get configuration information on any module in the system
map (memory, CPU or some I/O devices), select the desired module, then run the "Info" tool. In cstm:
1. Enter the command
map to display a system.
2. See what device number the device has. Select the desired device with the command:
select device DEVICE_NUMBER
3. Run the information tool on the selected device by entering the command information.
4. Look at the results by entering the command
infolog.
How do I look at logs? (What happened to logtool?)
Under the old SYSDIAG online diagnostic platform, the logtool utility was used to examine all logs. With STM, two different
versions of logtool are used:
STM version:
Coverage: I/O and hardware-related logs (I/O events, LPMCs, memory, etc.)
To start:
cstm: enter runutil. When prompted, choose logtool.
mstm: from the Tools pulldown menu, choose Utility, then Run. When prompted, choose Logtool.
Documentation: See the logtool Web pages in the "Online Diagnostics: Individual Tools" section of Diagnostics
home site.
Standalone version (similar to the old SYSDIAG logtool)
Coverage: System logs (e.g. auditing, security, etc.) not covered by the STM version of logtool.
To start: enter the command logtool at the MPE/iX prompt.
Documentation: "Standalone Logtool for MPE/iX". Please visit the BSC MPE/iX document collection for
additional information.
Why does STM use networking sockets (AF_INET) rather than local sockets (AF_UNIX)?
STM implemented its inter-process communication using AF_INET sockets to fulfill the requirement that communication
between the User Interface (UI) and the rest of the system be able to occur remotely. This means that a UI running on a local
system can connect to STM running on a remote system. This capability allows the UI to be connected to multiple systems
running STM, both local and remote, and control and run tests on each of those systems at the same time.
The STM developers did not want to implement a separate communication mechanism between the UI and STM for local and
remote connections.
The ability to run STM on a remote system has not been tested on the initial release (MPE/iX 6.5). This feature is planned to
be formally released in an upcoming version of MPE/iX.
The HP-UX version of STM also implements inter-process conmmunication using AF_INET sockets.
Entries in the system map are labeled "Unknown.
Many MPE/iX systems are "over-configured", that is, their configuration files have more entries for devices than are