× 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.



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

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.