KFAA50301-E

A communication error has occurred.

aa....aa: Cause of the error

• message: A message error

• netdown: Network failure

• resource: Insufficient system resources

• timeout: Timing out

bbbb: Operation at time error occurred

• cnct: Connection acceptance

• recv: Reception

• send: Transmission

S:

Terminates processing.

Action:

Take the corrective action for the cause of the error displayed for aa....aa.

▪ If the cause of the error is message:

Establish a connection to the HADB server from the HADB client. If you are using a product other than the HADB client or performing communication directly to the HADB server from the user program, use the HADB client.

If you are not aware of the connection to the HADB server, communications by a malicious third party are suspected. Consider countermeasures, such as identification of the remote party, and security measures.

▪ If the cause of the error is netdown:

If the remote party is an HADB server on another node, check the settings, such as the communication line, server process status, and message log.

If the remote party is an HADB client or a program (a product other than HADB or a user program) that performs communications without using the HADB communication function, no action is required for the HADB server. In this case, the possible causes of error are as follows.

• The HADB client forcibly disconnected communications due to detection of a timeout or error.

• A process on the client forcibly terminated for some reason. This occurs if, for example, the adbsql command is forcibly terminated by pressing the Ctrl + C keys.

• Processing of the application program is specified to terminate the application without explicitly disconnecting the connection with the HADB server.

• A server monitoring tool or a malicious third party might have scanned the HADB server port.

Take action such as notifying the persons who execute the application program or security measures according to the cause of the error.

▪ If the cause of the error is resource:

Take one of the corrective actions:

• Reduce the number of concurrent connections for the application program or command.

• Increase the maximum number of concurrent connections specified for the adb_sys_max_users operand in the server definition.

▪ If the cause of the error is timeout:

Carefully review the value specified in the adb_rpc_wait_time operand in the server definition. For details about the adb_rpc_wait_time operand, see the topic Operands related to status monitoring (set format) in Detailed descriptions of the server definition operands in Designing the Server Definition in the HADB Setup and Operation Guide.

If you want to permanently maintain communications to use connection pooling, specify 0 for the adb_rpc_wait_time operand in the server definition. However, if 0 is specified, the HADB server does not perform forced disconnection based on the elapsed time for any other communications. This might allow a malicious third party to continue unauthorized connections. Therefore, if you specify 0 for the adb_rpc_wait_time operand in the server definition, periodically monitor for suspicious connections.