Previous Topic: IDCMSCOP07 - restriction description columns changed by another transaction may not be detected prior to UPDATE and/or DELETENext Topic: 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

Compile (CM) Messages › › 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 length

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 length

Reason:

A MOVE or SET statement references the dataview as target, or a CALL statement references the dataview as an UPDATE parameter, in the scope of the FOR. The generated SQL, therefore, includes all columns that can cause it to perform poorly or exceed internal limits for SQL statement length, depending on the number of columns involved.

Action:

Review the code to see if the whole dataview is really needed. Passing only needed columns to a subprogram additionally minimizes the effects of database change on the subprogram. MOVE or SET statements only give rise to this message if the whole set of columns is involved, that is, the dataview and the other structure match completely. COPY dataview might be used when only a subset of the columns was actually needed.