To install the patch [UNIX]: 1. Change directory to the root directory of the Federation Server installation. This is the directory named 'fedserver' created during installation. For example, if you installed the server in /opt/dataflux, run this command: cd /opt/dataflux/fedserver 2. Stop the server if it is running. Run the command: ./bin/dfsadmin stop 3. (AIX only) Run this command: ./bin/uncache_libs or ask your sysadmin to run the slibclean command on the system. 4. Run this command: gzip -d -c PATH_TO/fedserver-fix19645-PLATFORM.tar.gz | tar xvf - replacing PATH_TO with the correct path to the patch file and PLATFORM with the platform name (linux, sol64, etc.). 5. If you stopped the Server in step one, restart it. Run the command: ./bin/dfsadmin start The following files will be installed or updated by this patch: [lin64] lib/tkeds.so lib/tkesqlc.so lib/tkesqlo.so To install the patch [Windows]: 1. If you have multiple instances of the server installed on the machine, determine the name of the server instance you will be patching. This was chosen during the initial installation, and defaults to 'server1'. 2. Stop the DataFlux Federation Server service for the instance if it is running. You can check the status of the service using the Services applet on the Windows Control Panel (may be found under Administrative Tools). The instance name is included in the display name in the applet, for example: DataFlux Federation Server (server1) 3. Unzip the archive fedserver-fix19645-win32.zip (32-bit DFS) or fedserver-fix19645-win64.zip (64-bit DFS) into the root directory of your Federation Server instance. This is typically: C:\Program Files\DataFlux\FedServer\server1 If the instance name is not 'server1' or you installed to a different location, adjust the path accordingly. 4. If you stopped the Federation Server service in step one, restart it. The following files will be installed or updated by this patch: [win] tkeds.dll tkesqlc.dll tkesqlo.dll Additional Notes: An environment variable has been added to enable Federation Server 3.1 to either run in SAS mode or in ANSI mode. However, if a DS2 package has been published with 'ds2_options sas' within the proc ds2 code, the 'ds2_options sas' takes precedence over the environment variable setting. If a DS2 package is published without 'ds2_options sas' setting, the Federation Server uses the environment variable to determine whether to run in SAS mode or ANSI mode. When the Federation Server runs in SAS mode, JAVA NULLs are converted to SAS missing values. To add the environment variable functionality, modify dfs_serv.xml to include the OptionSet defined below. The default and recommended value is TRUE. The dfs_serv.xml file is located in the etc directory of the Federation Server installation. Add the following OptionSet to dfs_serv.xml: Add an appender to dfs_log.xml if you require additional logging information. The dfs_log.xml file is located in the etc directory of the Federation Server installation. Add the following code to dfs_log.xml, substituting the full path to the Federation Server installation for PATH_TO_INSTALL: Verify that the file dfs_serv.log is created in the var/log directory of the Federation Server installation and the log displays the current value for the mode setting (ANSI vs SAS) that is being used by the Federation Server.