1

SAS

Operations Guide

Prepared by:

Narayana
Hewlett Packard Enterprise Ltd
Date Prepared: 16th March 2017
 SAS
O2 Nucleus
Operations Guide


Document Information
Project Name:
Project Manager: Document 1.0
Version No:
Opportunity Roadmap Document 16th March 2017
Phase: Version Date:
Prepared By: Narayana Preparation 16th March 2017
Date:
Reviewed By: Review Date:

Distribution List

To Action* Date Phone/Fax

V.Narayana 16/03/2017

* Action Types: Approve, Review, Inform, File, Action Required, Attend Meeting, Other (please specify)

Version History
Ver. No. Ver. Date Revised By Description

HP Global Method Error! Unknown document property name. Page 3 of 14

O2 NUCLEUS SAS Operational Procedures


Table of Contents
1 Proprietary Notice........................................................................................................................................ 5
2 Introduction .................................................................................................................................................. 5
3 SAS Environment .......................................................................................................................................... 5
4 SAS Versions ................................................................................................................................................. 6
5 SAS Technical Architecture ........................................................................................................................ 6
6 Health checks on the SAS System ............................................................................................................. 7
7 Backup Schedule & Frequency ................................................................................................................. 8
8 SAS User account Management................................................................................................................ 8
8.1 User Account Creation Process ...................................................................................................... 8
8.2 Linux Account Access ...................................................................................................................... 9
8.3 SAS Database Requirements .......................................................................................................... 9
8.4 User Logon Process ........................................................................................................................... 9
8.4.1 Teradata ............................................................................................................................................ 9
8.4.2 SAS Enterprise Guide 4.3 .................................................................................................................. 9
8.4.3 . SAS Enterprise Guide Explorer ....................................................................................................... 9
8.4.4 . SAS Enterprise Guide 4.3 .............................................................................................................. 10
8.5 User Creation ................................................................................................................................... 10
8.6 Business user..................................................................................................................................... 10
8.7 Steps for setting up the user accounts: ........................................................................................ 11
8.8 Restrictions on the password ......................................................................................................... 12
8.9 User Deactivation ........................................................................................................................... 12
8.10 Monthly auditing ............................................................................................................................. 12
8.11 Reactivation Users .......................................................................................................................... 12
9 Deliverables/weekly/monthly ................................................................................................................. 13
10 Application issues ...................................................................................................................................... 13
10.1 Profile issues: .................................................................................................................................... 13
10.2 Access requests: ............................................................................................................................. 14
10.3 Performance issues: ........................................................................................................................ 14
11 Start/Stop the server: ................................................................................................................................. 14

Hewlett Packard Enterprise Page 4 of 14

O2 NUCLEUS SAS Operational Procedures

1 Proprietary Notice
© 2004 Hewlett-Packard Limited. All rights reserved.

Hewlett-Packard Limited - Registered Office: Amen Corner Business Park, Cain Road,

Bracknell, Berkshire, RG12 1HN

This document is private and confidential and is not to be copied or reproduced, nor its
contents disclosed to any other company or individual other than to those employees and
contractors of O2 (the “Customer”) who have a bona fide need to review this document for the
purpose of evaluation. The information included in this document has been prepared and
included for the purpose of the response required by O2 only and must not be used as a model
or precedent or used in any other situation.

Whilst every effort has been made to ensure the accuracy of the information and statements
contained in this proposal, such statements are based on HPEs understanding of the
information and data supplied by O2. As such, HPE makes no warranty, representation or
undertaking as to the completeness or accuracy of the information contained herein and will not
be responsible for any reliance placed thereon nor for any loss or damage suffered as a result
of such reliance. The warranties for HPE products are contained in the express limited warranty
statements accompanying such products. Nothing herein should be construed as constituting
an additional warranty. Other than as expressly stated in this document, HPE excludes all
express or implied conditions and warranties (whether imposed by statute or otherwise).

2 Introduction

