Hot fix C9A001 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#C9A001
C9A001 is a "container" hot fix that contains the following "member" hot fixes which will update the software components
as needed.
C8Z001 updates SAS Scalable Performance Data Client 5.4
C8Y001 updates SAS Scalable Performance Data Server 5.4
D1A001 updates SAS Threaded Kernel Extensions for SAS Scalable Performance Data Server 5.4
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, C9A001r6.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 C9A001r6.zip on each machine or save it in a network location that is accessible to all machines.
Do NOT extract the contents of C9A001r6.zip. The hot fix installation process will extract the contents as needed.
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 C9A001r6.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.logfor 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.
For each product installed, click the link to be redirected to post-installation instructions.
C8Z001 updates SAS Scalable Performance Data Client 5.4
C8Y001 updates SAS Scalable Performance Data Server 5.4
D1A001 updates SAS Threaded Kernel Extensions for SAS Scalable Performance Data Server 5.4
C8Z001 updates SAS Scalable Performance Data Client 5.4
NONE
C8Y001 updates SAS Scalable Performance Data Server 5.4
he 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:
# 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
nohup spdsserv $FIPSOPT -parmfile $SPARM -libnamefile $LPARM \ nohup spdsserv $FIPSOPT -nameserverport $NSPORT \
TKERSA2_LIB_PATH=$SASHOME/Secure/sasexe export TKERSA2_LIB_PATH
D1A001 updates SAS Threaded Kernel Extensions for SAS Scalable Performance Data Server 5.4
NONE
This completes the installation of hot fix C9A001 on 64-bit Enabled AIX.
Copyright 2018 SAS Institute Inc. All Rights Reserved.