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 information.
You create an event binding in a CICS bundle project using the CICS event binding editor. Event bindings are included in bundles: bundles are the unit for deploying, enabling, and disabling CICS events. The event binding groups sets of event specifications that are to be handled using the same EP adapter or EP adapter set. For more information about bundles, see BUNDLE resources.
The business analyst creates an event specification. The application analyst then completes one or more corresponding capture specifications. The system programmer either completes the adapter specification embedded within the event binding or names an existing EP adapter or EP adapterset defined in a separate XML definition. For more information, see Event processing (EP) adapter specification. EP adapter set specification is an external EPADAPTERSET resource. For more information, see Event processing (EP) adapter set specification.
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 define, install, enable, disable, and uninstall a deployed CICS bundle in a CICS system. For more information about deploying an event binding, see Deploying a CICS bundle project.
The CICS event binding editor creates an XML file that conforms 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/cicsts52/schemas/eventprocessing/ :
For more information about schemas, see Schema versions.