Accessing a DB2 table using Windows SAS/ACCESS Interface to ODBC, the following error may be returned when trying to delete rows from a table:

   "ERROR: CLI open cursor error: [IBM][iSeries Access
   ODBC Driver][DB2 UDB]SQL7008 - VARname in DB2TableName
   not valid for operation."

Perhaps the most common reason for this error is that the physical file is not journaled. When running with commitment control (the SQL default), journaling is required.

If lack of journaling is the cause (find message SQL7008 in the job log and check reason code), you can either run without commitment control, or start journaling the file.

The DB2 DBA can provide more assistance with this.

If the DBA indicates the file cannot be journaled, you may be able to run without commitment control by altering your ODBC DSN:

Go to the ODBC Administrator and double-click on the DB2 DSN being used and select the Server tab. Press the Advanced button, and select Commitment type (Immediate *NONE).

Another workaround is to change the Commitment Type in the DB2 DSN to Read Committed (CS).

Operating System and Release Information