Note to Review Before You Install

Depending on your environment, one or more of the following notes might apply to your site:

When installing SAS 9.3 in a multiple machine deployment, you must install SAS 9.3 on the servers in a specific order. For more information, see Installation Order Rules for Multiple Machine Deployments in SAS Intelligence Platform: Installation and Configuration Guide.
When you are performing a new deployment on a UNIX system, the SAS Deployment Wizard prompts you to run setuid.sh as root (or sudo) before configuration. Certain SAS products and features use functionality that requires SAS to check user ID authentication and file access authorizations. This requirement necessitates that certain files within your SAS installation have setuid permissions and be owned by root.

In the second maintenance release for SAS 9.3, files that must be setuid are updated. Therefore, setuid must be run a second time.

If your site has a custom sasauth file that is supplied by SAS, as a best practice, store a backup of this file in a location other than SAS-installation-directory/SASFoundation/9.3/utilites/bin or SASHome/SASFoundation/9.3/utilites/bin/setuid.
If you are updating a deployment that runs on z/OS, you must update the deployment in the same order that you installed SAS in your initial deployment. For more information, see http://support.sas.com/documentation/installcenter/93/mvs/index.html.

Before you can start the SAS Deployment Wizard, the cell where you are going to perform the software upgrade must be running.
To specify a different version of the Java Runtime Environment (JRE) that you want to use with the SAS Java applications, see Specify a Different JRE in SAS Intelligence Platform: Installation and Configuration Guide.