From Application Event log--"Faulting application rexx.exe, version 126.96.36.19968, faulting module rexx.dll, version 188.8.131.5268, fault address 0x000322c3."
After this crash no rexx code is executed. I have an app that spawns short runnning rexx routines. After the crash rexx routines start but not executing. They will stay in memory until the server runs out of memory (at about 600 rexx processes) and crashes. If I get on in time to kill all rxapi.exe processes then everything goes back to normal without a change to the application. I have a monitor now that kills rxapi.exe processes when the number of rexx processes reaches a threshold--it seems to help. I need a resolution until my management forces me to get away from rexx as an unsupported product. This started happening after I upgraded from 3.2.0 to 4.0.0 (really bad problems) and then to 4.0.1. The current release is better but I still have a problem about twice a week.