In article <[log in to unmask]>, [log in to unmask] writes >I've recently experienced two incidents where a Telnet session has ended up >in a hung state, that is, after an abortjob, the session persisted and tied >up a database. Only after a reboot was I able to clear the session. > >What causes a session to hang like this? Is there anything I can do to >prevent it? Or, what action could I take (besides a reboot) to clear the >session. > >In attempting to clear it, I tried ABORTJOB, I stopped the INETD job, I >stopped Network services, I tried a PM program to KILL specified PIN's. >Nothing worked. > >Any insight would be appreciated. > Tied up a database? Could this be your problem? If you got a deadly embrace (User A locks dataset X, asks for dataset Y, while user B already has dataset Y locked, and is waiting for dataset X), then nothing short of a reboot will clear this. And it would look like the Telnet session had hung, although any session, hardwired or not, will hang under these circumstances. When/if it happens again, use DBUTIL to look at the tied-up database and see who holds what locks, and who is waiting. Might not be a Telnet problem at all.... -- Roy Brown Phone : (01684) 291710 Fax : (01684) 291712 Affirm Ltd Email : [log in to unmask] The Great Barn, Mill St 'Have nothing on your systems that you do not TEWKESBURY GL20 5SB (UK) know to be useful, or believe to be beautiful.'