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

Binder and Compilation Messages (4000 through
4999)
HP NonStop SQL/MX Messages Manual—523730-004
6-27
Recovery. Reword the query so that the expression inside the other sequence
function does not contain references to the THIS function.
SQL 4109
Cause. You specified a query that includes a SEQUENCE BY clause that contains an
illegally placed sequence function name. Sequence functions (such as RUNNINGSUM,
MOVINGSUM, LASTNOTNULL) are supported only in the select list or the HAVING
clause of the query expression containing the SEQUENCE BY clause. For example,
these queries are legal:
>>select a, runningcount(b) from T1 sequence by a;
>>select x from (select a, runningcount(b) from T1 sequence by
a) T2(x,y) where y > 10;
>>select count(*) from t1 sequence by b group by a having
runningsum(a) > count(*);
Effect. The operation fails.
Recovery. Correct the syntax and resubmit. For example:
>>select a from T1 where runningcount(b) > 10 sequence by a;
*** ERROR[4109] Sequence functions placed incorrectly:
RUNNINGCOUNT(CAT.SCH.HPPARTEST1.B).
*** ERROR[8822] Unable to prepare the statement.
SQL 4110
Cause. You specified a query that contains a sequence function name but no
SEQUENCE BY clause, which is not supported. The value of the sequence function
depends on the specific sequence (order) of the rows. If no sequence is defined, the
result of the sequence function is dependent on an arbitrary ordering of the rows,
which could lead to unexpected results.
Effect. The operation fails.
Recovery. Correct the syntax and resubmit. For example:
>>select runningsum(a) from t1;
*** ERROR[4110] The query contains sequence functions but no
SEQUENCE BY clause: RUNNINGSUM(CAT.SCH.T1.A).
4109 Sequence functions are placed incorrectly: name.
4110 The query contains sequence functions but no SEQUENCE BY
clause: name.