STM: Overview

physically present on the system. STM lists these phantom entries on the system map, but cannot get any information from the
non-existent devices to which they point. Consequently STM has to label these entries as "Unknown".
If having phantom entries in the system map is a problem for you, use the SYSGEN utility to remove the non-existent devices
from the system configuration files.
When I execute the
map command in cstm, I get an error message saying "map disabled".
This problem can arise if the system does not have loop configured through nmmgr. You can verify this as follows:
:netcontrol status;net=loop
THE ENTITY IS NOT ACTIVE. (NETXPORTERR 4054)
Encountered one or more errors while processing command. (CIERR 4436)
The solution is to configure in loop. If networking is properly configured, loop should be present.
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?
cstm looks for a file equation for "stmlp". If a file equation is not present when cstm is run, cstm will use the file equation
"file stmlp;dev=lp". To print to a printer other than LP, create a file equation for "stmlp" before running cstm.
Cannot start the STM interface.
If you cannot start the STM interface:
The most likely cause is that networking is not configured and enabled for remote access. Because STM uses Berkeley
Sockets/iX , STM requires networking to be configured and enabled for remote access via the NMMGR and NETCONTROL
commands before it can run. See "STM Dependencies on MPE/iX". Please visit the BSC MPE/iX
document collection for
additional information.
Symptoms: If you try to start STM by typing
cstm, you will see the following error message:
Unable to start the STM User Interface.
Failed to initialize the main window.
Possible Causes:
Internal Application error.
If console logging is enabled, you can see the following message in the system log files:
STM system manager is waiting for networking to startup.
This message was sent to the console shortly after boot to indicate that STM was idle and waiting for networking to come up.
In this state, you will not be able to access any of the tools and all of the diagnostic logging is disabled.
Another possible cause for not being able to start the STM user interface is that you are trying to run it too soon after
installation. During an installation of MPE/iX, a Customized System Load Tape (CSLT) is generated and is used to update the
system. The system is then rebooted. The STM interface (e.g.
cstm) is only fully enabled after this reboot.
If you try to run the STM user interface before the reboot, you may get an "Unknown Command" or other error message.
Interface problems with mstm (the menu-based interface). For example, the soft keys or device selection mechanism
don't work.
An early version of the mstm (menu) interface is included with MPE/iX 6.5. Testing indicates that mstm works correctly for
all configurations except for hardwired terminals connected to the console port. The configurations that work correctly include