DFHEP2001 date time applid The CICS event processing domain failed to create EPADAPTER resource adapter in BUNDLE bundle because the EP adapter, which is of type adapterType and emission mode emitmode {, requires a program name. | , does not support transactional events. | , requires a transaction ID. | , is invalid or unrecognised. | , has an invalid or unsupported event format. | , has an unsupported combination of attributes. | , failed the surrogate user check for some unexpected reason.}
Explanation
An error has occurred creating EPADAPTER adapter in BUNDLE bundle because of a problem with the EP adapter specification. The EPADAPTER is either being installed as a separate EPADAPTER bundle part or as part of an EVENTBINDING bundle part of the same name. The EPADAPTER is of type adapterType and its emission mode is emitmode. Possible reasons include:
- Requires a program name
-
A program name is required for a custom EP adapter when the emission mode is synchronous.
- Does not support transactional events
-
The EP adapter cannot be used for assured transactional events because it does not emit events to a recoverable transport. Transactional events and synchronous emission mode are mutually exclusive options for this EP adapter type.
- Requires a transaction ID
-
A transaction ID is required for a custom adapter when the emission mode is asynchronous.
- Is invalid or unrecognized
-
The EP adapter type, emission mode or both are unrecognized by this release of CICS.
- Has an invalid or unsupported event format
-
The format field in the EP adapter configuration container returned by the XML parse function is invalid or not supported by the EP adapter type.
- Has an unsupported combination of attributes
-
The emission mode is not supported by this type of EP adapter.
- Unexpected reason during the surrogate user check
-
The userid installing the EP adapter goes through a surrogate check for the userid specified in the EP adapter configuration. The surrogate user check failed for some unexpected reason.
System action
An exception entry is made in the trace table.
An exception response is returned to the caller of this domain and the EP adapter 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 appropriate event processing schema for the CICS system into which the bundle is being installed. Correct the XML, discard the BUNDLE, and reinstall it.
Module
XMEOUT parameters/Message inserts
- date
- time
- applid
- adapter
- bundle
- adapterType
- emitmode
- Value chosen from the following options:
1=, requires a program name., 2=, does not support transactional events., 3=, requires a transaction ID., 4=, is invalid or unrecognised., 5=, has an invalid or unsupported event format., 6=, has an unsupported combination of attributes., 7=, failed the surrogate user check for some unexpected reason.
Destination
CEPO