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.

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, seeNotes for SPD Server Administrators.
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:
```
     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;
```
When you verify these statements, you confirm the connectivity between the SAS client and the SPD Server environment. Successfully performing these LIBNAME assignments means that the network configuration is correct and that most of the SPD Server configuration is correct.

Substitute serverNode with the node name that runs the SPD Server environment that you want to test. This is the node that invokes rc.spds. The test assumes the temporary LIBNAME definition in the sample libnames.parm file was not changed during installation.
Watch the SAS log for error messages. You might see failures to properly one or more required SPD Server components. Examples of common error messages are displayed. If you receive one of the following error messages, check your -PATH option to confirm that the directory in which you installed SAS components is correctly set:
```
ERROR:    Protocol version mismatch. Proxy version
          is 4.5 while engine version is 3.x.

ERROR:    Module TEST not found  in search paths.

ERROR:    Error in the LIBNAME or FILENAME
          statement.
```
If you receive the following (or similar) error message describing failures to access messages, check your -SASMSG option and confirm that the directory in which you installed SPD Server components is properly set:
```
ERROR: unable to access message 608.108
```
If the attempted connection to the SPD Server hangs for several minutes, check the -PATH option and confirm that the directory in which you installed SAS components is correctly set. The spds45 client component directory needs to be at the beginning of the path option.
Once every LIBNAME is assigned, you can further verify by running the sample SAS program, InstallDir/samples/verify.sas. Submit the SAS command to execute the program:
```
%include 'InstallDir/samples/verify.sas'/source2;  
```
This test exercises many features of the SPD Server LIBNAME engine and proxy, and verifies your installation configuration. The test performs a sequence of DATA and PROC steps using a generated data set. It checks the results expected from various DATA step queries. If any query fails to produce the expected result, the SAS job is terminated. The job verify.sas requires that the SAS librefs TEST and TESTRL are assigned as shown in Step 2.
Verify that SQL Pass-Through services are working in SPD Server by submitting the following SAS commands:
```
%let spdshost=serverNode;
%let spdsport=port;
%include 'InstallDir/samples/verptsql.sas'/source2;
```
serverNode and port are described in Step 2.