Application events
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 programs; 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.
Capture points
You can capture events at program initiation (PGMINIT) and the following EXEC CICS API commands. Capture points that can be specified are shown in the following table:
Capture Point | Primary Predicate | Filter Predicate | Capture Data | ||
---|---|---|---|---|---|
Context | Event Option | Event option | Application Data | ||
CONVERSE | None | Transaction Id |
None | FROM |
None |
DELETE FILE | FILE | Transaction Id |
FILE | FILE | RIDFLD |
DELETEQ TD | QUEUE | Transaction Id |
QUEUE | QUEUE | None |
DELETEQ TS | QNAME | Transaction Id |
QNAME | QNAME | None |
INVOKE SERVICE | SERVICE | Transaction Id |
SERVICE |
SERVICE |
CHANNEL |
LINK PROGRAM | PROGRAM | Transaction Id |
PROGRAM |
PROGRAM |
COMMAREA |
PROGRAM INIT | PROGRAM | Transaction Id |
PROGRAM |
None | COMMAREA |
PUT CONTAINER | CONTAINER | Transaction Id |
CONTAINER |
CONTAINER |
FROM |
READ | FILE | Transaction Id |
FILE |
FILE | RIDFLD |
READNEXT | FILE | Transaction Id |
FILE |
FILE | RIDFLD |
READPREV | FILE | Transaction Id |
FILE |
FILE | RIDFLD |
READQ TD | QUEUE | Transaction Id |
QUEUE | QUEUE | INTO-SET |
READQ TS | QNAME | Transaction Id |
QNAME | QNAME | INTO-SET |
RECEIVE | None | Transaction Id |
NONE | NONE | INTO-SET |
RECEIVE MAP | MAP | Transaction Id |
MAP |
MAP |
INTO-SET |
RETRIEVE | None | Transaction Id |
NONE | NONE | INTO-SET |
RETURN | None | Transaction Id |
TRANSID |
TRANSID |
COMMAREA |
REWRITE | FILE | Transaction Id |
FILE | FILE | FROM |
SEND | None | Transaction Id |
NONE | NONE | FROM |
SEND MAP | MAP | Transaction Id |
MAP |
MAP |
FROM |
SEND TEXT | None | Transaction Id |
ALARM | NONE | FROM |
SIGNAL EVENT 1 | EVENT | Transaction Id |
EVENT |
EVENT |
FROM |
START | TRANSID | Transaction Id |
TRANSID |
TRANSID |
FROM |
WEB READ | None | Transaction Id |
NONE | NONE | FORMFIELD |
WEB READNEXT | None | Transaction Id |
NONE | NONE | FORMFIELD |
WRITE FILE | FILE | Transaction Id |
FILE | FILE | RIDFLD FROM |
WRITE OPERATOR | None | Transaction Id |
NONE | NONE | TEXT 2 |
WRITEQ TD | QUEUE | Transaction Id |
QUEUE | QUEUE | FROM |
WRITEQ TS | QNAME | Transaction Id |
QNAME | QNAME | FROM |
XCTL | PROGRAM | Transaction Id |
PROGRAM |
PROGRAM |
COMMAREA |
- CONVERSE
- DELETE FILE
- DELETEQ TD
- DELETEQ TS
- INVOKE SERVICE
- LINK PROGRAM
- PUT CONTAINER
- READ
- READNEXT
- READPREV
- READQ TD
- READQ TS
- RECEIVE
- RECEIVE MAP
- RETRIEVE
- RETURN
- REWRITE
- SEND
- SEND MAP
- SEND TEXT
- SIGNAL EVENT 1
- START
- WEB READ
- WEB READNEXT
- WRITE FILE
- WRITEQ TD
- WRITEQ TS
- XCTL
All capture points define the same context capture items, PROGRAM, TRANSID, and USERID.