Problem Note 64733: The SAS® Marketing Optimization sasmolauncher script returns an incorrect return code of 0 even before the data is completely refreshed
 |  |  |  |  |
When you execute SAS Marketing Optimization in batch mode using the sasmolauncher script, an incorrect code of 0 is returned. This incorrect code is displayed in the sasmolauncher.log file even before the data is completely refreshed.
This problem happens when you run the following command with the refresh option:
sasmolauncher.exe -w http://your-machine-name/SASWIPClientAccess/remote/ServiceRegistry -u sasdemo -p your-password -t refresh -i 111 -l en_US
The sasmolauncher.log file shows the following message with the incorrect return code:
02 Sep 2019 09:19:43,479 INFO LauncherApp : starting mo launcher
02 Sep 2019 09:19:43,481 DEBUG OptionUtil : parsing command line arguments
02 Sep 2019 09:19:43,481 DEBUG OptionUtil : mo launcher arguments:
02 Sep 2019 09:19:43,481 INFO OptionUtil : -t refresh
02 Sep 2019 09:19:43,481 INFO OptionUtil : -p ?????
02 Sep 2019 09:19:43,481 INFO OptionUtil : -l en_US
02 Sep 2019 09:19:43,481 INFO OptionUtil : -i 111
02 Sep 2019 09:19:43,481 INFO OptionUtil : -u sasdemo
02 Sep 2019 09:19:43,481 INFO OptionUtil : -w http://<your-machine-name>/SASWIPClientAccess/remote/ServiceRegistry
02 Sep 2019 09:19:43,488 DEBUG MORequestProcessor : processing job request
02 Sep 2019 09:19:49,776 DEBUG MORequestProcessor : Logged in as sasdemo sessionid == 1ec9fd05-6a2c-44b1-aee1-3cd2c5cc863b
02 Sep 2019 09:21:58,002 DEBUG MORequestProcessor : sasdemo closing the user session associated with the scheduled job
02 Sep 2019 09:21:58,106 INFO LauncherApp : Launcher complete...0
02 Sep 2019 09:19:43,481 DEBUG OptionUtil : parsing command line arguments
02 Sep 2019 09:19:43,481 DEBUG OptionUtil : mo launcher arguments:
02 Sep 2019 09:19:43,481 INFO OptionUtil : -t refresh
02 Sep 2019 09:19:43,481 INFO OptionUtil : -p ?????
02 Sep 2019 09:19:43,481 INFO OptionUtil : -l en_US
02 Sep 2019 09:19:43,481 INFO OptionUtil : -i 111
02 Sep 2019 09:19:43,481 INFO OptionUtil : -u sasdemo
02 Sep 2019 09:19:43,481 INFO OptionUtil : -w http://<your-machine-name>/SASWIPClientAccess/remote/ServiceRegistry
02 Sep 2019 09:19:43,488 DEBUG MORequestProcessor : processing job request
02 Sep 2019 09:19:49,776 DEBUG MORequestProcessor : Logged in as sasdemo sessionid == 1ec9fd05-6a2c-44b1-aee1-3cd2c5cc863b
02 Sep 2019 09:21:58,002 DEBUG MORequestProcessor : sasdemo closing the user session associated with the scheduled job
02 Sep 2019 09:21:58,106 INFO LauncherApp : Launcher complete...0
If the refresh job is not complete before the code is returned, executing a second sasmolauncher command with the optimize option causes the execution to stop responding, as shown below:
02 Sep 2019 09:36:20,150 INFO LauncherApp : starting mo launcher
02 Sep 2019 09:36:20,152 DEBUG OptionUtil : parsing command line arguments
02 Sep 2019 09:36:20,152 DEBUG OptionUtil : mo launcher arguments:
02 Sep 2019 09:36:20,152 INFO OptionUtil : -t optimize
02 Sep 2019 09:36:20,152 INFO OptionUtil : -p ?????
02 Sep 2019 09:36:20,152 INFO OptionUtil : -l en_US
02 Sep 2019 09:36:20,152 INFO OptionUtil : -i 264
02 Sep 2019 09:36:20,152 INFO OptionUtil : -u sasdemo
02 Sep 2019 09:36:20,152 INFO OptionUtil : -w http://<your-machine-name>/SASWIPClientAccess/remote/ServiceRegistry
02 Sep 2019 09:36:20,159 DEBUG MORequestProcessor : processing job request
02 Sep 2019 09:36:24,214 DEBUG MORequestProcessor : Logged in as sasdemo sessionid == 073f6671-9e61-448a-a201-5ae6e8124a49
02 Sep 2019 09:36:20,152 DEBUG OptionUtil : parsing command line arguments
02 Sep 2019 09:36:20,152 DEBUG OptionUtil : mo launcher arguments:
02 Sep 2019 09:36:20,152 INFO OptionUtil : -t optimize
02 Sep 2019 09:36:20,152 INFO OptionUtil : -p ?????
02 Sep 2019 09:36:20,152 INFO OptionUtil : -l en_US
02 Sep 2019 09:36:20,152 INFO OptionUtil : -i 264
02 Sep 2019 09:36:20,152 INFO OptionUtil : -u sasdemo
02 Sep 2019 09:36:20,152 INFO OptionUtil : -w http://<your-machine-name>/SASWIPClientAccess/remote/ServiceRegistry
02 Sep 2019 09:36:20,159 DEBUG MORequestProcessor : processing job request
02 Sep 2019 09:36:24,214 DEBUG MORequestProcessor : Logged in as sasdemo sessionid == 073f6671-9e61-448a-a201-5ae6e8124a49
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | SAS Marketing Optimization | Microsoft® Windows® for x64 | 6.5 | 9.4 TS1M3 | ||
| 64-bit Enabled AIX | 6.5 | 9.4 TS1M3 | ||||
| 64-bit Enabled Solaris | 6.5 | 9.4 TS1M3 | ||||
| HP-UX IPF | 6.5 | 9.4 TS1M3 | ||||
| Linux for x64 | 6.5 | 9.4 TS1M3 | ||||
| Solaris for x64 | 6.5 | 9.4 TS1M3 | ||||
A fix for this issue for SAS Marketing Optimization 6.5 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/Z82.html#64733| Type: | Problem Note |
| Priority: | medium |
| Date Modified: | 2019-09-11 08:24:37 |
| Date Created: | 2019-09-05 06:20:06 |