STM: Overview

STM Overview: FAQs
General questions:
What happened to SYSDIAG?
What happened to sysmap?
How do I get memory (or CPU or I/O) configuration if sysmap is gone?
How do I look at logs? (What happened to logtool?)
Exactly which STM tool should I use in place of the XXXX SYSDIAG diagnostic? ANSWER: See "STM Replacement
Tools for SYSDIAG". 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)?
Problems
Entries in the system map are labeled "Unknown."
When I execute the map command in cstm, I get an error message saying "map disabled".
When I use any of the print commands in cstm, the output always goes to LP. How can I get cstm to print to a different
printer?
Cannot start the STM interface.
Interface problems with mstm (the menu-based interface). For example, the soft keys or device selection mechanism
don't work.
Logtool displays some some I/O entries as a hex dump rather than decoding them.
When I run cstm's map command, the DGCC2300WD disk array is marked as unknown.
When I try to run cstm or mstm, I get an error saying "Program requires more capabilities..."
What happened to SYSDIAG?
As of MPE/iX 6.5, the SYSDIAG online diagnostic platform has been replaced by the STM diagnostic platform. (SYSDIAG
was known internally as "Sherlock.") See "MPE/iX Version of STM". Please visit the BSC MPE/iX
document collection for
additional information.
What happened to sysmap?
SYSDIAG tools like sysmap are no longer available on MPE/iX 6.5 and later, since the SYSDIAG online diagnostic platform
has been replaced by STM. However, similar functionality exists under STM.
For example, in the SYSDIAG platform, you could get a system map display by entering
iomap. You can get a similar display
in STM by entering the command
cstm, then at the cstm prompt entering the command map. With mstm, you can get a system

Summary of content (13 pages)