Problem Note 61609: You cannot split the input data and optimization process into two separate processes when you execute the task from the Launcher application
Currently, you cannot split the input data generation and the optimization process for the Marketing Optimization/Marketing Automation (MOMA) campaign group into two separate commands when you execute those tasks from the Launcher (malauncher) application.
This functionality is contrary to the functionality that is available when you execute those tasks in SAS® Customer Intelligence Studio. In SAS Customer Intelligence Studio, you can suppress the generation of input data for the MOMA campaign group when you optimize the group, as shown below:
Click the Hot Fix tab in this note to access the hot fix for this issue.
After you apply the hot fix, new MOMA capabilities are available for the Launcher application. You can schedule campaign groups with the following new optimize qualifier arguments:
- genOnly - This argument generates MOMA input-data tables only, without running the optimization. This argument appears at the end of the malauncher command, as shown in this example:
SAS-configuration-directory\Lev1\SASApp\MaLauncher\mabatch.bat" -u "sasdemo" –p {password} -x "MAMap" -d campaigngroup -e -v --FGAAH0WWFJAAQ1A4 optimize genOnly
- noRegen - This argument runs an optimization using the previously generated MOMA input-data tables. This argument also appears at the end of the malauncher command, as shown in this example:
SAS-configuration-directory\Lev1\SASApp\MaLauncher\mabatch.bat" -u "sasdemo" –p {password} -x "MAMap" -d campaigngroup -e -v --FGAAH0WWFJAAQ1A4 optimize noRegen
Without the trailing qualifier arguments genOnly or noRegen, the MOMA tables are regenerated and optimized in one process, as is done before you apply the hot fix.
Operating System and Release Information
SAS System | SAS Customer Intelligence Studio | Microsoft Windows 10 | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows 8.1 Pro x64 | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows 8.1 Pro 32-bit | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows 8.1 Enterprise x64 | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows 8.1 Enterprise 32-bit | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows 8 Pro x64 | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows 8 Pro 32-bit | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows 8 Enterprise x64 | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows 8 Enterprise 32-bit | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft® Windows® for x64 | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows Server 2008 | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows Server 2008 R2 | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows Server 2008 for x64 | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows Server 2012 Datacenter | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows Server 2012 R2 Datacenter | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows Server 2012 R2 Std | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows Server 2012 Std | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows Server 2016 | 6.5 | 6.6 | | 9.4 TS1M6 |
Microsoft Windows Server 2019 | 6.5 | 6.6 | | 9.4 TS1M6 |
Windows 7 Enterprise 32 bit | 6.5 | 6.6 | | 9.4 TS1M6 |
Windows 7 Enterprise x64 | 6.5 | 6.6 | | 9.4 TS1M6 |
Windows 7 Home Premium 32 bit | 6.5 | 6.6 | | 9.4 TS1M6 |
Windows 7 Home Premium x64 | 6.5 | 6.6 | | 9.4 TS1M6 |
Windows 7 Professional 32 bit | 6.5 | 6.6 | | 9.4 TS1M6 |
Windows 7 Professional x64 | 6.5 | 6.6 | | 9.4 TS1M6 |
Windows 7 Ultimate 32 bit | 6.5 | 6.6 | | 9.4 TS1M6 |
Windows 7 Ultimate x64 | 6.5 | 6.6 | | 9.4 TS1M6 |
64-bit Enabled AIX | 6.5 | 6.6 | | 9.4 TS1M6 |
64-bit Enabled Solaris | 6.5 | 6.6 | | 9.4 TS1M6 |
HP-UX IPF | 6.5 | 6.6 | | 9.4 TS1M6 |
Linux for x64 | 6.5 | 6.6 | | 9.4 TS1M6 |
Solaris for x64 | 6.5 | 6.6 | | 9.4 TS1M6 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | medium |
Date Modified: | 2018-02-21 16:58:34 |
Date Created: | 2017-12-20 09:22:35 |