Hot fix B3L002 addresses the issue(s) in SAS Forecast Analyst Workbench 5.3_M1 as documented
in the Issue(s) Addressed section of the hot fix download page:
http://ftp.sas.com/techsup/download/hotfix/HF2/B3L.html#B3L002
B3L002 is a "container" hot fix that contains the following "member" hot fixes which will update the software components
as needed.
B3N001 updates SAS Forecast Analyst Workbench Mid-Tier 5.3_M1
B3M002 updates SAS Forecast Analyst Workbench Server 5.3_M1
B4R001 updates SAS Forecast Analyst Workbench Server Configuration 5.3_M1
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, B3L002pt.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 B3L002pt.zip on each machine or save it in a network location that is accessible to all machines.
Do NOT extract the contents of B3L002pt.zip. The hot fix installation process will extract the contents as needed.
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 B3L002pt.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.logfor 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.
For each product installed, click the link to be redirected to post-installation instructions.
B3N001 updates SAS Forecast Analyst Workbench Mid-Tier 5.3_M1
B3M002 updates SAS Forecast Analyst Workbench Server 5.3_M1
B4R001 updates SAS Forecast Analyst Workbench Server Configuration 5.3_M1
B3N001 updates SAS Forecast Analyst Workbench Mid-Tier 5.3_M1
This hot fix requires post-installation steps that will update the web application deployed to your application server.
Follow the steps documented in the rebuild_redeploy_webapp doc to update and deploy the SAS Forecast Analyst Workbench Mid-Tier 5.3 webapp.
B3M002 updates SAS Forecast Analyst Workbench Server 5.3_M1
After you install the hotfix, you must add the following two configuration parameters
to specify the settings for time series disaggregation and the maximum time required to
check the lock of a database table: GL_RUN_DISAGGREGATION_IND and GL_CHECK_LOCK_MAX_TIME.
The GL_RUN_DISAGGREGATION_IND parameter specifies whether you want to disaggregate the predicted values for the time series while diagnosing a forecast. You might want to disaggregate the time series when you are using collaboration planning and product chaining. The value 1 indicates that SAS Forecast Analyst Workbench disaggregates the predicted values for time series. The value 0 indicates that SAS Forecast Analyst Workbench does not disaggregate the predicted values for the time series.
The GL_CHECK_LOCK_MAX_TIME parameter indicates the maximum time a process can check whether a database table is exclusively locked by another process. When a database table is being modified by multiple processes, the first process exclusively locks the database table to update it. The rest of the processes wait for the first process to get completed and to release the lock. The GL_CHECK_LOCK_MAX_TIME parameter specifies the time in milliseconds that the other processes wait to get the lock released. You might want to increase the time that is specified in GL_CHECK_LOCK_MAX_TIME parameter when the stored processes are failed due to locking error.
Perform the following steps to specify the settings for time series disaggregation and database lock:
B4R001 updates SAS Forecast Analyst Workbench Server Configuration 5.3_M1
Import faw_jobs.spk file in order to see the jobs in SAS Data Integration Studio
Perform the following instructions to import the faw_jobs.spk file so that the ETL jobs become available in the SAS Data Integration Studio.
The faw_1201_create_config_tables_for_forecast and faw_1202_create_and_diagnose_forecast jobs are imported.
Execute the following code through the Code Editor of SAS Data Integration Studio. (Ensure that the user,
who runs this macro, is a member of "SAS Administrator" group):
%ddcf_faw53m1_hotfix_migration;Once the code is executed successfully, verify that new parameter 'custom_model_task' is added to config.hpf_preferences and config.hpf_preferences
This completes the installation of hot fix B3L002 on Windows for x64.
Copyright 2017 SAS Institute Inc. All Rights Reserved.