Installation instructions for hot fix F84001 on Windows

Installation Instructions for Hot Fix F84001

Windows

Hot fix F84001 addresses the issue(s) in SAS Clinical Data Integration 2.3 as documented in the Issue(s) Addressed section of the hot fix download page:

https://tshf.sas.com/techsup/download/hotfix/HF2/F84.html#F84001

F84001 is a "container" hot fix that contains the following "member" hot fixes which will update the software components as indicated.

F86001 updates SAS Clinical Data Integration Client 2.3
F85001 updates SAS Integration Adapter for Medidata Rave Client 2.3

See What is a container hot fix? in the Hot Fix FAQ for more information about container hot fixes.

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

Do NOT extract the contents of F84001wn.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 F84001 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 Clinical Data Integration 2.3 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.

After downloading F84001wn.zip, follow the instructions provided in the SAS Deployment Wizard/SAS Deployment Manager 9.3: User's Guide; see the Apply Hot Fixes section in Chapter 5 -- SAS Deployment Manager Tasks to complete the installation of the hot fix.

The hot fix installation process generates the log file

<!SASHOME>\InstallMisc\InstallLogs\IT_date-and-time-stamp.log

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

POST-INSTALLATION INSTRUCTIONS

For each product installed, click the link to be redirected to post-installation instructions.

F86001 updates SAS Clinical Data Integration Client 2.3
F85001 updates SAS Integration Adapter for Medidata Rave Client 2.3

F86001 updates SAS Clinical Data Integration Client 2.3

If you have Clinical Data Integration Studio jobs containing CDISC-SDTM Compliance and/or CDISC-SDTM to CRT-DDS transformations, and these jobs are impacted by the problem detailed in SAS Note 44385:

For each affected job, you will need to regenerate the source code:

If you have manually edited the generated code in the DI Studio job or transformation Code tab, reset the 'Code Generation Mode' setting to 'Automatic' to generate the correct SAS source code for the transformation(s),
If you have deployed the job(s) for scheduling, redeploy them by selecting Tools > Redeploy for Scheduling in the DI Studio menu bar. The DI Studio inline Help offers additional details on how to redeploy jobs for scheduling.
If you have otherwise previously deployed the source code to another environment, you will need to redeploy the re-generated job source code to that environment.

F85001 updates SAS Integration Adapter for Medidata Rave Client 2.3

If you have Clinical Data Integration Studio jobs containing Extract Medidata Rave� Data and/or Update from Medidata Rave� Data transformations, and these jobs are impacted by the problem detailed in SAS Note 44975 or 44382:

For each affected job, you will need to regenerate the source code:

If you have manually edited the generated code in the DI Studio job or transformation Code tab, reset the 'Code Generation Mode' setting to 'Automatic' to generate the correct SAS source code for the transformation(s),
If you have deployed the job(s) for scheduling, redeploy them by selecting Tools > Redeploy for Scheduling in the DI Studio menu bar. The DI Studio inline Help offers additional details on how to redeploy jobs for scheduling.
If you have otherwise previously deployed the source code to another environment, you will need to redeploy the re-generated job source code to that environment.

This completes the installation of hot fix F84001 on Windows.