|
Thanks Randy
That (write) privilege is not one on which I can depend.
Additionally, I'm trying to avoid step & statement boundaries.
Right now, the quick solution is as offered by SI, capturing
proc contents ods output.
== through the boundaries..
The only way I can see to avoid the boundaries, involves
multiple %sysfunc calls to dread() member names of the
path given by pathname(libname)
So that appears to be my ultimate solution
many thanks
Peter
Thanks also for the assistance offered by others on and off SAS-L
Ed Heaton, Andre Wielki, Michael Sadol and Kilo
and of course SAS Customer Support
Datum: 01/08/2002 17:22
An: SAS-L@LISTSERV.UGA.EDU
Antwort an: Randy Herbison <RandyHerbison@WESTAT.COM>
Betreff: FW: retrieve libname options
Nachrichtentext:
Peter,
Following up on my previous e-mail, if you have write access for the
library, you could create a new library member using a name that doesn't
already exist and then use FILEEXIST to determine the extension.
RandyHerbison@westat.com
-----Original Message-----
From: Randy Herbison
Sent: Thursday, August 01, 2002 11:43 AM
To: SAS-L@LISTSERV.UGA.EDU
Subject: RE: retrieve libname options
Peter,
You can use the SCL function ATTRC to get the engine, but I haven't found a
way to determine whether a LIBRARY uses short or long extensions. You could
check by using FILEEXIST, but the folder could contain the same one-part
member name using both short and long extensions.
RandyHerbison@westat.com
-----Original Message-----
From: Ed Heaton
Sent: Thursday, August 01, 2002 11:15 AM
To: SAS-L@LISTSERV.UGA.EDU
Subject: Re: retrieve libname options
Peter,
I can get you part of the way there:
Proc sql noPrint ;
Select
path into :path
from sasHelp.vMember
where (
( upCase(libName) eq "SASUSER" )
& ( upCase(memName) eq "PILOTS" )
)
;
Quit ;
%put &path ;
I don't know how to get the file name.
Ed
Edward Heaton, Senior Systems Analyst,
Westat (An Employee-Owned Research Corporation),
1550 Research Boulevard, Room 2018, Rockville, MD 20850-3195
Voice: (301) 610-4818 Fax: (301) 294-3992
mailto:EdHeaton@westat.com http://www.westat.com
-----Original Message-----
From: Peter Crawford [mailto:peter.crawford@DB.COM]
Sent: Thursday, August 01, 2002 12:00 PM
To: SAS-L@LISTSERV.UGA.EDU
Subject: retrieve libname options
Hi
Do you know how I might discover the actual physical
name of a sas data set on winXX and/or unix ?
I have libname.memname, and would like to know
the actual path and filename.
I think I need only discover the engine of the libname
and whether it is using "long names" or 8.3 format names.
The pathname() function reveals the path, but
nothing I can find identifies whether the libname
has been prepared with the "ShortFileExt"
option.
WIth ods destination output, I can collect the physical
name from proc contents, but for this macro. I would
like to avoid going through a statement boundary, let
alone a step boundary.
with advance, thanks and appreciation of your interest
Peter Crawford
--
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte
Weitergabe dieser Mail ist nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.
--
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
| 
