Capture data is missing or incorrect

A capture specification can specify one or more items of data to be captured with an event; however, there are situations that can cause data items to be missed in the capture.

For example, any of the following circumstances could cause data items to be missed:
  • The data item is from an optional parameter that is not present.
  • The data item is from a channel or container that is not present.
  • The data item is from a container, communication area (COMMAREA), or data area that is too short to contain the data item.
In each of these cases, a level 2 trace for EC contains an ECEC EVENT trace record with UNAVAILABLE_DATA and the name of the source of the data. Examine earlier trace records to determine the relevant capture specification (CAPTURESPEC) and capture point. Perhaps an event is not required if that capture data is unavailable, in which case you can add a suitable predicate to the filter and redeploy the bundle that contains the CAPTURESPEC. However, if the events are required and some capture data is not available, you must configure the event consumer to handle this situation correctly.
Incorrect capture data can be caused by these situations:
  • Incorrect filtering. If your capture specification is too generic, you might be trying to capture data from commands that you did not intend to enable for events, or from records whose layout does not match the capture specification. For example: you might be filtering on all WRITE FILE commands where the file name starts with AB but where you did not intend to capture data from the write to file ABC. Or when capturing events on WRITE FILE (ABC) and more than one record format is written to the file, you might have to filter on the record format to extract data items from the record correctly. A level 1 and 2 trace for EI and EC components can help to identify this situation.
  • Incorrect capture data specification. For example: the data is being captured from the wrong parameter or container, or with the wrong offset, length, or both. In this situation, a dump formatted for EC to check the required capture data item ECCD: is useful.


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