Problem Note 61007: An incorrect time is published when you use a custom-written stored process in SAS® Customer Intelligence Studio
In SAS Customer Intelligence Studio, an incorrect time (+ 4 hours) is published to the SAS® Customer Intelligence Common Data Model. This problem happens when you perform steps similar to the following:
- Create a custom-written stored process that contains a macro variable for the time value.
- In SAS® Management Console, create a prompt that you can use to enter the time value.
- In SAS Customer Intelligence Studio, add the stored process to a Process node and enter a time value (for example, August 21, 2017 08:00:00 AM).
- Update the Process node.
When you complete these steps, the stored process or the pooled workspace server log shows a time shift of +4 hours, regardless what time zone is set:
2017-08-22T10:02:04,842 INFO [00003754] 6:sasdemo@SASBAP - Physical Name:
\Config\Lev1\Applications\SASCustomerIntelligence\CampaignManagement\Data\MATables
2017-08-22T10:02:04,842 INFO [00003754] 6:sasdemo@SASBAP - MPRINT(MASPINIT): ;
2017-08-22T10:02:04,842 INFO [00003754] 6:sasdemo@SASBAP - 5 +
2017-08-22T10:02:04,842 INFO [00003754] 6:sasdemo@SASBAP - 7 +%let E_ST_DT=&E_ST_DT;
2017-08-22T10:02:04,842 INFO [00003754] 6:sasdemo@SASBAP - 8 +
2017-08-22T10:02:04,842 INFO [00003754] 6:sasdemo@SASBAP - 10 +%put &E_ST_DT;
2017-08-22T10:02:04,842 INFO [00003754] 6:sasdemo@SASBAP - 21Aug2017 12:00:00
There is currently no workaround other than adjusting the time to -4 hours.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Customer Intelligence Studio | Microsoft® Windows® for x64 | 6.4 | 6.6 | 9.4 TS1M2 | 9.4 TS1M6 |
Microsoft Windows 8 Enterprise 32-bit | 6.4 | 6.6 | 9.4 TS1M2 | 9.4 TS1M6 |
Microsoft Windows 8 Enterprise x64 | 6.4 | 6.6 | 9.4 TS1M2 | 9.4 TS1M6 |
Microsoft Windows 8 Pro 32-bit | 6.4 | 6.6 | 9.4 TS1M2 | 9.4 TS1M6 |
Microsoft Windows 8 Pro x64 | 6.4 | 6.6 | 9.4 TS1M2 | 9.4 TS1M6 |
Microsoft Windows 8.1 Enterprise 32-bit | 6.4 | 6.6 | 9.4 TS1M2 | 9.4 TS1M6 |
Microsoft Windows 8.1 Enterprise x64 | 6.4 | 6.6 | 9.4 TS1M2 | 9.4 TS1M6 |
Microsoft Windows 8.1 Pro 32-bit | 6.4 | 6.6 | 9.4 TS1M2 | 9.4 TS1M6 |
Microsoft Windows 8.1 Pro x64 | 6.4 | 6.6 | 9.4 TS1M2 | 9.4 TS1M6 |
Microsoft Windows 10 | 6.4 | 6.6 | 9.4 TS1M2 | 9.4 TS1M6 |
Microsoft Windows Server 2008 | 6.4 | 6.6 | 9.4 TS1M2 | 9.4 TS1M6 |
Microsoft Windows Server 2008 R2 | 6.4 | 6.6 | 9.4 TS1M2 | 9.4 TS1M6 |
Microsoft Windows Server 2008 for x64 | 6.4 | 6.6 | 9.4 TS1M2 | 9.4 TS1M6 |
Microsoft Windows Server 2012 Datacenter | 6.4 | 6.6 | 9.4 TS1M2 | 9.4 TS1M6 |
Microsoft Windows Server 2012 R2 Datacenter | 6.4 | 6.6 | 9.4 TS1M2 | 9.4 TS1M6 |
Microsoft Windows Server 2012 R2 Std | 6.4 | 6.6 | 9.4 TS1M2 | 9.4 TS1M6 |
Microsoft Windows Server 2012 Std | 6.4 | 6.6 | 9.4 TS1M2 | 9.4 TS1M6 |
Windows 7 Enterprise 32 bit | 6.4 | 6.6 | 9.4 TS1M2 | 9.4 TS1M6 |
Windows 7 Enterprise x64 | 6.4 | 6.6 | 9.4 TS1M2 | 9.4 TS1M6 |
Windows 7 Home Premium 32 bit | 6.4 | 6.6 | 9.4 TS1M2 | 9.4 TS1M6 |
Windows 7 Home Premium x64 | 6.4 | 6.6 | 9.4 TS1M2 | 9.4 TS1M6 |
Windows 7 Professional 32 bit | 6.4 | 6.6 | 9.4 TS1M2 | 9.4 TS1M6 |
Windows 7 Professional x64 | 6.4 | 6.6 | 9.4 TS1M2 | 9.4 TS1M6 |
Windows 7 Ultimate 32 bit | 6.4 | 6.6 | 9.4 TS1M2 | 9.4 TS1M6 |
Windows 7 Ultimate x64 | 6.4 | 6.6 | 9.4 TS1M2 | 9.4 TS1M6 |
64-bit Enabled AIX | 6.4 | 6.6 | 9.4 TS1M2 | 9.4 TS1M6 |
64-bit Enabled Solaris | 6.4 | 6.6 | 9.4 TS1M2 | 9.4 TS1M6 |
HP-UX IPF | 6.4 | 6.6 | 9.4 TS1M2 | 9.4 TS1M6 |
Linux for x64 | 6.4 | 6.6 | 9.4 TS1M2 | 9.4 TS1M6 |
Solaris for x64 | 6.4 | 6.6 | 9.4 TS1M2 | 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: | high |
Date Modified: | 2017-12-08 15:45:13 |
Date Created: | 2017-09-01 06:55:21 |