port number that was used during the SPD Server host installation. If you are already
running SAS with an earlier version of SPD Server, 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 host can be accessed via the SAS ODBC driver, the SAS JDBC driver,
and SAS htmSQL. Each of these drivers can be downloaded from the support link of
the SAS Web at
.
For more information about connecting and configuring these applications, see Chapter
6 in the SAS Scalable Performance Data (SPD) Server 4.5: User's Guide, "Using SPD
Server with Other Clients.".
ODBC client applications require installation of the
spds.dll
application extension.
Install the ODBC client application extension as follows:
•
Install the SAS/ODBC Driver Version 9
•
Copy
InstallDir\lib\spds.dll
into
<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 relatively simple. To verify, you only need to make
two SAS LIBNAME assignments using the SPD Server LIBNAME engine. The examples
in this section refer to the SASSPDS engine, the engine for SAS 9.2.
1. Start the SPD Server environment as described in step 3 of the section
Default Port and Library Assignments” on page 41
.
2. On the SPD Server client machine, invoke SAS and make the following LIBNAME
assignments:
libname test sasspds 'tmp' server=serverNode.port user='anonymous';
ServerNode
is the Name Server's network node name and
port
is either the numeric
value used to start the Name Server or the named service you chose to use to access
the SPD Server Name Server. Remember that name services allow you to connect to a
Name Server using a character string instead of specifying a port number. Assuming
you used the default numeric port assignment of 5400, your assignment would look
like:
libname test sasspds 'tmp' server=serverNode.5400 user='anonymous';
Or if you were using
spdsname
to provide named services, your assignment would
resemble this:
libname test sasspds 'tmp' server=serverNode.spdsname user='anonymous';
In addition, you should verify that the Row Level Integrity LIBNAME assignment
works correctly:
libname testrl sasspds 'tmp' server=serverNode.port user='anonymous' locking=YES;
Testing Your SPD Server Installation Using SAS
47
Summary of Contents for Scalable Performance Data Server 4.5
Page 1: ...SAS Scalable Performance Data Server 4 5 Administrator s Guide...
Page 7: ...Part 1 Product Notes Chapter 1 SPD Server 4 5 Product Notes 3 1...
Page 8: ...2...
Page 12: ...6...
Page 63: ...Part 3 Migration Chapter 5 SPD Server 3 x to SPD Server 4 5 Conversion Utility 59 57...
Page 64: ...58...
Page 70: ...64 Chapter 5 SPD Server 3 x to SPD Server 4 5 Conversion Utility...
Page 72: ...66...
Page 76: ...70 Chapter 6 Using the SPD Server Name Server to Manage Resources...
Page 94: ...88 Chapter 7 Administering and Configuring SPD Server Using the SAS Management Console...
Page 98: ...92 Chapter 8 SPD Server SQL Query Rewrite Facility...
Page 116: ...110 Chapter 10 Configuring Disk Storage for SPD Server...
Page 128: ...122 Chapter 11 Setting Up SPD Server Parameter Files...
Page 154: ...148...
Page 198: ...192 Chapter 14 ACL Security Overview...
Page 212: ...206 Chapter 15 Managing SPD Server Passwords Users and Table ACLs...
Page 214: ...208...
Page 224: ...218 Chapter 16 SPD Server Operator Interface Procedure PROC SPDO...
Page 236: ...230 Chapter 18 SPD Server Table List Utility Spdsls...
Page 256: ...250 Chapter 19 SPD Server Backup and Restore Utilities...
Page 264: ...258 Chapter 20 SPD Server Directory Cleanup Utility...
Page 270: ......