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 email@example.com.
See the CRTPF command, prompt, press F10 for additional parameters, and look for:
Allow update operation . . . . . ALWUPD *YES
Allow delete operation . . . . . ALWDLT *YES
This is useful for example when creating a "log" or history file where you want to allow the application to write new records, but you do not want users to be able to update or delete the "history" (so then set the above attributes to *NO).
It is only the "Allow Read" and "Allow Write" that are apparently reserved for IBM internal use only.
Mark S. Waterbury
On Friday, April 1, 2022, 10:07:53 AM EDT, Rob Berendt <rob@xxxxxxxxx> wrote:
Then the "real" file it is being overridden to may be different on one system to the next. Do a DSPFD on the file it is being overridden to.
Look for these options on the DSPFD:
Allow read operation
Allow write operation
Allow update operation
Allow delete operation
Normally changing these is out of the hands of us mortals and is reserved by IBM. A very simple example of when this occurs is when you start a "temporal" table the history table will have write's and updates blocked but you can still delete so that you can purge off old rows.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2023 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
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.