KAVB1801-E
The oldest response-waiting event was released from the hold-and-accumulate state because the maximum number of response-waiting events that can be accumulated was exceeded. (event ID = event ID, host that sent response-waiting event = host that sent response-waiting event, name of product that sent response-waiting event = name of product that sent response-waiting event, response ID = response ID, event database serial number for response-waiting event = event database serial number for response-waiting event)
The oldest response-waiting event on the manager was released from the hold-and-accumulate state because the maximum number of response-waiting events that can be accumulated was exceeded.
- S:
-
Continues processing.
- O:
-
For the product that issues response-waiting events, review the estimate of the number of response-waiting events that can be issued.
If the number of response-waiting events issued by the product exceeds the estimate, contact the supplier of the product.
To respond to a response-waiting event that has been released from the hold-and-accumulate state, use the Search Events page to find the target event.
A response from JP1/IM - View is not possible unless the response-waiting event exists in both the event database and the file for accumulated response-waiting events. If you want to respond to the response-waiting event for which a response from JP1/IM - View is no longer possible, take the corrective action for the product that issued the event.