This section describes the CICS® business transaction services event-related commands.
This section is a brief reminder of some of the terms used to describe BTS events. For a more detailed introduction to BTS events, see BTS events.
An event can be in one of two states: FIRED (true) or NOTFIRED (false). Which state it is in is known as the event’s fire status.
Atomic events are simple, "low-level" events. The BTS atomic events are:
A composite event is a method of grouping user-defined (that is, non-system) atomic events in a logical expression, which is named. An atomic event that is included in a composite event is known as a sub-event. Sub-events that fire are placed on the composite event’s sub-event queue. Each composite event has a sub-event queue associated with it. The sub-event queue:
An event that fires, and thereby causes an activity to be reattached, is known as a reattachment event. All user-defined events except sub-events cause the activity to which they are defined to be reattached when they fire. Thus, all user-defined events (both atomic and composite, but excluding sub-events) are potentially reattachment events. All system events are reattachment events.
At times, reattachment may occur because of the firing of more than one event. Reattachment events are placed on the activity’s reattachment queue, from which they can be retrieved. Each activity has a reattachment queue, which:
A timer is a BTS object that expires when the system time becomes greater than a specified time, or after a specified period has elapsed. When you define a timer, a timer event is automatically associated with it. When the timer expires, its associated event fires.
Events are defined within event pools. Each activity has an event pool, which contains the set of events that it recognizes (that is, events that have been defined to it, and system events). An activity’s event pool is initialized when the activity is created, and deleted when the activity is deleted. All the event-related commands except FORCE TIMER operate on the event pool associated with the current activity.
All the event-related commands operate on the current activity’s event pool.
Use these commands to define user events other than activity completion and timer events:
Use these commands to control timers and timer events:
Use these commands to manipulate events:
Use this command to check whether an event has fired: