Hi Everyone :)
   Ok... I have been following all the CSTM posts (and rants) lately ... and
now I have a question!

   We are on 6.5 pp2 (latest full patch) and are running network connections
(hundreds) to both of our boxes (928 & 979/200) ... since we have terminals
connected around the NW that occasionally need to have their terminals
'reset' we rely heavily on being able to use TERMDSM at a moments notice
(picture being told that you have to wait for the "computer" to be cleared
up before you can leave after having a filling put in a tooth- the client is
not wanting to wait!)

   Below you will find what I see about 50% of the time when we fire up
CSTM.... the 'ru' command produces only a nasty message about run utilities
being disabled...I then have to shut down the functions with a 'ssd' command
and then stop the JINETD job (I use the inetd.net.sys;info="-k" command)
wait 10 minutes and start up JINETD again and then go into CSTM and issue a
'ssu' command.

   I then go into cstm and the 'ru' command is no longer disabled :) ...
TermDSM still runs dog slow!  Like it was being run on a series 44 with half
a meg of RAM  and a single processor rather than a 979/200 with 5.8 gig of
RAM!! :( :(

   I figure that we aren't going to get SysDiag back... but cstm seems not
to be ready for primetime (as Freddy would put it hehe) any hope of getting
some work done to get cstm up to the level we expect?

Thanks,
Art "you know it's bad when we read the manuals voluntarily! hehe" Bahrs

Screen Shot:
:cstm
Running Command File (/usr/sbin/stm/ui/config/.stmrc).

This operation may take approximately one minute.

Waiting to obtain host information from the local host localhost.
The diagnostic daemon "diagmond" may have been started recently and is busy
building the device map.

If this message persists for a long time, it is possible that either the
diagnostic daemon is not running, or that networking is improperly
configured.

If you cancel this message, the User Interface (UI) will not automatically
connect to a Unit Under Test (UUT).  It will be necessary to use the Select
Current System command in the System menu to attach the UI to a UUT.

-- Error --
An unexpected error was encountered while attempting to retrieve the
host info for hostname (localhost).
This could be due to either of the following conditions:

1) The support tool daemon "diagmond" may not be running on that system.
Use the STM Startup command (in the administration menu under the
file menu.)

2) The IP address for the system may be invalid or may not be associated
with a valid host.  Use a valid IP address.

3) Networking may be incorrectly configured on one of the systems involved.

More details may be available in the System Activity Log or on
the system console on that system.

It may be necessary to access the System Activity Log using the
Local Unit Under Test (UUT) logs (in the administration menu
under the file menu.)
Please Refer to the UI Activity Log for more details.

-- Error --
An unexpected error has been encountered.
Please Refer to the UI Activity Log for more details.

-- Information --
Aborting all open command files.

cstm>ssd
-- Support Tool System Shutdown --
The Support Tool system will be shutdown.

If the local system is currently connected it will be disconnected prior to
attempting the shutdown.

The Support Tool system may only be shutdown and restarted by manager.sys.

Are you sure you want to shutdown the Support Tool system?

Enter Cancel, Help, or OK: [Cancel] ok
cstm>
cstm>
cstm>
cstm>exit
-- Exit the Support Tool Manager --
Are you sure you want to exit the Support Tool Manager?
Enter Cancel, Help, or OK: [OK] ok