Yes, due to Windows architecture, we have not a good way to bring UV's debugger into the picture from another process. However, UNIX is another story... Regards, LeRoy F. Dreyfuss Advanced Technical Services - UniVerse IBM U2 Data Management Solutions Tel: 303-672-1254 Fax: 303-294-4832 Mobile: 720-341-4317 External email: [EMAIL PROTECTED] WWW: http://www.ibm.com/software/data/u2/support www.ibm.com/software/data/u2/support - Open, Query, Update, Search - Online! HENDERSON MICHAEL MR <MICHAEL.HENDERSO To [EMAIL PROTECTED]> "'U2 Users Discussion List'" Sent by: <[EMAIL PROTECTED]> u2-users-bounces@ cc oliver.com Subject RE: UNCLASSIFIED RE: How to safely 03/10/2004 02:46 kill a runaway UniVerse (was u AM nidata) process Please respond to U2 Users Discussion List Sorry LeRoy, I have confused you! I don't have any problem killing a UniVerse task, I prefer to try this sequence "LOGOUT <pid>", then "...\uv\bin\kill <pid>", a couple of times - almost always works, then "...\uv\bin\kill -2 <pid>", then "...\uv\bin\kill -9 <pid>", then ONLY AS A LAST RESORT Task manager "Kill" What I can't do is chuck the process into the debugger, because the 'debug' option in the task manager right-button menu is greyed out. When I have a mysteriously-stuck program in the development environment, being able to throw it into the UniVerse debugger would be really useful: at least I could find out where it is and what it thinks it is doing. Maybe a debugger has to be registered for /associated with the process in some way to make this menu option visible? Since Wol said he _does_ see 'debug' in UniData, and I don't in UniVerse, maybe there's something you guys could do in the UV product to make it happen for us too? Please :-) Thanks Mike -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Leroy Dreyfuss Sent: Wednesday, 10 March 2004 12:49 a.m. To: U2 Users Discussion List Subject: Re: UNCLASSIFIED RE: How to safely kill a runaway UniVerse (was unida ta) process Actually, at release 10+, it should be successful via Windows Task Manager's kill option. UV 10 and higher use detached processes by default, and KeepAlive (for tl_server processes) was added as well. If it really becomes necessary to kill a process that for some reason has ignored its KeepAlive setting (assuming the telnet client has been disconnected from the socket), the kill.exe in uv\bin was updated in 10 to do a better job at killing processes, though it could take a few seconds to come back to the DOS prompt. I cannot recall when it hasn't work at 10.x. When all else fails, download the sysinternals.com Process Explorer and use its kill option. Remember that if you have updates pending, your open files may be at some risk. Regards, LeRoy F. Dreyfuss Advanced Technical Services - UniVerse IBM U2 Data Management Solutions Tel: 303-672-1254 Fax: 303-294-4832 Mobile: 720-341-4317 External email: [EMAIL PROTECTED] WWW: http://www.ibm.com/software/data/u2/support The information contained in this Internet Email message is intended for the addressee only and may contain privileged information, but not necessarily the official views or opinions of the New Zealand Defence Force. If you are not the intended recipient you must not use, disclose, copy or distribute this message or the information in it. If you have received this message in error, please Email or telephone the sender immediately. -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
-- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
