The %Lookfor_filelock parameter is needed to prevent the following error from occurring when using SAS Merchandise Data Integration:

The examine_sas_log.sas program contains a code problem that causes this issue, which is recorded in the mdi_loadfact.sas log. The error occurs at the point during the load in which SAS Merchandise Data Integration tries to read the Oracle SQL*Loader log. However, that log file does not exist.

The circumvention is to change the setting for the parameter BL_DELETE_DATAFILE in the bulk_insert.sas program. This is set to YES by default and should be set to NO. This ensures that the data files, which are not being found because they are being deleted, are not deleted when the load is finished. Be aware that the DAT, LOG, and CTL files that are retained with this change in the BL_DELETE_DATAFILE can be quite large and will need to be cleaned up manually.

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

The new option BL_DELETE_ONLY_DATAFILE that is associated with BL_DELETE_DATAFILE has been added with this hot fix. See SAS Note 36595 "The BL_DELETE_FILES option deletes all file types(.ctl, .log, and .dat) that are created with the bulk loader" for more information.

Note that the 6.1.3 M3 Release Notes has an incorrect description of the new setting. BL_DELETE_DATAFILE_ONLY was used when it should read BL_DELETE_ONLY_DATAFILE.

Operating System and Release Information

Product Family	Product	System	Product Release		SAS Release
			Reported	Fixed*	Reported	Fixed*
SAS System	SAS Merchandise Financial Planning and SAS Merchandise In-Season Management	Microsoft® Windows® for x64	6.1.2	6.1.3	9.1 TS1M3 SP4	9.1 TS1M3 SP4
		Microsoft Windows 2000 Advanced Server	6.1.2	6.1.3	9.1 TS1M3 SP4	9.1 TS1M3 SP4
		Microsoft Windows 2000 Datacenter Server	6.1.2	6.1.3	9.1 TS1M3 SP4	9.1 TS1M3 SP4
		Microsoft Windows 2000 Server	6.1.2	6.1.3	9.1 TS1M3 SP4	9.1 TS1M3 SP4
		Microsoft Windows 2000 Professional	6.1.2	6.1.3	9.1 TS1M3 SP4	9.1 TS1M3 SP4
		Microsoft Windows NT Workstation	6.1.2	6.1.3	9.1 TS1M3 SP4	9.1 TS1M3 SP4
		Microsoft Windows Server 2003 Datacenter Edition	6.1.2	6.1.3	9.1 TS1M3 SP4	9.1 TS1M3 SP4
		Microsoft Windows Server 2003 Enterprise Edition	6.1.2	6.1.3	9.1 TS1M3 SP4	9.1 TS1M3 SP4
		Microsoft Windows Server 2003 Standard Edition	6.1.2	6.1.3	9.1 TS1M3 SP4	9.1 TS1M3 SP4
		Microsoft Windows XP Professional	6.1.2	6.1.3	9.1 TS1M3 SP4	9.1 TS1M3 SP4
		Windows Vista	6.1.2	6.1.3	9.1 TS1M3 SP4	9.1 TS1M3 SP4
		64-bit Enabled AIX	6.1.2	6.1.3	9.1 TS1M3 SP4	9.1 TS1M3 SP4
		64-bit Enabled Solaris	6.1.2	6.1.3	9.1 TS1M3 SP4	9.1 TS1M3 SP4
SAS System	SAS/ACCESS Interface to Oracle	Microsoft® Windows® for 64-Bit Itanium-based Systems			9.1 TS1M3 SP4
		Microsoft Windows Server 2003 Datacenter 64-bit Edition			9.1 TS1M3 SP4
		Microsoft Windows Server 2003 Enterprise 64-bit Edition			9.1 TS1M3 SP4
		Microsoft Windows XP 64-bit Edition			9.1 TS1M3 SP4
		Microsoft Windows 2000 Advanced Server			9.1 TS1M3 SP4
		Microsoft Windows 2000 Datacenter Server			9.1 TS1M3 SP4
		Microsoft Windows 2000 Server			9.1 TS1M3 SP4
		Microsoft Windows 2000 Professional			9.1 TS1M3 SP4
		Microsoft Windows NT Workstation			9.1 TS1M3 SP4
		Microsoft Windows Server 2003 Datacenter Edition			9.1 TS1M3 SP4
		Microsoft Windows Server 2003 Enterprise Edition			9.1 TS1M3 SP4
		Microsoft Windows Server 2003 Standard Edition			9.1 TS1M3 SP4
		Microsoft Windows XP Professional			9.1 TS1M3 SP4
		Windows Vista			9.1 TS1M3 SP4
		64-bit Enabled AIX			9.1 TS1M3 SP4
		64-bit Enabled HP-UX			9.1 TS1M3 SP4
		64-bit Enabled Solaris			9.1 TS1M3 SP4
		HP-UX IPF			9.1 TS1M3 SP4
		Linux			9.1 TS1M3 SP4
		Linux on Itanium			9.1 TS1M3 SP4
		OpenVMS Alpha			9.1 TS1M3 SP4
		Solaris for x64			9.1 TS1M3 SP4
		Tru64 UNIX			9.1 TS1M3 SP4

* 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 SAS 9.1.3 (9.1 TS1M3) for this issue is available at:

http://www.sas.com/techsup/download/hotfix/e9_sbcs_prod_list.html#033135

---

A fix for SAS 9.1.3 (9.1 TS1M3) with Asian Language Support (DBCS) for this issue is available at:

http://www.sas.com/techsup/download/hotfix/e9_dbcs_prod_list.html#033135

---

The %Lookfor_filelock parameter is needed to prevent "Error: Physical file does not exist" from occurring when you use SAS® Merchandise Data Integration. The examine_sas_log.sas program contains a code problem that causes the following issue which is recorded in the mdi_loadfact.sas log.

Type:	Problem Note
Priority:	high

Date Modified:	2009-07-22 17:27:41
Date Created:	2008-09-03 14:06:38