19.8 Return values of the CLI functions
The table below shows the return values of the following types of CLI functions:
-
CLI functions for connecting to and disconnecting from the HADB server
-
CLI functions for controlling transactions
-
CLI functions for execution of SQL statements
|
No. |
Event |
Symbolic literal |
Value |
|---|---|---|---|
|
1 |
CLI function terminated normally. |
a_rdb_RC_SQL_SUCCESS |
0 |
|
2 |
CLI function terminated with a warning. |
a_rdb_RC_SQL_WARNING |
+1 |
|
3 |
There is no data. |
a_rdb_RC_SQL_NO_DATA |
+100 |
|
4 |
An SQL error occurred. |
-- |
SQLCODE |
|
5 |
An error occurred that disabled output of messages to the client message log file. |
-- |
error-cause-code# |
|
6 |
Other error occurred. |
a_rdb_RC_SQL_ERROR |
-1 |
- Legend:
-
--: Not applicable.
- #
-
The following table lists and describes the error cause codes.
|
No. |
Error cause code |
Cause of the error |
|---|---|---|
|
1 |
-10000 |
The specified ConnectionHandle argument is invalid (NULL was specified). |
|
2 |
-11000 |
Acquisition of the absolute path of the message catalog file of the client message log file failed. |
|
3 |
-12XXX |
open processing on the message catalog file of the client message log file failed. errno (error number) is set in XXX. |
|
4 |
-13000 |
Acquisition of the ADBMSGLOGSIZE environment variable (size of the client message log file) failed. |
|
5 |
-14000 |
Acquisition of the absolute path of the client message log file failed. |
|
6 |
-15XXX |
open processing on the client message log file failed. errno (error number) is set in XXX. |
|
7 |
-16XXX |
fstat processing on the client message log file failed. errno (error number) is set in XXX. |
|
8 |
-17XXX |
read processing on the client message log file failed. errno (error number) is set in XXX. |
|
9 |
-18XXX |
lseek processing on the client message log file failed. errno (error number) is set in XXX. |
|
10 |
-19XXX |
write processing on the client message log file failed. errno (error number) is set in XXX. |
|
11 |
-21000 |
The versions of the HADB client and ODBC driver do not match. |
The following table lists and describes the return values of the CLI functions for data type conversion.
|
No. |
Event |
Symbolic literal |
Value |
Action |
|---|---|---|---|---|
|
1 |
The CLI function terminated normally. |
a_rdb_RC_CNV_SUCCESS |
0 |
None |
|
2 |
The address of the area storing the data before conversion is not valid. |
a_rdb_RC_CNV_INVALID_SRC_ADDRESS |
1 |
Check the address of the area storing the data before conversion. |
|
3 |
The length of the data to be converted is not valid. |
a_rdb_RC_CNV_INVALID_SRC_LENGTH |
2 |
Check the length of the data to be converted for any error. |
|
4 |
The data before conversion contains data that cannot be converted. |
a_rdb_RC_CNV_INVALID_FORMAT |
3 |
Check the data to be converted. |
|
5 |
The data type after conversion is not valid. |
a_rdb_RC_CNV_INVALID_DEST_LENGTH |
4 |
For details about the SQL data types, see the topic Data types in the manual HADB SQL Reference. Then check the following specification for any error:
|
|
6 |
The address of the area for storing the data after conversion is not valid. |
a_rdb_RC_CNV_INVALID_DEST_ADDRESS |
5 |
Check the address of the area for storing the data after conversion. |
|
7 |
The length of the area for storing the data after conversion is not valid. |
a_rdb_RC_CNV_INVALID_BUF_LENGTH |
6 |
Check the value of the argument (BufferLength) that specifies the length of the area for storing the converted data. |
|
8 |
The area storing the data before conversion overlaps the area for storing the data after conversion. |
a_rdb_RC_CNV_OVERRAPPING_AREA |
7 |
Check the argument values to make sure that the specified areas do not overlap. |
|
9 |
The specified character string type is invalid. |
a_rdb_RC_CNV_INVALID_CHAR_TYPE |
8 |
Specify the correct character string type. |