Re: Enforcing Read Only Access on files open for maintenance

["Peter Dow (ML)" <maillist@xxxxxxxxxxxxxxx>]

Hi Jerry,

You could try OVRDBF INHWRT(*YES).

*Peter Dow* /
Dow Software Services, Inc.
909 793-9050
pdow@xxxxxxxxxxxxxxx <mailto:pdow@xxxxxxxxxxxxxxx> /

GKern@xxxxxxxxxxxxxxxx wrote:
> Not sure if the title is 'correct' for this discussion but here is what I 
> need to analyze:
>
> We want to purge some rather large files by moving (identified) records 
> into an image of the files that will reside in a different (Purge) 
> library. The Purge library will contain only physical files and all 
> related LF's and SQL indexes.
>
> Since users will need to be able to access the data in the Purge library, 
> I need to ensure they cannot update it since it is now 'historical'.
>
> I'd prefer that the users be able to use the same programs to access the 
> production and purged data. An option from their initial menu will allow 
> them to add/remove the Purge library to/from the top of their library 
> list. 
>
> The question is this: Is it practical/possible to just change the object 
> authority of all of the objects in the Purge library to read only? Will 
> this prevent unwanted updates to the historical data - even though the 
> existing/unmodified programs (used for production data) may attempt to 
> maintain the data? Would SQL updates (with *commit = NO) be able to update 
> the 'read only' data in the Purge library?
>
> Any gotcha's? Suggestions?
>
> Thanks!
>
> 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.
>