Text |
SQLDISCONNECT not allowed while a transaction is open. |
Explanation |
SQLDISCONNECT cannot be executed while a transaction is open. |
Action |
Issue END TRANSACTION or BACKOUT TRANSACTION before executing SQLDISCONNECT. |
Text |
Syntax error found in SQLDISCONNECT statement. |
Explanation |
A syntax error was detected in an SQLDISCONNECT statement. |
Action |
Correct the SQLDISCONNECT statement. |
Text |
Already connected to SQL database. |
Explanation |
SQLCONNECT failed, because a connection to an SQL database is already established. |
Action |
Close the existing connection with SQLDISCONNECT before executing SQLCONNECT. |
Text |
Syntax error found in SQLCONNECT statement. |
Explanation |
A syntax error was detected in an SQLCONNECT statement. |
Action |
Correct the SQLCONNECT statement. |
Text |
SQL date/time conversion failed. |
Explanation |
SQL date/time conversion failed, because the data to be converted do not correspond to the date/time conversion mask. |
Action |
Check the mask for SQL date/time conversion which is specified for this DBID. |
Text |
IF NO RECORDS not allowed in SELECT with SCROLL and GIVING. |
Explanation |
IF NO RECORDS FOUND is not allowed in a SELECT statement with SCROLL and GIVING clause. When using SCROLL and GIVING clauses the application requests to act on the returned SQLCODE in the GIVING variable. This causes the NO RECORDS FOUND block never to be executed. Therefore the NO RECORDS FOUND clause is useless and not allowed. |
Action |
Remove either the NO RECORDS FOUND clause or the GIVING clause from the SQL statement. |
Text |
SQL database connection has been terminated. |
Explanation |
In high-availability (HA) mode a connection to an SQL database was terminated due to the termination of the hosting process during terminal I/O. |
Action |
Assure that the access to an SQL database is finished before a terminal I/O happens. This can be accomplished by using the SQLCONNECT/SQLDISCONNECT statements in the application. |