[Info-vax] DEC server monitoring and alerting

[Jan-Erik Soderholm]

CY wrote 2012-05-16 18:02:
> Wonderful, Im not alone with those, but only DS200 as the 100 has been
> replaced (better with 200, nope - but it feels better). Now replacing
> the 200  with 90. And when only 90s then move frpm LAT to raw TCP.
>
> Anyway, mc latcp sho port using LAT and investigate the output with
> DCL.

If you are refering to the post where I wrote about SHO PORT as
a way to save a term.server configuration, that is the SHO PORT
command *on the server* itself, not from LATCP !

The script in TSM first does a MCR CON NODE... to get into the
term.server, *then* a SHO PORT. Now, it must have been over
20 yrs since I looked at the TSM scripts, but anyway... :-)

Sorry if I was unclear.

Jan-Erik.


>
> I have an suspicion that the LAT port might seem to be connected or
> active as latcp would say but still dead.
>
> The best way IMHO is if the program using the lat ports frequently
> also generate a alarm if no data is returned.
>
> Good luck!