Re: Enforcing Read Only Access on files open for maintenance

Hi Jerry
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



Alan Shore

NBTY, Inc
(631) 244-2000 ext. 5019
AShore@xxxxxxxx
"If you're going through Hell, keep going" - Winston Churchill

midrange-l-bounces@xxxxxxxxxxxx wrote on 09/18/2007 03:47:56 PM:

Thanks Alan,

"Any user that has *USE access to these files and attempts to use an
existing program that opens one of these files with update, that program
will error out with invalid authority."

I need to avoid that (obviously).

"If any of these programs have adopted authority, bang goes you

security."

I just tested using read only access, but adopted authority 'broke' that
theory. The next test was to issue OVRDBF to specify *INHWRT = YES and
that did seem to work. Since there will be less than 100 objects in the
Purge library, it might be practical to issue OVRDBF *INHWRT = YES
whenever they add the purge library to their library list (and then

delete

the overrides when the remove the purge library). I'm not sure about SQL
updates... but we only have a few programs that do SQL updates and those
could be included in the purge library and compiled with commit = Yes to
prevent them from doing their updates.

Thanks for the 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.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.