Installation Instructions for Hot Fix E3Y023

64-bit Enabled Solaris


Hot fix E3Y023 addresses the issue(s) in SAS Workload Orchestrator 9.46 as documented in the Issue(s) Addressed section of the hot fix download page:

https://tshf.sas.com/techsup/download/hotfix/HF2/E3Y.html#E3Y023


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

D9W015  updates  SAS Threaded Kernel Grid 9.4_M6
G5Q008  updates  SAS Threaded Kernel Grid 9.4_M7
E5U011  updates  SAS Threaded Kernel Secure 9.4_M6
E3W003  updates  SAS Workload Orchestrator 9.46
E3N004  updates  SAS Workload Orchestrator Threaded Kernel Administration Utility 9.4
E3M015  updates  SAS Workload Orchestrator Threaded Kernel Daemon 9.4

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

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


IMPORTANT NOTES

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

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

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

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

  5. CONFIGURATION: No automatic configuration scripting is included for this hot fix. If you have previously configured software installed, the SAS Deployment Manager may present a screen where you will see "Apply SAS Hot Fixes" and "Configure SAS Hot Fixes" options. On this screen, you must ensure that the "Configure SAS Hot Fix" option is *not* selected. If this option is automatically selected, please de-select it prior to proceeding with the SAS Deployment Manager Screens. Failure to do so could have unintended consequences when applying this hot fix.


INSTALLATION

Hot Fix E3Y023 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 Workload Orchestrator 9.46 require updating on the machine. See SAS Note 44810 for more details.

The hot fix will be applied using the SAS Deployment Manager. By default, the SAS Deployment Manager 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 E3Y023pt.zip, follow the instructions for applying hot fixes in the SAS Deployment Wizard and SAS Deployment Manager 9.4: User's Guide.

Please review the CONFIGURATION Important Note above concerning proper selection of the "Configure SAS Hot Fix" option in the SAS Deployment Manager.


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


The content of this hot fix is listed in the hot fix manifest.


POST-INSTALLATION INSTRUCTIONS

In order to prevent the SAS or command log output from being saved in the SAS Workload Orchestrator job information, and to keep the log
output information from becoming so large that it has a detrimental effect on the performance of SAS Workload Orchestrator (such as hosts
appearing to go inactive when jobs with large log files are run), add the following options to the grid_usermods file:

  1. For a Windows grid, the change goes into
    SAS-configuration-directory\LevX\SAS-Application-Server-name\GridServer\grid_usermods.cfg.cmd

    1. For SAS processing: set SASREDIRSASOPTS=-stdoutcnt number_of_buffers
    2. For command processing: set SASREDIRCMDOPTS=-stdoutcnt number_of_buffers

  2. For a Linux grid, the change goes into
    SAS-configuration-directory/LevX/SAS-Application-Server-name/GridServer/grid_usermods.cfg

    1. For SAS processing: SASREDIRSASOPTS="-stdoutcnt number_of_buffers"
    2. For command processing: SASREDIRCMDOPTS="-stdoutcnt number_of_buffers"
The number_of_buffers value is the number of STDOUT data buffers to dump. Usually, 5-10 buffers limits the output while providing the ability to see any SAS initialization errors.

An additional option can limit the number of lines written to STDOUT. This option is set by modifying 'maxStdOutLines' in the sgmg.cfg file. That file is located in the shared directory for SAS Workload Orchestrator.

  1. For a Windows grid, the change goes into
    SAS-Workload-Orchestrator-shared-directory\sgmg.cfg.

    - Edit the following line to indicate the number of STDERR and STDOUT lines to be used.

    "maxStdOutLines": number_of_stderr_lines_and_stdout_lines, to the section denoted by the first line, "version":1,

    For example:

    "version": 1,
    "maxStdOutLines": 50,

  2. For a Linux grid, the change goes into
    SAS-Workload-Orchestrator-shared-directory/sgmg.cfg.

    - Edit the following line to indicate the number of STDERR and STDOUT lines to be used.

    "maxStdOutLines": number_of_stderr_lines_and_stdout_lines, to the section denoted by the first line, "version":1,

    For example:

    "version": 1,
    "maxStdOutLines": 50,

    3. The number_of_stderr_lines_and_stdout_lines value sets the number of STDERR and STDOUT lines. The value of 50 is suggested to be used initally.


  3. Restart all SAS Workload Orchestrator sgmg daemons on all machines.

Copyright SAS Institute Inc. All Rights Reserved.