Endless loops on abstract quitting?

Hello netters! My system is I-OnLine 4.1 with I-4GL RDS on an IBM R-6000 320 AIX 3.1 with users coming in through ethernet. Now sometimes when they quit abstractly (like turning off the terminal/computer without quiting the system or breaking out with ctrl-c or somesuch) the 'fglgo' process goes into an endless loop eating up all the cpu it can get. When first I set up the connection for the users I ran the program with the 'exec' command and this problem happened all the time. Then I stopped using the 'exec' command and let the programs run in their own shell and now it only happens once in a while. My guru suggested that what happens is that a read command gets an 'eof' message when the connection breaks but doesn't get or doesn't interpret correctly the exit code that says the connections dead. Has anyone had a similar problem, and maybe an explanation and a fix? Any help greatly appreciated, Gaukur. gaukur@rhi.hi.is