Installation Instructions for Hot Fix C9A002

Windows for x64


Hot fix C9A002 addresses the issue(s) in SAS Scalable Performance Data Server 5.4 as documented in the Issue(s) Addressed section of the hot fix download page:

http://ftp.sas.com/techsup/download/hotfix/HF2/C9A.html#C9A002


C9A002 is a "container" hot fix that contains the following "member" hot fixes which will update the software components as needed.

C8Z002  updates  SAS Scalable Performance Data Client 5.4
C8Y002  updates  SAS Scalable Performance Data Server 5.4
E8V001  updates  SAS Scalable Performance Data Server Plug-in for SAS Management Console 5.4
D1A001  updates  SAS Threaded Kernel Extensions for SAS Scalable Performance Data Server 5.4

See What is a container hot fix? in the Hot Fix FAQ for more information about container hot fixes.


Before applying this hot fix, follow the instructions in SAS Note 35968 to generate a SAS Deployment Registry report, then verify that the appropriate product releases are installed on your system. The release number information in the Registry report should match the 'member' release number information provided above for the software components installed on each machine in your deployment.

The hot fix downloaded, C9A002x6.zip, includes the updates required for all components listed above on all applicable operating systems. To apply this hot fix on multiple machines, you can either save C9A002x6.zip on each machine or save it in a network location that is accessible to all machines.

Do NOT extract the contents of C9A002x6.zip. The hot fix installation process will extract the contents as needed.


IMPORTANT NOTES

  1. Files delivered in this hot fix will be backed up during the installation process. However, it is good general practice to back up your system before applying updates to software.

  2. You must have Administrator Privileges on your CLIENT or SERVER machine.

  3. All currently active SAS sessions, daemons, spawners and servers must be terminated before applying this hot fix.

  4. This hot fix should be installed using the same userid who performed the initial software installation.

  5. CONFIGURATION: No automatic configuration scripting is included for this hot fix. If you have previously configured software installed, the SAS Deployment Manager may present a screen where you will see "Apply SAS Hot Fixes" and "Configure SAS Hot Fixes" options. On this screen, you must ensure that the "Configure SAS Hot Fix" option is *not* selected. If this option is automatically selected, please de-select it prior to proceeding with the SAS Deployment Manager Screens. Failure to do so could have unintended consequences when applying this hot fix.


INSTALLATION

Hot Fix C9A002 must be installed on each machine where the updated components of the product, listed above, are installed. During the installation process you may see references to all operating systems for which updates are provided in the hot fix. The installation process will determine the operating system and which component(s) of SAS Scalable Performance Data Server 5.4 require updating on the machine. See SAS Note 44810 for more details.

The hot fix will be applied using the SAS Deployment Manager. By default, the SAS Deployment Manager will search in the <SASHOME>\InstallMisc\HotFixes\New directory for hot fixes to be applied, but will also prompt for a location if you have downloaded hot fixes to a different directory.

After downloading C9A002x6.zip, follow the instructions for applying hot fixes in the SAS Deployment Wizard and SAS Deployment Manager 9.4: User's Guide.

Please review the CONFIGURATION Important Note above concerning proper selection of the "Configure SAS Hot Fix" option in the SAS Deployment Manager.


The hot fix installation process generates the log file

<!SASHOME>\InstallMisc\InstallLogs\IT_date-and-time-stamp.log
for example, IT_2011-10-31-13.18.21.log. Each attempt to apply a hot fix results in the creation of a new log file giving detailed information regarding the installation process.

Postexec log files are created after the installation is completed and identifies the files that were added, backed up, changed and removed. These log files include the ‘member’ hot fix id in the name of the file and are also written to the <!SASHOME>\InstallMisc\InstallLogs directory. There is one postexec log for each ‘member’ hot fix applied (member hot fixes are listed at the top of these instructions).


The content of this hot fix is listed in the hot fix manifest.


POST-INSTALLATION INSTRUCTIONS

For each product installed, click the link to be redirected to post-installation instructions.

C8Z002  updates  SAS Scalable Performance Data Client 5.4
C8Y002  updates  SAS Scalable Performance Data Server 5.4
E8V001  updates  SAS Scalable Performance Data Server Plug-in for SAS Management Console 5.4
D1A001  updates  SAS Threaded Kernel Extensions for SAS Scalable Performance Data Server 5.4


C8Z002  updates  SAS Scalable Performance Data Client 5.4

NONE


C8Y002  updates  SAS Scalable Performance Data Server 5.4

The SAS Scalable Performance Data Server 5.4 hot fix supports changes that allow the SPD Server to be started in FIPS 140-2 compliance mode for secure communications and SPD Server user passwords. Whether you decide to run SPD Server to be FIPS 140-2 compliant or not, the following changes are necessary in your Unix site/rc.spds server start-up script, and Unix site/pwdb Password Manager Database start-up script:

  1. Copy the following lines from the samples/rc.spds script to the same location in your site/rc.spds script:
    # Define FIPS=YES if you want your server to start
    # up in FIPS encrypt mode.  The server will validate
    # the SSL encryption libraries are FIPS compliant
    # and the Password Manager Database is using FIPS
    # compliant encryption of user passwords.
    #
    # If the Password Manager Database is not using
    # FIPS compliant encryption, the server will print
    # an error in the server log and will not start up.
    #
    # If the SSL encryption libraries are not FIPS
    # compliant and the server is using secure connections
    # between the server and client (the SSLSECURE="YES"
    # server option is set) any libname connection will fail
    # and an error will be logged in the SPD server log.
    
    FIPS=NO
    if [ "$FIPS" = "YES" ]; then
       FIPSOPT="-ENCRYPTFIPS -- "
    else
       FIPSOPT=
    fi
    
  2. Replace the site/rc.spds lines that start the spdsserv process with the following lines from the samples/rc.spds script:
    nohup spdsserv $FIPSOPT -parmfile $SPARM -libnamefile $LPARM \
    
    nohup spdsserv $FIPSOPT -nameserverport $NSPORT \
    
  3. Copy the following lines from the samples/pwdb script to the same location in your site/pwdb script:
    TKERSA2_LIB_PATH=$SASHOME/Secure/sasexe
    export TKERSA2_LIB_PATH
    
For more information on starting your Unix or Windows SPD Server to be FIPS 140-2 compliant please refer to the security section of the SAS Scalable Performance Data Server 5.4 Administrator’s Guild found here: http://support.sas.com/documentation/onlinedoc/spds/index.html


E8V001  updates  SAS Scalable Performance Data Server Plug-in for SAS Management Console 5.4

SAS Security Updates

SAS Security Updates are applied during the initial installation of your software. In order to maintain the latest level of security offered by SAS, security updates should be applied and/or re-applied after any changes to your software, including installation of hot fixes. The current SAS Security Updates for all releases of SAS are available at http://ftp.sas.com/techsup/download/hotfix/HF2/SAS_Security_Updates.html. Please re-apply security updates in accordance with the SAS Security Updates and Hot Fixes document available on the SAS Security Updates web page.


D1A001  updates  SAS Threaded Kernel Extensions for SAS Scalable Performance Data Server 5.4

NONE


This completes the installation of hot fix C9A002 on Windows for x64.


Copyright 2019 SAS Institute Inc. All Rights Reserved.