×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
-----Original Message-----
From: Rob Berendt [mailto:rob@xxxxxxxxx]
Sent: Friday, November 09, 2018 9:04 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: Authority for temporal tables?
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.
This mailing list archive is Copyright 1997-2024 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.
midrange.com
