Testing Your SPD Server Installation Using SAS

Testing your SPD Server installation is simple. To verify, you make only 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 as described in Step 3 of Validating Default Port and Library Assignments.
  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 used to start the Name Server or the service name you use to access the SPD Server Name Server. Name services allow you to connect to a Name Server using a character string, instead of specifying a port number. If you used the default numeric port assignment of 5400, your assignment would look similar to the following:
    LIBNAME test sasspds 'tmp' 
     server=serverNode.5400 
     user='anonymous';
    If you used 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 Name Server and Data Server. The test assumes that 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 locate one or more of the required SPD Server components. Examples of common error messages are displayed.
    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 correctly set.
    ERROR: unable to access message 608.108 
  3. Once every LIBNAME is assigned, you can further verify by running the sample SAS program, InstallDir\samples\verify.sas. Submit the following 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 results, the SAS job is terminated. The job verify.sas requires that the SAS librefs TEST and TESTRL are assigned as shown in Step 2 above.
  4. 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.