RE: Possible ODBC weirdness when deleting records

Does the same thing happen regardless of run order?

So you delete the contents of table A then table B and table A shows no deleted records and table be does show them.

Does deleting the contents of table B then table A show table B as not having any deleted records and table A showing deleted records?

Thanks,

Gary Monnier


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John Yeung
Sent: Wednesday, March 09, 2016 1:55 PM
To: Midrange Systems Technical Discussion
Subject: Re: Possible ODBC weirdness when deleting records

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.