An event binding is an XML definition that defines one or more business events to CICS®. An event binding consists of event specifications, capture specifications, and adapter and dispatcher information.
The event binding is the unit for deploying, enabling, and disabling CICS events. The event binding groups sets of events that are to be handled using the same EP adapter and configuration and the same dispatching policy.
You create an event binding in a CICS bundle project using the CICS event binding editor. Development of an event binding can be top-down or bottom-up:
When the business analyst has completed the event specification and the application analyst has completed the corresponding capture specifications and dispatcher information, the event binding is complete.
An event binding is saved by the CICS event binding editor as an XML event binding file with the suffix .evbind in a CICS bundle project. You can deploy the bundle to a CICS system. You can define, install, enable, disable, and uninstall a deployed CICS bundle in a CICS system. In addition, you can enable and disable individual deployed event bindings.
The CICS event binding editor creates
an XML file conforming to the event binding schemas. To deploy to
a CICS system, an event binding must be included in a CICS bundle
and must conform to the event binding schemas. The following event
binding schema files are installed with CICS in /usr/lpp/cicsts/cicsts41/schemas/eventprocessing/
:
For more information about schemas, see Schema versions.