Re: Possible ODBC weirdness when deleting records

On Wed, Mar 9, 2016 at 5:17 PM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:

I'm assuming both files are on the same system?

Yes, and we do not have commitment control or journals.

How about a referential integrity? Is the PK of file getting the deleted
records used as a FK someplace else?

No, no referential integrity, no foreign keys.

Do a DSPFD on both and compare, anything jump out at you? Maybe FRCRATIO?

FRCRATIO is *NONE for both. Every attribute that is shown by DSPFD is
the same, except for file name, file level identifier, number of
records, operation counts, etc.

This technique will only be used if all the following are true:

Nice! This is the kind of fine print I was talking about.

v The target table is not a view.

Check. Neither is a view.

v A significant number of rows are being deleted.

No WHERE clause in either case, so all records.

v The job issuing the DELETE statement does not have an open cursor on the
file
(not including pseudo-closed SQL cursors).

This one is at least a little intriguing. I don't know what a
"pseudo-closed" cursor is. I guess it's conceivable that the SQL
engine is managing cursors in such a way that, the one file is treated
differently than the others. But this is of course opaque to me and
out of my control, and I did everything I could to change up the order
of things and release any explicitly open cursors or locks.

v No other job has a lock on the table.

Nothing showed up using WRKOBJLCK, and I could issue CLRPFM from the
command line on either file when I wasn't deliberately holding a lock
on them.

v The table does not have an active delete trigger.

Check, no triggers.

v The table is not the parent in a referential constraint with a CASCADE,
SET
NULL, or SET DEFAULT delete rule.

We don't use referential constraints.

v The user issuing the DELETE statement has *OBJMGT or *OBJALTER system
authority on the table in addition to the DELETE privilege."

Sorry for my ignorance, but how do I check these? As I reported in a
previous post, everything shown by DSPOBJAUT is identical between the
two files. And of course my user profile is identical to itself.

John Y.