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

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