Re: Preventing an update or delete

[Booth Martin <booth@xxxxxxxxxxxx>]

Define the affected fields as I (input only) fields.  Those fields can 
still be validated, but existing data can not be updated.

Another choice would be to allow B (both) from the subfile, but when a 
request is made to update or delete, not let the change take place and 
send the data, the time, and the user's name to an undisclosed location 
where it can be evaluating for "creativeness" by supervisory personnel.

And yes, you can add an indicator and make the field DSPATR(PR) (protected)

On 3/15/2016 4:38 PM, Hoteltravelfundotcom wrote:
> HI we have a program which is a subfile. It tracks company rebates. They
> would like to only allow the user to enter data. No delete and no update.
> If they want that, they will ask us.
>
> The reason is the company suspects some creativeness that the sales folks
> are doing.
>
> My question is, what is the easiest and best way to accomplish this? Is
> there an indicator on the DDS level I can use that would protect the field
> on any other than enter?