Skip to main content

What is the scope of SAS Admin?

You know SAS is a tool installed on top of OS like Windows or Linux. Often SAS Admins were assigned task done by system admin. There is no harm in learning new stuffs but in the end we are not aware which task belongs to whom.

SAS Admin role starts once the SAS platform is installed, configured and validated. In my experience, primary installation and configuration were done by SAS Tech Support. Once installation is done, it is responsibility of SAS Admin to keep the platform active.

High priority tasks:

Security:

Major task of SAS Admin will be planning the security. Security should be added in the OS level where all the SAS configuration file resides. You know that making changes to repository data sets will make them unusable. Proper security should be added to that directory in OS level so that normal users won't have access to that directory.

Backup:

Plan your backup activity. It will be a one time task. It is necessary to backup both metadata repository as well as the associated physical files.

Standard tasks:

Add users:

Adding user in metadata level and making sure that the added user is able to access SAS. Adding user may sounds easy but later if the user is not able to access SAS it is responsibility of SAS Admin. It is responsibility of SAS admin to provide working installation guide.

Taking care of Metadata folder:

You know all the metadata like library, table, info map and report were stored in SAS folders. SAS Admin need to take care of the folder structure and permission to that folder.

Data sources:

It is duty of SAS Admin to establish connection to the data source that your customer requests. Usually it requires changes to be made in OS level. For example: to make connection to Oracle database you need to make the entry of data source name in odbc.ini file. This task can be done by SAS Admin if he/she has proper permission to access the file or request your system admin to do the task. By the end it is duty of SAS admin to validate the connectivity.

Creating repository:

SAS Admin should know how to create a new custom and project repository.

Everyday activity:
SAS Admin should take care of all the servers (Metadata server, Workspace server etc). You need to make sure that servers are up and running fine. Backup also comes under everyday activity. Make sure you do full backup of metadata server. Metadata backup can be automated but ensure that the backup is successful and usable.

Promoting object (Import and Export):

In any typical organization we have a test environment and production environment. Objects were tested first in test environment and then promoted to production environment. SAS Admin should know how to promote single object or group of object from one environment to other.

SAS Admin vs System Admin
In many organization, the role of SAS admin and system admin were split.

SAS admin: He/she should have little knowledge of SAS and the architecture. He/she should be familiar with the content created. SAS deployment should be taken care by SAS Admin. SAS Admin have limited/little access to physical host where the SAS runs.

System Admin: Should take care of physical system. Can be with no knowledge about SAS.

Comments

Post a Comment

Popular posts from this blog

Starting Gemfire in SAS

Gemfire is available in both Compute and Mid. The default port is 41415. If you have many gemfire, you may have port numbers incremented by 1, for example: 41416. Gemfire is located under Web. <SASCONFIG>/Web/gemfire. To Start: <SASCONFIG>/Web/gemfire/instances/ins_41415/gemfire-locator.sh start To check Status: <SASCONFIG>/Web/gemfire/instances/ins_41415/gemfire-locator.sh status To stop: <SASCONFIG>/Web/gemfire/instances/ins_41415/gemfire-locator.sh stop If it doesn;t start check port number is occupied by any other process. lsof -i tcp:41415 If you only have one instance then 41415 will be default. If you have Lev2 then it will be 41416
Post a Comment
Read more

SAS 9.4 server startup order

In Linux / Unix OS we normally use sas.servers to start the services. The script in the background follows an order to start the services. It is important to follow the order to run the services correctly. In this post we can see what is the order to start / stop and to generate the sas.servers script. It is not really required to memorize the order because SAS provide an utility to create the sas.servers script automatically which will start / stop the service in order. Starting order SAS Metadata server Olap server SAS object spawner SAS / SHARE server SAS / connect spawner SAP table server SAP remote services SAS deployment tester server Stopping will be the same in reverse. How to create sas.server script? We can create sas.server script by using generate_boot_script.sh. if you have made any changes to your environment like adding a new server or spawner we can use the script to generate new sas.server. You can use the script even if you have removed the spanner o...
Post a Comment
Read more

Insufficient authorization to access PIPE error in SAS EG

Issue: When I tried to run SAS code in SAS Enterprise Guide it throws following errors: ERROR: Insufficient authorization to access PIPE. ERROR: Error in the FILENAME statement. Screenshot of error: Solution: This error occurs when you try to run OS commands in SAS code. To run the OS commands in SAS code you need to enable XCMD option. You check it in SAS Management Console by following below steps.   Open SMC -> Expand Servers -> Expand   In SASApp , expand Logical Workspace Server -> right click on Workspace Server. Click properties -> option tab -> advanced options -> launch properties. Check whether Allow XCMD is checked. The issue arises if the Allow XCMD is not checked. In above image, Allow XCMD option is not checked. It should be checked to run OS commands from SAS code. In Unix /Linux machines, this XCMD option can be enabled by using system option XCMD in sasv9 config file or workspaceserver.sh script f...
2 comments
Read more