HP NonStop SQL/MX Messages Manual page 384

Table of Contents

Advertisement

SQLC and SQLCO Preprocessor Messages (13000
through 13999)
SQL 13511
13511 End of input file was reached while processing EXEC
SQL.
Cause. NonStop SQL/MX reached the end of the input file while processing EXEC
SQL. The preprocessor was looking for the termination of the EXEC SQL/MX
statement and reached the end of the file before detecting the end of the statement.
There can be mismatched quote marks or parentheses.
Effect. The operation fails.
Recovery. Correct the syntax of the EXEC SQL/MX statement and resubmit.
SQL 13512
13512 Input file error while processing EXEC SQL.
Cause. NonStop SQL/MX received an input file error while processing EXEC SQL.
Effect. The operation fails.
Recovery. Use the errors that accompany this one to diagnose and correct the
problem.
SQL 13513
13513 The BIT data type is not implemented in SQL/MX.
Cause. You specified the BIT data type, which is not supported in NonStop SQL/MX.
Effect. The operation fails.
Recovery. Specify a data type that NonStop SQL/MX supports.
SQL 13514
13514 The CHARACTER SET attribute is not implemented in
SQL/MX.
Cause. You specified the CHARACTER SET attribute, which is not supported in
NonStop SQL/MX.
Effect. The operation fails.
Recovery. Specify a data type that NonStop SQL/MX supports.
HP NonStop SQL/MX Messages Manual—640324-001
14 -24

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

Nonstop sql/mx 3.0

Table of Contents