SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 60227: An incorrect command is generated when you add a campaign to a SAS® Customer Intelligence campaign group

DetailsHotfixAboutRate It

When you add a campaign to an existing SAS Customer Intelligence campaign group, the Launcher (malauncher.exe) utility command is generated with the –p option instead of the –g option. This behavior occurs when you perform steps similar to the following:

  1. Create two campaigns (for example,  CAMP_1 and CAMP_2).
  2. Create a campaign group (for example, GROUP_1).
  3. Add only CAMP_1 to the GROUP_1 campaign group.
  4. Generate optimization data and create an optimization scenario (analytical or priority-based), optimize the scenario, and assign the scenario as the preferred scenario.
  5. On the Schedule tab, set a schedule for optimization (not for the campaign). The schedule details are not important.
  6. On the Execution tab, select Optimization Schedule and click Send schedule. In the dialog box that is displayed, select Send the schedule to administrator.
  7. Next, add CAMP_2 to the campaign group.
  8. On the Schedule tab, you should see that CAMP_2 is marked with a yellow triangle. Select Edit Schedule, and then select CAMP_2, and set schedule type to Offset to optimization schedule.
  9. On the Execution tab, select CAMP_2 and click Send schedule. In the dialog box that is displayed, select Send the schedule to administrator

If you then open the Schedule Manager plug-in in SAS® Management Console, you will see that the second command for CAMP_2 uses the –p option rather than the –g option, as shown below:

CAMP_1 - "SAS-configuration-directory/LevN/SASApp/MaLauncher/mabatch.sh" -u "user-ID" -g 2222222222222222222222222 -x "business-context" -d camp -e -v --FGFHZKU2FVG5TIXZ
CAMP_2 - "SAS-configuration-directory/LevN/SASApp/MaLauncher/mabatch.sh" -u "user-ID" -p {sasenc}11111111111111111 -x "business-context" -d camp -e -v -- GEBHDDURXBANQRJK

As a workaround, click Remove Schedule before you add the second campaign.

Click the Hot Fix tab in this note to access the hot fix for this issue.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Customer Intelligence StudioMicrosoft® Windows® for x646.36.69.4 TS1M6
Microsoft Windows 8 Enterprise 32-bit6.36.69.4 TS1M6
Microsoft Windows 8 Enterprise x646.36.69.4 TS1M6
Microsoft Windows 8 Pro 32-bit6.36.69.4 TS1M6
Microsoft Windows 8 Pro x646.36.69.4 TS1M6
Microsoft Windows 8.1 Enterprise 32-bit6.36.69.4 TS1M6
Microsoft Windows 8.1 Enterprise x646.36.69.4 TS1M6
Microsoft Windows 8.1 Pro 32-bit6.36.69.4 TS1M6
Microsoft Windows 8.1 Pro x646.36.69.4 TS1M6
Microsoft Windows 106.36.69.4 TS1M6
Microsoft Windows Server 20086.36.69.4 TS1M6
Microsoft Windows Server 2008 R26.36.69.4 TS1M6
Microsoft Windows Server 2008 for x646.36.69.4 TS1M6
Microsoft Windows Server 2012 Datacenter6.36.69.4 TS1M6
Microsoft Windows Server 2012 R2 Datacenter6.36.69.4 TS1M6
Microsoft Windows Server 2012 R2 Std6.36.69.4 TS1M6
Microsoft Windows Server 2012 Std6.36.69.4 TS1M6
Windows 7 Enterprise 32 bit6.36.69.4 TS1M6
Windows 7 Enterprise x646.36.69.4 TS1M6
Windows 7 Home Premium 32 bit6.36.69.4 TS1M6
Windows 7 Home Premium x646.36.69.4 TS1M6
Windows 7 Professional 32 bit6.36.69.4 TS1M6
Windows 7 Professional x646.36.69.4 TS1M6
Windows 7 Ultimate 32 bit6.36.69.4 TS1M6
Windows 7 Ultimate x646.36.69.4 TS1M6
64-bit Enabled AIX6.36.69.4 TS1M6
64-bit Enabled Solaris6.36.69.4 TS1M6
HP-UX IPF6.36.69.4 TS1M6
Linux for x646.36.69.4 TS1M6
Solaris for x646.36.69.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.