DFHEC1012    date time applid The CICS event capture component failed to create the EVENTBINDING resource evbname in BUNDLE bundle because the capture specification capspec { has an invalid event name | exceeds the maximum number of data items | contains invalid capture data type, item number | has an invalid business information name | has an overlength formatPrecision in data item | has an invalid captureDataPrecision in data item | has an invalid captureLength in data item | has an invalid formatdataType in data item | has an invalid formatLength in data item | has an invalid captureDataType in data item | has a filter with an invalid filterOperator | has a filter with an invalid keyword | has a filter with an invalid filterValue | has an invalid context capture item | has an invalid capturePoint}: error_data.

Explanation

An error has occurred creating event binding evbname in bundle bundle due to a problem with capture specification capspec. Possible reasons include:

Event name is invalid

The acceptable 1-32 characters of an event name are A-Z a-z 0-9 and _. Leading and embedded blank characters are not permitted. The name may not begin with 0-9, _ or the characters xml (in any case).

Exceeds the maximum number of data items

The number of capture data items is bounded by the maximum size of the EPDE descriptor which must fit into a global catalog record.

Invalid capture data type

Capture data item number error_data is of an unknown or unsupported type.

Business information name is invalid

The acceptable 1-32 characters of a business information name are A-Z a-z 0-9 and _. Leading and embedded blank characters are not permitted. The name may not begin with 0-9, _ or the characters xml (in any case).

Invalid formatPrecision

The formatPrecision value of a capture data item is too large for the formatlength of the item when decimal point and leading digit are taken into account.

Invalid captureDataPrecision

The capture data precision exceeds the total number of digits captured.

Invalid captureLength

The capture data length is invalid for the capture data type. Numeric capture data types have the following restrictions:

  • PACKED must be between 1-16 bytes

  • ZONED must be between 1-32 bytes

  • UHWORD must be 2 bytes

  • UFWORD must be 4 bytes

  • SHWORD must be 2 bytes

  • SFWORD must be 4 bytes

  • HEXFLOAT must be 4 or 8 bytes

  • BINFLOAT must be 4 or 8 bytes

  • DECFLOAT must be 4 or 8 bytes

Invalid formatdataType

The format data type is unsupported or invalid for the capture data type. For example, a format data type of scientific is only valid for one of the xxxFLOAT capture data types.

Invalid formatLength

The formatted data length is invalid for the format type. For example, a format type of scientific requires space for the mantissa, 'E' and the exponent: a minimum of 3 bytes. A format length must be specified for floating point capture data unless it has a format type of scientific.

Invalid captureDataType

The capture data type is unsupported.

Invalid filterOperator

The filter operator is invalid or unsupported for the filter keyword.

Invalid keyword

The filter keyword is invalid or unsupported for the capture point.

Invalid filterValue

The filter value is invalid for the filter keyword. For example this situation can occur when the filter keyword is a status field and the filter value given is not a valid status.

Invalid context capture item

The context capture item is invalid or unsupported for the capture point.

Invalid capture point

The capture point name is invalid or is not a supported system capture point.

System action

An exception entry is made in the trace table.

An exception response is returned to the caller of this domain and the event binding create is terminated.

Message DFHME0116, which contains the symptom string for this problem, is produced.

User response

This is probably caused by an error or inconsistency in the event binding XML. If the event binding was built by the CICS event binding editor, this message might indicate an error in CICS code. Inspect the CICS trace and EC domain message log for any related trace entries or messages. Validate the event binding against the event processing schema for the CICS system into which the bundle is being installed. Correct the event binding, discard the bundle, and reinstall it.

Module

DFHECRL

XMEOUT parameters/Message inserts

  1. date
  2. time
  3. applid
  4. evbname
  5. bundle
  6. capspec
  7. Value chosen from the following options:
  8. error_data

Destination

CECO



DFHEC1012.html | Timestamp icon Last updated: Sunday, 4 June 2017