Diagnosing SAS Enterprise Guide 4.1 Connectivity Problems Using the SAS Integration Technologies Configuration Utility TS-790

Transcription

1 Diagnosing SAS Enterprise Guide 4.1 Connectivity Problems Using the SAS Integration Technologies Configuration Utility TS-790 Diagnosing SAS Enterprise Guide Connectivity Problems Using the SAS Integration Technologies Utility

2

3 Table of Contents Introduction...1 Testing for Connectivity between SAS Enterprise Guide and SAS Servers...1 SAS.EXE Is Local...3 SAS.EXE Is Remote...4 Common ITCONFIG Messages and...6 References...30 i

4

5 Introduction For SAS Enterprise Guide 4.1 to operate correctly, the application must be able to invoke a SAS session. To do that, you must have connectivity between SAS Enterprise Guide 4.1 and your SAS servers. This note explains how you can use the release of the SAS Integration Technologies configuration (ITCONFIG) utility to test that connectivity and to invoke SAS. It also describes some common error messages you might see as well as troubleshooting checklists for each of those errors. This paper was written (and the error messages compiled) for the system administrator or the advanced user. Readers of the document should have an understanding of where the SAS program has been installed and that SAS.EXE is the primary SAS software executable file. Testing for Connectivity between SAS Enterprise Guide and SAS Servers To test the connectivity between SAS Enterprise Guide and your SAS servers, follow these steps: 1. Start the SAS Integration Technologies Configuration utility on the SAS Enterprise Guide client workstation by selecting Start Programs SAS SAS 9.1 Utilities Integration Technologies Configuration. You can also start ITCONFIG by selecting Start Run and submitting the following path: C:\Program Files\SAS\Shared Files\Integration Technologies\itconfig.exe 2. Starting the utility displays the SAS Integration Technologies Configuration dialog box. Display 1. Starting the SAS Integration Technologies utility 1

6 3. Select Test Connection. 4. Click Next>>. 5. In the Choose How to Test dialog box, select Enter a SAS server definition manually. Display 2. Choosing to test by entering a SAS server definition manually 6. Click Next>>. 7. In the Run Tests dialog box, you will see three radio buttons for the connection protocol, as shown here: Display 3. Selecting a connection protocol Situations for the Remote Connection DCOM protocol rarely occur, so that particular protocol is not discussed. Instead, you should select one of the following protocol options: Local Connection (COM): This protocol is used when SAS.EXE is local. Bridge: This protocol is used when SAS.EXE is remote. The steps for selecting these protocols are explained in the following sections. 2

7 SAS.EXE Is Local Use the following steps to select the appropriate protocol to use when SAS.EXE is local: 1. Select SAS Workspace Server as the server type and Local Connection (COM) as the connection protocol to test. Note: SAS Workspace Server is the only server type you should choose for a local connection. Display 4. Selecting a server when SAS.EXE is local 2. Click Next>>. The Connection Successful dialog box should display with the following congratulations message: Display 5. Successful connection message If you see anything other than the congratulations message, you have an error condition. For information on the error condition and possible solutions, see Common ITCONFIG Messages and. 3. If you do not have any errors, click OK to close the Connection Successful dialog box. 4. Click Exit to close the SAS Integration Technologies Configuration dialog box. 3

8 SAS.EXE Is Remote Use the following steps to select the appropriate protocol to use when SAS.EXE is remote: 1. Select either SAS Workspace Server or SAS Metadata Server as the server type, and select Bridge as the connection protocol to test. Display 6. Selecting a server when SAS.EXE is remote 2. Click Next>>, which displays the Bridge Parameters dialog box. Display 7. Setting bridge parameters 4

9 3. In the Bridge Parameters dialog box: a. In the Machine Name field, enter either the fully qualified machine name (in the form machine.company.com) or the IP address where the server resides. b. Select the Port radio button and enter the port number (based on the server type) in the Port field. Default ports are as follows: SAS Metadata Server: 8561 SAS Workspace Server: 8591 SAS Workspace Server with an object spawner file: 5308 (see also TS-721: Quick Start: Object Spawner and Workspace Server with a Basic SAS 9 Foundation Install) c. Enter your user ID in the Username field. d. Enter your password in the Password field. e. Click Test. At this point, the Connection Results dialog box should display with a congratulations message. Display 8. Successful connection message If you see anything other than the congratulations message, you have an error condition. For more information on the error condition and possible solutions, see Common ITCONFIG Messages and Troubleshooting Suggestions. f. If you do not have any errors, click OK to close the Connection Successful dialog box. g. Click Cancel to close the Bridge Parameters dialog box. h. Click Exit to close the SAS Integration Technologies Configuration dialog box. 5

