Exception traces

Exception tracing is always performed by the Web User Interface server when it detects an exceptional condition.

The goal of this type of trace is first failure data capture, to capture data that might be relevant to the exception as soon as possible after it has been detected.

Exception tracing cannot be disabled and all exception trace points are always active.

First-failure data capture is provided in two ways, as follows:
  • Unexpected CICS and CICSPlex SM responses and other detectable error conditions will result in non-maskable trace records being written.
  • Errors such as program checks and abends will also result in a system dump and abend operator messages.


eyus1c0016.html | Timestamp icon Last updated: Monday, 5 June 2017