KAVB0554-E

Response processing failed.

S:

Aborts response processing.

O:

Check the following items depending on the reason that is displayed.

Fail to connect server.

A connection could not be established with JP1/Base on the server that issued the response-waiting event. JP1/Base might not be running on that server. Check the status of the server. In addition, a communication error might have occurred. Check the status of the connection with the server that issued the response-waiting event.

Connection has timed out.

A timeout occurred because the server or network that issued the response-waiting event was in high load status. Wait a while and then retry the operation. If this message is output frequently, revise the timeout value specified for the response or status check of response-waiting events.

Socket error occurred.

A communication error occurred. Check the status of the network of the server that issued the response-waiting event.

Invalid data was received from the program product that sent the response-waiting event.

Collect the following data, and then contact a system administrator:

• Data of the product that issued the response-waiting event

• JP1/IM - Manager data (collected by using the data collection tool)

A message for the product that issued the response-waiting event is indicated in reason:

Take the corrective action given for the message indicated in reason.

Server is busy.

The request was not accepted because the connected server was busy. Wait a while, and then retry the operation.

There is no valid receiver for the response.

Processing could not be executed because the product that issued the response-waiting event was in an invalid environment. Revise the environment of the product.

The reason is other than the above:

Use the data collection tool to collect data, and then contact a system administrator.