Kumar, if you are already moving towards an "admin" role: - read, read, read. Since there are literally tons (in terms of paper, if printed) of SAS documentation out there, that is an absolute prerogative. I have found that posting the contents of an error message or a log in google with "SAS" prepended often returns a usable link to information immediately. - get a solid grip on the operating system which is used for the SAS server. With CLI access, you may find you can solve lots of problems quickly using generic OS tools. Server OS's are VERY powerful, and the "read, read, read" is also valid there. Knowledge of the server OS puts you on an equal footing with those who run/administrate it. Large operations tend to produce people who avoid work by feeding bullshit to those that they consider to have no clue. Proving them wrong can be exhilarating and rewarding . I often find myself (in the admin role) close to falling into this trap, so I force myself to rethink WHY I have placed certain restrictions on users. - real security for data has to be done at the OS level. Only there can you be sure that nothing untowards happens (think of your case: restricting access via metadata is useless if you can still use the CL to copy a file to your sasuser directory). - if then you have problems that seem impossible to solve, or if you suspect that there may be more efficient solutions, don't hesitate to open threads here or in other places (stackexchange.com, stackoverflow.com etc). That way you tap into the cumulative wisdom of the whole _planet_.
... View more