Re: *ALLOBJ question

my head just exploded.

On 11/21/2023 9:17 AM, Rob Berendt wrote:

There are a number of ways to do this. As Jim said, many of them require
the following:

Resource
ID Option Feature Description
5770SS1 47 5119 IBM Advanced Data Security for i

One way is by RCAC or Row and Column Access Control.
https://www.ibm.com/docs/en/i/7.5?topic=files-using-permissions-masks-secure-data

ALTER TABLE ... RESTRICT ON DROP will thwart DLTF even from someone with
*ALLOBJ.https://www.ibm.com/docs/en/i/7.5?topic=object-restrict-drop

There are properties on CRTPF like ALWUPD, ALWDLT.
https://www.ibm.com/docs/en/i/7.5?topic=files-using-database-file-capabilities-control-io-operations

A temporal table history table will have some restrictions like ALWUPD,
ALWADD set so that only the temporal table operations can add rows. Delete
will still be allowed so you can purge obsolete history.

And, since you mentioned authorization lists, you might be interested in
the following.
https://www.ibm.com/docs/en/i/7.5?topic=changes-authority-requirements-change-autl-interfaces

There are many functions which come into play also:
https://www.ibm.com/docs/en/i/7.5?topic=reference-supplied-function-ids

And I suppose you could write a trigger that if user DOUG is the job user
then throw an exception on an update or add.

Some of these may not be applicable to *CMD objects.