10 Common ITCONFIG Messages and This section describes some of the most common errors you might encounter. Troubleshooting suggestions are also provided for each error. Notes: The are lists of things that you can try in order to resolve the error. When possible, the troubleshooting suggestions are placed in the order that you should try them. If these suggestions do not solve the error, contact SAS Technical Support for further help. Links to references that are discussed in this document are available in the References section. List Click on your specific error message in the following list to link to the full error message and the troubleshooting suggestions for that error. A username is required Access denied. authenticating user <username> in function LogonUser... Class not registered Connection reset by peer. An existing connection was forcibly closed by the remote host... Could not establish a connection to the SAS Server on the requested machine... Element not found ERROR: The requested function was not performed due to an invalid or expired product license. ERROR: Unable to launch SAS ObjectServer (CreateProcessAsUser failure) ERROR: Unable to launch SAS ObjectServer (exec failure No such file or directory) Failed to start the server Invalid class string. Failed to create the Object Manager... Invalid pointer <ITCONFIG does not produce any output> Machine name could not be resolved to an IP address. 6

11 Server execution failed <status>0x Server execution failed <status>0x The client has connected to a SAS <server type> (v1.0) when it intended to connect to a SAS <server type> Server. The file SAS.TLB could not be found on this machine The hostname is not recognized or invalid The process cannot be launched by client <username> The RPC server is unavailable The system cannot find the path specified User does not have authority A username is required. Enter a user ID and password with the Log on to a batch job permission. The following steps illustrate how to set this permission for a user or group name on Windows XP Service Pack 2: 1. Select Start Settings Control Panel Administrative Tools Local Security Policy to display the Local Security Settings window. 2. Select User Rights Assignments in the left pane of the Local Security Settings window. 7

12 Display 9. Setting user or group permissions via the Local Security Settings window 3. Then double-click Log on to a batch job in the right pane to display the Log on as a batch job Properties dialog box. 8 Display 10. Adding users or groups

13 4. Click Add User or Group to display the Select Users or Groups dialog box. Display 11. Selecting specific users or groups 5. Click Object Types to display the Object Types dialog box. Display 12. Selecting the object type that you want to find 6. In this dialog box, select the appropriate object type that you want to add (either Users or Groups). Then click OK to return to the Select Users or Groups dialog box. 9

14 7. Enter the user or group name in the Enter the object names to select text box. Display 13. Entering the user or group name that you want to find 8. Click OK to close the Select Users or Groups dialog box. 9. Click OK to close the Log on as a batch job Properties dialog box. 10. Select File Exit to close the Local Security Settings window. 11. Select File Close to close the Administrative Tools window. Access denied. authenticating user <username> in function LogonUser (Logon failure: unknown user name or bad password.) (Logon failure: the user has not been granted the requested logon type at this computer) (A required privilege is not held by the client.) Current user probably does not have the right to act as part of the operating system. Verify that your user ID has been assigned Log on to a batch job permission. Follow the steps outlined in the suggestions for the error A username is required. Verify that the user ID and password combination is valid. Make sure that the password has not expired. 10

15 Make sure that you can invoke SAS with the user ID by submitting the RUNAS command, as follows: 1. Locate the SAS.EXE file on your C drive. 2. Open a command-prompt window and enter the following command. (Note: The following examples use the default SAS location for SAS.EXE.) For SAS 9 runas/user:mydomain\myhostname\username C:\Program Files\SAS\SAS \9.1\sas.exe For SAS 8 runas/user:mydomain\myhostname\username C:\Program Files\SAS Institute \SAS\v8\sas.exe 3. Enter the user password when you are prompted. Try adding the domain name or the host name to the user ID (for example, domain-name\user_id). Class not registered. Re-register a local copy of SAS.EXE by selecting Start Run and entering one of the following commands. Note: These examples use the default SAS location for SAS.EXE. For SAS 9 C:\Program Files\SAS\SAS 9.1\sas.exe /regserver For SAS 8 C:\Program Files\SAS Institute\SAS\v8\sas.exe /regserver Connection reset by peer. An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped, the host is rebooted, or the remote host used a hard close. Make sure that you can invoke SAS by selecting Start Programs SAS SAS 9.1 or by double-clicking the SAS.EXE file in C:\Program Files\SAS\SAS 9.1 Note: This is the default SAS location for SAS.EXE. 11

