4GL "Prompt" and zombies

> To all the 4GL gurus out here: > > We have a 4GL (4GL version 4.11 and 5.01.UD4 on HP9000's) application that > is being accessed over telnet from a PC over the network. Occasionally > (we think the #*@# users are rebooting the PC), the 4GL program > becomes a zombie (top shows a ? as it's owning terminal) and the 4GL program > sucks up 95-100% of the CPU time. All the code is doing is waiting for the > user to enter data via a prompt command. > > Does anyone have any experience with this? > > Thanks, > Joe Yeah, I've seen these undead 4GL's from Hell before, and yes, it's typically because of the client being rebooted. They happened consistently enough to notice, but not consistently enough to fix. They eventually went away. I'm not sure why. The only thing that comes to mind is that our clients are more stable (don't reboot as often) and that maybe we changed our telnet program on the PC. But as a datapoint, I've seen 'em, and I've got enough of their heads on my wall to show I've killed my fair share of 'em too. Will