SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 64606: File events for Platform Process Manager flows are not mapped correctly after you import a SAS® package file

DetailsHotfixAboutRate It

When you import a SAS package file that contains a flow that uses file events, the file mappings might swap with each other. The flow then does not run as expected.

This behavior has been observed when both of the following are true:

  • The flow has one or more file triggers.
  • The flow contains jobs or subflows that have one or more file dependencies.

The workaround is to edit the flow, update the file dependencies, and reschedule the flow with the corrected flow trigger file.

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

After the hot fix is installed, re-export the flow from the source system and import it into the target system. However, if your source system is an earlier maintenance release than SAS® 9.4M6 (TS1M6), contact SAS Technical Support. Provide the following information:

  • This SAS Note number (64606)
  • A SAS Deployment Registry report, as discussed in SAS KB0036131, "Using the ViewRegistry Report and other methods to determine the software releases and hot fixes that are installed."


Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Management ConsoleMicrosoft® Windows® for x649.4_M59.4 TS1M5
Microsoft Windows 8 Enterprise 32-bit9.4_M59.4 TS1M5
Microsoft Windows 8 Enterprise x649.4_M59.4 TS1M5
Microsoft Windows 8 Pro 32-bit9.4_M59.4 TS1M5
Microsoft Windows 8 Pro x649.4_M59.4 TS1M5
Microsoft Windows 8.1 Enterprise 32-bit9.4_M59.4 TS1M5
Microsoft Windows 8.1 Enterprise x649.4_M59.4 TS1M5
Microsoft Windows 8.1 Pro 32-bit9.4_M59.4 TS1M5
Microsoft Windows 8.1 Pro x649.4_M59.4 TS1M5
Microsoft Windows 109.4_M59.4 TS1M5
Microsoft Windows Server 20089.4_M59.4 TS1M5
Microsoft Windows Server 2008 R29.4_M59.4 TS1M5
Microsoft Windows Server 2008 for x649.4_M59.4 TS1M5
Microsoft Windows Server 2012 Datacenter9.4_M59.4 TS1M5
Microsoft Windows Server 2012 R2 Datacenter9.4_M59.4 TS1M5
Microsoft Windows Server 2012 R2 Std9.4_M59.4 TS1M5
Microsoft Windows Server 2012 Std9.4_M59.4 TS1M5
Microsoft Windows Server 20169.4_M59.4 TS1M5
Windows 7 Enterprise 32 bit9.4_M59.4 TS1M5
Windows 7 Enterprise x649.4_M59.4 TS1M5
Windows 7 Home Premium 32 bit9.4_M59.4 TS1M5
Windows 7 Home Premium x649.4_M59.4 TS1M5
Windows 7 Professional 32 bit9.4_M59.4 TS1M5
Windows 7 Professional x649.4_M59.4 TS1M5
Windows 7 Ultimate 32 bit9.4_M59.4 TS1M5
Windows 7 Ultimate x649.4_M59.4 TS1M5
64-bit Enabled AIX9.4_M59.4 TS1M5
64-bit Enabled Solaris9.4_M59.4 TS1M5
HP-UX IPF9.4_M59.4 TS1M5
Linux for x649.4_M59.4 TS1M5
Solaris for x649.4_M59.4 TS1M5
* 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.