You add capture specifications to an event specification to create capture points in CICS®.
The CICS event binding editor guides you through creation of one or more capture specifications. These specifications identify the following items:
For example, you can specify that any READQ TS (temporary storage READ) command is a potential event. You then qualify the conditions under which the event is raised by adding predicates of the types available for the command that you want to intercept.
You can define three types of predicates:The format of application command options is known to CICS.
Application data predicates are processed by CICS in the order specified. For example, the first predicate is processed, then the second, and so on.
Application data is used for storage areas such as a COMMAREA or container that are passed as options on CICS commands. The format of these areas is unknown to CICS, but is known by your application program. You probably have a source language description that you can import to describe the format.
The basic event binding information, entered by the business manager during the high-level definition of the event binding, includes an event specification. This event binding information identified data that was known to be required for further processing, but gave no details of its location. You specify information sources to provide these details.
The CICS event binding editor helps by presenting in the Information Sources panel a table of the information it needs to meet the business specification. The table is partially filled as a result of the event specifications entered earlier by the business manager. The table has empty spaces that must be filled so that CICS knows the location of the data it must capture.