HP NonStop SQL/MX Messages Manual page 460

MXCI Messages (15000 through 15999)
Effect. No report is generated.
Recovery. Enter a BREAK command for the specified column, or reissue the
command that treats the column as a BREAK column.
SQL 15535
15535 The operand of JULTIME or DATEFORMAT function must have
a DATETIME data type.
Cause. You used a JULIANTIMESTAMP or DATEFORMAT function with a column
name having a data type other than DATETIME.
Effect. The operation fails.
Recovery. Reissue the command after connecting it.
SQL 15536
15536 The operand of the CONVERTTIMESTAMP function must have
a LARGEINT data type (binary 64) with a scale of zero.
Cause. You used a CONVERTTIMESTAMP function with a column name having a
data type other than LARGEINT (binary 64 with scale of zero).
Effect. The operation fails.
Recovery. Correct the problem and resubmit.
SQL 15537
15537 An invalid arithmetic operation was attempted between
type1 and type2 data types.
Cause. The two operands of the binary arithmetic operator did not belong to data type
classes that can be operated upon.
Effect. The operation fails.
Recovery. Check that the operands belong to data type classes that can be operated
upon in a binary arithmetic expression.
HP NonStop SQL/MX Messages Manual—640324-001
15 -72