16 If you cannot invoke SAS, check for the following items: an expired license invalid paths for the WORK or the SASUSER libraries permissions issues data execution prevention (DEP) issues Check the SAS invocation command in the objspawn.cfg file, per TS-721, Quick Start: Object Spawner and Workspace Server with a Basic SAS 9 Foundation Install. If you still cannot find the problem, you can invoke SAS with the RUNAS command: For SAS 9 runas/user:mydomain\myhostname\username C:\Program Files\SAS\SAS \9.1\sas.exe For SAS 8 runas/user:mydomain\myhostname\username C:\Program Files\SAS Institute \SAS\v8\sas.exe Could not establish a connection to the SAS Server on the requested machine. Verify that the SAS server has been started with the objectserver option or that the SAS spawner has been started. Verify that the port Combridge is attempting to connect to is the same as the port SAS (or the spawner) is listening on If you are using a SAS Metadata Server: Make sure that the SAS Metadata Server service is running (with a status of Started) in the Windows environment s Services window: 12

17 Display 14. Verifying that the SAS Metadata Service is running Make sure that the SAS object spawner service is running (with a status of Started) in the Windows environment s Services window, as shown in the following example. The default service name is SAS Lev1 OB. Display 15. Verifying that the object spawner service is running Try to enable your object spawner log file for debugging purposes. For instructions on how to enable the object spawner log for SAS 9.1.3, Service Pack 4, see SAS Note (support.sas.com/kb/15/992.html). Make sure that the servers have been defined for the metadata s object spawner, per the SASMain Spawner Properties dialog box: 13

18 Display 16. Servers that are defined in SAS Metadata Server s object spawner If you do not see the servers listed, follow these steps: 1. In the Available servers box, highlight the server that you want to add. 2. Click the single arrow to move that server to the Selected servers box. 3. Click OK to save your selections. 4. Restart the SAS object spawner by selecting Start Programs SAS plan-filename Restart SAS Object Spawner. 14

19 If you use a SAS Metadata Server and you are connecting to the SAS Metadata Server in ITCONFIG (see step 2 in the section SAS.EXE Is Remote ), make sure that the port setting for the SAS Metadata Server matches the port number that you entered in the ITCONFIG Bridge Parameters dialog box. The suggested default port is 8561, but your port designation might be different. Verify the port setting for the SAS Metadata Server in SAS Management Console, as shown here: Display 17. Checking the port settings for the SAS Metadata Server 15

20 If you use a SAS Metadata Server and you are connecting to the SAS Workspace Server in ITCONFIG (see step 2 in the section SAS.EXE Is Remote ), make sure that the port setting for the SAS Workspace Server matches the port number that you entered in the ITCONFIG Bridge Parameters dialog box. The suggested default port is 8591, but your port designation might be different. Verify the port setting for the SAS Workspace Server in SAS Management Console, as shown here: Display 18. Checking the port settings for the SAS Workspace Server 16

21 If you DO NOT use a SAS Metadata Server and you are connecting to the SAS object spawner per the instructions in TS-721: Make sure that the object spawner service is running (with a status of Started) in the Windows environment s Services window, as shown in the following example. The default service name is SAS Object Spawner Daemon II. Display 19. Verifying that the object spawner service is running Make sure that the objspawn.cfg file s sasport setting matches the port number that you entered in the ITCONFIG Bridge Parameters box (see step 2 in the section SAS.EXE Is Remote ). The suggested default port is 8561, but your port designation might be different. Make sure that the objspawn.cfg file follows the syntax found in the instructions in TS-721. Common syntax issues that you might encounter: The objspawn.cfg file must have one (and only one) blank line between the Object Spawner section and the Object Server section. You might have an invalid path to SAS.EXE or to the sasv9.cfg file in the sascommand line. Paths that have embedded blanks must be surrounded by parentheses. Command lines (such as config) that break to another line must begin in column 2. The objspawn.cfg file must be a flat text file that does not contain any control characters. Check the Microsoft Event Viewer for error messages. Make sure that your firewall does not have a rule in place that blocks the SAS Enterprise Guide executable (SEGUIDE.EXE) from running. 17

