Randy Smith wrote:
> We have had a similar problem with our boxes ever since we moved
> to 5.0.  Here's what we do to solve the problem:
> 1)  TERMDSM the port 3 or more times
> 2)  FILE RESTPORT;DEV=portid
> 3)  ECHO press return to continue >>*RESTPORT  (do that a few times)
 
I've "discovered" the same thing, except that we use DTC Manager.  The
ports will often show up "Not Available" when you show connections for the
offending SIC (port card).  The *MOST* annoying part of this is that DTC
Manager does not generate an alarm for this situation and you have no
clue the port is hung up (though show connections is aware, if you manually
display them).
 
> Sometimes all it will take is a TERMDSM.  Sometimes all it will take is
> just the ECHO.  Sometimes we use the formula.  Sometimes we try
> a variation on the formula.  For instance, sometimes the ECHO will
> hang the session that issued it.  We start another session and do
> the echo again and that cleared it up.
 
Sometimes it hangs the session, sometimes it gets a "device unavailable"
type of error.  Further, sometimes a DTC Manager port reset (twice) clears
the port.  On 5.5, this clears 3-pin direct ports but sometimes not a modem
port.  On the "hung" ports, the port often acts like loopback (it echoes
input back), and break produces a linefeed.
 
> All things considered, once we started doing those types of things,
> we haven't had to reboot due to terminal hangs.
 
Power-cycling the DTC occasionally clears this up as well.
 
Jeff Kell <[log in to unmask]>