Previous Topic: IDCMSCOP05 - The FOR construct is specified with an ORDERED clause and has dataview updates or DELETEs in its scope. To support this, dataview dvw-name must have a ROWIDNext Topic: IDCMSCOP07 - restriction description columns changed by another transaction may not be detected prior to UPDATE and/or DELETE

Compile (CM) Messages › › IDCMSCOP06 - Since DVW dvw-name does not have a ROWID, a RUN-time error will occur if an update at the ENDFOR or a DELETE is attempted after the database LUW has ended

IDCMSCOP06 - Since DVW dvw-name does not have a ROWID, a RUN-time error will occur if an update at the ENDFOR or a DELETE is attempted after the database LUW has ended

Reason:

Warning: No set of columns in the dataview constitutes a unique key for the underlying SQL TABLE. In the scope of the FOR-construct, the SQL CURSOR can be lost due to a TRANSMIT, CHECKPOINT/ROLLBACK, COMMIT/BACKOUT, or a CALL (which is presumed to do a TRANSMIT, and so on). Subsequent updates or deletes cause a run-time error.

Action:

There is no error involved if the FOR construct is QUIT before update or DELETE is actually processed or if there is no TRANSMIT or database commit processing is actually executed in the scope of the FOR (either by this program or the CALLed sub-program).