SAS Hot Fix Downloads

What is a hot fix?
The answer can vary. To some it is a quick fix to an immediate problem or an essential fix to a commonly recurring problem. To others, it is system maintenance.
Originally, Technical Support’s hot fix focus was on the need to solve critical and frequently recurring problems. When the hot fix process was first introduced, alert priority defects (i.e. wrong numbers) and defects that affected many customers were targeted for hot fixes. With such a limited focus, the number of hot fixes was minimal in Release 8.1. The fact that Release 8.2 was in development and would give customers an upgrade option also allowed the deferment of some of the fix requests until the new release.
Alert and commonly encountered defects are still the primary focus for hot fixes. However, with Release 8.2 being the last scheduled V8 release, and with some of the V8 operating systems no longer supported in V9, the hot fix process is branching out to provide fixes to less critical and less widespread defects.
Developing a viable work around to a problem is still the preferred approach over providing a hot fix, and hot fixing every problem that customers encounter is not practical. However, we do want to provide fixes that allow customers to “maintain” their installed production SAS System until they are reasonably able to upgrade to the latest SAS release. For this reason, we have seen an increase in the number of hot fixes for Release 8.2.
Hot fixes have been tested and are fully supported, and most hot fixes are incorporated into the next scheduled release.

Top ^

Which hot fixes should I apply?
There are two philosophies which can be followed when determining which hot fixes should be applied.
Philosophy 1: ”Install only what is needed”
Some sites are interested in fixing only those problems that they encounter. They do not see the necessity of installing fixes for problems that do not affect them. They want to install just the fixes that are needed to keep their existing jobs running successfully. This minimizes the number of changes and regression testing to their SAS installations and the time spent installing hot fixes. These sites should download hot fixes only on an as-needed basis.
Philosophy 2: “Install every fix that is available”
Other sites want to be proactive by keeping their SAS installation updated with all of the latest fixes. These are typically larger sites that use many different components of the software. There are also users who are just more comfortable with always running the “latest and greatest”. For these sites, downloading the product bundles at set intervals of time is the best and most efficient approach.
There are customers who would still prefer to get hot fixes on media in the same format as the old style “maintenance” releases. For these sites, downloading the hot fix bundles, and supplementing with individual hot fixes when needed, is the best alternative. The bundles can be downloaded and applied at predetermined time intervals set by the site. The only differences between the hot fix bundles and the old maintenance releases are:

The tslevel is not incremented when a bundle is applied.
Hot fix bundles are available via web download only; media distribution is not available.
Hot fix bundles are distributed by product.

Neither philosophy is better or more correct than the other; they are just two different ways of thinking. It is up to each site to determine which philosophy best meets its business needs.

Top ^

How can I receive automatic notification when a new hot fix becomes available?
When new hot fixes become available, announcements are posted to tsnews-l. If you are not subscribed to this listserv, you can do so from:
http://support.sas.com/techsup/news/tsnews.html

Top ^

Are all Release 8.1 hot fixes included in Release 8.2?
Many of the defects for which Release 8.1 hot fixes were provided are fixed in Release 8.2. For those defects that are not fixed in Release 8.2, hot fixes will be provided. For detailed information, view the document:
Status of Release 8.1 Hot Fixes in Release 8.2

Every Release 8.1 hot fix can have one of the following statuses:

Fixed
The defect is fixed in production Release 8.2.

Hot Fix Available
This status is a link to the Release 8.2 hot fix.

Top ^

How can I determine which hot fixes have been applied to my SAS installation?
For SAS 9.2, see SN-35968 for information regarding hot fixes that have been applied to your SAS installation.
For SAS 8.2 and SAS 9.1.3, an audit file is installed with every SAS Foundation hot fix. This text file contains hot fix specific information such as the hot fix name, product involved, files included in the hot fix, port date, SAS Note numbers and comments. Audit files have the same name as the hot fix (i.e. e9ba01wn.aud) and are installed in a location specific to each host.
Do not delete installed audit files. These files may be used by Technical Support to troubleshoot problems.

OS/390 Audit files are installed in a location (&prefix) specified by the person who installed the hot fix; there is not a default installation location for these files on OS/390. The dataset where audit files are installed is
&prefix.HF<hot-fix-number>.AUDIT
where &prefix is the prefix of your SAS Installation data sets; for example,
SASTSD.SAS81.HF81BA06.AUDIT

UNIX For SAS 8.2:
Audit files are installed in
!SASROOT/.install/hotfix
In this directory, an audit file will exist for every hot fix that has been installed. The filenames are in the format of
<hot-fix-name><platform-code>.aud
For example
!SASROOT/.install/hotfix/81ba06h8.aud

For SAS 9.1.3:
Audit files are installed in
!SASROOT/install/admin/hotfix
Review the file
!SASROOT/install/admin/history.hotfix
to see a list of all hot fixes that have been applied to your system.

