Re: Delete Capable Files?

[Rob Berendt <robertowenberendt@xxxxxxxxx>]

Capability is there.  For example:
DSPFD FILE(SYSIBM/SYSDUMMY1)
Allow read operation  . . . . . . . . . . . :            Yes
Allow write operation . . . . . . . . . . . :            No
Allow update operation  . . . . . . . . . . : ALWUPD     *NO
Allow delete operation  . . . . . . . . . . : ALWDLT     *NO
Restrict on drop  . . . . . . . . . . . . . :            No

Some of these are turned on/off by simple operations.  An example would be
the history file for temporal tables.  When it's 'active' you cannot write
or update it.  It does allow deletes so you can purge old records.

With that being said I'm not sure how mortals control this.
An option would be to add a trigger on the file and that trigger would put
a stop to any deletes.

On Tue, Mar 28, 2023 at 12:00 PM Rich Loeber <rich@xxxxxxxxx> wrote:

> In the S/36 days, I recall that a file could be created so that records
> could not be deleted from them.  I'm looking for a way to do this using a
> PF in DDS, but I'm not seeing it.  Is this just not an option in IBM i DB2
> for a physical file?
>
> Rich Loeber
> Kisco Systems LLC
> https://www.kisco.com
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.