Rob
IIRC, the Application Administration stuff can block even an *ALLOBJ
user from certain actions. Now I don't know that file operations are
registered there.
Nor do I know if QSECOFR can be blocked from anything - probably not!
Vern
On 2/6/2013 3:11 PM, rob@xxxxxxxxx wrote:
He doesn't want to do it with security.
He wants to do it with options that even QSECOFR can't update or delete
rows.
He sees the options in CRTPF:
CRTPF ... ALWUPD(*NO) ALWDLT(*NO)
and wants those options on CHGPF.
However I don't think that's possible. I think he may have to study how
one is supposed to initially put data into a table created with
ALWUPD(*NO) ALWDLT(*NO).