22 Element not found Re-install the SAS Integration Technologies component. To re-install the component, run the following executable file from the SAS Enterprise Guide installation CD: CD_drive_name:\eguide\bundles\inttechc\setup.exe ERROR: The requested function was not performed due to an invalid or expired product license. Make sure that you are licensed for SAS software and the SAS Integration Technologies utility. To check the status of your SAS license, invoke SAS and run the following code: proc setinit noalias; run; ERROR: Unable to launch SAS ObjectServer (CreateProcessAsUser) failure) Verify that the object spawner is running under Services in the Windows environment s Services window, as shown here: 18

23 Display 20. Verifying that the object spawner service is running If you are connecting to the SAS object spawner per the instructions in TS-721, Quick Start: Object Spawner and Workspace Server with a Basic SAS 9 Foundation Install, verify the following items: Make sure that the sascommand line in the objspawn.cfg file is a valid command for invoking SAS. Make sure that the sasport setting in the objspawn.cfg file matches the port number that you entered in the ITCONFIG test. If you connecting to the SAS Metadata Server, use SAS Management Console to make sure that the port settings are the same as what you entered in the ITCONFIG test. ERROR: Unable to launch SAS ObjectServer (exec failure No such file or directory) Verify that the object spawner is running under Services in the Windows environment s Services window, as shown here: 19

24 Display 21. Verifying that the object spawner service is running If you are connecting to the SAS object spawner per the instructions in TS-721, Quick Start: Object Spawner and Workspace Server with a Basic SAS 9 Foundation Install, verify the following items: Make sure that the sascommand line in the objspawn.cfg file is a valid command for invoking SAS. Make sure that the sasport setting in the objspawn.cfg file matches the port number that you entered in the ITCONFIG test. If you connecting to the SAS Metadata Server, use SAS Management Console to make sure that the port settings are the same as what you entered in the ITCONFIG test. Failed to start the server Verify that your user ID has been assigned Log on to a batch job permission. Follow the steps outlined in the troubleshooting suggestions for A username is required. Verify that the user ID and password combination is valid. Make sure that the password has not expired. Make sure that you can invoke SAS with the user ID by submitting the RUNAS command, as follows: 1. Locate the SAS.EXE file on your C drive. 2. Open a command-prompt window and enter one of the following commands. (Note: The following examples use the default SAS location for SAS.EXE.) 20

