Re: Possible ODBC weirdness when deleting records

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

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

What's the journal status of the files?

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

Just guessing at this point. From the manual and SQL delete that doesn't
use a WHERE clause
"will delete all rows of a table. In this case, the rows may be deleted
using
either a clear operation (if not running under commitment control) or a
change file
operation (if running under commitment control). If running under commitment
control, the deletes can still be committed or rolled back. This
implementation will
be much faster than individually deleting each row, but individual journal
entries
for each row will not be recorded in the journal. This technique will only
be used
if all the following are true:
v The target table is not a view.
v A significant number of rows are being deleted.
v The job issuing the DELETE statement does not have an open cursor on the
file
(not including pseudo-closed SQL cursors).
v No other job has a lock on the table.
v The table does not have an active delete trigger.
v The table is not the parent in a referential constraint with a CASCADE,
SET
NULL, or SET DEFAULT delete rule.
v The user issuing the DELETE statement has *OBJMGT or *OBJALTER system
authority on the table in addition to the DELETE privilege."

Charles



On Wed, Mar 9, 2016 at 4:55 PM, John Yeung <gallium.arsenide@xxxxxxxxx>
wrote:

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

Delete triggers also cause a record by record deletion to occur.

Neither of the files has any triggers.

Lastly, only need *CHG authority to the data to delete every record. You
have to have more authority than that to use CLRPFM or for SQL to delete
the data in one shot.

That makes sense. But the DSPOBJAUT output of the two files is
identical except for the object name. Specifically, *PUBLIC has *ALL
object authority, there is an 'X' in all the object and data columns,
and *NONE for authorization list. Both show QPGMR as the owner and
*NONE as primary group. And *SYSBAS as the ASP device, for
completeness. :P

Anywhere else to look for this kind of thing?

John Y.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.