4.9.1 Behavior of the completed-action linkage function

The following describes, by way of examples, how the completed-action linkage function works when the user manually changes the response status of a JP1 event in the Central Console after a monitoring object change status while the system is being monitored from the Central Scope.

The example below is based on the following assumptions:

• Both error events and warning events are set as status change conditions for monitoring object 1.

• Monitoring object 1 is defined so that its status changes to Error when an error event occurs, and to Warning when a warning event occurs.

• No status change condition is set for monitoring group 1 (the default applies).

The following example shows the behavior of the completed-action linkage function when the user changes the response status of a JP1 event to Processed.

Figure 4‒25: Example of the completed-action linkage function (1)

The flow of processing is described below, following the numbers in the figure:

1. JP1/IM receives a JP1 event matching a status change condition of monitoring object 1, and the object's status changes to Error. The status of the higher-level monitoring group 1 also changes to Error.

   The user investigates the cause of the error by searching for status change events, for example.

2. The status change events that occurred in monitoring object 1 appear on the Search Events page of the Central Console.

   In this example, both error events and warning events will change the status of monitoring object 1. The object's status has changed to Error here as a result of both types of events.

   The user acts on the problem that needs to be resolved first, according to the event level of the JP1 events.

3. The user changes the response status of the error event that caused the status change in monitoring object 1 to Processed.

   The user sets Processed only for the event that has been resolved.

4. In tandem with the JP1 event changing to Processed, the Error status of monitoring object 1 is cleared, and its status changes to Warning. The status of the higher-level monitoring group 1 also changes to Warning.

   Because the error event has changed to Processed, monitoring object 1 changes to the status corresponding to a warning event.

   The user investigates and resolves the remaining warning events. When all the JP1 events matching the status change conditions have been changed to Processed, the status of the monitoring object changes to Normal.

The next example shows the behavior of the completed-action linkage function when the user changes the response status of a JP1 event from Processed to a different value.^#

#

Other possible values are Processing, Held, or Unprocessed.

Delete is not included. Delete simply hides the JP1 event on the Severe Events page. JP1 events deleted on this page might still be listed on the Monitor Events page and Search Events page. Thus, setting the response status of a JP1 event to Delete does not change the status of the monitoring object.

Figure 4‒26: Example of the completed-action linkage function (2)

The flow of processing is described below, following the numbers in the figure:

1. The user changes the response status of the JP1 event to Unprocessed.

   A processed JP1 event might need to be changed to another response status if the problem had not been resolved after all, or if the Processed status was set by mistake, for example.

2. In tandem with the JP1 event changing to Unprocessed, the status of monitoring object 1 changes back to Error. The status of the higher-level monitoring group 1 also changes back to Error.

   Because the error event is now Unprocessed, the object's status also changes back to Error, which has higher priority than Warning.

   The user now proceeds to fix the problem.

To Page Top