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 Family	Product	System	Product Release		SAS Release
			Reported	Fixed*	Reported	Fixed*
SAS System	SAS Management Console	Microsoft® Windows® for x64	9.4_M5		9.4 TS1M5
		Microsoft Windows 8 Enterprise 32-bit	9.4_M5		9.4 TS1M5
		Microsoft Windows 8 Enterprise x64	9.4_M5		9.4 TS1M5
		Microsoft Windows 8 Pro 32-bit	9.4_M5		9.4 TS1M5
		Microsoft Windows 8 Pro x64	9.4_M5		9.4 TS1M5
		Microsoft Windows 8.1 Enterprise 32-bit	9.4_M5		9.4 TS1M5
		Microsoft Windows 8.1 Enterprise x64	9.4_M5		9.4 TS1M5
		Microsoft Windows 8.1 Pro 32-bit	9.4_M5		9.4 TS1M5
		Microsoft Windows 8.1 Pro x64	9.4_M5		9.4 TS1M5
		Microsoft Windows 10	9.4_M5		9.4 TS1M5
		Microsoft Windows Server 2008	9.4_M5		9.4 TS1M5
		Microsoft Windows Server 2008 R2	9.4_M5		9.4 TS1M5
		Microsoft Windows Server 2008 for x64	9.4_M5		9.4 TS1M5
		Microsoft Windows Server 2012 Datacenter	9.4_M5		9.4 TS1M5
		Microsoft Windows Server 2012 R2 Datacenter	9.4_M5		9.4 TS1M5
		Microsoft Windows Server 2012 R2 Std	9.4_M5		9.4 TS1M5
		Microsoft Windows Server 2012 Std	9.4_M5		9.4 TS1M5
		Microsoft Windows Server 2016	9.4_M5		9.4 TS1M5
		Windows 7 Enterprise 32 bit	9.4_M5		9.4 TS1M5
		Windows 7 Enterprise x64	9.4_M5		9.4 TS1M5
		Windows 7 Home Premium 32 bit	9.4_M5		9.4 TS1M5
		Windows 7 Home Premium x64	9.4_M5		9.4 TS1M5
		Windows 7 Professional 32 bit	9.4_M5		9.4 TS1M5
		Windows 7 Professional x64	9.4_M5		9.4 TS1M5
		Windows 7 Ultimate 32 bit	9.4_M5		9.4 TS1M5
		Windows 7 Ultimate x64	9.4_M5		9.4 TS1M5
		64-bit Enabled AIX	9.4_M5		9.4 TS1M5
		64-bit Enabled Solaris	9.4_M5		9.4 TS1M5
		HP-UX IPF	9.4_M5		9.4 TS1M5
		Linux for x64	9.4_M5		9.4 TS1M5
		Solaris for x64	9.4_M5		9.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.

---

A fix for this issue for SAS Management Console 9.4_M6 is available at:

https://tshf.sas.com/techsup/download/hotfix/HF2/D8N.html#64606

---

A fix for this issue for SAS Middle Tier 9.4_M6 is available at:

https://tshf.sas.com/techsup/download/hotfix/HF2/D8T.html#64606

---

A fix for this issue for Data Integration Studio 4.904 is available at:

https://tshf.sas.com/techsup/download/hotfix/HF2/D8Y.html#64606

---

When you import a SAS package file with a flow that has both a file trigger event for the flow, and file dependencies within the flow, the file events might not map correctly.

Type:	Problem Note
Priority:	high
Topic:	System Administration ==> Scheduling

Date Modified:	2019-09-09 10:39:25
Date Created:	2019-08-13 10:08:12