Re: Strange Error Message

The file in question is set up like this:

Allow read operation . . . . . . . . . . . : Yes
Allow write operation . . . . . . . . . . . : Yes
Allow update operation . . . . . . . . . . : ALWUPD *YES
Allow delete operation . . . . . . . . . . : ALWDLT *YES

The customer should have full access to maintain this file.

I'm really puzzled by the reference to a file named MYLIB in library QGPL. Our application does NOTHING in QGPL. I'm going to open a ticket with ProGen to see if they've seen this before.

I'm also puzzled because I can't get it to fail locally.

Rich

________________________________


On 4/1/2022 10:17 AM, Mark Waterbury wrote:

Rob,

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><mailto: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.

Rob Berendt