The SAS Hot Fix Analysis, Download and Deployment Tool (SASHFADD):
WINDOWS and UNIX versions of SASHFADD are available. SASHFADD installed on a Windows or UNIX machine can be used to analyze SAS deployments for Windows, UNIX, z/OS and OpenVMS Itanium systems.
Important message about file transfers:
SASHFADD generates scripts which execute anonymous FTP commands to download data files and hot fixes from SAS.
If your site does not allow FTP, there are publically available 3rd party utilities designed to transfer files via
HTTP. The download scripts generated by SASHFADD can be converted for use by these utilities.
If your site does not allow FTP or the use of a 3rd party utility, see Troubleshooting for instructions on manually downloading the hot fix data file required by SASHFADD. The Download links in the Hot Fix Analysis report generated by SASHFADD can be individually clicked to download the hot fixes.
NOTE: Neither FTP nor any 3rd party file transfer utilities are supported by SAS Technical Support. For file transfer issues at your site, please contact your system administrator.
WINDOWS
There are no special system requirements for Windows platforms |
UNIX
SASHFADD requires Perl 5 on UNIX platforms. |
Carefully read this Usage Guide and review the Hot Fix Report generated by SASHFADD prior to using the generated scripts to download and deploy hot fixes. The Hot Fix Report contains critical information regarding hot fix dependencies that may affect your decision to use the download and deployment scripts as generated versus modifying them for your site-specific needs.
Important note concerning "ALERT" issues: New for SASHFADD Ver 1.1 is the reporting of, and separate script generation for, hot fixes that address "ALERT" issues. This feature is provided to support customers who wish to apply hot fixes only for critical issues as determined by SAS Technical Support consultants.
Hot fixes that address ALERT issues are identified in the Hot Fix report with [A]. Scripts designated "ALERT_ONLY" contain just hot fixes for ALERT issues. Scripts NOT specifically designated "ALERT_ONLY" contain ALL hot fixes which are eligible for download and installation via scripting, including hot fixes for "ALERT" issues.
Run the ViewRegistry tool (See SAS Note 35968) to create a DeploymentRegistry.txt file containing the latest information regarding your SAS installation.
SASHFADD run on WINDOWS or UNIX can analyze the DeploymentRegistry.txt file generated from a SAS installation on a different host operating system. For example, you can generate a DeploymentRegistry.txt for your SAS installation on z/OS or OpenVMS Itanium, then copy the DeploymentRegistry.txt into the directory on a WINDOWS or UNIX machine where SASHFADD is installed.
WINDOWS
The C:\Program Files\SAS\SASHFADD directory should now contain the following files: |
UNIX
Your current directory should now contain the following files: * You may choose to delete "SASHFADDux.tar" since it is no longer needed. |
Instructions for making configuration changes are included within the installed SASHFADD.cfg file, and can also be viewed in the Default SASHFADD.cfg. Confirmed SASHFADD configuration settings will appear at the bottom of the Hot Fix Report and in the SASHFADD Log file.
** Note about the SAS Release being analyzed: You are not required to specify in SASHFADD.cfg whether
SASHFADD is analyzing a SAS 9.2 or a SAS 9.3 deployment. SASHFADD should be able to make that determination
by looking for key products in DeploymentRegistry.txt. However, in the event of an unusual SAS deployment where
that determination can not be made, you should "uncomment" either "-SAS 9.2" or "-SAS 9.3" to explicitly specify the
release of SAS. If you accidentally uncomment both releases, SASHFADD will report a failure and will not
proceed with the hot fix analysis.
WINDOWS
Double-click the SASHFADD.exe file to execute the tool. |
UNIXExecute the command: perl SASHFADD.plYour system settings may require you to enter a fully qualified path to the PERL 5 executable. If PERL 5 is not installed on your system, you will need to either install it or use the Windows version of SASHFADD. |
If you did not select the "-SILENT" option in SASHFADD.cfg, you will be prompted to enter a descriptive name for the machine that contains the SAS deployment being analyzed. This name will be used for the creation of the output directory containing the SASHFADD report and scripts. Only alphanumeric characters and underscores '_' are allowed in the name. (Examples: "My_PC", "ALECs_pc", "server4321", "Test_Machine_5")
During SASHFADD processing, scripts are generated and executed that download a required data file from the SAS Technical Support Hot Fix site. The file is download via FTP and will be either "SAS92_hot_fix_data.xml" or "SAS93_hot_fix_data.xml" depending on whether SASHFADD is analyzing a SAS 9.2 or a SAS 9.3 deployment. If you do not see either of these files in your current directory after running SASHFADD, refer to Troubleshooting for more information.
SASHFADD will also create a new directory. If you entered a descriptive name when prompted by SASHFADD, the new directory will be called:
* <name_you_entered>_<timestamp> is used so that a unique directory name is created each time SASHFADD is run. The timestamp is in DayMonthYear_Hour.Minute.Second format. For example, "My_PC_17Feb2011_13.24.33".
- ANALYSIS_
- DEPLOY_
- DOWNLOAD_
- LOG_
IMPORTANT! Carefully review the SAS_Hot_Fix_Report documented in this section
prior to downloading and deploying hot fixes!
It is especially important that you carefully follow any pre/post installation instructions in Documentation designated by a
[ D ] in the report
The Hot Fix Report can be found in the ANALYSIS_ directory. The report lists the hot fixes that are available for your installed SAS products based on the DeploymentRegistry.txt file.
The Hot Fix Report may contain up to three sections:
- Hot fixes that may be downloaded and installed individually or by using the generated scripts
This section will always appear in the Hot Fix Report and will list hot fixes that can be downloaded and installed individually, or by using the generated ftp_scripts (step 9), SAS Deployment Manager for SAS 9.3 (step 10) or install_scripts for SAS 9.2 (step 11).Successful installation of these hot fixes will be recorded in the deployment registry. If your system is up-to-date with these hot fixes, then an appropriate message will appear.
- Hot fixes that are available only by clicking the Download link and following installation instructions
This section may appear in the Hot Fix Report, and will list hot fixes which must be downloaded and installed individually by closely following the instructions in the documentation.Successful installation of these hot fixes may be recorded in the SAS Deployment Registry depending on the unique properties of the hot fix. It is possible that you will continue to see these hot fixes in the report even if they have been successfully installed. If you have already applied these hot fixes by following the installation instructions, then you can safely ignore their reappearance in the report.
- Hot fixes containing updates only to non-English software components
This section may appear in the Hot Fix Report and will list hot fixes which can be applied only to systems where the languages listed with the hot fix are installed for the specific SAS product.Successful installation of these hot fixes will be recorded in the SAS Deployment Registry. If you are ineligible to install these hot fixes because you have not installed the SAS product for the languages listed, then you can safely ignore the appearance of these hot fixes in the report.
If you do not wish to see these hot fixes in the report, select "-ENGLISH_ONLY" in the SASHFADD.cfg.
Each section of the report includes a list of available hot fixes and links to review Issue(s) Addressed, Documentation, and to Download the hot fix.
IMPORTANT (2): The instructions in the following sections assume that you have NOT selected in SASHFADD.cfg one specific type of scripting that you want SASHFADD to generate.
|
WINDOWS
In the DOWNLOAD_ directory, you will find the following files: ALERT_ONLY_README.txt ** Files will appear only if there are hot fixes for "ALERT" issues. The ftp_script.txt and ftp_script_ALERT_ONLY.txt files can be modified as needed to exclude hot fixes from download or to change the transfer protocol as required by your site. If you are satisfied with the list of hot fixes to be downloaded based on the Hot Fix Report, double-click ftp_script.bat or ftp_script_ALERT_ONLY.bat to begin downloading the hot fixes. A window will appear showing the progress of the downloads. These .bat files MUST be run from within the DOWNLOAD_ directory. It may take several minutes to complete the download process. Hot fix download files will be placed in the DEPLOY_ directory. |
UNIX
In the DOWNLOAD_ directory, you will find the following files: ALERT_ONLY_README.txt ** Files will appear only if there are hot fixes for "ALERT" issues. The ftp_script.sh and ftp_script_ALERT_ONLY.sh files can be modified as needed to exclude hot fixes from download or to change the transfer protocol as required by your site. If you are satisfied with the list of hot fixes to be downloaded based on the Hot Fix Report, then execute one of the
following commands: These scripts MUST be run from within the DOWNLOAD_ directory. It may take several minutes to complete the download process. Hot fix download files will be placed in the DEPLOY_ directory. |
NOTE: The MD5_checksums files contain MD5 checksum values for each hot fix download available for your installed SAS products. This file can be useful should you wish
to validate the integrity of the downloaded hot fix files. Tools used for performing MD5 validation are not available from SAS and are not supported by SAS Technical Support.
In the DEPLOY_ directory, you will find the hot fixes downloaded by the download script.
The SAS Deployment Manager (SDM) is used to apply SAS 9.3 hot fixes. Information on using the SDM is
available in the
SAS Deployment Wizard/SAS Deployment Manager 9.3: User’s Guide.
http://support.sas.com/documentation/installcenter/en/ikdeploywizug/64204/PDF/default/user.pdf
See the Apply Hot Fixes section in Chapter 5 -- SAS Deployment Manager Tasks
By default, the SDM will search in the ' <SASHOME>/InstallMisc/HotFixes/New ' directory for hot fixes to be applied. To complete the installation of the hot fixes you may either:
Before running the install script:
In the DEPLOY_ directory, you will find the hot fixes downloaded by the download script, and for WINDOWS and UNIX systems, host-specific installation scripts that can be used to silently install all of the hot fixes.
IMPORTANT! In the following sections, files designated "_ALERT_ONLY" include just hot fixes that address ALERT issues as indicated by [A] on the Hot Fix Report. Files NOT designated _ALERT_ONLY include all hot fixes eligible for scripted download and silent installation, including hot fixes that address ALERT issues.
|
SASHFADD run on WINDOWS or UNIX to analyze a WINDOWS SAS 9.2 deployment
In the DEPLOY_ directory, you will find the following files: ALERT_ONLY_README.txt ** Files will appear only if there are hot fixes for "ALERT" issues. To install the downloaded hot fixes "silently" on your Windows system:
|
|
SASHFADD run on WINDOWS or UNIX to analyze a UNIX SAS 9.2 deployment
In the DEPLOY_ directory, you will find the following files: ALERT_ONLY_README.txt ** Files will appear only if there are hot fixes for "ALERT" issues. To install the downloaded hot fixes "silently" on your UNIX system:
|
SASHFADD run on UNIX or WINDOWS to analyze a z/OS SAS 9.2 deployment
The installation script used to silently install all of the hot fixes is not available at this time for z/OS. However, you can still use the FTP download script to download hot fixes. Once downloaded, the hot fixes will need to be applied individually by following the instructions provided in the documentation links in the Hot Fix Report. |
SASHFADD run on UNIX or WINDOWS to analyze an OpenVMS Itanium SAS 9.2 deployment
The installation script used to silently install all of the hot fixes is not available at this time for OpenVMS Itanium. However, you can still use the FTP download script to download hot fixes. Once downloaded, you can apply the hot fixes individually by following the instructions provided in the documentation links in the Hot Fix Report, or you can create a script to apply the hot fixes "silently" (without the GUI interface). |
To verify that all hot fixes have been installed:
- After installation of all hot fixes, rerun the deployment registry tool to create a new DeploymentRegistry.txt. (See Step 4)
- Copy the updated DeploymentRegistry.txt to the directory where SASHFADD is located.
- Run SASHFADD to create a new directory containing a new ANALYSIS_ subdirectory.
- Review the Hot Fix Report as outlined in Step 8 and, if necessary, compare the Hot Fix Report with the report generated in the previous execution of SASHFADD.
New in SASHFADD 2.0: Reports listing all of the installed hot fixes that appear in DeploymentRegistry.txt are now generated by SASHFADD. These reports appear in the LOG_ directory and are in HTML and XML formats.
When the installation scripts are run for SAS 9.2, the logs pertaining to installation are MIT logs. If problems are
encountered with installation of the hot fixes, please refer to the:
Using the Maintenance Installation Tool to Install SAS® Hot Fixes - Usage and Troubleshooting Guide
Common Problems and Solutions
...or you see the following message on the command console:
SASHFADD was unable to download or open a critical hot fix data file.
...or you see the following messages on the command console:
FTP> Invalid Command...or you see the following message near the top of the hot fix report:
FTP> Not Connected
Warning: Hot Fix Data file (SAS9[2-3]_hot_fix_data.xml) is not found or is more than 96 hours old....or you see the following ERROR in the SASHFADD_LOG_:
>> %%% ERROR: Unable to open SAS9[2-3]_hot_fix_data.xmlThese errors indicate that SASHFADD could not access current hot fix data. A problem in downloading either SAS92_hot_fix_data.xml or SAS93_hot_fix_data.xml may have been encountered. Depending on the SAS release being analyzed, SASHFADD must have access to one of these files. This warning is likely due to an FTP problem that affected the generated SAS9[2-3]_hot_fix_data_ftp_download_script.txt (Windows) or SAS9[2-3]_hot_fix_data_ftp_download.sh (UNIX) file.
This problem is most likely to occur when a SASHFADD script makes an FTP request through a network "firewall", but the firewall prevents the FTP request from being fulfilled.
If you or your system administrator are unable to correct the FTP and/or firewall issue, you can download the necessary data file manually:
Note: If you are unable to resolve the FTP problem, then you most likely will NOT be able to successfully download hot fixes using the automated scripts described in step 8. However, you should still be able to download the hot fixes individually by clicking the Download link(s) in the "SAS_Hot_Fix_Report_".
- Click: SAS92_hot_fix_data.xml if SASHFADD is analyzing a SAS 9.2 image
Click: SAS93_hot_fix_data.xml if SASHFADD is analyzing a SAS 9.3 image
If you are not certain which release of SAS is being analyzed, download both of the above files. SASHFADD will use the one it needs.- Select "File", then "Save As"
- Confirm that you are saving SAS92_hot_fix_data.xml and/or SAS93_hot_fix_data.xml (file names are case sensitive!)
- Save SAS92_hot_fix_data.xml and/or SAS93_hot_fix_data.xml to the same directory as SASHFADD
> > %%% ERROR: Unable to open DeploymentRegistry.txtin the Log/tool_log.txt file indicates that the DeploymentRegistry.txt file generated in Step 4 does not exist in the same directory as SASHFADD.
> > %%% ERROR: Deployment Registry Host () could not be identified.