If you have a failure at run time that is consistently reproducible then we suggest that when reporting the incident you include the following:
- The code necessary to reproduce the failure – this should be cut down as much as possible.
- Any data needed to reproduce the failure.
- The details of what the failure actually is; the run-time error message, a corruption, or that the code is not behaving as you expect.
- Set the appropriate first point of failure diagnostics; adjust them based on your own judgement as to what you believe will help us to understand and diagnose the problem – for instance, if it is a File Handler problem, refer to that section for possible additional tracing; if a memory corruption seems to be occurring, consider the memory strategy settings.
- Collect the output from the run, using the MFESdiags script.
- Report the problem to
Micro Focus, and upload the diagnostics captured by the MFESdiags script, using the naming conventions recommended.
-
We would also be happy to hear of any hypothesis or theory that you have that might help us to address the failure more quickly.
