10.2.3 Accumulation of response-waiting events
When you enable the response-waiting event management function, response-waiting events that arrive in the event database on the manager host are recorded in a file for accumulated response-waiting events in addition to the event database. A maximum of 2,000 response-waiting events are stored in this file. This process is called accumulation of response-waiting events.
The Response-Waiting Events page displays information about the response-waiting events in the file for accumulated response-waiting events.
- Organization of this subsection
(1) When response-waiting events are released from the hold-and-accumulate state
Response-waiting events are deleted from the file for accumulated response-waiting events and released from the hold-and-accumulate state when:
-
An operator successfully responds to a response-waiting event
-
The response-waiting event is canceled in BJEX or JP1/AS
-
An operator manually releases the event from the hold-and-accumulate state
-
There are more than 2,000 response-waiting events
In this case, accumulated response-waiting events are released in order from the oldest.
-
You disable the response-waiting event management function and restart JP1/IM - Manager
A response-waiting event that is released from the hold-and-accumulate state disappears from the Response-Waiting Events page when you next refresh the list of events in JP1/IM - View. Note that such events, while no longer appearing in the Response-Waiting Events page, still appear in search results in the Search Events page as long as they remain in the event database.
(2) Notification when the number of response-waiting events exceeds 2,000
JP1/IM - Manager monitors the number of response-waiting events in the hold-and-accumulate state, and notifies the operator when the number exceeds 2,000 by issuing a JP1 event (event ID: 00003F41). The message KAVB0551-E also appears on the Response-Waiting Events page.
|
|
![[Figure]](GRAPHICS/CS230500.GIF)
The JP1 event reporting that the number of response-waiting events in the hold-and-accumulate state has exceeded the maximum is issued only once. The message KAVB0551-E remains on the Response-Waiting Events page. When the number of events in the hold-and-accumulate state exceeds the limit, take action as described in the message to resume monitoring events in the hold-and-accumulate state in the usual way. Then the message KAVB0551-E disappears from the Response-Waiting Events page. The JP1 event is issued again when the number of events next exceeds 2,000.
For details about how to resume monitoring of events in the hold-and-accumulate state, see 10.4.4 Resuming monitoring of events in the hold-and-accumulate state.
- Responding to response-waiting events that have been released from the hold-and-accumulate state
-
You can respond to a response-waiting event that was removed from the Response Waiting Events page after exceeding the maximum number of events by searching for the event from the Search Events page. You can identify an event that was released from the hold-and-accumulate state by viewing the KAVB1801-E message in the integrated trace log on the manager host.
If the response-waiting event was also deleted from the event database, you can respond to the event by executing the response command (bjexchmsg or adshchmsg) on the host that issued the event. For details about how to respond using the response command (adshchmsg) of JP1/AS, see JP1/Advanced Shell Description, User's Guide, Reference, and Operator's Guide.