SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 35853: RLS LIBNAME assignments are misassigned when it contains the same value for the HOSTNAME= option as in the previous LIBNAME assignment

DetailsHotfixAboutRate It

Remote Library Services (RLS) LIBNAME assignments can be misassigned if the value for the HOSTNAME= option has the same first eight characters as the previous RLS LIBNAME assignment. For example, if you submit the following LIBNAME statements, the libref DOG might be assigned to the same server as that for libref CAT:

libname cat server=__7551 hostname='12.34.56.78'; libname dog server=__7551 hostname='12.34.56.87';

The second assignment in this example will only work if the libref DOG is assigned to the server on host '12.34.56.78'. However, that means the statements are executed without a failure, not that they necessarily work correctly. These LIBNAME assignments also can fail for a number of other reasons, such as a situation where the second LIBNAME statement specifies a SERVER= value that is not in use on the first host, or a situation where a specified pathname cannot be found by the first host server.

Prior to SAS®9, the syntax for RLS LIBNAME assignments was the following:

libname libref <'path-name'> server=host-name.serverid ...more options. . .;

In cases where host-name exceeded eight characters, you could use macro-symbol table lookup to avoid such a problem, as shown here:

%let catserv=12.34.56.78; %let dogserv=12.34.56.87; libname cat server=catserv.__7551; libname dog server=dogserv.__7551;

The HOSTNAME= option was added for the LIBNAME statement in SAS®9 to provide more flexibility in RLS LIBNAME assignments. You cannot include the %LET macro statements in SAS® 9.1 Management Console when you are building LIBNAME statements, so the HOSTNAME= option was created be used directly in a LIBNAME statement and to perform the same task as the %LET statements.

As a workaround for the problem that occurs with the HOSTNAME= option, you can still use the macro-symbol table lookup solution.

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



Operating System and Release Information

Product FamilyProductSystemSAS Release
ReportedFixed*
SAS SystemSAS/SHAREz/OS9.1 TS1M3 SP49.2 TS2M0
Microsoft® Windows® for 64-Bit Itanium-based Systems9.1 TS1M3 SP49.2 TS2M0
Microsoft Windows Server 2003 Datacenter 64-bit Edition9.1 TS1M3 SP49.2 TS2M0
Microsoft Windows Server 2003 Enterprise 64-bit Edition9.1 TS1M3 SP49.2 TS2M0
Microsoft Windows XP 64-bit Edition9.1 TS1M3 SP49.2 TS2M0
Microsoft Windows 2000 Advanced Server9.1 TS1M3 SP4
Microsoft Windows 2000 Datacenter Server9.1 TS1M3 SP4
Microsoft Windows 2000 Server9.1 TS1M3 SP4
Microsoft Windows 2000 Professional9.1 TS1M3 SP4
Microsoft Windows NT Workstation9.1 TS1M3 SP4
Microsoft Windows Server 2003 Datacenter Edition9.1 TS1M3 SP49.2 TS2M0
Microsoft Windows Server 2003 Enterprise Edition9.1 TS1M3 SP49.2 TS2M0
Microsoft Windows Server 2003 Standard Edition9.1 TS1M3 SP49.2 TS2M0
Microsoft Windows XP Professional9.1 TS1M3 SP49.2 TS2M0
Windows Vista9.1 TS1M3 SP49.2 TS2M0
64-bit Enabled AIX9.1 TS1M3 SP49.2 TS2M0
64-bit Enabled HP-UX9.1 TS1M3 SP49.2 TS2M0
64-bit Enabled Solaris9.1 TS1M3 SP49.2 TS2M0
HP-UX IPF9.1 TS1M3 SP49.2 TS2M0
Linux9.1 TS1M3 SP49.2 TS2M0
Linux on Itanium9.1 TS1M3 SP49.2 TS2M0
OpenVMS Alpha9.1 TS1M3 SP49.2 TS2M0
Solaris for x649.1 TS1M3 SP49.2 TS2M0
Tru64 UNIX9.1 TS1M3 SP49.2 TS2M0
* 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.