You can specify that an event is emitted when your application
issues any of the event enabled EXEC CICS API commands or when an
application program is initiated. The event enabled EXEC CICS® commands are shown in Capture points.A limited set of CICS modules have also been event
enabled so that you can capture events from, for example: file and
temporary storage commands coming from Atom support; EXEC CICS LINK commands issued by the CICS WebSphere® MQ bridge program; commands from
the CICS samples and the CECI
transaction.
The capture specification defines the criteria for event emission by using filters, such as the transaction ID, program name, or EXEC CICS command option value. This capture specification can be further refined by filtering on the application data associated with the command. For example, you can specify that the COMMAREA field containing an order value must be greater than 10,000. The capture specification also defines the location of the data to be captured.
The location of the event in the application logic depends on how it is specified. If a CICS application contains two instances of the same EXEC CICS API command, and the filter specification does not distinguish between the two commands, an event is emitted when both commands are issued. If the same EXEC CICS API command occurs in two applications and there is no filter on the transaction ID or program name, an event is emitted when both applications run.
You can capture events at program initiation (PGMINIT) and the following EXEC CICS API capture points.