An Idea Exchange for SAS software and services

Comments
by PROC Star
on ‎08-25-2015 01:10 AM

is the goal to know the physical path?

by Regular Contributor
on ‎08-25-2015 09:27 AM

Yes.  With regard to the V9 LIBNAME engine there can be multiple paths for one library reference.  Consequently there can be two or more files existing in the LIBNAME "path" with the same file name, for which the physical file which is found first in the LIBNAME path will be the file that is read from and written to.  So, yes, to know the path of the file that is being operated on, versus those that are not.

SAS(R) 9.3 Statements: Reference

by PROC Star
on ‎08-25-2015 05:21 PM

The path is available as part of an ODS output of proc content's. The data set metadata is just too hard to gather or even source. See idea 2808 for a more general aim of making all data set metadata easily available.

by Regular Contributor
on ‎08-27-2015 01:44 PM

Good to know.  You are knowledgeable about these things.  I'm just encouraged to ask the question, more so because the column seems to be a fundamental piece of information that pertains to each dataset.

I don't follow you though...idea 2808, what's the link?

by PROC Star
on ‎08-27-2015 05:26 PM
by Regular Contributor
on ‎08-28-2015 09:16 AM

That's a big idea. I don't see this getting revamped like I think you are proposing. I believe it will happen by expanding on what exists.  I think the Dictionary library could eventually do this.  It already allows one to count a dataset's indexes via a database query and has the engine listed along with the information for each assigned libname.  Your arguments seems, to me, MHO, to be based only on frustrations occurring from only using PROC CONTENTS.  (And PROC CONTENTS is frustrating.)

Idea Statuses
Top Liked Authors