Previous Topic: IDCMSCOP08 - A group move into the dataview has been detected in the scope of the FOR. This may cause unnecessary column access, and/or excessive SQL text lengthNext Topic: IDCMSCOP10 - Variable/Literal after FOR FIRST is too long (max. 9 characters are allowed)

Compile (CM) Messages › › IDCMSCOP09 - Columns are being dropped from the search condition to avoid SQL text overflow. Columns updated by another transaction may not be detected prior to UPDATE and/or DELETE

IDCMSCOP09 - Columns are being dropped from the search condition to avoid SQL text overflow. Columns updated by another transaction may not be detected prior to UPDATE and/or DELETE

Reason:

Not all columns updated in the scope of the FOR construct can be checked for simultaneous update by another transaction because of internal limits on the length of the generated SQL text. To avoid run-time error conditions, CA Ideal limits the total length of the SQL text by not including all referenced columns. This situation is most likely to arise when message CMSCOP08 is also issued.

Action:

Review the code to see if the columns involved are really updated by the program. Moving unchanged values into the dataview buffer cause CA Ideal to generate inappropriate SQL integrity checking.