SAS92HFADD has been renamed to SASHFADD
- "92" was removed from the name because SASHFADD can analyze both SAS 9.2 and SAS 9.3 deployments.
- SASHFADD determines if it is analyzing a SAS 9.2 or SAS 9.3 deployment by looking for key products in DeploymentRegistry.txt.
- SASHFADD will generate scripts to download SAS 9.2 and SAS 9.3 hot fixes and to silently install SAS 9.2 hot fixes.
SAS 9.3 hot fixes are installed using the SAS Deployment Manager.
|
SASHFADD Configuration File (SASHFADD.cfg)
- SASHFADD.cfg can be used to customize how SASHFADD works by:
- If necessary, specifically telling SASHFADD to interpret a DeploymentRegistry.txt as coming from a SAS 9.2 or a SAS 9.3 deployment.
Typically you should not need to set this option, but it is available in case there is an unusual deployment scenario which
prevents SASHFADD from making the correct SAS 9.2 vs. SAS 9.3 determination.
- Running SASHFADD "silently"
- Generating just "Alert only" or "All eligible" hot fix scripts
- Suppressing the display of non-English hot fixes in the Hot Fix Analysis Report
- See SASHFADD Usage Guide - Configuration
for more information.
|
Reporting of Currently Installed Hot Fixes
- Along with the report of hot fixes that are eligible to be installed, SASHFADD also generates a report
of hot fixes that are currently installed on your SAS Deployment.
- The report of currently installed hot fixes is generated in HTML and XML formats.
- The report files are stored in the SASHFADD "LOG" directory.
|
Miscellaneous enhancements
- SASHFADD generated directories have been renamed to make the output from multiple executions of SASHFADD easier to organize.
- SASHFADD 2.0 uses a substantially smaller "hot_fix_data.xml" file than previous versions of SAS92HFADD.
- A SAS92HFADD bug has been fixed that caused reporting errors when multiple operating systems appeared in DeploymentRegistry.txt.
|