Re: Authority for temporal tables? -- MIDRANGE-L

Subject: Re: Authority for temporal tables?
From: Rob Berendt <rob@xxxxxxxxx>
Date: Fri, 9 Nov 2018 10:04:09 -0500
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Justin,

The temporal table history table is a whole different animal. QSECOFR
does not have change authority to it. Actually it is not done by
authority at all. Pick any file. Do a DSPFD on it. Notice these fields?
Allow read operation . . . . . . . . . . . :
Allow write operation . . . . . . . . . . . :
Allow update operation . . . . . . . . . . : ALWUPD
Allow delete operation . . . . . . . . . . : ALWDLT

In a temporal table history file, the only allow turned on is delete and
read. Delete is so that one can purge data. All other updates come from
IBM approved APIs. The way you flip that off/on is to use the commands to
unlink the temporal function.

So your assumption that DB2 is doing the insert and the user does not need
access is correct.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Authority for temporal tables? , Justin Taylor

This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.