Problem Note 18857: Using the WebDAV filename option without specifying a full file path might cause problems when writing to or reading from a directory
Under SAS® 9.1.3 SP4, problems might occur when writing to, or reading from, a directory that supports the WebDAV protocal if you use the WebDAV filename option without specifying a full file path.
This problem can be addressed by applying the hox fix that is provided in this SAS note. The hot fix provides access to two new options; DIR and FILEEXT.
The DIR option
The new FILENAME SASXBAMW statement DIR option enables you to access directory members. You must use valid directory syntax for the specified host, and specify the directory name in the external-file argument. See the examples below:
- Writing to a new member of a directory on a server that supports the WebDAV protocol:
filename foo sasxbamw
"https://<machine_name>:<server_port_number>/testing1/"
DIR user="xxxx" pass="xxxx";
data _null_;
file foo (shoes);
set sashelp.shoes;
put region $25. product $14.;
run;
- Reading from a member of a directory on a server that supports the WebDAV protocol:
filename foo sasxbamw
"https://<machine_name>:<server_port_number>/testing1/"
DIR user="xxxx" pass="xxxx";
data shoes;
length region $25 product $14;
infile foo (shoes);
input region $25. product $14.;
run;
The FILEEXT option
- Using a WebDAV location as an autocall macro library:
Note: The autocall macro facility expects uppercase file names. If you use a WebDAV location as an autocall macro library, you must use uppercase file names for your macros. Refer to SAS Note 35483 for an available fix that will allow you to use lowercase file names.
Additionally, if the files in your autocall macro library have names that end in
".sas", you must use the FILEEXT option as shown in the example below.
filename foo sasxbamw "https://xxxdemo.sas.com/webdav/macrolib"
user="xxxxxxx" password="xxxxxxx" dir fileext;
options SASAUTOS=(foo);
%mytest; /* expects a file called MYTEST.SAS */
Select the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | Base SAS | Microsoft Windows NT Workstation | 9.1 TS1M3 SP4 | |
Microsoft Windows XP Professional | 9.1 TS1M3 SP4 | 9.2 TS1M0 |
Microsoft Windows XP 64-bit Edition | 9.1 TS1M3 SP4 | 9.2 TS1M0 |
Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.1 TS1M3 SP4 | 9.2 TS1M0 |
Microsoft Windows Server 2003 Standard Edition | 9.1 TS1M3 SP4 | 9.2 TS1M0 |
Microsoft Windows Server 2003 Datacenter Edition | 9.1 TS1M3 SP4 | 9.2 TS1M0 |
Microsoft Windows Server 2003 Enterprise Edition | 9.1 TS1M3 SP4 | 9.2 TS1M0 |
Microsoft Windows 2000 Professional | 9.1 TS1M3 SP4 | 9.2 TS1M0 |
Microsoft Windows 2000 Server | 9.1 TS1M3 SP4 | 9.2 TS1M0 |
Linux on Itanium | 9.1 TS1M3 SP4 | |
Linux | 9.1 TS1M3 SP4 | 9.2 TS1M0 |
64-bit Enabled Solaris | 9.1 TS1M3 SP4 | 9.2 TS1M0 |
Solaris for x64 | 9.1 TS1M3 SP4 | 9.2 TS1M0 |
Microsoft Windows 2000 Advanced Server | 9.1 TS1M3 SP4 | 9.2 TS1M0 |
HP-UX IPF | 9.1 TS1M3 SP4 | 9.2 TS1M0 |
Microsoft Windows 2000 Datacenter Server | 9.1 TS1M3 SP4 | 9.2 TS1M0 |
64-bit Enabled AIX | 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.
Type: | Problem Note |
Priority: | high |
Topic: | SAS Reference ==> LIBNAME Engines SAS Reference ==> Statements ==> Data Access ==> LIBNAME
|
Date Modified: | 2006-12-06 09:50:47 |
Date Created: | 2006-10-27 15:47:04 |