SAS® Scalable Performance
Data Server® 4.5
Administrator’s Guide
The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2009. SAS® Scalable Performance Data Server® 4.5: Administrator’s Guide. Cary, NC: SAS Institute Inc.
SAS® Scalable Performance Data Server® 4.5: Administrator’s Guide
Copyright © 2009, SAS Institute Inc., Cary, NC, USA
All rights reserved. Produced in the United States of America.
For a hard-copy book: No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, or otherwise, without the prior written permission of the publisher, SAS Institute Inc.
For a Web download or e-book: Your use of this publication shall be governed by the terms established by the vendor at the time you acquire this publication.
U.S. Government Restricted Rights Notice: Use, duplication, or disclosure of this software and related documentation by the U.S. government is subject to the Agreement with SAS Institute and the restrictions set forth in FAR 52.227-19, Commercial Computer Software-Restricted Rights (June 1987).
SAS Institute Inc., SAS Campus Drive, Cary, North Carolina 27513.
1st electronic book, June 2009
SAS® Publishing provides a complete selection of books and electronic products to help customers use SAS software to its fullest potential. For more information about our e-books, e-learning products, CDs, and hard-copy books, visit the SAS Publishing Web site at support.sas.com/publishing or call 1-800- 727-3228.
SAS® and all other SAS Institute Inc. product or service names are registered trademarks or trademarks of SAS Institute Inc. in the USA and other countries. ® indicates USA registration.
Other brand and product names are registered trademarks or trademarks of their respective companies.
Contents
PART 1 Product Notes 1
Chapter 1 • SPD Server 4.5 Product Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 What's New in SPD Server 4.5? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 SPD Server 4.5 Platform Support Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
PART 2 Installation 5
Chapter 2 • SPD Server Pre-Installation and System Requirements Guide . . . . . . . . . . . . . . . . . 7
AIX Requirements and Tuning for 64-bit SPD Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 HP-UX Requirements and Tuning for 64-bit SPD Server . . . . . . . . . . . . . . . . . . . . . . . . 7 Required Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Solaris on Sparc Requirements and Tuning for 64-bit SPD Server . . . . . . . . . . . . . . . . . 9 Solaris on X64 Requirements and Tuning for 64-bit SPD Server . . . . . . . . . . . . . . . . . . 9 Linux on X64 Requirements and Tuning for 64-bit SPD Server . . . . . . . . . . . . . . . . . . . 9 Windows Requirements and Tuning for 32-bit SPD Server . . . . . . . . . . . . . . . . . . . . . 10 SPD Server 4.5 Client Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Chapter 3 • SPD Server UNIX Installation Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
SAS Scalable Performance Data Server 4.5 and SAS Deployment Wizard . . . . . . . . . 12 Before You Install: Precautions and Required Permissions . . . . . . . . . . . . . . . . . . . . . . 12 Packing List for SPD Server Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Upgrading SPD Server 3.x to SPD Server 4.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Upgrading SPD Server 4.x to SPD Server 4.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Configuring SPD Server Host Software for Your Site . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Verify That SPD Server 4.5 Is Running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Configuring SPD Server Client Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Testing Your SPD Server Installation Using SAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 SPD Server Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 SPD Server 4.5 and the SAS Management Console Utility . . . . . . . . . . . . . . . . . . . . . . 30 SPD Server Lightweight Directory Access Protocol (LDAP) Authentication . . . . . . . . 30 Notes for SPD Server Administrators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Chapter 4 • SPD Server Windows Installation Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
SAS Scalable Performance Data Server 4.5 and SAS Deployment Wizard . . . . . . . . . 38 Before You Install: Precautions and Required Permissions . . . . . . . . . . . . . . . . . . . . . . 38 Packing List for SPD Server Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Validating Default Port and Library Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Initializing the Password Manager Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Installing SPD Server as a Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Configuring SPD Server Software on Your Windows Host . . . . . . . . . . . . . . . . . . . . . 44 Upgrading SPD Server 3.x to SPD Server 4.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Upgrading SPD Server 4.4 to SPD Server 4.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Installing and Configuring SPD Server Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Testing Your SPD Server Installation Using SAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
iv Contents
SPD Server Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 SPD Server and the SAS Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Lightweight Directory Access Protocol (LDAP) Authentication . . . . . . . . . . . . . . . . . . 52 Notes for SPD Server Administrators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
PART 3 Migration 57
Chapter 5 • SPD Server 3.x to SPD Server 4.5 Conversion Utility . . . . . . . . . . . . . . . . . . . . . . . . 59
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Before You Convert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Overview of the SPDSCONV Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Using SPDSCONV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 SPDSCONV Utility Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
PART 4 Configuration 65
Chapter 6 • Using the SPD Server Name Server to Manage Resources . . . . . . . . . . . . . . . . . . . 67
Managing Computing Resources with a Name Server . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Configuring SPD Server on a Corporate Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Chapter 7 • Administering and Configuring SPD Server Using the SAS
Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
The SAS Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Accessing the SPD Server Manager in SAS Management Console . . . . . . . . . . . . . . . . 72
Password Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
ACL Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Server Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
SPD Process Profiler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Proxy Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Chapter 8 • SPD Server SQL Query Rewrite Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Overview of the SQL Query Rewrite Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Configuring Storage Space for the SQL Query Rewrite Facility . . . . . . . . . . . . . . . . . . 89 SQL Query Rewrite Facility Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Chapter 9 • Using SPD Server With Other Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Using Open Database Connectivity (ODBC) to Access SPD Server Tables . . . . . . . . . 94 Using JDBC (Java) to Access SPD Server Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Using htmSQL to Access SPD Server Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Using SQL C API to Access SPD Server Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Chapter 10 • Configuring Disk Storage for SPD Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 SPD Server Component File Types and Sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Creating SPD Server Component Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Configuring LIBNAME Domain Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Recommended: Use ROPTIONS= . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Chapter 11 • Setting Up SPD Server Parameter Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Contents v
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Syntax for the -PARMFILE Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112 Syntax for the spdsserv.parm Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 spdsserv.parm Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 SPD Server Parameter File Configurations for LDAP . . . . . . . . . . . . . . . . . . . . . . . . .119 SPD Server Parameter File Configurations for Auditing . . . . . . . . . . . . . . . . . . . . . . .120
Chapter 12 • Setting Up SPD Server Libname Parameter Files . . . . . . . . . . . . . . . . . . . . . . . . .123
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123 Domain Naming Syntax for Libnames.parm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Domain Path Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Consistency in Nomenclature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126 Domain Access Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127 Organizing Domains for Scalability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .131 Domains and Data Spaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133 Example Libname.parm File Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Chapter 13 • Setting Up SPD Server Performance Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141
Starting the SPD Server Performance Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142
Performance Server Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
PART 5 Security 147
Chapter 14 • ACL Security Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
ACL Security Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150 SPD Server ACL Security Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .150 Controlling SPD Server Resources with PROC SPDO and ACL Commands . . . . . . .154 Symbolic Substitution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .165 DICTIONARY.PWDB and DICTIONARY.ACLS . . . . . . . . . . . . . . . . . . . . . . . . . . .186 Using SPD Server with an Internet Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 SPD Server Auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Chapter 15 • Managing SPD Server Passwords, Users, and Table ACLs . . . . . . . . . . . . . . . . .193
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193 The Password Manager Utility psmgr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193 SAS Management Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204 LDAP Authentication Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .204
PART 6 System Management 207
Chapter 16 • SPD Server Operator Interface Procedure (PROC SPDO) . . . . . . . . . . . . . . . . . . 209
Special SPDO Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 LIBNAME Proxy Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Privileged OPER Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213 TRUNCATE Command and Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .214 Refreshing SPD Server Parameter and LIBNAME Files . . . . . . . . . . . . . . . . . . . . . . .215 Commands to Nonexistent Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Chapter 17 • SPD Server Index Utility Ixutil . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219
The Index Utility Ixutil . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219
vi Contents
Ixutil Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .221
Chapter 18 • SPD Server Table List Utility Spdsls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
SPD Server Table List Utility Spdsls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Chapter 19 • SPD Server Backup and Restore Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Overview of the SAS Scalable Performance Data Server Backup
and Restore Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 Using Utilities with SPD Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 Compatibility with Previous Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 Privileged Access Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233 Spdsbkup - the Table Backup Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234 Backup Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 Backup Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 Backup Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 Backup Return Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 Backup Data File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238 Backup Table of Contents File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Backup User Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 Spdsrstr - the SPD Server Table Restore Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240 Using PROC SPDO to Back Up and Restore SPD Server Tables . . . . . . . . . . . . . . . . 246 Back Up and Restore Table Indexes using SPD Server Full Backups . . . . . . . . . . . . . 247 Back Up and Restore SPD Server Table Indexes using System Full Backups . . . . . . 248
Chapter 20 • SPD Server Directory Cleanup Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Using the Directory Cleanup Utility Spdsclean . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Spdsclean Wildcards and Pattern Matching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Spdsclean Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Spdsclean Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Chapter 21 • SPD Server Debugging Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259 SPD Server 4.5 LIBNAME Statement Debug Options . . . . . . . . . . . . . . . . . . . . . . . . 259 SPD Server 4.5 Server Parameter File Debug Options . . . . . . . . . . . . . . . . . . . . . . . . 260
1
Part 1
Product Notes
Chapter 1
SPD Server 4.5 Product Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2
3
Chapter 1
SPD Server 4.5 Product Notes
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
What's New in SPD Server 4.5? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Overview of SPD Server 4.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
SPD Server 4.5 Platform Support Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Overview
This document summarizes enhancements and changes in SPD Server 4.5.
•The SPD Server 4.5 installation includes client modules that are compatible with SAS 9.2.
•SPD Server 4.5 is not compatible with SAS versions earlier than SAS 9.2. Refer to the appropriate SPD Server UNIX or Windows installation guide for more information about SAS software requirements for use with SPD Server 4.5.
What's New in SPD Server 4.5?
Overview of SPD Server 4.5
The operating system requirements for SPD Server 4.5 have changed from the operating system requirements for SPD Server 4.4. For more detailed information about operating system requirements for SPD Server 4.5, see the SPD Server Pre-Installation and System Requirements Guide on page 7.
•SPD Audit logging has been enhanced to include the user LIBNAME in the proxy and SQL audit logs. For additional information, see the section on SPD Server auditing in “SPD Server Auditing” on page 189.
•You can now specify recycle times for the SPD Server Name Server log and the SPD Server Snet log. For additional information about configuring SPD Server log cycle times for Windows installations, see “Configuring SPD Server Software on Your Windows Host” on page 44. For additional information about configuring SPD Server log cycle times for UNIX installations, see “Configuring SPD Server Host Software for Your Site” on page 16.
4 Chapter 1 • SPD Server 4.5 Product Notes
•SPD Server now supports user formats with the put() function that are greater than 8 characters in length. An SPD Server host can read user format catalog files that were created by SAS running on Windows, or on the same machine as the SPD Server host. The spdsls list utility has been enhanced to add a -verbose option. The -verbose option provides information such as the number of observations, observation length, index segment size, partition size, and whether the table is compressed, encrypted, or is a member of a cluster. For more information about SPD Server list utilities, see “SPD Server Table List Utility Spdsls” on page 227.
•SAS implicit pass-through SQL now permits SQL queries to SPD Server that include supported SPD Server functions. The "SPD Server SQL Features" chapter of the SAS Scalable Performance Data Server 4.5: User's Guide contains a section, "Differences between SAS SQL and SPD Server SQL," that lists the functions that SPD Server supports via implicit pass-through SQL.
•The installation and delivery of the SPD Server 4.5 client components for SAS is now part of your SAS installation. For more detailed information about installing SPD Server 4.5 on a Windows platform, see “Before You Install: Precautions and Required Permissions” on page 38. For more detailed information about installing SPD Server
4.5on a UNIX platform, see “ Before You Install: Precautions and Required Permissions” on page 12.
•The installation and delivery of SAS Management Console components for SPD Server
4.5is now part of your SAS Management Console installation. For more detailed information about installing SAS Management Console components for SPD Server
4.5on a Windows platform, see “Before You Install: Precautions and Required Permissions” on page 38. For more detailed information about installing SAS Management Console components for SPD Server 4.5 on a UNIX platform, see “ Before You Install: Precautions and Required Permissions” on page 12
SPD Server 4.5 Platform Support Changes
SPD Server 4.5 now supports the Linux x64 platform.
5
Part 2
Installation
Chapter 2
SPD Server Pre-Installation and System Requirements Guide . . . . . . 7
Chapter 3
SPD Server UNIX Installation Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Chapter 4
SPD Server Windows Installation Guide . . . . . . . . . . . . . . . . . . . . . . . . . . 37
6
7
Chapter 2
SPD Server Pre-Installation and
System Requirements Guide
AIX Requirements and Tuning for 64-bit SPD Server . . . . . . . . . . . . . . . . . . . . . . . . 7
HP-UX Requirements and Tuning for 64-bit SPD Server . . . . . . . . . . . . . . . . . . . . . 7
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Kernel Tuning Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Required Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Solaris on Sparc Requirements and Tuning for 64-bit SPD Server . . . . . . . . . . . . . 9
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Solaris on X64 Requirements and Tuning for 64-bit SPD Server . . . . . . . . . . . . . . . 9
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Linux on X64 Requirements and Tuning for 64-bit SPD Server . . . . . . . . . . . . . . . . 9
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Windows Requirements and Tuning for 32-bit SPD Server . . . . . . . . . . . . . . . . . . 10
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
SPD Server 4.5 Client Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
AIX Requirements and Tuning for 64-bit SPD
Server
For complete information about AIX tuning for SAS SPD Server, see the white paper selection available on SAS Institute's external Web site at: www.sas.com/partners/ directory/ibm/papers.html
HP-UX Requirements and Tuning for 64-bit SPD Server
System Requirements
•Required OS level: HP-UX 11i 64-bit OS (HP-UX 11.11 for PA-RISC or HP-IA64 64bit OS (HP-UX 11i v2, HP-UX 11.23 for Itanium)
8 Chapter 2 • SPD Server Pre-Installation and System Requirements Guide
•Minimum System Configuration: HP-PA 2.0 server system with minimum 2Gb memory.
Kernel Tuning Requirements
The following kernel parameters are for HP-UX 11.11 and HP-UX 11.23. They need to be adjusted on the HP server system where you will run SPD Server.
After you make these kernel parameter changes, be sure to reboot the system before you attempt to use the SPD Server. In the following, MAX(a,b) means to take the maximum of the values a or b.
• dcb_max_pct = 10% dcb_min_pct = 2% max_thread_proc = 512
maxdsiz_64 = 1Gb + MAX(SORTSIZE, INDEX_SORTSIZE) maxuprc = 4 + #concurrent SPD Server users
nproc = current nproc value + 4 + #concurrent SPD Server users
•
Note: SORTSIZE and INDEX_SORTSIZE are SPD Server parameters from the spdsserv.parm file. Increasing these SPD Server parameters may require adjusting the HP-UX kernel parameters accordingly. For more information on SPD Server parameters consult the “SPD Server UNIX Installation Guide ” on page 11
•Other HP-UX kernel parameters that may need to be increased depending on the way you use the SPD Server include:
•ninode= Maximum open inodes in memory. Adjust for the maximum number of concurrently open SPD tables multiplied by the maximum number of partitions in an SPD Server table.
•nfile= System-wide open file limit. Adjust for the maximum number of concurrently open SPD Server tables multiplied by the maximum number of partitions in an SPD Server table.
•nflocks= System-wide file lock limit. Adjust for the maximum number of concurrently open SPD Server tables.
•maxfiles_lim = Process hard limit for open files. Adjust for the maximum number of concurrently open SPD Server tables multiplied by the maximum number of partitions in an SPD Server table. The minimum recommended setting is 8192
Required Patches
The following HP-UX 11.23 for Itanium (IA-64) patches should be applied for SPD Server 4.4:
•PHCO_30543 s700_800 11.23 Pthread library cumulative patch
•PHCO_30531 s700_800 11.23 libc cumulative patch
•The HP September 2004 Base Patch Bundle for HP-UX 11.23
System Requirements 9
Solaris on Sparc Requirements and Tuning for 64bit SPD Server
System Requirements
The following kernel parameter needs to be adjusted on Solaris server systems where you will run SPD Server.
•rlim_fd_max = Process limit for open files. Adjust the parameter to accommodate the maximum number of the number of concurrently open SPD tables multiplied by the maximum number of partitions in an SPD Server table. The minimum recommended setting is 8192
•Required OS level: Solaris Version 5.9
Solaris on X64 Requirements and Tuning for 64-bit SPD Server
System Requirements
The following kernel parameter needs to be adjusted on Solaris server systems where you will run SPD Server.
•rlim_fd_max = Process limit for open files. Adjust the parameter to accommodate the maximum number of the number of concurrently open SPD tables multiplied by the maximum number of partitions in an SPD Server table. The minimum recommended setting is 8192
•Required OS level: Solaris Version 5.10, Update 3
Linux on X64 Requirements and Tuning for 64-bit SPD Server
System Requirements
•Required OS level: Red Hat Enterprise Linux 4 and 5, SuSE Linux Enterprise
Server 9 and 10.
10 Chapter 2 • SPD Server Pre-Installation and System Requirements Guide
Windows Requirements and Tuning for 32-bit SPD Server
System Requirements
•Required OS level: Windows NT 4.0 Service pack 3 or greater
•Minimum System Configuration: NT server system.
SPD Server 4.5 Client Requirements
System Requirements
•Required SAS level: SPD Server 4.5 requires SAS 9.2.
11
Chapter 3
SPD Server UNIX Installation
Guide
SAS Scalable Performance Data Server 4.5 and SAS Deployment Wizard . . . . . . 12 Before You Install: Precautions and Required Permissions . . . . . . . . . . . . . . . . . . . 12
Packing List for SPD Server Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Directory Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Upgrading SPD Server 3.x to SPD Server 4.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Overview of Upgrading from SPD Server 3.x to SPD Server 4.5 . . . . . . . . . . . . . . 15
Upgrading SPD Server 4.x to SPD Server 4.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Overview of Upgrading from SPD Server 4.x to SPD Server 4.5 . . . . . . . . . . . . . . 16
Configuring SPD Server Host Software for Your Site . . . . . . . . . . . . . . . . . . . . . . . 16 Verify That SPD Server 4.5 Is Running . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Configuring SPD Server Client Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Testing Your SPD Server Installation Using SAS . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
SPD Server Command Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
SPD Server Name Server Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
SPD Server Host Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
SNET Server Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Password Utility Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Performance Server Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
SPD Server 4.5 and the SAS Management Console Utility . . . . . . . . . . . . . . . . . . . 30 SPD Server Lightweight Directory Access Protocol (LDAP) Authentication . . . . 30
Notes for SPD Server Administrators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 UNIX User IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 SPD Server User IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 LDAP Password Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Name Server Start-Up Failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 SPD Server Host Start-Up Failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 SAS LIBNAME Assignment Failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Using SETINIT to Extend SPD Server Software . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
12 Chapter 3 • SPD Server UNIX Installation Guide
SAS Scalable Performance Data Server 4.5 and
SAS Deployment Wizard
SAS Scalable Performance Data Server (SPD Server) 4.5 can be installed as part of your initial SAS 9.2 installation. Or, SPD Server 4.5 can be installed as an add-on product to an existing SAS 9.2 installation. In either case, the SPD Server 4.5 installation is facilitated by the SAS Deployment Wizard. The SAS Deployment Wizard installs SPD Server to the following location on your computer: <SASROOT>/ SASScalablePerformanceDataServer/4.5/.
Note: <SASROOT> is a placeholder for the full path specification to the base directory of your SAS 9.2 installation.
Before You Install: Precautions and Required
Permissions
Note: Before you install, see “SPD Server 4.5 Product Notes ” on page 3 for important information about features in this release.
Review the following precautions and required permissions:
•Read “SPD Server Pre-Installation and System Requirements Guide ” on page 7 .
•SPD Server 4.5 is distributed only as a 64-bit environment application for Solaris by Sun, AIX by IBM, Linux by SUSE or Red Hat, and HP-UX by Hewlett-Packard.
•SAS recommends that you use a UNIX user ID other than root to run your production SPD Server environment. Although there are no known security or integrity problems with SPD Server 4.5, root access is not required to run SPD Server. After you correctly configure UNIX directory ownership and you set permissions on your LIBNAME domains, there is no real need or benefit for root access to SPD Server. For more information and a list of options to use when configuring SPD Server, see“Notes for SPD Server Administrators” on page 32 .
•SAS recommends that you install SPD Server in a location that is adequately mirrored and backed up to assure reliability. The SPD Server installation location should use system space in which the SPD Server Administrator has full rights.
•General familiarity with the UNIX language is required to install SPD Server 4.5. At a minimum, installers should be familiar with basic UNIX shell entities (such as sh, csh, and ksh), Bourne shell scripts, the UNIX tar command, and how to modify files using a UNIX text editor.
•You need appropriate access permissions to create the installation directory for SPD Server on the file system where you install the server software. The owner of the SPD Server installation directory should be the UNIX user ID of the SPD Server administrator. For more information, see“Notes for SPD Server Administrators” on page 32 .
•You need Write access to your server machine's /etc/inet/services or /etc/ services file, if you want SPD Server clients to connect to the SPD Server host using name services instead of specifying port numbers at invocation. Name services require you to define registered ports that use the services file appropriate to your machine.
Directory Contents 13
•If your SPD Server clients access the SPD Server host using name services instead of specifying port numbers, you need Write access to the services files on the clients, in the path /etc/services or /etc/inet/services
For Windows, the path is C:\winnt\system32\drivers\etc\services
•Insert the WORKPATH= server option in your spdsserv.parm file. Use the WORKPATH= option to configure your server to use a high-performance file system. Ideally this system has RAID-structured volumes with sufficient disk space to accommodate the transient storage needs for Server. The spdsserv.parm file is located in the root directory of your SPD Server host installation. For more information about the WORKPATH= option and configuring servers for performance, see the SAS Scalable Performance Data (SPD) Server 4.5: User's Guide.
Packing List for SPD Server Distribution
Directory Contents
Directory names in the packing list are subdirectories of your SPD Server host installation directory, whose path is represented by InstallDir/.
Note: InstallDir/ represents the root directory where SPD Server is installed.
The bin/ subdirectory contains the following binary files:
•spdsnsrv is the SPD Server Name Server.
•spdsservis the SPD Server host.
•spdsbase is the LIBNAME proxy.
•spdslog is the message logger.
•spdsaud is the audit logger.
•spdseng is the SQL Pass-Through engine.
•ixutil is the data set index utility .
•psmgr is the password file utility.
•spdssnet is the ODBC, JDBC, and htmSQL gateway,
•spdsperf is the Performance server.
•spdsls gives physical file listings for a LIBNAME domain.
•spdsbkup performs full or incremental table backups.
•spdsrstr restores full or incremental table backups
•spqldrive is a stand-alone SQL Pass-Through driver.
•spdsconv is the SPD Server 3.x to SPD Server 4.x table conversion utility.
•spdsclean is the SPD Server disk cleanup utility.
•dulibv3 is the SPD Server 3.x 64-bit version of the shared library used by spdsconv. The dulibv3 file is included only if your system previously supported SPD Server 3.x tables.
•spdsbased is the debug version of spdsbase.
•spdsengd is the debug version of spdseng.
14 Chapter 3 • SPD Server UNIX Installation Guide
•spdsnlslib is the NLS library.
•spdsnlslibd is the debug version of spdsnlslib.
•spdsiotest is the stand alone SPD Server I/O scalability test.
The lib/ subdirectory contains the following SPD Server library files:
•spdslib is the run-time library that performs SQL Pass-Through from C and C++ applications to SPD Server.
•spds.dll is the application extension library that is accessed via the SAS ODBC Driver. The samples/ directory contains the following files of interest:
•auditraw.sasis used to read proxy audit files that do not include WHERE clause auditing.
•auditwh.sasis used to read proxy audit files that include WHERE clause auditing.
•audit.sql.sasis used to read an SQL audit file.
•libnames.parm is a sample SPD Server host LIBNAME configuration file. Use with the -libnamefile option for the spdsserv command.
•libsamp.parm is a more advanced example of a LIBNAME configuration file.
•pwdb is a script to start the Password Manager executable.
•spdsserv.parm is a sample SPD Server host parameter file. It sets the defaults for SPD Server options. Use this file with the -PARMFILE option for the spdsserv command.
•rc.spds is a Bourne shell script to start a standard SPD Server environment.
•rc.perf is a Bourne shell script to start a standard Performance Server.
•killspds is a shell script that kills all processes for a UNIX user beginning with the letters spds. Do not use the killspds script if you have any processes running in UNIX that do not belong to SPD Server, but whose executable names begin with the letters spds.
•killrc is a shell script that kills all processes related to a run of rc.spds. The killrc script is selective. It does not kill SPD Server processes that are not related to core processes started by rc.spds. Those core processes are initially started when rc.spds runs. The core processes are typically spdsnsrv, spdsserv, spdsbase, spdslog, and spdssnet, based on the rc.spds script the /samples directory.
•doc_examples.sas contains sample SAS code that is used in the SAS Scalable Performance Data (SPD) Server 4.5: User's Guide documentation. This guide provides SPD Server LIBNAME and data set usage and syntax options.
•verify.sas is a SAS installation verification job. You should run it after you install SPD Server.
•spdsinst.sas demonstrates the simple use of WHERE clauses and WHERE planner output.
•passthru.sas demonstrates SQL Pass-Through usage. It gives examples of simple, single-level Pass-Through and secondary libref and connection scenarios.
•tempwork.sas demonstrates temporary LIBNAME domain support. Files created in a temporary LIBNAME domain are automatically deleted when the SAS session ends.
•paraload.sas shows how to perform parallel loads from an existing table into an SPD Server table. This technique exploits a parallel load capability in the LIBNAME proxy.
•aclcolrw.sas shows the use of ACL row and column security features.
Overview of Upgrading from SPD Server 3.x to SPD Server 4.5 15
•symbsub.sas shows how symbolic substitution in SQL Pass-Through statements can provide row-level security in tables.
•fmtgrpby.sas shows how to use formatted parallel GROUP BY statements in SQL Pass-Through.
•scale.sas can be used to benchmark the scalability of your SPD Server.
•dynamic_cluster*.sas shows how to use dynamic clusters with a MIN and MAX variable list.
•minmax*.sasshows how to use a MIN and MAX variable list on an SPD Server table.
•paralleljoin*.sasshows the use of the SQL Parallel Join performance enhancement.
•starjoin*.sas shows the use of the SQL Star Join performance enhancement.
•index_scan*.sas shows the use of the SQL index scan performance enhancement.
•materialize_view*.sas shows the use of the SQL materialized view performance enhancement.
•process_perf_log is a Perl script that processes a Performance Server log and server log into data that can be read into a SAS data set for post-performance analysis. The parameters are detailed in the script.
•PerfDataSample.sas is used to read a processed Performance Server log into a SAS data set.
The doc/ directory contains information to locate the online SAS Scalable Performance Data (SPD) Server 4.5: Administrator's Guide and the SAS Scalable Performance Data (SPD) Server 4.5: User's Guide in PDF format.
The lic/ directory contains the SPD Server license file for your installation.
The spds.lic file is used by the SPD Server Name Server to validate SPD Server hosts for their target hardware configurations. Once you obtain a valid SPD Server SETINIT for a machine, you need to append it to this file.
The msg/ directory contains SPD Server message files. The collection of *.m files are used by various SPD Server components to generate message text.
The site/ directory is a storage directory for a user's site-specific customization of the sample SPD Server start-up and configuration files. No SPD Server files are delivered in this directory. It is for customer use only.
The spdssmc/ directory contains the SAS Management Console files that support SPD Server.
Upgrading SPD Server 3.x to SPD Server 4.5
Overview of Upgrading from SPD Server 3.x to SPD Server 4.5
SPD Server 3.x tables are not compatible with SPD Server 4.x tables, including SPD Server 4.5. If you want to use your SPD Server 3.x tables with SPD Server 4.5, you must first convert your SPD Server 3.x tables to SPD Server 4.x format. For more information about converting SPD Server 3.x table for use with SPD Server 4.5, see “Introduction” on page 59.
16 Chapter 3 • SPD Server UNIX Installation Guide
Upgrading SPD Server 4.x to SPD Server 4.5
Overview of Upgrading from SPD Server 4.x to SPD Server 4.5
SPD Server 4.x tables are compatible for use with SPD Server 4.5. No conversion is required to use SPD Server 4.x tables with SPD Server 4.5. You can start SPD Server 4.5 using domains that include tables created by any SPD Server 4.x host.
Configuring SPD Server Host Software for Your Site
After you install SPD Server 4.5, you must configure SPD Server to run on your server machine. The SPD Server 4.5 installation contains only 64-bit components.
Complete the following steps to install the SPD Server system:
1. For ksh users:
export PATH=$PATH:InstallDir/bin
For csh users:
set path = ($path InstallDir/bin)
2.Six files need to be copied from the InstallDir/samples directory to the
InstallDir/site directory:
rc.spds pwdb
spdsserv.parm killrc libnames.parm rc.perf
3.In the InstallDir/site directory, edit the pwdb script file.
Note: Depending on the shell that you are running, you have to make minor modifications to the script file.
The pwdb file configuration must be modified to point to the INSTDIR= path, the path where your copy of SPD Server is installed.
The INSTDIR= path in your pwdb file should be changed to
INSTDIR=<explicit UNIX path to your SPD Server Installation Directory>
4.Invoke the pwdb script from the /site subdirectory to create an initial SPD Server password file. The password file is created in InstallDir/ by executing the following command:
pwdb
First, use the Password Manager groupdef command to define a group called admingrp. Next, use the Password Manager add command to add an SPD Server user ID for yourself. (This is assuming that you are the SPD Server administrator). Both the
Configuring SPD Server Host Software for Your Site 17
groupdef and add commands prompt you for values to enter. Use the following transcript file from a typical command sequence for reference. You should notice that the password prompt does not echo any characters as you type. If you want to verify your work, you can use the Password Manager list command to print the contents of the SPD Server password file, following the add command.
You should see content similar to the following:
SAS Scalable Performance Data Server Host 4.50 Password Manager Utility
Copyright (c) 1996-2009 by SAS Institute Inc, Cary NC 27513 USA
Enter command
> groupdef admingrp Group admingrp defined
Enter command > add
Enter username to add > admin
Enter password for admin
>
Verify password
>
Enter authorization level (0 to 7) for admin: > 7
Enter IP Address or <Return
>
Enter password expiration time in days > 365
Enter group name or <Return> > admingrp
Enter the maximum allowed time (in days) between successful logins <Default = infinite>
>
Enter the maximum allowed login failures <Default = infinite>
>
Enter admin’s performance class(1=LOW 2=MED 3=HIGH carriage return for LOW)
>
User admin added Enter command
> quit
These commands initialize the user password database.
You should add other user IDs before opening the SPD Server system for use. Authorization level 7 is privileged. Authorization level 7 allows users to circumvent desirable SPD Server ACL security measures. Unlike the previous example, most or all users should be given authorization level 0 (which is non-privileged), so that SPD Server security cannot be bypassed. For more information, see “Notes for SPD Server Administrators” on page 32 .
Note: The administrator password expires during the first logon to the SPD Server host. For more information about passwords, see the psmgr utility reference documentation.
5.In the InstallDir/site directory, edit the libnames.parm file to add the sitespecific LIBNAME domains that your SPD Server will support. This step requires some
18 Chapter 3 • SPD Server UNIX Installation Guide
thought and planning. You should decide how to organize your existing disk storage to best exploit the capabilities of the SPD Server. For more information, see “SPD Server Host Commands” on page 27 and the libsamp.parm file. For more information about managing resources, see “Managing Computing Resources with a Name Server” on page 67 .
6.Edit and configure the resource script file rc.spds. In the /InstallDir/site directory, use a UNIX text editor to open the rc.spds file. The tasks to configure the rc.spds file include the following:
•Specify the SQL audit file cycle time and the file prefix using AUDTIME= and AUDFILESQL=.
•Confirm settings for the INSTDIR= pointers to your installation directory.
•Confirm settings for the INSTDIR= pointers to your /bin directory.
•Specify whether to start up the SNET Server.
•Check SNET port assignments if you use SNET.
•Reassign SNET ports if there are conflicts.
•Specify whether to create a log using LOGDIR=.
•Specify the log cycle time and the file prefix using LOGTIME= and LOGFILE=.
•Specify whether to create an audit file facility using AUDDIR=.
•Specify the audit file cycle time and the file prefix with AUDTIME= and AUDFILE=.
•Specify the location of your server user password database and parameter files.
Here is an example of a typical unmodified rc.spds file:
#!/bin/sh -x
#Sample startup script for SPDS.
#This script starts the SPDS Name Server
#data server and ODBC server processes
#using assumed install directories. Most
#paths are controlled through shell variables
#defined at the beginning of the script.
#If you change this script, copy it to
#the SPDS site directory and modify that
#copy just to make sure that a subsequent
#SPDS software upgrade doesn't wipe out
#your site modifications to the script.
#------------------------------------------
#
#Define some primary variables. INSTDIR is the
#root directory of your installation. INSTDIR is
#initialized to run rc.spds from the site dir
#of your installation.
#
#NSPORT is the SPDS name server listen port;
#if omitted uses "spdsname" service entry.
#SNSPORT is the SPDS ODBC server listen port;
#if omitted uses "spdssnet" service entry.
#If you are running through a firewall the NSPORT and
#SNSPORT must be surfaced through the firewall. In
Configuring SPD Server Host Software for Your Site 19
#addition, the SPDS server listen port and operator port
#must be surfaced through the firewall. If you are not
#running through a firewall allow the server to choose
#these ports.
#
#SRVLPORT is the SPDS server listen port;
#leave as 0 if NOT running through a firewall.
#SRVOPORT is the SPDS server operator port;
#leave as 0 if NOT running through a firewall.
#Refer to the SPDS Admin Doc section on Security for
#more information on running SPDS through a firewall.
NSPORT=5190
SNSPORT=5191
SRVLPORT=0
SRVOPORT=0 INSTDIR=$PWD/.. PARMDIR=$INSTDIR/site ACLDIR=$INSTDIR/site LICDIR=$INSTDIR/lic
The rc.spds file configurations you need to examine are the following:
•INSTDIR: Your SPD Server installation directory assumes that you are running the rc.spds script from your /site directory. The INSTDIR= variable provides the relative path to the installation directory from your /site directory.
•INSTDIR/bin: The PATH=, LD_LIBRARY_PATH, and LIBPATH= statements in the default rc.spds file refer to the INSTDIR/bin directory. The PATH=, LD_LIBRARY_PATH, and LIBPATH= statements are in the following section of the rc.spds file:
#
# Define some secondary variables for server
#parameter files
SPARM=$PARMDIR/spdsserv.parm LICFILE=$LICDIR/spds.lic PATH=$INSTDIR/bin
export PATH MSGPATH=$INSTDIR/msg/ export MSGPATH
LPARM=$INSTDIR/site/libnames.parm LD_LIBRARY_PATH=$INSTDIR/bin export LD_LIBRARY_PATH LIBPATH=$INSTDIR/bin
export LIBPATH
•SNET: The rc.spds script assumes that you want to start the SNET Server (spdssnet) to support OBDC, JDBC, or htmSQL access to SPD Server data stores. If this is not what you want, you can delete or comment out the following lines near the bottom of the rc.spds script.
#Startup the spdssnet server. This server supports
#ODBC access to SPDS data. Note the
#only parameter is the optional spdssnet listen
20 Chapter 3 • SPD Server UNIX Installation Guide
#port number. If not explicitly specified it
#will default to the "spdssnet" service in /etc/services
/bin/sleep 2
if [ -z "$SNSPORT" ]; then spdssnet 1>$SNSLOG 2>&1 &
else
spdssnet -listenport $SNSPORT 1>$SNSLOG 2>&1 &
•SNET Port Assignments: The rc.spds script assumes that you are running SPD Server concurrently with an SPD Server 3.x environment. It assumes that the SPD Server Name Server and the SNET Server will run using explicit port number assignments. The following lines at the beginning of rc.spds assign the ports numbers:
NSPORT=5190 (name server port for spdsnsrv)
SNSPORT=5191 (SNET Server port for spdssnet)
If these ports are in use, or if resources specify otherwise, choose new port numbers. If you omit these assignments, rc.spds uses the name services entries SPDSNAME and SPDSSNET. If you do not run the Snet Server, you do not need to be concerned about the SNSPORT definition.
•Logging: The rc.spds script assumes that you want to keep the logs from messages written to STDOUT or STDERR of the spdsnsrv ( SPD Server Name Server) and spdsserv (SPD Server host) processes. The shell variable LOGDIR= defines the directory where these logs are kept. If you do not want to keep these logs, change LOGDIR= and the rc.spds script will use /dev/null. If you want to keep the logs in another location besides InstallDir/log, change LOGDIR=.
The DSRVFILE= and DSRVTIME= spdsserv options, NSRVFILE= and NSRVTIME= spdsnsrv options, and SNSFILE= and SNSTIME= spdssnet options are enabled by default with the following shell variables:
DSRVFILE=spdsserv
Specifies the spdsserv process log file prefix.
DSRVTIME=00:00
Specifies the time of day to cycle the spdsserv log file.
NSRVFILE=spdsnsrv
Specifies the spdsnsrv process log file prefix.
NSRVTIME=00:00
Specifies the time of day to cycle the spdsnsrv log file.
SNSFILE=spdsnet
Specifies the spdssnet process log file prefix.
SNSTIME=00:00
Specifies the time of day to cycle the spdssnet log file.
These settings enable automatic log filename generation and cycling by specifying the log file prefix and the log file cycle time of day. The file path for the -LOGFILE option is generated by concatenating the LOGDIR= and LOGFILE= variables. For more information about these options, see “SPD Server Host Commands” on page 27. When automatic log filename generation and cycling are enabled, the only messages that go to the default log file are those written to STDERR. If you want to disable automatic log filename generation and cycling, change the settings to empty pointers such as the DSRVFILE= and DSRVTIME= options.
Configuring SPD Server Host Software for Your Site 21
The LOGFILE= and LOGTIME= spdsserv options are enabled by default with the following shell variables:
LOGFILE=spdsserv
Specifies the spdsserv process log file prefix.
LOGTIME=00:00
Specifies the time of day to cycle the log file.
These settings enable automatic log filename generation and cycling by specifying the log file prefix and the log file cycle time of day. The file path for the -logfile option is generated by concatenating the LOGDIR= and LOGFILE= variables. For more information about these options, see “SPD Server Host Commands” on page 27. When automatic log filename generation and cycling are enabled, the only messages that go to the InstallDir/log/spdsserv.log file are those written to STDERR. If you want to disable automatic log filename generation and cycling, , change the settings to empty pointers, such as the LOGFILE= and LOGTIME= options.
•The rc.spds script allows you to use the SPD Server audit file facility, but the audit file facility is not enabled by default. Use the following shell variables to configure the SPD Server audit file facility:
AUDDIR=
Use the AUDDIR= shell variable to specify the directory for the audit log files.
AUDFILE=
Use the AUDFILE= shell variable to specify the prefix for audit log files.
AUDFILESQL=
Use the AUDFILESQL= shell variable to specify the prefix for SQL audit log files.
AUDTIME=
Use the AUDTIME= shell variable to specify the time of day (HH:MM) to cycle the audit log file.
When AUDDIR= and AUDFILE= are set, you enable proxy audit file creation. When AUDDIR= and AUDFILESQL= are set, you enable SQL audit file creation. If AUDTIME= is set, automatic audit file cycling occurs at the specified time of day. For more information about the audit file facility, see “SPD Server Host Commands” on page 27.
•User Password and Parameter Files: The rc.spds script assumes that you keep your spdsserv.parm parameter file and your SPD Server user password file in the InstallDir/site directory. If you do not, you need to change the ACLDIR= and PARMDIR= assignments. You can include this script into your system start-up file so that it executeds as part of starting the system. Otherwise, the SPD Server administrator must manually start SPD Server after the system starts up.
•After you have finished making your changes, save and close the rc.spds file.
Note: The example rc.spds script provided in the next step is a generic UNIX script. Some additional path changes might be required for other operating environments. For example, Linux operating systems do not keep the ps and grep commands in / usr/bin, so changes are required.
1.Assuming that you want to use registered ports for your SPD Server host, and you choose to use the default SPD Server Name Server port of 5190 and the SNET Server port of 5191, add the following services to your /etc/services or /etc/inet/ services file on the SPD Server host machine.
spdsname 5190/tcp # SPDS Name Server
22 Chapter 3 • SPD Server UNIX Installation Guide
Service declaration for the SPD Server Name Server
spdssnet 5191/tcp # SPDs SNET
Server Service declaration for the SNET Server.
You only need the SNET service if you plan to run the SNET Server. By default, the sample rc.spds script runs spdssnet.
If you choose to use different port addressses, replace the ???? strings with unused 4- digit port addresses. Also remember to update your rc.spds script accordingly. Determine unused port addresses by scanning the existing addresses and then choosing a number that does not appear. Choosing a number greater than 5000 avoids conflicts with reserved and system-defined port addresses.
spdsname ????/tcp # SPDS Name Server
Service declaration for the SPD Server Name Server
spdssnet ????/tcp # SPDS SNET Server
Service declaration for the SNET Server.
Note: If you installed a previous version of SPD Server software and you have the service name spdsoper defined, you should remove it from your /etc/ services or /etc/inet/services file on the SPD Server system.
2.You are now ready to start SPD Server. Execute the InstallDir/site/rc.spds script that you customized in the previous steps. This starts the SPD Server environment in the context of your current UNIX user ID.
The rc.spds script customization is important because it defines UNIX ownership and file access permissions on SPD Server resources. Ownership and file permissions are set in the context of the SPD Server run-time environment. If you plan to execute rc.spds from your system startup, the rc.spds script should be executed in the context of the appropriate UNIX user ID. Using the appropriate UNIX user ID ensures that the resources created in the startup configuration meet the necessary file ownership and permission requirements for SPD Server.
3.The rc.perf script is an example script to start the Performance Server.
Verify That SPD Server 4.5 Is Running
If you connected to SPD Server through a SAS connection, verify that both the SPD Server Name Server (spdsnsrv) and the SPD Server host (sdpsserv) processes are running. Issue the UNIX ps command. You should see processes for spdsnsrv, spdsserv, spdsbase (row level integrity proxy), and spdssnet as shown in the following example:
PID |
TTY |
TIME |
CMD |
24012 |
pts/26 |
00:00:00 |
ksh |
24114 |
pts/26 |
00:00:00 |
spdsnsrv |
24116 |
pts/26 |
00:00:00 |
spdslog |
24117 |
pts/26 |
00:00:00 |
spdsserv |
24119 |
pts/26 |
00:00:00 |
spdslog |
24120 |
pts/26 |
00:00:00 |
spdssnet |
24130 |
pts/26 |
00:00:00 |
spdslog |
24136 |
pts/26 |
00:00:00 |
spdsbase |
24139 |
pts/26 |
00:00:00 |
ps |
Configuring SPD Server Client Software 23
If the spds* processes are not running, check the log for errors. Unless you change the log file defaults in rc.spds, the log paths are the following:
•InstallDir/log/spdsnsrv.log
•InstallDir/log/spdsnsrv_mmddyyyy_hh:mm:ss.spdslog
•InstallDir/log/spdsserv.log
•InstallDir/log/spdsserv_mmddyyyy_hh:mm:ss.spdslog
•InstallDir/log/spdssnet.log
•InstallDir/log/spdssnet_mmddyyyy_hh:mm:ss.spdslog
If there were problems during start-up and any processes failed to initialize, terminate the remaining SPD Server processes before re-invoking the rc.spds script. Use the killspds shell script in the \samples directory, or terminate the process manually using the UNIX kill command as shown in the following example:
$ kill 834 831 832 836 835
Upgrade Notice: If you upgrade from SPD Server 3.x to SPD Server 4.5, when you are satisfied with your SPD Server installation, you should copy the libnames.parm file from your SPD Server 3.x location to your SPD Server 4.5 location. The new libnames.parm file overwrites the temporary file that was created when you verified your SPD Server 4.5 installation. The new file provides you with access to all of the SPD Server 3.x LIBNAME domains from your previous environment.
Configuring SPD Server Client Software
The SPD Server client software is used to make SAS LIBNAME connections and perform user-specified operations on the SPD Server host. The SPD Server client software is installed with SAS 9.2, and contains the following SAS modules:
•sasspds is the LIBNAME engine that is required to access the SPD Server environment from SAS 9.2.
•sasspdo is the SPD Server operator procedure that is required to access the SPD Server 4.5 environment from SAS 9.2.
•spds.msg is the SAS compatible message file for the SPD Server LIBNAME engine and SPD Server operator procedure.
The SPD Server client software is installed with SAS 9.2 Foundation at <SASROOT>/ SASFoundation/9.2/spdclient. The SAS 9.2 configuration file automatically includes your SPD Server client software directory in its required path list.
Once the SPD Server environment is configured and running, you need to complete other installation functions on the SAS clients that will use SPD Server. This might include the system that is actually running SPD Server. Therefore, some of these steps might have already been performed during the installation of the SPD Server host. If so, skip the duplicated steps.
Perform the following steps on each SAS client that will access SPD Server:
1.If you want to access SPD Server through a registered port (name service), add the following service to your /etc/inet/services or /etc/services file if not already there:
spdsname ????/tcp # SPDS Name Service
24 Chapter 3 • SPD Server UNIX Installation Guide
The service defines the port number for the SPD Server Name Server process. Make sure the added port number matches the port number used during the SPD Server installation. If you are running SAS with an existing SPD Server installation, this service name is probably already defined. You can either define another service name for the SAS client to use (for example, sp45name) or you can directly include the SPD Server port number in your SAS statements.
2.The SPD Server can be accessed with the SAS 9.2 ODBC Driver, JDBC Driver, and htmSQL driver. Each of these drivers can be downloaded from the Support tab at support.sas.com
ODBC client applications require installation of the spds.dll application extension. Install the ODBC client application extension as follows
•Install the SAS 9.2 ODBC Driver
•Copy
InstallDir/lib/spds.dll
to
<drive letter>:\Program Files\sas\shared files\general
•Configure an ODBC data source for direct SPD Server access.
Testing Your SPD Server Installation Using SAS
Testing your SPD Server installation is simple. To verify, you make two SAS LIBNAME assignments using the SPD Server LIBNAME engine. The examples in this section refer to the SASSPDS engine, which is the engine for SAS 9.2.
1.Start the SPD Server environment by executing your customized rc.spds script. Execute this script from the UNIX user ID that owns the LIBNAME directories that are configured in the SPD Server LIBNAME file. For more information about the rc.spds script and SPD Server LIBNAME files, see“Notes for SPD Server Administrators” on page 32.
2.On a correctly configured client system, invoke SAS, and make the following LIBNAME assignments:
LIBNAME test sasspds 'tmp' server=serverNode.port user='anonymous';
serverNode is the server's node name and port is either the numeric value assigned to NSPORT from the rc.spds file, or the service name you use to access the SPD Server Name Server. If you used the sample rc.spds, your LIBNAME assignment would look similar to the following:
LIBNAME test sasspds 'tmp' server=serverNode.5190 user='anonymous';
If you use the spdsname service, your LIBNAME assignment would look similar to the following:
Loading...