DFHEP2002 date time applid The CICS event processing domain failed to create the EPADAPTER resource adaptername in BUNDLE bundle because {the EP adapter name is invalid. | the XML data for the EP adapter could not be parsed. | the eventDispatcher is missing or invalid. | the configuration data is too long. | it is a duplicate of another EPADAPTER in the BUNDLE.}

Explanation

An error has occurred creating EPADAPTER adaptername in BUNDLE bundle. The EPADAPTER is either being installed as a separate EPADAPTER bundle part or as part of an EVENTBINDING bundle part of the same name. Possible reasons include:

EP adapter name is invalid.

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

XML data for the EP adapter could not be parsed.

The preceding DFHPInnnn message gives further information about the cause of the problem.

eventDispatcher is missing or invalid

The eventDispatcher section of the event binding or EP adapter cannot be located by the XML parser.

Configuration data is too long

The configuration data specified for a custom EP adapter is too long.

Duplicate of another EPADAPTER

The EPADAPTER being installed has the same name as a previously installed EPADAPTER from the same BUNDLE. Note that an EPADAPTER may be:

  • standalone: installed from a separate epadapter part within the BUNDLE

  • embedded: installed with an EVENTBINDING from an evbind part within the bundle. The EPADAPTER has the same name as the related EVENTBINDING.

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

If this is a separately installed EPADAPTER, the condition is probably caused by an error or inconsistency in the EP adapter XML. If installed as part of an EVENTBINDING, the condition is probably caused by an error in the eventDispatcherSpecification section of the event binding XML. If the XML was built by the CICS event binding editor, this condition might indicate an error in CICS code. Inspect the CICS trace and EP domain message log for any related trace entries or messages. Validate the XML 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

DFHEPRL

XMEOUT parameters/Message inserts

  1. date
  2. time
  3. applid
  4. adaptername
  5. bundle
  6. Value chosen from the following options:

Destination

CEPO

Applicable releases in Version 6

  • beta
  • 6.3
  • 6.2
  • 6.1