4.5 Notes
-
Because the adbcancel command is executed asynchronously with the HADB server's processing, use the adbls -d cnct command to verify that the target of the processing has been disconnected from HADB. If no target connection information is displayed for the connection ID specified in the adbcancel command, the processing target has been disconnected from HADB.
-
The adbcancel command is used only to forcibly terminate a command (the adbimport command, for example) that has established a connection with the HADB server. To determine whether a connection has been established, check the PROGRAM column of the execution results of the adbls -d cnct command. If a connection has been established, the command name is displayed in the PROGRAM column.
-
If you use the adbcancel command to forcibly terminate an executing application program, the command rolls back the transaction and then disconnects the application program from the HADB server. To determine whether the target application program was executing a transaction when the adbcancel command was issued, check if STARTED is displayed in the STATUS column of the adbls -d cnct command's execution results. A transaction was executing if STARTED is displayed.
-
In the case where an application program has terminated abnormally but its transaction is still running, the transaction will be rolled back and the application program disconnected from the HADB server when the time specified in the adb_clt_rpc_sql_wait_time operand in the corresponding application program's client definition is reached, without having to execute the adbcancel command.
-
If you are using the multi-node function, the adbcancel command is asynchronously executed between nodes. Therefore, information displayed by the adbls command might be temporarily inconsistent between nodes.