Use the name of the looping process to classify the failure. If the looping process is a service execution process (cassi on Windows and cassi32 on UNIX, but referred to in the remainder of this chapter as cassi), the loop could either be in an enterprise server subsystem or in the application; look at the active trace dataset and the system trace table from the dump X dataset to determine which module last got control. If it was the application, consider using FaultFind on the process to acquire more information on the next occurrence of the failure.
If the looping process is cassi but the last module to get control was not part of the application, or if the looping process is not cassi, you should refer the problem to Micro Focus technical support.