Planning Information for Specific Operating Environments :: Planning for Maintenance Releases and Product Upgrades for SAS(R) 9.2

Additional Support for Operating Systems

In the second maintenance release for SAS 9.2, support was added for the following operating systems.

Windows Server 2008
SuSE SLES 11

In the third maintenance release for SAS 9.2, support was added for the following operating systems.

AIX 7
Red Hat Enterprise Linux (RHEL) 6

To determine the level of support for each operating environment (for example, exactly which editions of Windows Server 2008 are supported), see http://support.sas.com/resources/sysreq/hosts.

Installing a Maintenance Release in a UNIX Environment

Modifying the Date-and-Time Stamps for Non-Versioned Files

Note: The tar command is the recommended method for copying and moving a SAS deployment in UNIX because this command preserves the date-and-time stamps of the files. The information in this topic is relevant only if you used the cp command without the -p option (which is required to preserve the date-and-time stamps on your files) to copy your SAS deployment from one location to another.

The installation process for a maintenance release uses the date-and-time stamps for some non-versioned files to determine whether the file needs to be updated. If you copied a deployment of SAS 9.2 (using the cp command without the -p option ), then the maintenance release might not install properly because the date-and-time stamps on the copied files might be different from the deployment that was installed using the SAS Deployment Wizard. In order for the maintenance release to install correctly, the date-and-time stamps of the copied files must be February 20, 2009.

To change the date-and-time stamp of your files to February 20, 2009, enter the following command from the SAS installation directory:

find . | xargs touch -t 200902200000.00

You must run this UNIX command under the user ID that was used to install SAS 9.2. You can modify the attributes of these SAS files under that user ID only.

Using Pluggable Authentication Models (PAM) for Authentication

SAS deployments can be configured to integrate with various authentication technologies. In the third maintenance release for SAS 9.2, SAS provides a better way to specify PAM authentication when initially configuring a system. (A new deployment option for PAM authentication was added to the SAS Deployment Wizard in the third maintenance release for SAS 9.2. For more information, see SAS Intelligence Platform: Installation and Configuration Guide.)

Sites that are applying the third maintenance release for SAS 9.2 will already have integrated with the PAM authentication process. For these sites, the new process will not affect their deployment.

Installing a Maintenance Release in a z/OS Environment

If you are installing a maintenance release in a z/OS environment, you should not complete the steps described in How to Install and Configure the Third Maintenance Release for SAS 9.2. Instead, you should refer to the following resources:

Installation and maintenance instructions for z/OS environments are available from Installation Note 36008 at http://support.sas.com/kb/36/008.html.
After you install the maintenance release, you need to restart your SAS servers. For more information, see “Starting and Stopping SAS Servers on z/OS” in the SAS Intelligence Platform: System Administration Guide.

Note: If your z/OS environment does not have Java or an X11 display, then you might have used basicins.rexx to install SAS 9.2. If you used basicins.rexx, then you will not have a SAS-installation-directory/deploymntreg directory. Before installing the third maintenance release for SAS 9.2, contact SAS Technical Support for additional instructions on how to install the maintenance release at your site.Support for the basicins.rexx script was dropped in the second maintenance release for SAS 9.2. If your order is from 09w44 or later, then you used the linemode.rexx script, and you will have a SAS-installation-directory/deploymntreg directory. Therefore, this note does not apply to you.