Steve Belkacem <[log in to unmask]> wrote:

>We have an automated ABORTJOB on our HP. Sometimes we
>can't kill sessions. I know the HP line of using
>NSCONTROL KILLSESS before the ABORTJOB cammand , but
>this is not practical as the KILLSESS command requires
>the session number(ABORTJOB is within MPEX).
>
>Dropping the LAN did not work the other night and I
>had to SHUTDOWN and RESTART the system . This ain't my
>idea of fun.
>
>This is also a TELNET session, which I believe talks
>to the HP differently than standard NS/VT sessions.
>
>Has anyone got a magic way of getting rid of one of my
>major pains?

Not magic, really... Did you kill the JINETD job? I believe Telnet sessions
require this job to be running in order to connect/stay connected. If you did
that and the session *still* didn't go away, maybe it *is* magic!

Patrick
--
Patrick Santucci
Technical Services Analyst
Seabury & Smith, Inc.