Skip to main content

SAS Admin interview question dump

In this post I will put all the SAS Admin questions that were asked in interview. Few of these questions were asked in SAS India, Pune and most of them were from service based companies like TCS, Wipro, Tech Mahindra etc.
Questions:
SAS Hotfix Apply - Detailed steps:
SAS Installation and configuration - Detailed steps
SAS SSL Certificate detailed steps
Difference between Workspace Server and Pooled Workspace Server.
Difference between Pooled Workspace Server and Stored Process Server.
How you will create library?
Have you made connection to DB2 and follow up questions?
Do you know about sasenv file and what is the purpose of it?
What is the purpose of adminusers.txt?
Pre-requisite for SAS installation. Mostly about the SAS part like using tools related to SAS deployment.
In SAS web tier what is SAS_Server1, SAS_Server2 etc.
What is JMS broker?
What is SAS Cache locator?
What is SAS trust not SAS trusted user?
Where do you configure SAS Workspace Server log?
What are the different types of authentication you know?
What is token authentication?
What is IWA?
Difference between PAM and AD?
Metadata clustering.
How grid environment works?
How do you create new queue in LSF?
Command to get job list for last 24 hours in LSF.
Where do user profile get stored in SAS? Profile.sasbcat
What are the components in SAS web tier?
What is plan file? This is related to SAS installation.
What are the Linux scripts you have written.
How do you find the software that are installed in your SAS environment? Deployment registry.

Linux related questions:
How will you get number of CPU core? 
How to get Linux OS name?
How crontab is used?

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.
2 comments
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