Job and information map objects associated with tables that are not unique by name, but reside in different libraries, might not import and link properly because the search mechanism does not make a disinction between the different tables. This could result in jobs or maps with the wrong tables connected to them.

Select 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 Data Integration Studio	Microsoft Windows 2000 Advanced Server	3.4	4.2	9.1 TS1M3 SP4	9.2 TS1M0
		Microsoft Windows 2000 Datacenter Server	3.4	4.2	9.1 TS1M3 SP4	9.2 TS1M0
		Microsoft Windows 2000 Server	3.4	4.2	9.1 TS1M3 SP4	9.2 TS1M0
		Microsoft Windows 2000 Professional	3.4	4.2	9.1 TS1M3 SP4	9.2 TS1M0
		Microsoft Windows Server 2003 Datacenter Edition	3.4	4.2	9.1 TS1M3 SP4	9.2 TS1M0
		Microsoft Windows Server 2003 Enterprise Edition	3.4	4.2	9.1 TS1M3 SP4	9.2 TS1M0
		Microsoft Windows Server 2003 Standard Edition	3.4	4.2	9.1 TS1M3 SP4	9.2 TS1M0
		Microsoft Windows XP Professional	3.4	4.2	9.1 TS1M3 SP4	9.2 TS1M0

* 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 Data Integration Studio 3.4 is available at:

http://www.sas.com/techsup/download/hotfix/dis34.html#030515

---

If a package file contains a job with dependent table objects that are not unique by name, but are associated to different distinct libraries in the target repository, the job might import incorrectly due to the search mechanism being applied.

Type:	Problem Note
Priority:	alert

Date Modified:	2008-03-14 14:19:57
Date Created:	2007-11-09 13:54:48