Very timely for us! ... View more

I can't add enough likes to your response @Kurt_Bremser. I have been a sysadmin and a SAS admin for over 20 years. I have to say, I couldn't have survived without the help of TS, especially over the last 5-10 years. They are 3rd level support for us, and for any sensibly-minded SAS admin. ... View more

Sounds interesting, I'll have to take a look when I have a moment.   Thanks so much for the suggestions. ... View more

I'm still reluctant to implement something like that. I can't be absolutely sure but I think there are users who will run things, go and do something else, and then come back and expect the contents of their WORK library still to be there. Although I suppose I could just make the change and then sit back and see how many yells of anguish I get! Thanks for your suggestions anyway ... View more

Thanks @gwootton. How would these settings affect people who are signed in but just not doing anything? A lot of our users start up SAS at the beginning of the day and just leave it idle for most of the time. I'd rather not have them being kicked out ... View more

Sorry, I can't help there, never used that sort of Linux. But looking at version numbers on the MariaDB website I don't think it's any of those. I think they're for installing the DB package. But you probably need the MariaDB Connector/ODBC package if you can find it, or download it from their site. Latest version is 3.1. ... View more

Take a look in the MariaDB website's KnowledgeBase (I don't seem to be able to create any links here). According to this, you need to add something like this to your odbcinst.ini file: [MariaDB ODBC 3.0 Driver] Description = MariaDB Connector/ODBC v.3.0 Driver = /usr/lib64/libmaodbc.so But the path would depend where you've installed the driver. ... View more

Hi Madhan   I have played around with importad.sas but only for the purposes of experimentation in a Lev2 environment. We also don't have Employee ID. samaccountname or distinguishedName are options: samaccountname is the recommended alternative because in some establishments users get put into different OUs. I used distinguishedName because that doesn't happen with us, and our users sometimes get their user IDs changed (different prefixes for different types of user). Even so, distinguishedName can also change if someone has a change of name. It's one (minor) reason why I decided not to take it beyond the experimentation into Lev1. It's worth reading in detail the KB referenced by @Kurt_Bremser, and the appropriate appendix in the Intelligence Platform Security Administration Guide referred to in that. Also, the comments in importad.sas are very useful too. Regarding the filters, I think they will depend on your own AD structure. Mine subsetted the LDAP queries by the initial letter of users' DisplayNames to stop each query timing out in AD (might be the default, can't remember), and only returned groups with a specific prefix (related to users' permissions on the SAS server). But if nothing is getting returned it might be that you need to check the values of the ADPerBaseDN and ADGrpBaseDN macro variables initialised at the beginning. These specify where in the LDAP hierarchy searches for people and groups begin. Hope this helps.   ... View more