Re: How to change the allow delete status on a PF

Hi Mark,

I understand the rationale when deliberately setting it, but in the same fashion as allowing changing the initial file size, number of members or other file attributes that may have been set deliberately, I want full control over the operations allowed to my data. If I have object operational authority I think it should be allowed.

As it happens, the files were originally created on a S/36. The default of the BLDFILE command is to NOT allow deletions. When the files get restored to an i they retain that attribute. It was likely not a deliberate decision, rather one of omission. That means that I'll need to rebuild most or all of the files with ALWDLT set to *YES. I was hoping there's a better/easier way.

-mark

On 8/20/2019 12:55 PM, Mark Waterbury wrote:

Mark,

No and for an important reason. Suppose you want to create an "audit trail" type of "history log" database table? You do not want anyone to ever be able to write a program or use a tool like STRSQL to just go in there and alter the "history" (the historical record ...).

In effect, you would create such a table with ALWUPD(*NO) and ALWDLT(*NO), so it is a "write only" table. Of course, you can still read from it, to query the history, but you can only ever "append" to the history.

Does that help?

Mark S. Waterbury

On Tuesday, August 20, 2019, 12:39:04 PM EDT, mlazarus<mlazarus@xxxxxxxxxxxx> wrote:

Is there a way to change the ALWDLT value from *YES to *NO or *NO to
*YES on a file after it has been created? I don't see it in the CHGPF
command.

-mark