The overview of Business as Usual of O2 SAS production system. The main focus is on server

czhrk-dl580nucprod-310-fe and the SAS applications used by Business users.

3 SAS Environment

There are four services that should be checked if running or not.

1. SAS Metadata Server services.

2. Object Spanner services.

3. Workspace server services.

4. Analytics Platform Server services.

5. Oracle WebLogic Middle tier services.

6. SAS Connect Spanner services.

7. SAS Remote Services.

8. SAS Deployment Tester Server services.

Hewlett Packard Enterprise Page 5 of 14

O2 NUCLEUS SAS Operational Procedures

4 SAS Versions

SAS 9.2 (English)

SAS Data Interaration Studio 4.2

SAS Deployment Manager

SAS Enterprise Guide 4.3

SAS ETS Model Editor 2.1

SAS Locale Setup Manager 2.1

SAS Management Console 9.2

SAS Model Manager Client 2.3

SAS Personal Login Manager 9.2

Platform Computing Flow Manger -7.1

SAS Enterprise Miner Client 6.3

5 SAS Technical Architecture

Hewlett Packard Enterprise Page 6 of 14

O2 NUCLEUS SAS Operational Procedures

The order of events is as given below:

Order of
Event Description
Events
1 Teradata DW will be loaded with the data from ETL Process

2 Establish the ODBC connectivity between Teradata and SAS environment

using SAS DI Studio.
3 SAS DI studio jobs will extract delta data from Teradata into SAS Analytics
SAS Datasets
4 SAS Analytical datasets will be used by all Business users

5 Business Users Extraction of external flat files, Transformation & Adhoc

Reporting Using SAS Enterprise guide application.
6 CRM Insights to generate Predictive Modeling using SAS Enterprise Miner
and SAS Model Manger

6 Health checks on the SAS System

1. Ensure that all the SAS services mentioned are up and running. Using SAS login these can be
checked. If any of the services is down or stopped we have restart the services.

2. Check the status of /saswork

Hewlett Packard Enterprise Page 7 of 14

O2 NUCLEUS SAS Operational Procedures

The SAS workspace server at /saswork on the SAS server shouldn’t reach 100%. Old /
unwanted files of the Business users should be cleared. Individual user will be contacted if
they can delete or not.

3. There are times when a user SAS miner Project diagram will be locked in order to unlock it
the <projectName>.lck file should be deleted manually.

4. The space available on the /home should be always less than 100%; Sometimes Business
users will be saving their files at their /home/<userid>. Advise the user to move the files to
/SASCommon/ instead of their home directory.

6. /SASCommon can’t be more than 95%, should inform the all the SAS users to clear any
unwanted/old files under the /SASCommon directory.

7. User Activities will be captured in the SAS metadata Logs on SAS server. All successful
login/failures will be captured there. Using SAS login we can access the logs.

8. The Default location of logs would be at /opt/sas92/config/Lev1/SASMeta/Logs/

9. Check the SAS EG application login and run sample code.

7 Backup Schedule & Frequency

1. SAS Metadata server backup occurs every day at 2 pm BST.

2. Backup will be available for the last 15 days only.

3. Full /SASCommon backup happens weekly.

4. SAS License will be renewed yearly once.

8 SAS User account Management

Overview of user management of O2 SAS Analytical platform production environment. Main

focus is on SAS Production and Applications SAS EG & SAS Miner.

8.1 User Account Creation Process

1. User LanID
2. Full user name
3. Team or Project that the requesting user is working for.
Hewlett Packard Enterprise Page 8 of 14
O2 NUCLEUS SAS Operational Procedures


4. Business need for using SAS applications – SAS EG/SAS Miner.
5. Approval from the user Service Line Manager/Lead.

Requests will come either from CRM Insights/Tree London/ O2 Media/ Marketing & Consumer
teams. With the authorization procedure by Line Manager or Team leader approval required

8.2 Linux Account Access

UNIX account creation on server czhrk-dl580nucprod-310-fe is based on User account creation