PC (Windows and OS/2) Audit files are installed in
!SASROOT\core\sasinst\hotfix
In this directory, an audit file will exist for every hot fix that has been installed. The filenames are in the format of
<hot-fix-name><platform-code>.aud
For example
!SASROOT\core\sasinst\hotfix\81ba06wn.aud

VMS (Alpha and VAX) Audit files are installed in
SAS$ROOT:[TOOLS.SUPPORT.HOTFIX]
In this directory, an audit file will exist for every hot fix that has been installed. The filenames are in the format of
<hot-fix-name><platform-code>.aud
For example
SAS$ROOT:[TOOLS.SUPPORT.HOTFIX]81BA06AV.AUD

CMS For every hot fix installed, the contents of the audit file is appended to the file HOTFIX AUDIT <fm> on the SAS System Disk. This file will contain a cumulative list of all hot fixes installed to the system.

Top ^

What is a hot fix bundle?
A hot fix bundle is simply an accumulation of one or more individual hot fixes. Hot fix bundles are currently available for Base SAS (for Release 8.2 and SAS 9.1.3 Service Pack 4) and SAS/STAT (for Release 8.2 only). New Base SAS and SAS/STAT hot fixes t hat are released after a bundle is created must be downloaded and installed individually or installed with the next bundle. Hot fixes for other products must also still be downloaded individually.
The bundle for Base SAS is the largest, and it is updated most frequently. Since Base SAS has a number of fixes in different components of the software, the bundle allows customers to download and install multiple Base SAS hot fixes at one time instead o f downloading and installing hot fixes individually.
These bundles are available by platform. Fix lists are provided to document which hot fixes are included in a bundle. Audit files will also be installed with each bundle. These files may be used by Technical Support to troubleshoot problems, so please do not remove them.
The frequency at which these bundles are updated and released is based on the number of hot fixes released since the last bundle and on the number and nature of hot fixes under development at a given time.
While neither the SAS release number nor the tslevel are incremented when a bundle in installed, a new message is written to the log at invocation time:

For Release 8.2:
NOTE: This installation is running Base SAS hot fix bundle 82BX09.

For SAS 9.1.3 (9.1 TS1M3) Service Pack 4:
NOTE: (E9BX05) SAS 9.1.3 SP 4

Top ^

What is the significance of the IMPORTANT! message and hot fix list displayed before I am able to download a bundle ?
How does this list compare to the hot fixes listed on the Hot Fixes not included in Hot Fix Bundle report?

When the download of a bundle is initiated, you may see the following:
IMPORTANT!
If you have applied the following hot fix(es) to your system,
these hot fix(es) must be reapplied AFTER installing E9BX01:

The hot fixes listed on this intermediate download page are ones which were released after the hot fix bundle was released, but which contain updated versions of modules that are included in the bundle. If any of these recent hot fixes have been applied to your system, and the hot fix bundle is installed afterward, the recent fixes will be lost (overwritten). This synchronization problem can be avoided by reapplying to your system any hot fixes that are listed on the IMPORTANT! message page. It is critical that you review this page carefully and reinstall any hot fixes that appear on the list!
The hot fixes listed on the IMPORTANT! message page are only a subset of the fixes listed on Hot Fixes NOT included in bundle report, which shows all hot fixes that are not included in the bundle. These hot fixes were either intentionallly excluded from the bundle, or they are new hot fixes that have been rel eased since the bundle was produced. Most of the hot fixes on this report will be included in the next iteration of the bundle.

Top ^

Should hot fixes be installed in a specific order?
Will installing one hot fix over-write another fix?
No, hot fixes do not have to be installed in any specific order ...
and
No, installing one hot fix will not overwrite a previously installed fix ...
for three reasons:

All of the updated files (i.e. modules, catalogs, message files, etc) necessary for a fix are included in the one hot fix.
No two production hot fixes contain the same updated files.
Hot fixes are cumulative. When a existing hot fix is replaced with a newer version which contains additional fixes, all previous fixes are also included.
There are three exceptions:

Once a hot fix bundle (Base SAS only) has been installed, do not re-install any of the individual hot fixes that are included in that bundle.
Many hot fixes have been replaced with newer versions which contain additional fixes. Once a current hot fix has been applied, do not install a previous version (i.e. replaced version) of that hot fix.
If you have previously applied hot fixes to SAS Release 8.2 (TS2M0) that are more recent than the current bundle, then you must reapply those same fixes after installing the bundle. A hot fix is more recent than the bundle if i t does NOT appear on the bundle fix list for your operating system. This is required to ensure that you have the latest versions of all modules that have been impacted by hot fixes.
Neither scenarios #1 nor #2 should be necessary; however, if you believe they are, please contact Technical Support before executing either of these exceptions.

Top ^

Is a "silent" installer or "batch mode" installer available for hot fixes?

For SAS 9.1.3 (9.1 TS1M3) "Silent" installers are available according to guidelines in SAS Note SN-21020
SAS 9.2 (TS2M0), Hot Fix, "Silent" installation is an option. More information can be found in the Maint_Install_Tool.pdf.
NOTE: SAS 9.1.3 Service Pack,only, Silent Installation options are discussed in SAS Note: SN-13752

