Skip to main content

Whom does SAS Admin serve?

It is responsibility of a SAS Admin to know who are the users in their environment. We know that SAS is platform for business analytics. There are five roles who make use of this platform, they are.


  • SAS Admin/platform administrator
  • DI developer
  • Data Quality Steward
  • Power User
  • Information consumer.


SAS Admin needs to have little knowledge about all the roles. It will be easy for SAS Admin to solve the issues when people from other roles report an error.

What SAS Admin need to know about other role?
SAS Admin will have access to all client tools. Mostly we will get issues related to tools. By the tools we can deduce what kind of role the user is. For example: Primary tool for DI developer is SAS Data Integration Studio. So if the user reports issues with SAS DI studio we can deduce he/she is a DI Developer.

DI Developer:

DI Developer often create and manages metadata objects used for ETL processing. They deal with libraries and tables. DI developer ask SAS Admins create/remove permission in a particular library/table. Admin need to know does providing permission impact the production. You will be also asked to register table in a particular library.

Tools used by DI Developer are:
SAS Data integration studio
SAS Data quality solution
SAS Scalable performance data server

Data Quality Steward:

Data Quality Steward role is to cleanse data by applying data-cleansing techniques. They monitor data to make sure that the data is consistent and can be used in analysis and reports. They don't have much business with SAS Admin unless they face issue in following applications:

DataFlux Data Management Sutdio
DataFlux Data Management Server

Power User:

The role of power user is to create reports. SAS Admins will be asked to monitor the jobs created by power users. SAS Admins should make sure that the reports are generated. Jobs can be monitored using Platform Manager - Flow Manager tool. Admins are most likely to deal with power user. During migration you need to co-ordinate with power user to ensure all metadata objects gets migrated. Tools used by power user are:

SAS BI dashboard (Also needed for Admin)
SAS Enterprise Guide
SAS Information Map Studio
SAS OLAP Cube Studio
SAS Stored Process

SAS Enterpise Guide is a widely used tool by power user. SAS Admin should know how to install SAS Enterprise Guide. It is wise to keep a document about installation process. You will face lot of issues while SAS EG installation. For example, user may not have installed proper Java version in their computer. Admin need to guide them with proper procedure.

Information Consumer:

Information Consumer use application like Information Delivery Portal, Web Report Studio and SAS Add-in for Microsoft Office. They contact SAS Admin whenever web application is down. Information Delivery Portal and Web Report Studio run on SAS Web Tier. These two applications run on web browser.

SAS Add-in for Microsoft Office is a plugin like feature, once installed, will be visible in Excel and Word. The Add-in integrates SAS menu and tools in Microsoft Office Suite.

Comments

Post a Comment

Popular posts from this blog

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

The authentication server is not SETUID ROOT error in SAS

Question: When validating the SAS Server from SAS Management Console, I received the following error: The authentication server is not SETUID ROOT.  So, I ran the setuid.sh utility and restarted the services many times. I just checked the elssrv sasauth sasperm setuid bit. There were no error in sasauth-debug.log, sasauth-access.log, sasauth-error.log.  Any suggestions? Answer: Please do the following:    1) Run /<SASConfig>/Lev<X>/ObjectSpawner/ObjectSpawner.sh stop  2) Edit /<SASConfig>/Lev<X>/ObjectSpawner/ObjectSpawner.sh and add the code shown below right after SCRIPT=`basename $0`:  if [ -n ""$TKPATH"" ]; then  unset TKPATH  fi   if [ -n ""$TK_PATHLIST"" ]; then  unset TK_PATHLIST  fi    3) Run /<SASConfig>/Lev<X>/ObjectSpawner/ObjectSpawner.sh start  The above code change in ObjectSpawner.sh should fix the issue.
1 comment
Read more

SAS - CLI error trying to establish connection

Issue: User asked me to make a database connectivity to SQL Server. They provided following details SQL server hostname and ip address Database/DSN name Username Password I made entry in ODBC.ini file. You know, SQL Server entries were made in ODBC.ini and Oracle entries were made in TNS.ora file. Everything went fine, took back up of odbc.ini, made entry and saved the file. So to test this connection I ran the libname statement in SAS Enterprise Guide 6.1. It throwed following error. Error Message: My DB team showed that they are able to login   14 GOPTIONS ACCESSIBLE; 15 LIBNAME test ODBC DATASRC=SGE_DS SCHEMA=VST USER=sales PASSWORD=XXXXXXXXX; ERROR: CLI error trying to establish connection: [SAS/ACCESS to SQL Server][ODBC SQL Server Legacy Driver][SQL Server]Login failed for user 'sales'. Solution: First I suspected that Login failed for user 'sales' meant the password provided by DB team was wrong. They responded that they were able to login wi...
3 comments
Read more