SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 63355: An incorrect date (-1 day) is passed when you use a custom-written stored process in SAS® Customer Intelligence Studio

DetailsHotfixAboutRate It

In SAS Customer Intelligence Studio, an incorrect date (-1 day) is passed to the SAS® code for a Process node. This problem happens when you perform steps similar to the following:

  1. Create a custom-written stored process that contains a macro variable for the date value.
  2. In SAS® Management Console, create a prompt that you can use to enter the date value.
  3. In SAS Customer Intelligence Studio, add the stored process to a Process node and enter a date value (for example, August 31, 2018).
  4. Click OK in the Process node.
  5. Re-open the Process node. When you do this, the date value that is shown is one day earlier (minus one): August 30, 2018.

If you update the Process node, the stored process or the pooled workspace-server log shows an earlier (-1) date value, regardless of what time zone is set:

98        +%PUT INFO >> Execution Date is &mExe_dt;
INFO >> Execution Date is 30Oct2018

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.56.69.4 TS1M39.4 TS1M6
Microsoft Windows 8 Enterprise 32-bit6.56.69.4 TS1M39.4 TS1M6
Microsoft Windows 8 Enterprise x646.56.69.4 TS1M39.4 TS1M6
Microsoft Windows 8 Pro 32-bit6.56.69.4 TS1M39.4 TS1M6
Microsoft Windows 8 Pro x646.56.69.4 TS1M39.4 TS1M6
Microsoft Windows 8.1 Enterprise 32-bit6.56.69.4 TS1M39.4 TS1M6
Microsoft Windows 8.1 Enterprise x646.56.69.4 TS1M39.4 TS1M6
Microsoft Windows 8.1 Pro 32-bit6.56.69.4 TS1M39.4 TS1M6
Microsoft Windows 8.1 Pro x646.56.69.4 TS1M39.4 TS1M6
Microsoft Windows 106.56.69.4 TS1M39.4 TS1M6
Microsoft Windows Server 20086.56.69.4 TS1M39.4 TS1M6
Microsoft Windows Server 2008 R26.56.69.4 TS1M39.4 TS1M6
Microsoft Windows Server 2008 for x646.56.69.4 TS1M39.4 TS1M6
Microsoft Windows Server 2012 Datacenter6.56.69.4 TS1M39.4 TS1M6
Microsoft Windows Server 2012 R2 Datacenter6.56.69.4 TS1M39.4 TS1M6
Microsoft Windows Server 2012 R2 Std6.56.69.4 TS1M39.4 TS1M6
Microsoft Windows Server 2012 Std6.56.69.4 TS1M39.4 TS1M6
Windows 7 Enterprise 32 bit6.56.69.4 TS1M39.4 TS1M6
Windows 7 Enterprise x646.56.69.4 TS1M39.4 TS1M6
Windows 7 Home Premium 32 bit6.56.69.4 TS1M39.4 TS1M6
Windows 7 Home Premium x646.56.69.4 TS1M39.4 TS1M6
Windows 7 Professional 32 bit6.56.69.4 TS1M39.4 TS1M6
Windows 7 Professional x646.56.69.4 TS1M39.4 TS1M6
Windows 7 Ultimate 32 bit6.56.69.4 TS1M39.4 TS1M6
Windows 7 Ultimate x646.56.69.4 TS1M39.4 TS1M6
64-bit Enabled AIX6.56.69.4 TS1M39.4 TS1M6
64-bit Enabled Solaris6.56.69.4 TS1M39.4 TS1M6
HP-UX IPF6.56.69.4 TS1M39.4 TS1M6
Linux for x646.56.69.4 TS1M39.4 TS1M6
Solaris for x646.56.69.4 TS1M39.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.