Hot fix I9S002 addresses the issue(s) in Base SAS 9.4_M7 as documented in the Issue(s) Addressed section of the hot fix download page:
I9S002 is a "container" hot fix that contains the following "member" hot fixes which will update the software components as needed.
I9N002 updates SAS Compiler and Symbolic Differentiator 9.58
I9P002 updates SAS Thread-safe Compiler and Symbolic Differentiator 9.59
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, I9S002s6.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 I9S002s6.zip on each machine or save it in a network location that is accessible to all machines.
Do NOT extract the contents of I9S002s6.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 I9S002s6.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.
Required only for distributed deployments:
$ umask 022
$ cd /install
$ /bin/sh ./TKGrid_HF_x86_64_tkcmp02.sh
You should see the following:
Verifying archive integrity... All good.
running TKGrid/bin_tkcmp_02/hfInstall TKGrid /install
TKGrid HotFix Configuration Utility.
Running on 'gridnode01.orion.com'
Using stdin for options.
Shared install or replicate to each node? (Y=SHARED/n=replicated)
The updated shared libraries will be located in the /install/TKGrid/lib_tkcmp_02 folder.
If necessary, the permissions on the /install/TKGrid folder for all computing appliance nodes may need to be updated for group read/write permissions.
Edit the TKGrid_REP/tkmpirsh.sh file
/opt/TKGrid/bin/simcp /opt/TKGrid_REP/tkmpirsh.sh /opt/TKGrid_REP
This completes the installation of hot fix I9S002 on 64-bit Enabled Solaris.
Copyright 2022 SAS Institute Inc. All Rights Reserved.