scripts.

SAS user account – created with the same username as the UNIX account by the SAS admin.

Teradata user account – assumed this is already created.

8.3 SAS Database Requirements

No specific SAS Teradata requirements, usually defined by pre-existing access set based on role.
Currently this is normally Insights.

8.4 User Logon Process

Please follow the process steps below in order to access Teradata via SAS Enterprise Guide.

8.4.1 Teradata

Log onto Teradata using one of the Teradata client applications, e.g. Teradata SQL Assistant

On the first log on you will be asked to change your Teradata password.

8.4.2 SAS Enterprise Guide 4.3

Logon to the SAS Server czhrk-dl580nucprod-310-fe as:

user = O2 LAN id (e.g. kguthri1, akumar12 etc.)

password = <available on request>

a) Select Tools > SAS Enterprise Guide Explorer from the drop down menu.

8.4.3 . SAS Enterprise Guide Explorer

Hewlett Packard Enterprise Page 9 of 14

O2 NUCLEUS SAS Operational Procedures


Select File > Manage Logins from the drop down menu.

a). Select TeraAuth

b) .Modify the Teradata logon credentials, enter and verify your new Teradata password.

c) Save and close SAS Enterprise Guide Explorer.

8.4.4 . SAS Enterprise Guide 4.3

a) .Select Servers > SASApp within Server window

b) .Right-click on SASApp, select Disconnect from SASApp to clear all existing
Libraries.
c) .Expand SASApp using the "+" to re-load all applicable Libraries
d). Expand each Library in turn using the "+" to load all the Teradata tables/views that can be
accessed by your account as per the role privileges applicable to your Teradata user account.
e) .Test the Teradata connection by double clicking dataset twmProject in
library Insights_Other, this should run a query against Teradata and return the same data as in
step 1c.

Admin will set up the user accounts on SAS Server, and provide the access required for their role
and tasks, as per the request.

8.5 User Creation

There are four user categories that exist in the O2 SAS environment.

Numbers Business Users Tasks

1 O2 Media Extraction of external flat files,

Transformation & Adhoc
Reporting

2 CRM Insights Predictive Modeling, Advanced

Data Analysis and campaigning

3 Tree London Users Data Analysis and Modeling

8.6 Business user

These user accounts are used for the accessing the SAS applications for developing Predictive
models using SAS Enterprise Miner and using SAS EG for Data Analysis, Extraction of data from
external flat files and import into Teradata Sandbox. These accounts are provided with necessary

Hewlett Packard Enterprise Page 10 of 14

O2 NUCLEUS SAS Operational Procedures


access on the application based on roles and responsibilities of the users.. For Example SAS
Developer, Data Analysts, Advanced Data Modeling Analyst, Support Team etc …

There is a standard procedure in place for creating these accounts on SAS Server environment .

8.7 Steps for setting up the user accounts:

1. Gather the LAN ID from the user as per standard naming conventions also get access
requirements and the name of the applicant.
2. Check if the account setup request is provided with an BMC Remedy case by requestor before
processing the account creation, if yes, proceeds else reject.
3. Check for approval from his Service Line Manager or Project Lead.
4. Grant the required access to the applications, as per the roles and the access requested.
5. Once the account is set up, credentials and instructions will be sent to the requesting user.
Below are different roles, and these can be granted to users, based on the associated groups.

Roles

User Group Description

Insight users CRM Insight users.

Tree London users Tree users.

O2 Media users O2 Priority Moments users.

Support Nucleus users SAS Administrators

Note:

There are certain restrictions on the password usage/maintenance, as shown below in password
standards matrix where as these are exempted from Batch and Reporting users.

Do’s

1. Change the Passwords for every 90 days since the SAS server is on Linux server
password never expires. If user tries wrong password for more than 3 times account will
be locked. User should raise a BMC Remedy to reset the password.

