[Info-vax] DEC server monitoring and alerting

[Jan-Erik Soderholm]

Bob Koehler wrote 2012-05-16 16:04:
> In article<fff401b5-a37e-4f10-820a-ca7e2dd7573b at l5g2000vbo.googlegroups.com>, John Wallace<johnwallace4 at yahoo.co.uk>  writes:
>>
>> There are lots of other options too, given more info on your actual
>> interests. TSM, as suggested by Henry, is a good one which *should*
>> work on a DECserver 100.
>
>     Well, TSM should work on any product described as a "terminal server"
>     that comes under the category DECserver.  But without more
>     information from the OP I can't even tell which protocol is important
>     to him.
>
>     IIRC, DECserver 100 only supported LAT, but later models supported
>     TCP/IP, and it's possible that only TCP/IP is important to the OP.
>
>     Meanwhile, programming something in DCL is probably unreasonable,
>     but there are likely to be DCL commands that can get close enough.
>     And the OP expressed an interest in storing something in a file
>     without giving a clear concept of what data and how it would be used.
>

As far as I know, TSM uses plain DCL to analyze the result of SHOW PORT
commands and save the equivalent SET/DEF PORT commands in a text file
that can be run against a new term.server to recreate the setup.

Nothing fancy there.

It was 15 (?) years ago that a DECServer *100* was the wrong
DECServer for more or less everyone. Wasn't it replaced by the
200 long before that?