Event Capture Function Collection Methods

Event Capture Option › Event Capture Function Collection Methods

Event Capture Function Collection Methods

The Event Capture function takes snapshots of a specific system at a given time. Use this snapshot to diagnosing current or potential problems on that system.

The Event Capture function collects, groups, and saves the captured CA SYSVIEW command displays by event name in chronological order. This information is then indexed for easy retrieval. A single Capture index can include data for multiple systems or for only one system. Multiple Event Capture indexes can be in use across all of your systems. However, a single system can only use one Event Capture index at any given time.

This information is not restricted to those systems participating in a sysplex. Regardless of the index method, you can display the list of indexed events from a single index or from a group of indexes. Remember that any index can represent more than one physical system.

You can collect data with Event Capture using the following methods:

On Demand by User Request
You can request the capture of an event at any time. To do so, first determine if any existing CAPLIB event member contains the desired list of commands you want to capture. If so, capture the event by issuing the following command:
```
CAPTURE eventname
```
You can also initiate a capture event from the system console by issuing the following command:
```
MODIFY sysview,CAPTURE eventname
```
Scheduled Time Events
CA SYSVIEW contains an event scheduler that can execute CAPTURE events at predefined times or intervals. With the scheduler, you can have one or more schedule events, each of which can perform one or more CAPTURE events.
Threshold- or Exception‑Driven Events
CA SYSVIEW contains hundreds of monitored metrics that can have associated threshold or state definitions. These definitions provide a mechanism to alert you of current or potential problems. You can assign problem and warning levels to each definition, and then take proactive measures upon receiving early alerts of a problem. When a threshold definition is triggered, you can specify one or more actions to take, including capturing an event. You can set thresholds in the threshold definition members in the parmlib, or with the online definition commands. Capturing the status or look of the system at the time of an alert helps you to debug or solve a problem at another time.
Automated Operations Events
Similar to threshold-driven events, automated operation events track and monitor the state of hundreds of resources. The automated operations rules or definitions can be used to trigger event captures.