Creating an event

The CICS Explorer® provides an event binding editor to create events for an application.

About this task

The event binding editor is available in the Resource perspective of the CICS Explorer. Using the editor, you can create event bindings and capture specifications for applications. You can also create an event processing adapter that handles the captured events and emits them to an event consumer. Event bindings and adapters are packaged as CICS® bundle projects.

Typically an application developer, who knows about the application, creates the event bindings and capture specifications. The system administrator can either create a separate event processing adapter or provide the information to the developer to include in the event binding.

The general insurance application supplies an event binding that captures information every time a business user adds or inquires about customers, or adds, inquires, deletes, or updates a customer policy. This file is called Transaction_Counters.evbind. You must import this file into a CICS bundle project in CICS Explorer. If you are unfamiliar with events in CICS, you can complete the following steps to import the supplied binding into a project, and open the editor to understand each part of the event binding. If you are familiar with events and capture specifications, you can create the project, import the file, and deploy it directly to CICS.

Procedure

  1. Open the Resource perspective in CICS Explorer.
  2. Create a bundle project by clicking the Bundle Project icon or clicking New > CICS Bundle project.
    Screen capture of selecting a CICS Bundle project from the menu.
  3. In the wizard, enter a suitable name for the project and click Finish. The project is created in the Project Explorer view.
  4. Right-click the project in the Project Explorer view and click Import to import the event binding for the general insurance application into the project. The Import wizard selection page is displayed.
  5. Expand General, select File System, and click Next.
  6. Click Browse to find the directory where you extracted the Supportpac, select the directory, and click OK. The files that are in the directory are listed in the wizard.
  7. Select the Transaction_Counters.evbind file and click Finish.
    Screen capture of the Import wizard with the event binding selected.

    The event binding is added to the CICS bundle project.

  8. Optional: Double-click the event binding to open the event binding editor. An event binding has three tabs:
    • The Event Binding tab contains information that applies to the whole event binding and lists the events that are defined in specifications. An event specification represents a business event and contains the event name and emitted business information. You can have one or many event specifications in an event binding.

      The general insurance event binding contains one event specification called Count_business_trans. You can click Edit details or click the Specification tab to view the details.

      Screen capture of the event binding in CICS Explorer.

    • The Specification tab contains the event specification that defines what business information is captured, and a capture specification that defines at what point the event is captured from the application. The capture specification can also include filters to ensure that the system is not flooded with events, but emits only events that are relevant.

      The general insurance event specifies that for every request made by a business user, the request type and return code are emitted in an event. The business user can add and inquire about customers, or add, delete, inquire, and update policies. Each type of business request, and whether the request was successful or failed, is included in the event.

      Screen capture of the event specification in CICS Explorer.

      The general insurance event has one capture specification. Click genapp_program to view the capture point, filtering, and information sources for the event. An event is captured only after an EXEC CICS LINK to a program.

      Click the Filtering tab to view the filters that are applied to the event. The event is emitted only if the calling program starts with LG, which means that programs in the general insurance application are used to capture information. All other application programs are excluded.

      Screen capture showing the filtering for the event.

      Click the Information Sources tab to view the source and format of the business information. When an event is emitted, the business information is taken from a COMMAREA that is passed between programs in the general insurance application.

      Screen capture showing the Information Sources tab, where the location and format of the business information is specified for the general insurance application.
    • The Adapter tab specifies the event processing (EP) adapter that is used to emit the event from CICS. The best practice is for system administrators to specify EP adapters separately from the event bindings, so that adapters can be separately defined and managed in CICS and many events can use the same EP adapter. CICS can emit events to many consumers, including other IBM® products such as WebSphere® MQ.

      The general insurance event is emitted to an adapter that starts a CICS transaction called LGST. When an event is emitted, CICS starts transaction LGST and passes the business data that was specified in the event specification. For convenience, the event processing adapter is included with the event. You can view it by clicking the Adapter tab.

      Screen capture showing the Adapter tab in CICS Explorer with the Transaction Start adapter selected and the transaction ID specified as LGST.

Results

You added an event binding to a CICS bundle project in CICS Explorer and optionally used the Event Binding Editor to view the event and capture specifications.

What to do next

Deploy the bundle project to CICS and install it in the terminal-owning region.


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