I'm just seeing this part of the thread so forgive me if I am off base, but
is this a commitment control issue?
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John
Yeung
Sent: Wednesday, March 09, 2016 5:21 PM
To: Midrange Systems Technical Discussion
Subject: Re: Possible ODBC weirdness when deleting records
On Wed, Mar 9, 2016 at 5:01 PM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:
Wild guess. DSPFD and see if one is an SQL file type -> TABLE.
No, they are both classic DDS-based data PFs. In DSPFD, "Type of file"
says "Physical" and "File type" says "*DATA". There is no "SQL file type"
attribute. The only mention of SQL or tables is the attribute labeled
"Partitioned SQL Table", and that's "No".
Interestingly, the clearable one does have an SQL view that includes it. But
that view uses a bunch of files, and the other files in the view are not
SQL-clearable.
So the situation is
FileA (used by ViewX) - needs a lock to SQL DELETE, which performs clear,
not delete
FileB (not used by any view) - SQL DELETE always leaves deleted records,
never clears, even when there is no lock
FileC (used by ViewX) - SQL DELETE always leaves deleted records, never
clears, even when there is no lock
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.
As an Amazon Associate we earn from qualifying purchases.