Problem Note 62205: You might encounter "ERROR: Error in the FILENAME statement" after lockdown processing
 |  |  |  |  |
In the lockdown code, when you add lockdown paths provided in a fileref specified file, the physical file is not closed after lockdown processing. You encounter this issue and receive error messages similar to the following when you try to deassign the lockdown fileref in your autoexec file:
ERROR: At least one file associated with fileref fileref-name is still in use.
ERROR: Error in the FILENAME statement.
ERROR: Error in the FILENAME statement.
Click 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 | Base SAS | z/OS | 9.4_M5 | 9.4_M5 | 9.4 TS1M5 | 9.4 TS1M5 |
| z/OS 64-bit | 9.4_M5 | 9.4_M5 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| Microsoft® Windows® for x64 | 9.4_M5 | 9.4_M5 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| Microsoft Windows 8 Enterprise 32-bit | 9.4_M5 | 9.4_M5 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| Microsoft Windows 8 Enterprise x64 | 9.4_M5 | 9.4_M5 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| Microsoft Windows 8 Pro 32-bit | 9.4_M5 | 9.4_M5 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| Microsoft Windows 8 Pro x64 | 9.4_M5 | 9.4_M5 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| Microsoft Windows 8.1 Enterprise 32-bit | 9.4_M5 | 9.4_M5 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| Microsoft Windows 8.1 Enterprise x64 | 9.4_M5 | 9.4_M5 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| Microsoft Windows 8.1 Pro 32-bit | 9.4_M5 | 9.4_M5 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| Microsoft Windows 8.1 Pro x64 | 9.4_M5 | 9.4_M5 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| Microsoft Windows 10 | 9.4_M5 | 9.4_M5 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| Microsoft Windows Server 2008 | 9.4_M5 | 9.4_M5 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| Microsoft Windows Server 2008 R2 | 9.4_M5 | 9.4_M5 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| Microsoft Windows Server 2008 for x64 | 9.4_M5 | 9.4_M5 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| Microsoft Windows Server 2012 Datacenter | 9.4_M5 | 9.4_M5 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| Microsoft Windows Server 2012 R2 Datacenter | 9.4_M5 | 9.4_M5 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| Microsoft Windows Server 2012 R2 Std | 9.4_M5 | 9.4_M5 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| Microsoft Windows Server 2012 Std | 9.4_M5 | 9.4_M5 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| Microsoft Windows Server 2016 | 9.4_M5 | 9.4_M5 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| Windows 7 Enterprise 32 bit | 9.4_M5 | 9.4_M5 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| Windows 7 Enterprise x64 | 9.4_M5 | 9.4_M5 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| Windows 7 Home Premium 32 bit | 9.4_M5 | 9.4_M5 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| Windows 7 Home Premium x64 | 9.4_M5 | 9.4_M5 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| Windows 7 Professional 32 bit | 9.4_M5 | 9.4_M5 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| Windows 7 Professional x64 | 9.4_M5 | 9.4_M5 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| Windows 7 Ultimate 32 bit | 9.4_M5 | 9.4_M5 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| Windows 7 Ultimate x64 | 9.4_M5 | 9.4_M5 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| 64-bit Enabled AIX | 9.4_M5 | 9.4_M5 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| 64-bit Enabled Solaris | 9.4_M5 | 9.4_M5 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| HP-UX IPF | 9.4_M5 | 9.4_M5 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| Linux for x64 | 9.4_M5 | 9.4_M5 | 9.4 TS1M5 | 9.4 TS1M5 | ||
| Solaris for x64 | 9.4_M5 | 9.4_M5 | 9.4 TS1M5 | 9.4 TS1M5 | ||
A fix for this issue for Base SAS 9.4_M5 is available at:
https://tshf.sas.com/techsup/download/hotfix/HF2/B6Q.html#62205
You might encounter a bug in the lockdown code when adding lockdown paths provided in a fileref specified file. In this scenario, the following errors occur: "ERROR: At least one file associated with fileref 'fileref-name' is still in use. ERROR: Error in the FILENAME statement."
| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2018-05-08 13:38:20 |
| Date Created: | 2018-04-25 14:44:39 |