Previous Topic: IDCMSCOP01 - Dataview dvw-name, a read-only dataview, is updated or DELETEd in the scope of the FOR constructNext Topic: IDCMSCOP03 - "NO UPDATE" was specified, but dataview dvw-name is updated or DELETEd in the scope of the FOR construct

Compile (CM) Messages › › IDCMSCOP02 - The set of rows selected can be lost in the scope of the FOR-construct by crossing an LUW boundary (for example, TRANSMIT, COMMIT/BACKOUT, CHECKPOINT/ROLLBACK)

IDCMSCOP02 - The set of rows selected can be lost in the scope of the FOR-construct by crossing an LUW boundary (for example, TRANSMIT, COMMIT/BACKOUT, CHECKPOINT/ROLLBACK)

Reason:

Warning only: In the FOR-construct, a TRANSMIT or other database commit point was detected. If executed at run-time, the program loses the SQL CURSOR active for that FOR construct and subsequent references to the SQL CURSOR used by the FOR-construct causes a run-time error.

Action:

Executing a TRANSMIT, CHECKPOINT/COMMIT, or BACKOUT/ROLLBACK is generally acceptable as long as the FOR construct is QUIT before obtaining the next record (for example, as part of an error logic path). An <<ERROR>> PROCEDURE is considered to be logically in the scope of all FOR constructs in a program.