7.1 How to identify disconnected client sessid

I have seen this occur on numerous occassions, where a client connected with a nettype of soctcp aborts (ie the PC is rebooted, power lost, etc). The sessid is still active and if holding a lock presents some problems. T date, all that I have found to rectify the problem is to have that client disconnect (if they have already re-connected) and then use the onmode -Z and onmode -z commands to terminate the transactions and the sessid, thus removing any locks and freeing up memory used by that session. Is there a way to identify a sessid that is inactive? I intentionally had one of our developers shut his system off while connected, watching the process for the rest of the day showed no sign of change. I expected that at some point the onstat -g ath would show some status change for that particular thread, but it didn't. Any ideas? Environment: INFORMIX 7.10.UD1 HP-UX 9.04 I-NET for Windows 5.01 Powerbuilder 4.0 Windows for Workgroups 3.11 HP Vectr 5/75 Regards -- RJC Enterprises 72242.111@compuserve.com ____ ____ ___ __ ____ _ _ ____ ____ ____ ( _ \\ (_ _) / __)( ) (_ _)( \\( )( ___) (_ _)(_ _) rcline@netcom.com ) / .-_)( ( (__ )(__ _)(_ ) ( )__) _)(_ _)(_ (_)\\_) \\____) \\___)(____)(____)(_)\\_)(____) (____)(____) Semper Fi