We have a customer site that has implemented a UNIX menu script to start their PRO-IV sessions as ksh processes. This method of starting PRO-IV seems to be fine except when the PRO-IV client's disconnects from the server abnormally, ie. due to PC reboot or network disruption. What happens then, is the ksh process starts spinning and starts using up a high amount of CPU resources. The PRO-IV timeout settings we implemented does not kick in here as the process is not idle as such as it is using up CPU.
Basically, the script goes:
echo " 1. Start Application" read -r Ans case $Ans in 1) $DIR/start_proiv_apps_script ;; esac done exit
The are running on an RS6000/AIX 4.3.
Has anyone had any experience with similar problems running PRO-IV as a ksh? Any suggestions would be greatly appreciated.