STM: Tutorial

into problems, press the "Break" key, then enter "ABORT" at the MPE/iX prompt.
All STM functionality is currently available from the cstm (command-line) interface.
STM Dependencies on MPE/iX
The Support Tools Manager (STM) is loaded onto the MPE/iX 6.5 system via the Fundamental Operating System (FOS)
tape and relies on certain MPE/iX features for its operation.
This page describes the MPE/iX features on which STM is dependent, and the consequences to STM if any of these
features are altered, disabled, or removed.
CAUTION: STM is dependent on Berkeley Sockets/iX. Without this feature, STM will be completely disabled.
STM uses the Berkeley Sockets/iX to make socket system calls using the address family of AF_INET. Sockets/iX,
in turn, requires that a supported networking link product be installed on the system.
NOTE: Networking sockets (AF_INET) are used by STM rather than local sockets (AF_UNIX) so that STM can
be run remotely -- with the User Interface running on a local machine and STM itself running on one or more
remote machines. This feature is planned to be introduced in an upcoming release. is planned to be formally
released in an upcoming version of MPE/iX.
This requirement usually means the system must have a network card which is configured and enabled for remote
access to the system. In general, the process involves steps similar to the following:
1. Configure the card via NMMGR. (LOOP is automatically configured.)
2. Enable the card via a NETCONTROL command.
3. Enable LOOP via another NETCONTROL command.
For details on the process, see the MPE/iX Networking documentation.
If networking is not up, STM is completed disabled. I/O, LPMC, and memory logging are disabled. Memory page
deallocation is disabled. The STM user interfaces (cstm and mstm) will not come up, and therefore, all support
tools are not accessible.
NOTE: The resolution of the node name "localhost" is necessary for STM to complete networking sockets host
name resolution to the local machine. Without "localhost" configured, STM will not be able to connect to, and
diagnose, the local computer.
STM uses the following XL/shared library files, which are also loaded via the FOS tape:
/lib/libm.sl
/usr/dt/lib/libdthelp.sl
/usr/dt/lib/libnew.sl
/usr/lib/libIO.sl
/usr/lib/libmcats.sl
/usr/lib/libmcurs.sl
/usr/lib/libsocket.sl
/lib/libsvipc.sl
/lib/libc.sl
XL.PUB.SYS
If any of these files are removed from the system, various STM program files will abort with a loader error of
unresolved externals. Again, STM will be partially or completely disabled, depending on which library is
removed.
Note: Since all XL/Shared libraries used by STM will be "busy", STM must be shut down before updating or
patching any of the XL/shared library files listed above. Otherwise these files cannot be overwritten with new
versions. Also, users must exit from all invocations of STM user interfaces (cstm or mstm). To shut down STM,
run the program
stmshut.diag.sys
.