Looking for a way to put our UniData system in a read-only mode.  I'm not talking about the UniData files, just our production files.

I was thinking I'd have to do it at the OS level.  But I thought I'd check with the community to see if such a "switch" exist. 

We are running UniData 8.2 on Window2019 server.

Thanks.

------------------------------
David Green
Computer Programmer
Rocket Forum Shared Account
------------------------------

You can use BEFORE triggers here based upon a user property. e.g. UID, GID, or a flag in named COMMON set by the application,

------------------------------
John Jenkins
Thame, Oxfordshire
------------------------------

---

Looking for a way to put our UniData system in a read-only mode.  I'm not talking about the UniData files, just our production files.

I was thinking I'd have to do it at the OS level.  But I thought I'd check with the community to see if such a "switch" exist. 

We are running UniData 8.2 on Window2019 server.

Thanks.

------------------------------
David Green
Computer Programmer
Rocket Forum Shared Account
------------------------------

David,

The simplest method for this is use OS permissions as you have noted. You could also look at using a BEFORE TRIGGER but that would need to be added to each file you wish to restrict. The follow on question I would have from making the production files read only is how are going to deal with a blocked write failure in your application code, the write statements would need some ON ERROR processing to avoid lots of messy messages appearing.

One environmet variable you may find useful if you do this the VOC_READONLY environment variable, as users must have read and write access to the VOC unless you set the VOC_READONLY environment variable. There are certain UniData files you don't want to lock out though, please refer to the Administration pdf for more details on that.

I did think about discussing SQL permissions here for you but I think that is even more work to implement.

Regards,



------------------------------
Jonathan Smith
UniData ATS
Rocket Support
------------------------------

---

You can use BEFORE triggers here based upon a user property. e.g. UID, GID, or a flag in named COMMON set by the application,

------------------------------
John Jenkins
Thame, Oxfordshire
------------------------------

Thanks for all the replies. We'll probably just use the OS permissions with a full backup copy of our production files for any easy resets.

------------------------------
David Green
Computer Programmer
Rocket Forum Shared Account
------------------------------

---