SQL/MX 3.2 Messages Manual (H06.25+, J06.14+)

SQLC and SQLCO Preprocessor Messages (13000
through 13999)
HP NonStop SQL/MX Release 3.2 Messages Manual—691121-001
14-8
SQL 13029
Cause. 32-bit and 64-bit modes have different sizes for long data type. Because of
this, there might be some differences in behavior between 32-bit and 64-bit
applications.
Effect. This is a warning message. The application behavior is undefined. The
application behavior differs between 32-bit and 64-bit modes depending on how you
intend to use the long data type.
Recovery. Review the use of long data type in the application. You can ignore this
warning if you intend to use 8 byte data type in 64-bit mode and a 4 byte data type in
32-bit mode. Consider using int data type if you intend to use 4 byte data type in both
32-bit and 64-bit modes, and using a long long data type if you intend to use 8 byte
data type in both modes. Also, if you want to maintain a single source code and
compile the application for both 32-bit and 64-bit modes, consider using int for 32-bit
storage and long long for 64-bit storage.
SQL 13030
Cause. This generic error is displayed when the preprocessor detects a syntax error.
Effect. The preprocessor could not prepare the statement.
Recovery. Use the detail text to determine the problem.
SQL 13031
Cause. You attempted to execute a PREPARE or EXECUTE IMMEDIATE statement.
The preprocessor found one of these errors:

You did not specified more than one host variable of this type.

The host variable that you specified is not character type STRING.
Effect. The preprocessor ignores the host variable.
Recovery. Correct the host variable and resubmit.
13029 Found host variable(s) declared as long. The size of
this data type is 4 bytes for 32-bit and 8 bytes for 64-bit
applications. This can cause unintended behavior if not used
properly.
13030 line number detail text
13031 Expecting a single host variable of type string.