If you use the sassetup script to apply a hot fix to SAS 9.2 TS2M0 that was intended for SAS 9.2 TS1M0, segmentation violations are likely to occur afterward when you run SAS programs.

Beginning with SAS 9.2 TS2M0, the correct method for installing hot fixes is via the Maintenance Install Tool, which is included within all downloaded hot fixes. Any hot fix applied to SAS 9.2 TS2M0 using the sassetup script has been applied in error.

   ERROR: Command failed:return_code=50: install/admin/hotfix/script/updt_chksum
   `utilities/bin/patchname sasexe/sas | cut -d= -f2` f9st03

There are two ways to recover from this situation. The first is to re-install SAS 9.2 TS2M0. The other solution is to restore the original files to the SASFoundation/9.2/sasexe directory.

Each hot fix that is applied creates a backup directory similar in name to the following:

The last level of the directory path corresponds to the name of the hot fix. This directory contains files that have names of this form:

   sasexe-sasdsa.06102009.130149

The filename consists of the original directory name ( sasexe), the filename (sasdsa), and a date and time stamp (06102009.130149) that correspond to when the hot fix was applied.

Each file replaced by the hot fix must be restored to its original location. In the example above, the module sasdsa must be moved back to the sasexe directory. This can be done by executing the following commands:

   $ pwd
   SASHOME/SASFoundation/9.2/install/admin/backups/f9ba07
   $ cp sasexe-sasdsa.06102009.130149 
   SASHOME/SASFoundation/9.2/sasexe/sasdsa

Analogous commands must be executed to restore the original version of each file that the hot fix has replaced.

The ability to apply hot fixes is removed from the sassetup script in SAS 9.2 TS2M2.

Operating System and Release Information