10.2.2 Monitoring response-waiting events
Because JP1/IM handles response-waiting events in the same manner as ordinary JP1 events, you can use automated action notification and other JP1/IM features with these events.
The following describes how each of the following features works with waiting-response events. Features that are not described here work the same way as with ordinary JP1 events.
-
Monitoring in the Event Console window
-
JP1 event filtering
-
Monitoring repeated events
-
Searching for events
-
Outputting information from JP1/IM - View in CSV format
- Organization of this subsection
(1) Monitoring in the Event Console window
Waiting-response events appear in the lists of events on the Monitor Events page, Severe Events page, and Search Events page, like ordinary JP1 events. The Response-Waiting Events page only shows response-waiting events. This page is displayed only when the response-waiting event management function and the setting that allows users to respond to and work with response-waiting events is enabled.
From the list of events in the Event Console window, you can perform the following operations and configuration with respect to response-waiting events in the same manner as ordinary JP1 events:
-
Display detailed information about a response-waiting event
-
Open the monitors of linked products
-
Display execution results of automated actions
-
Change display items for JP1 events
-
Set the background color for JP1 events
-
Set the response status for response-waiting events
-
Specify the event display period
For details about these features, see 4.1 Centralized monitoring using JP1 events in the JP1/Integrated Management 2 - Manager Overview and System Design Guide.
(a) Monitoring on the Response-Waiting Events page
The Response-Waiting Events page displays a list of response-waiting events for which a response is not yet provided. This page is shown below.
|
|
![[Figure]](GRAPHICS/CS230400.GIF)
An indicator on the tab of the Response-Waiting Events page lets the operator know whether there are events that require a response. When there are response-waiting events listed on the Response-Waiting Events page, the indicator on the tab is lit green.
In addition to the event database, response-waiting events are stored in a file for accumulated response-waiting events in a process called response-waiting event accumulation. The Response-Waiting Event page displays information about the events recorded in the file for accumulated response-waiting events.
Response-waiting events are removed from the Response-Waiting Events page when:
-
An operator responds to the response-waiting event
-
The response-waiting event is released from the hold-and-accumulate state
-
The response-waiting event is canceled
For details about what causes response-waiting events to be released from the hold-and-accumulate state, see 10.2.3 Accumulation of response-waiting events.
The indicator on the tab becomes unlit after all response-waiting events have disappeared from the Response-Waiting Events page.
To allow the operator to distinguish response-waiting events, the ![[Figure]](GRAPHICS/CI230100.GIF)
icon appears in the Type column for these events on each page of the Event Console window.
Note that the Response-Waiting Events page does not display the background colors that have been assigned to JP1 events.
(2) Filtering response-waiting events
You can use the following filters to filter response-waiting events:
-
Event receiver filter
-
Severe events filter
-
View filter
When you enable the response-waiting event management function, items that allow the operator to select whether to display response-waiting events appear in the condition definition windows for the event receiver filter and severe events filter. To filter response-waiting events using the view filter, the response-waiting event management function and the setting that allows users to respond to and work with response-waiting events must be enabled.
For details about the windows in which filter conditions are defined, see 3.44.8 Filter condition definition windows in the manual JP1/Integrated Management 2 - Manager GUI Reference.
Note that event acquisition filters do not allow you to specify conditions that specifically identify response-waiting events. Configure event acquisition filters so that they filter events at the product level for products that issue response-waiting events.
(3) Consolidated display of response-waiting events
If a network problem or some other issue causes the same batch job to issue the same response-waiting event several times in succession, the events are displayed as a single consolidated event. Events are only consolidated on the Monitor Events page and Severe Events page.
If identical response-waiting events are issued as a result of an error of some kind, the operator does not need to respond to each and every event. If you respond to one of these waiting-response events, you do not need to respond to the others. However, response-waiting events that no longer require a response remain on the Response-Waiting Events page until they are released from the hold-and-accumulate state. For details about how to release these events, see 10.2.3 Accumulation of response-waiting events.
(4) Searching for response-waiting events
When searching for JP1 events, you can specify a response-waiting event as a search condition. Conditions that apply to response-waiting events only appear in the Event Search Conditions window if you enable the response-waiting event management function and the setting that allows users to respond to and work with response-waiting events.
For details about the Event Search Conditions window, see 3.44.7 Event Search Conditions window in the manual JP1/Integrated Management 2 - Manager GUI Reference.
You can only respond to response-waiting events from the search results if you search the logged-in JP1/IM manager host for response-waiting events. If you do not specify the logged-in manager host, you cannot respond to the response-waiting events that appear in the search results.
(5) Outputting information from JP1/IM - View in CSV format
You can output information about response-waiting events displayed in the list of events in CSV format. You can output CSV information in two ways:
-
Save the information in the list of events to a file
You can save a snapshot of the event information displayed in JP1/IM - View to a CSV file. A snapshot means information extracted at a specific time.
-
Copy JP1 event information, action execution results, or other information to the clipboard
If the feature that allows you to copy information to the clipboard is enabled, you can copy selected parts of response-waiting event information, action execution results, and other information to the clipboard in CSV format. This feature is enabled by default.
The following table shows the events lists whose response-waiting events can be saved to a CSV file or copied to the clipboard in CSV format.
|
Operation |
Monitor Events page |
Severe Events page |
Related Events window |
Response-Waiting Events page |
Search Events page |
|---|---|---|---|---|---|
|
CSV output |
Y |
Y |
N |
Y |
Y |
|
Copy to clipboard |
Y |
Y |
Y |
Y |
Y |
- Legend:
-
Y: Can be saved or copied.
N: Cannot be saved or copied.
When you save information about response-waiting events to a CSV file or copy it to the clipboard, the icon in the Type column is replaced with the text Response-waiting event in the CSV data. If icons indicating a repeated event and a response-waiting event are output for an event, the icons are replaced with the text Repeated event, Response-waiting event in the CSV data. When you output the information on the Response-Waiting Events page in CSV format, Response-Waiting Events appears as the name of the source window in the header information.
For details about how to enable the copy to clipboard feature, see 1.19.2 Customizing operation of JP1/IM - View (Central Console viewer and Central Scope viewer) (for Windows) in the JP1/Integrated Management 2 - Manager Configuration Guide.