Top ^

How can I tell which release of SAS a hot fix can be applied to?

Unless otherwise noted on the hot fix download page, individual hot fixes are designed for specific releases of SAS. A hot fix should NOT be applied to a SAS release or to an Additional SAS Product or Solution other than the one for which it was intended.
The easy way to know if a hot fix is designed for a specific release of SAS is to look at the first 2 characters of the hot fix ID number and compare with the following table:

Hot Fix ID begins with: Hot Fix can be applied to:
81 Release 8.1
82 Release 8.2
B9^* SAS 9.1^*
C9^* SAS 9.1.2 (9.1 TS1M2)^*
D9^{* #} SAS 9.1.3 (9.1 TS1M3 - Service Pack 3)^{* #}
E9^* SAS 9.1.3 (9.1 TS1M3 - Service Pack 4)^*
F9 SAS 9.2 (9.2 TS1M0)
For SAS 9.2 (9.2 TS2M0) information, refer to the naming convention section of the Important Changes to Hot Fixes document

^* Note: Beginning with SAS 9.1, hot fix ID numbers use a letter-number combination to identify the applicable release of SAS. This identifier is unique to hot fixes.
^# Note: A limited number of "D9...." hot fixes can be applied to either Service Pack 3 or to Service Pack 4. If a "D9..." hot fix can be applied to multiple Service Packs, it is indicated on the hot fix download table.

Top ^

Why are some issues addressed in hot fixes labeled "ALERT"?

ALERT issues are problems that you need to be aware of before you install or use the software. These may include, but are not limited to, security, data integrity and incorrect output. The Hot Fix download site includes the following features to help you quickly identify hot fixes for ALERT issues:

SAS 9.1.3 (9.1 TS1M3) - Download pages which reference hot fixes for ALERT Issues only are available. These same ALERT issue hot fixes also appear on our comprehensive SAS 9.1.3 hot fix download pages.
If you are running SAS 9.1.3 (9.1 TS1M3) with Asian Language Support (DBCS), please view the Asian Language Support ALERT Issues page.

Additional SAS Products and Solutions - An ^A has been added to the links to individual products and solutions which have hot fixes that address ALERT issues.
Hot Fix announcements made to the TSNEWS-L listserv also include special notification when a hot fix is released for an ALERT issue.

Top ^

What is a Service Pack?

A Service Pack is a software update containing system enhancements and bug fixes in one installable package. Service Packs are available only for SAS 9.1.3 (9.1 TS1M3).
Service Packs contain all previously released SAS 9.1.3 hot fixes. The individual hot fixes contained in a Service Pack are no longer available for separate download.
The latest Service Pack can be downloaded from the SAS Hot Fix web site, and must be applied to your system before installing any currently available hot fixes.
Note - Service Pack download is not available for all operating systems.
The content of Service Packs varies by operating system. Click on an operating system link below to view the list of fixes and enhancements included in the latest Service Pack:

MAINFRAME: z/OS_(OS/390)

PC: Windows, Windows for IPF (64bit)

VMS: OpenVMS_Alpha

UNIX: HPUX, Solaris, AIX, Tru_64, Linux, HPUX_for_Itanium, Linux_f or_Itanium

Top ^

Are Service Packs Cumulative?

Yes. The fixes and enhancements (including hot fixes) that were in previous service packs are included in the latest service pack.

Top ^

Why are previously available hot fixes no longer available for download?

All 9.1.3 hot fixes released prior to the current service pack have been removed from the hot fix download site. These hot fixes are all contained within the current service pack and will no longer be available for individual download.

Top ^

The SASNote I am reading says there is a 9.1.3 Fix available. I clicked on the link and it takes me to a table that says "SAS 9.1.3 Service Pack * ". What does this mean?

It means that the fix you are looking for is contained in the latest service pack. This can be verified on a fix-by-fix basis by clicking on the Service Pack Fix List link that is included in the service pack download table.

Top ^

Will there still be 9.1.3 hot fixes?

YES. New hot fixes are being developed that can be applied on top of the latest service pack. If you want to apply any new 9.1.3 hot fixes, you MUST install the latest service pack first before installing the new hot fixes.

Top ^

Can I apply new 9.1.3 hot fixes without having the latest SAS 9.1.3 Service Pack on my system?

In most cases, the latest service pack is required for all new 9.1.3 hot fixes. For Foundation software, changes have been made to the hot fix installers to specifically check for the presence of the latest service pack. If the service pack is not found, then the hot fix installers will fail with a clearly stated error message. For mid-tier and client java applications, the hot fix installation will not check for the latest service pack. You should confirm that the latest service pack is installed before applying these hot fixes.

Contact Us | Sitemap | RSS Feeds | www.sas.com | Terms of Use & Legal Information | Privacy Statement

Copyright © 2010 SAS Institute Inc. All Rights Reserved.