25 For SAS 9 runas/user:mydomain\myhostname\username C:\Program Files\SAS\SAS \9.1\sas.exe For SAS 8 runas/user:mydomain\myhostname\username C:\Program Files\SAS Institute \SAS\v8\sas.exe 3. Enter the user password when you are prompted. Try adding the domain name or the host name to the user ID (for example, domain-name\user_id). Invalid class string. Failed to create the Object Manager. This could be caused by not having the Object Manager (sasoman.dll) installed. Try installing inttech.exe (available on the SAS web site at Re-install the SAS Integration Technologies component. To re-install the component, run the following executable file from the SAS Enterprise Guide installation CD: CD_drive_name:\eguide\bundles\inttechc\setup.exe Invalid pointer Make sure that you can invoke SAS with the user ID by submitting the RUNAS command, as follows: 1. Locate the SAS.EXE file on your C drive. 2. Open a command-prompt window and enter one of the following command. (Note: The following examples use the default SAS location for SAS.EXE.) For SAS 9 runas/user:mydomain\myhostname\username C:\Program Files\SAS\SAS \9.1\sas.exe For SAS 8 runas/user:mydomain\myhostname\username C:\Program Files\SAS Institute \SAS\v8\sas.exe 3. Enter the user password when you are prompted. 21

26 <ITCONFIG does not produce any output> Make sure that your DCOM configuration settings are correct, per the information in SAS Usage Note (support.sas.com/kb/10/805.html). Machine name could not be resolved to an IP address This error indicates that the software is not recognizing the value you are using for your server name. Test connectivity with the server host by pinging the SAS server s host name from the SAS Enterprise Guide client PC. Make sure that your firewall does not have a rule in place that blocks the SAS Enterprise Guide 4.1 executable file (SEGUIDE.EXE) from running. Be sure that you have used fully qualified host names in SAS Management Console and in SAS Enterprise Guide. Make sure that your IP address is resolving. This error message will provide the node name and the Domain Name Service (DSN) suffix of your computer. These two values combined should resolve to the IP address unless there are problems with the operating system. If they do not resolve, you can determine the IP address by issuing the command ipconfig /all at a DOS command prompt. (Note: You can use as the IP address for localhost.) Try the host name instead of the IP address. Use the command nslookup host-name to find details about the host machine (including the IP address of a particular computer) that relate to DNS issues. Replace host-name with the fully qualified name of the host machine and submit the command from a command prompt. Contact your system administrator if you find that you have problems with domain policies in the domain server. Re-register your local copy of SAS by selecting Start Run and submitting one of the following commands. Note: These examples use the default SAS location for SAS.EXE. For SAS 9 C:\Program Files\SAS\SAS 9.1\sas.exe /regserver For SAS 8 C:\Program Files\SAS Institute\SAS\v8\sas.exe /regserver 22

27 If you are using a file in C:\WIINDOWS\system32\drivers\etc\hosts, make sure that the host names and IP addresses are correct. Make sure that you do not have an old server name in the SAS Enterprise Guide configuration file. If you experience problems with Internet Protocol Version 6, contact your system administrator. Server execution failed <status>0x Select Bridge as the connection protocol. See step 1 in the section SAS.EXE Is Remote. Server execution failed <status>0x Make sure that you can execute SAS (via the SAS.EXE file). Re-register you local copy of SAS by selecting Start Run and submitting one of the following commands. Note: These examples use the default SAS location for SAS.EXE. For SAS 9 C:\Program Files\SAS\SAS 9.1\sas.exe /regserver For SAS 8 C:\Program Files\SAS Institute\SAS\v8\sas.exe /regserver If SAS.EXE is local, check the registry entry, as shown in the following steps. Warning: Always back up your registry before you make any registry changes. For assistance, refer to the Microsoft Windows help, Microsoft documentation, or the Microsoft Windows Web site. SAS is not responsible when you edit the Windows registry. Changes in the Windows registry can render your system unusable and will require that you re-install the operating system. 1. Select Start Run and submit the REGEDIT command. 2. In the Registry Editor window, select HKEY_LOCAL_MACHINE SOFTWARE Classes CLSID {440196D4-90F0-11D0-9F41-00A024BB830C}. 3. Right-click the key that appears in the right pane and select Modify. 23

28 Display 22. Checking the registry entry This action opens the Edit String dialog box. 4. In the dialog box, copy the SAS command that appears in the Value data field. Display 23.The Edit String dialog box 5. Open a command window. Paste the SAS command in the command line and submit it. If you receive an error or if SAS.EXE does not appear in the task manager, remove nologo noterminal noxcmd from the command line. Then resubmit it and check for error messages. If the SAS Workspace Server test is okay but the SAS Metadata Server test displays error messages, check to see if an XML library is assigned. If an XML library is assigned in the metadata, contact SAS Technical Support for help. 24

29 Try re-creating the SdsLocal repository by following these steps: 1. Select Start Run. 2. In the Open field of the Run dialog box, type cmd and click OK. 3. In the command window, navigate to C:\Program Files\SAS\Shared Files\SAS Directory Services and rename the SdsLocal repository file to SdsLocal.old. 4. While you are still in the C:\Program Files\SAS\Shared Files\SAS Directory Services folder, submit the following command to re-create the SdsLocal repository: sdsdbmnt n sdslocal Make sure that your DCOM configuration settings are correct, per the information in SAS Note (support.sas.com/kb/10/805.html) The client has connected to a SAS <server type> Server (v1.0) when it intended to connect to a SAS <server type> Server. Enter the appropriate server port (per the following table) in the Bridge Parameters dialog box. Server Type Default Ports SAS Workspace Server with an object spawner file (TS721) 5308 SAS Workspace Server 8591 SAS Metadata Server 8561 The file SAS.TLB could not be found on this machine. Re-install the SAS Integration Technologies component. To re-install the component, run the following executable file from the SAS Enterprise Guide installation CD: CD_drive_name:\eguide\bundles\inttechc\setup.exe 25

30 The hostname is not recognized or invalid. Test connectivity with the server host by pinging the SAS server s host name from the SAS Enterprise Guide client PC. If you cannot connect, contact your system administrator. The process cannot be launched for client <username> Check the SAS launch command in SAS Management Console s SASMain Workspace Server Properties dialog box to verify that you have the correct SAS command. The RPC server is unavailable. Make sure that the Remote Procedure Call (RPC) service is running in the Services window, as show here: Display 24. Verifying that the Remote Procedure Call (RPC) Service is running The PC client might not recognize the server through the domain. You can use the command nslookup hostname to find details about the host machine (including the IP address of a particular computer) that relate to DNS issues. Replace host-name with the fully qualified name of the host machine and submit the command from a command prompt. Test connectivity with the server host by pinging the SAS server s host name from the SAS Enterprise Guide client PC. 26

31 Make sure that your firewall does not have a rule in place that blocks the SAS Enterprise Guide 4 executable file (SEGUIDE.EXE) from running. For additional details, see SAS Note 3902 (support.sas.com/kb/3/902.html). The system cannot find the path specified Check the SAS command line in the registry, as follows in the steps below. Warning: Always back up your registry before you make any registry changes. For assistance, refer to Microsoft Windows help, Microsoft documentation, or the Microsoft Windows Web site. SAS is not responsible when you edit the Windows registry. Changes in the Windows registry can render your system unusable and will require that you re-install the operating system. 1. Select Start Run and submit the REGEDIT command. 2. In the Registry Editor window, select HKEY_LOCAL_MACHINE SOFTWARE Classes CLSID {440196D4-90F0-11D0-9F41-00A024BB830C} LocalServer Right-click the key that appears in the right pane and select Modify. Display 25. Modifying a registry entry in the Registry Editor window This action opens the Edit String dialog box. 27

32 4. In the dialog box, copy the SAS command that appears in the Value data field. Display 26. Copying the SAS command from the Edit String dialog box 5. Open a command window. Paste this command in the command line and submit it. If you receive an error message or if SAS.EXE does not appear in the task manager, remove nologo noterminal noxcmd from the command line, resubmit the command, and check for error messages. User does not have authority Verify that your user ID has been assigned Log on to a batch job permission. Follow the steps outlined in the troubleshooting suggestions for A username is required. Verify that the user ID and password combination is valid. Make sure that the password has not expired. Make sure that you can invoke SAS with the user ID by submitting the RUNAS command, as follows: 1. Locate the SAS.EXE file on your C drive. 2. Open a command-prompt window and enter one of the following commands. Note: The following examples use the default SAS location for SAS.EXE. For SAS 9 runas/user:mydomain\myhostname\username C:\Program Files\SAS\SAS \9.1\sas.exe For SAS 8 runas/user:mydomain\myhostname\username C:\Program Files\SAS Institute \SAS\v8\sas.exe 3. Enter the user password when you are prompted. Try adding the domain name or the host name to the user ID (for example, domain-name\user_id). 28

33 If you are connecting to the SAS object spawner per the instructions in TS-721 (Quick Start Object Spawner and Workspace Server with a Basic SAS 9 Foundation Install), make sure that the sascommand line in the objspawn.cfg file contains a valid command line for invoking SAS. Display 27. Verifying the SAS command in the SASMain Workspace Server Properties dialog box 29

34 References SAS Institute Inc TS-721 Quick Start: Object Spawner and Workspace Server with a Basic SAS 9 Foundation Install. Cary, NC: SAS Institute Inc. Available at support.sas.com/techsup/technote/ts721.pdf. SAS Institute Inc SAS Note 15992, SAS Object Spawner log file is no longer created by default. Cary, NC: SAS Institute Inc. Available at support.sas.com/kb/15/992.html. SAS Institute Inc SAS Note 10805, SAS Enterprise Guide clients cannot connect to a remote repository process running under Windows XP or Windows Cary, NC: SAS Institute Inc. Available at support.sas.com/kb/10/805.html. SAS Institute Inc Usage Note 3902, Windows CoCreateInstance(SDSDBR) API failed (result 0x800706ba The RPC server is unavailable.) Cary, NC: SAS Institute Inc. Available at support.sas.com/kb/3/902.html. 30

35

36 Paper Title Copyright 2008 SAS Institute Inc., Cary, NC, USA. All rights reserved. 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. All Rights Reserved.