LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous (more recent) messageNext (less recent) messagePrevious (more recent) in topicNext (less recent) in topicPrevious (more recent) by same authorNext (less recent) by same authorPrevious page (April 2008, week 3)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Tue, 15 Apr 2008 19:25:32 -0400
Reply-To:     Scott Bass <sas_l_739@YAHOO.COM.AU>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Scott Bass <sas_l_739@YAHOO.COM.AU>
Subject:      Re: Allocating SASHELP as readonly under Windows

On Tue, 15 Apr 2008 10:53:07 -0400, Richard A. DeVenezia <rdevenezia@WILDBLUE.NET> wrote:

>Scott Bass wrote: >> Hi, >> >> Is there a way to ensure SASHELP is readonly under Windows? Without >> the gory details, I'd prefer to do this in SAS rather than NTFS >> permissions. >> >> I see the configuration option: >> >> /* Setup the SAS System help directory definition */ >> -SASHELP ( >> "!SASCFG\SASCFG" >> "!sasroot\core\sashelp" >> "!sasext0\inttech\sashelp" >> "!sasext0\mddbserv\sashelp" >> "!sasext0\access\sashelp" >> "!sasext0\af\sashelp" >> "!sasext0\connect\sashelp" >> "!sasext0\graph\sashelp" >> ) >> >> but no way (that I can see) to make this readonly. I have EG users >> saving datasets to SASHELP, which I want to prevent. > >I don't think there is a way in the config file. >- Why not use operating system permissions? >- Why are EG users given admin rights ? >- Is this version 8? > >-- >Richard A. DeVenezia

Thanks to all for the replies so far...

The gory details (gory summary really) is: - All the SAS users are in an NTFS group "SAS Users" - "SAS Users" has been given write access to D:\SAS ***and all subdirectories*** (Base SAS, Conf\Lev1 directories, saswork directory, etc) - These users are not administrators, but have write access to directories they shouldn't modify. - Most users (except admin types) don't have Remote Desktop access, so can't delete DLL's, etc. as one poster responded. - I'm responsible for supporting the SAS environment, but I'm not an administrator myself. - So this issue must be handled by IS, with forms, lag time, the usual bureaucracy.

I was hoping there was a way to allocate SASHELP as a readonly library. Seems like a sensible request really. I'm surprised it's not the SAS default.

It looks like NTFS permissions is the best approach, so I'll raise this issue with IS. They can sort it out.

Thanks, Scott


Back to: Top of message | Previous page | Main SAS-L page