System events
You can be alerted to certain CICS® system conditions by capturing events for those conditions. Receiving a notification for any changes to the state of system resources avoids the need to poll for changes after they happen; it also means that you can quickly respond to these system events.
- DB2CONN connection status
- FILE enable or disable status
- FILE open or close status
- MESSAGE
- TASK threshold
- TRANCLASS TASK threshold
- Unhandled transaction abend
Capture points
Capture point | Primary predicate | Filter Predicate Context | Filter Predicate Event Option | Capture Data Event Option | Description |
---|---|---|---|---|---|
DB2 CONNECTION STATUS | None | Transaction ID |
FROM_CONNECTST |
DB2ID |
You can capture an event whenever a DB2CONN connection status changes.1 |
FILE ENABLE STATUS | FILE | Transaction ID |
FILE |
FILE |
You can capture an event whenever a file ENABLESTATUS changes.1 |
FILE OPEN STATUS | FILE | Transaction ID |
FILE |
FILE |
You can capture an event whenever a file OPENSTATUS changes.1 |
MESSAGE | MESSAGE_ID | Transaction ID |
MESSAGE_ID |
MESSAGE_ID |
You can capture an event whenever CICS emits a DFHxxnnnn 3 message or CPSM emits a EYUxxnnnn message. |
TASK THRESHOLD | None | None | PERCENT_MAXTASKS | FROM_TASKS |
You can capture an event whenever a task threshold is crossed. The threshold is chosen from a predefined list of 50%, 60%, 70%, 80%, 90, or 100%. |
TRANCLASS TASK THRESHOLD | TRANCLASS | None | TRANCLASS |
TRANCLASS |
You can capture an event whenever a TRANCLASS task threshold is crossed. The threshold is chosen from a predefined list of 50%, 60%, 70%, 80%, 90%, or 100%. |
TRANSACTION ABEND (Unhandled) | TRANSACTION | User ID | TRANSACTION |
TRANSACTION |
You can capture an event whenever a transaction encounters any unhandled abend. |
- The change can occur either through explicit operator actions, EXEC CICS SET commands, or implicitly as a result of CICS internal processing.
- You can choose up to 10 message insert filters. Ensure that you use an available insert, because the CICS event binding editor does not prevent you from defining a filter on an unavailable insert and does not flag the error. Instead, the result is a runtime exception trace, the predicate evaluates as false, and no event is emitted. For example, message DFHFC0200 has 7 inserts. If you define a filter on INSERT 8 through 22, no event is emitted. Message inserts are shown in the individual message topics (see CICS messages in Reference in the CICS TS V5.2 product documentation).
- You cannot event enable any of the
following messages:
- Any CICS initialization messages issued before event processing starts. Event processing is started just before phase 2 initialization PLT programs are run.
- Any CICS termination messages issued after event processing stops. Event processing is stopped after all shutdown PLT programs have run.
- Any messages sent to a CICS user, for example, messages issued by CICS supplied transactions such as CEMT and CEDA.
- Any messages issued by the EC component, for example, all DFHECnnnn messages.