I wouldn’t expect that to need a change in punctuation because the ‘not found’ message seems to indicate that it was parsed correctly. A punctuation change should be indicated by a SQL syntax error that pointed to a particular token. It wouldn’t get far enough actually to look for the object.

I would want to see the a sample of at least a couple of the fields listed from a DSPFFD XLIB/MD.ALTAD command. First, the command shouldn’t error out with the same ‘not found’ error. Second, the existence of a couple fields would be verified to show that it was a reasonable target for an INSERT statement.

Changing the syntax is a reasonable thing to try. I just wouldn’t expect it to make a difference. But it might.

Tom

But the software tag says “interactive SQL”.

Tom

But you only showed a fragment of your INSERT, so we can’t tell if it was written correctly. We don’t know anything about the file AB.CDE, so we don’t know if it even allows updates. We don’t know if you are authorized to update AB.CDE. We don’t know if AB.CDE is journaled nor what your session attributes were. We might need to know the OS version/release as well as the DB2 group PTF level.

We don’t know what error message you received. Most especially, we don’t know what the message identifier was; so we can’t check any documentation. And we don’t know if any related messages were sent before the error that might have signaled a condition that resulted in the error.

Please provide more detail. It’s almost certain that an answer can be provided.

Tom

In RPG,

C/EXEC SQL SET OPTION commit=*none, closqlcsr=*endmod
C/END-EXEC