Filtering tab
Each predicate consists of information identifying the predicate, an operator, and a value. You can specify as many predicates as you want to identify the situation in which you want this capture point to emit an event. The three types of predicates that you can specify are Context, Event Options, and Application Data.
Some capture points have a primary predicate. A primary predicate is a predicate for which you select Equals as the Operator setting and provide a value to avoid a performance impact as you add more capture specifications at a capture point.

Context
The predicates in the capture specification are used for filtering on the context of the capture point.
Every capture point has context items for which you can specify predicates. An example is the transaction ID. All of the available context predicates are shown in the Filtering tab. Context predicates are optional; however, you typically specify the transaction ID or current program to emit events from a particular application.
The Context area is used to set filtering options for events. Based on other information that you supply in the Event binding editor, not all fields apply; the context predicates available depend on the capture point. The predicates that you might want to specify are: transaction ID, current program, and user ID.
- Transaction ID
- Operator choices for all capture points:
- All
- Equals
- Does Not Equal
- Does Not Start With
- Starts With
Additional choices for application capture points:- Less Than
- Not Less Than
- Greater Than
- Not Greater Than
- Current® Program
- Operator choices for all capture points:
- All
- Equals
- Does Not Equal
- Does Not Start With
- Starts With
- Less Than
- Not Less Than
- Greater Than
- Not Greater Than
- User ID
- Operator choices for all capture points:
- All
- Equals
- Does Not Equal
- Does Not Start With
- Starts With
Additional choices for application capture points:- Less Than
- Not Less Than
- Greater Than
- Not Greater Than
- Response Code
- Operator choices:
- All
- Equals
Event Options
The predicates in the capture specification are used for filtering on the values of event options for a CICS command or system event.
Each capture point can have event options for which you can specify predicates. Some commands have no event options. Event options correspond with the options for a particular EXEC CICS command or system event. An example for the SEND MAP command is the MAP name. An example for the Db2® connection status event is the FROM_CONNECTST status. All the available fixed data values for the capture point are shown in the Filtering tab. The format of event options is known to CICS.
- Name
- The name of the capture specification.
- Operator
- Operator choices for all capture points:
- All
- Equals
- Does Not Equal
- Does Not Start With
- Starts With
Additional choices for application capture points:- All
- Equals
- Does Not Equal
- Does Not Start With
- Starts with
Additional choices for system capture points:- Goes Higher Than
- Goes Lower Than
- Value
- The value that you specify for the predicate.
For more information about event options for CICS API calls, see Application events in the CICS TS product documentation.
For more information about event options for system events, see System events in the CICS TS product documentation and Information Sources tab.
Application Data
The predicates in the capture specification are used for filtering on application data that is specified in a CICS command.
Application capture points can have variable length data values for which you can specify predicates. The application data corresponds with the options for a particular EXEC CICS command. An example for the SEND MAP command is the FROM field. All the available variable data values for the EXEC CICS command for that capture point are shown in the Filtering tab.
Application data predicates are processed by CICS in the order specified; that is, the first predicate is processed, followed by the second predicate, and so on.
- Location
- The value of the Location field depends on the CICS API call.
- Container
- Specifies a CICS channel container. The container field can be selected only when the application data has a channel specified. In all other situations, the field is disabled.
- Offset
- Specifies the distance from the beginning, where the data starts. Offset 0 is the start of the field.
- Length
- The length of the field in bytes. A length of 0 means filter on the whole data area or container. This is useful when filtering on, for example, the contents of a container regardless of its length.
- Operator
- Operator choices:
- All
- Exists
- Equals
- Does Not Equal
- Does Not Exist
- Starts With
- Does Not Start With
- Less Than
- Not Less Than
- Greater Than
- Not Greater Than
- Value
- The value that you specify for the predicate.