2 .Logging onto the system, at least for every 90 days and avoid disabling users by admin.
SAS user ids will be disabled when users do not logon to the Linux SAS server
continuously for 90 days.
Don’ts

1. Users should not try logging onto the system with wrong passwords more than 3 times as
this with disable the account leaving the user needed to raise an BMC Remedy for the
account to be re-enabled and password reset.

Hewlett Packard Enterprise Page 11 of 14

O2 NUCLEUS SAS Operational Procedures

2. Password length must be between 6-12 characters (case sensitive).

8.8 Restrictions on the password

Minimum password length is 8 and maximum length is 20.

Passwords are case sensitive.
They should be always associated with the user LANID only (lowercase).
By default passwords on SAS server never expire but it is advised to change the password
every90 days.

8.9 User Deactivation

SAS user ids are disabled when users are not logon to the SAS Server for 60 days consecutive days
and the account is removed if the user dos not request reactivation (SAS Admin) after a further 30
days.

8.10 Monthly auditing

DBA will check the below activities as part of monthly auditing of users accounts.

Any user is consuming more space on /home or /saswork.

The space on /SASCommon will be monitored if it’s below the threshold.
If any user is violating the best practices shared. (Example: bulkload option while importing
external files into Teradata).

8.11 Reactivation Users

Disabled users can be enabled by SAS Admin when there is a BMC Remedy request from user
with Approvals.

Roles

Based on the user access requirements access is granted through the role names, which are listed in
the below table.

Hewlett Packard Enterprise Page 12 of 14

O2 NUCLEUS SAS Operational Procedures


RoleName User Group

O2_Insights_Consumer Insights

O2_Insights_SMECorp Insights

O2_Insights_Admin Insights

O2_Insights_Other Insights

O2_Insights_PostPay Insights

Support_Role R&O Support

9 Deliverables/weekly/monthly

Audit Report – User activities.

Capacity Report - Space, CPU, Mounts, performance.

SRM Report – Service Report Monthly. This presents the outages occurred in the month.

High and lows updated share point report for weekly basis.

SAS Metrics updated for weekly basis.

10 Application issues

SAS EG and SAS Miner.

a) User unable to login to SAS application – Check if the user has got the correct
permissions.
b) User not trying correct password or upper case lanID.
c) User query is taking too long time to execute – Check if the query is syntactically correct
and optimized.
d) User not able to access the Teradata Sandbox – Check if the user has read permission on
that particular sandbox.
e) User not able to create a table in the Teradata Sandbox. – Check if the user has write
permission on that particular sandbox.
f) User unable to assign a library – Check if the user has given the right schema name with
case sensitive credentials. Also check that the user has read permission to view the
contents of that table.

10.1 Profile issues:

User unable to launch SAS application.

Hewlett Packard Enterprise Page 13 of 14

O2 NUCLEUS SAS Operational Procedures

a) Check the SAS workspace server of the user.

b) Check whether the username/password is locked or not due to unsuccessful
login attempts.
c) User profile space could be full. Should are advised to clear the unwanted or old files on
their temporary workspace on terminal servers.

10.2 Access requests:

There are three levels of access request: SAS Enterprise Guide or SAS Enterprise miner or both.

10.3 Performance issues:

User submitting bad queries from SAS to Teradata.

11 Start/Stop the server:

Logon to SAS server as “sas” user.

1. To Start the SAS services /opt/sas92/config/Lev1/sas.servers start

2. To Stop the SAS services /opt/sas92/config/Lev1/sas.servers stop
3. To know the status of SAS services à /opt/sas92/config/Lev1/sas.servers status

For all the information of services logs are available at the below location.
/opt/sas92/config/Lev1/SASMeta/Logs/

SAS server would take 15-30 mins approximately to stop the services depending on the number of
users connected to the server at a given time.

It would take 10-15 mins to start up the SAS services and another 10-15 mins to validate the
connectivity to Teradata database and SAS applications Enterprise Guide and Enterprise Miner.

Hewlett Packard Enterprise Page 14 of 14