Unexpected transaction abend ASP7

The unit of work that an event originated from is backed out with transaction abend code ASP7 when a synchronous event cannot be emitted.

Transaction abend (abnormal end) code ASP7 can be logged for reasons other than event processing, so the first task is to find out whether event processing caused the event to end abnormally.

  • Check for exception trace entry AP 05AE, which is displayed in the log shortly before the abnormal end. If this exception trace entry is not displayed, the abnormal end was caused by something other than event processing.
  • If exception trace entry AP 05AE is logged, check the CICS® message log for message DFHEC1022; this message contains the name of the related event binding.
    Note: For long-running transactions, message DFHEC1022 might appear long before transaction abend code ASP7 because the message occurs only when the first synchronous event in the unit of work cannot be emitted, while the abend code occurs only when the unit of work is committed.
  • If you do not expect the named event binding to cause events to be captured from the failing unit of work, review the filters of the CAPTURESPECS in the event binding. Change the filters to prevent the unwanted events and deploy the changed event binding to CICS.
  • If you expect the named event binding to cause events to be captured from the failing unit of work, examine the CICS message log and the CICS exception trace just before message DFHEC1022 to see why the event was not emitted.

    Exception trace entry 040A indicates that the link to the EP adapter failed and why. One possibility is that the EP adapter program is not enabled or defined to CICS. Another possibility is an EP adapter abend code, which indicates that the EP adapter detected an error. When the EP adapter detects an error, the IBM-supplied EP adapters generate both messages and exception trace entries to describe the problem in more detail.

    Common problems that are detected by EP adapters:
    • Message queues are not defined.
    • A message queue is defined with characteristics that are incorrect for the type of event.

    Correct the problem that is indicated and run your program again to capture the events correctly.