SQL/MX 2.x Messages Manual (G06.24+, H06.03+)

MXCI Messages (15000 through 15999)
HP NonStop SQL/MX Messages Manual—523730-004
14-70
Effect. The operation fails.
Recovery. Use only unique names and resubmit.
SQL 15533
Cause. You specified a SUBTOTAL, BREAK TITLE, or BREAK FOOTING command
or a LINE_NUMBER function for a column that is not a BREAK column.
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
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
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
Cause. The two operands of the binary arithmetic operator did not belong to data type
classes that can be operated upon.
15533 You have specified subtotal or break title or break
footing or line_number on text1. You must specify a BREAK
command on text2 before the LIST command.
15535 The operand of JULTIME or DATEFORMAT function must have
a DATETIME data type.
15536 The operand of the CONVERTTIMESTAMP function must have
a LARGEINT data type (binary 64) with a scale of zero.
15537 An invalid arithmetic operation was attempted between
type1 and type2 data types.