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, S63001pt.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
S63001pt.zip on each machine or save it in a network location that is accessible to all machines.

Do NOT extract the contents of S63001pt.zip. The hot fix installation process will extract the contents
as needed.

IMPORTANT NOTES

Files delivered in this hot fix will be backed up during the installation process.
However, it is good general practice to back up your system before applying updates
to software.

You must have Administrator Privileges on your CLIENT or SERVER machine.

All currently active SAS sessions, daemons, spawners and servers must be terminated
before applying this hot fix.

This hot fix should be installed using the same userid who performed the initial
software installation.

INSTALLATION

Hot Fix S63001 must be installed on each machine where the updated components of the product, listed above, are installed.
During the installation process you may see references to all operating systems for which updates
are provided in the hot fix. The installation process will determine the operating system and which
component(s) of SAS Compliance Solutions 6.2_M1 require updating on the machine. See
SAS Note 44810 for more details.

The hot fix will be applied using the SAS Deployment Manager (SDM). By default, the SDM 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.

for 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).

Important Note:
For ease of completion of post-installation tasks, you can export the following:

SASHOME=/install/SASHome This should be the path that SAS was installed to.
SASCONFIG=/install/config/Lev1 This should be the path that SAS was deployed/configured to.
FCFMIDROOT=$SASCONFIG/Web/Applications/SASComplianceSolutions6.2

Copy the following files from $SASHOME/SASComplianceSolutionsMidTier/6.2 to $FCFMIDROOT/install/uidef, removing the ‘.orig’ extension:

The post-installation instructions below assume the following references to installation paths:

SASHOME=/install/SASHome This should be the path that SAS was installed to.
SASCONFIG=/install/config/Lev1 This should be the path that SAS was deployed/configured to.
FCFROOT=$SASCONFIG/Applications/SASComplianceSolutions6.2

Copy the following file from $SASHOME/SASFoundation/9.4 to $FCFROOT/custom/config:

antimnycmn/sasmisc/deploy/fcf_autoexec.sas

Make the following token substitutions in the file above. You should merge it with a backup of your previous fcf_autoexec.sas, because
there are a lot of settings that need to be the same as before. Be sure to fully expand any environment variables like SASHOME and SASCONFIG: