× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi Jerry

Apart from Rob's idea (which looks interesting) unless the box is reasonably
well secured this could be difficult. In any event, *ALLOBJ will always
trump whatever you think of from an authority perspective.

Another option would be to lock the files, although off hand I'm not sure
what lock you would need to leave read access available (*EXCLRD ?). Of
course you'd also have to make sure the job locking the files stayed active
"forever" and would need to allow for this in your backup scripts.

This is what some of the HA vendors do to prevent access on the target
system and I;m figuring they have had plenty of time to think about the
various options...

Hope this helps
Regards
Evan Harris

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]
On Behalf Of GKern@xxxxxxxxxxxxxxxx
Sent: Wednesday, 19 September 2007 7:20 a.m.
To: midrange-l@xxxxxxxxxxxx
Subject: Enforcing Read Only Access on files open for maintenance

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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.