Re: Enforcing Read Only Access on files open for maintenance

Alan,

"I had never heard of
OVRDBF to specify *INHWRT = YES
until just now.
You may want to see what happens when the PURGE library is chosen and then
a program is executed that also has an OVRDBF. Does the second OVRDBF
supersede the OVRDBF with *INHWRT = YES"

The ovrdbf also has a SECURE = YES parm that (IIRC) allows the INHWRT =
YES to not be 'overridden' by other (subsequent) ovrdbf commands.

The INHWRT = YES seems to work - my program gave the appearance of a
record being added/maintained but when I DBU'd the file the original
contents were intact.

Eric:

"Do you use group profiles to manage user access to prod data?"

Yes we do use group profiles

"If so, you can enable *USE access to the user's group profile. For the
purge program that writes to the history, use adopted authority for this
program and then grant that user *change authority...."

I think you've misunderstood my intent - I need to prevent users from
updating the Purge library, even though the programs may give the
appearance that the files have been maintained. That's where "OVRDBF
FILE(filename) INHWRT(*YES) SECURE(*YES)" comes into play.

Dennis:

We use group profiles (one of which owns the objects) and *PUBLIC is
always *EXCLUDE. No one has special access. I'm trying to avoid any
program modifications if at all possible. I'll review your items and see
what issues they might raise.

Thanks everyone for your input.

Regards, Jerry

Gerald Kern - MIS Project Leader
Lotus Notes/Domino Administrator
IBM Certified RPG IV Developer
The Toledo Clinic, Inc.
4235 Secor Road
Toledo, OH 43623-4299
Phone 419-479-5535
gkern@xxxxxxxxxxxxxxxx


This e-mail message, including any attachments, is for the sole use of the
intended recipient(s) and may contain confidential and privileged
information. Any unauthorized use, disclosure or distribution is
prohibited. If you are not the intended recipient, please inform the
sender by reply e-mail and destroy this and all copies of this message.