- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Posted 09-01-2007 12:51 AM
(2943 views)
Hello!
I have to retrieve all the metadata library names that were already defined under a metadata server. Each library is defined to its physical location and a few datasets already imported under each library.
How can I retrieve all Metadata library names into a macro variable or display using an sql would also be fine.
Any help is greatly appreciated!
Raja
I have to retrieve all the metadata library names that were already defined under a metadata server. Each library is defined to its physical location and a few datasets already imported under each library.
How can I retrieve all Metadata library names into a macro variable or display using an sql would also be fine.
Any help is greatly appreciated!
Raja
6 REPLIES 6
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Hi:
I do not believe it is possible to -easily- get this information into a single macro variable or even multiple macro variables or to do an SQL query against the Metadata repository. Both DI Studio and SAS Management Console will show you the property information for the data libraries that have been defined to the Metadata repository. In addition, DIStudio provides a way that you can EXPORT library object information into an XML file format.
You might consider contacting Tech Support for more help. They would know whether there are any utility programs that a SAS Administrator could use to report on this kind of information.
cynthia
I do not believe it is possible to -easily- get this information into a single macro variable or even multiple macro variables or to do an SQL query against the Metadata repository. Both DI Studio and SAS Management Console will show you the property information for the data libraries that have been defined to the Metadata repository. In addition, DIStudio provides a way that you can EXPORT library object information into an XML file format.
You might consider contacting Tech Support for more help. They would know whether there are any utility programs that a SAS Administrator could use to report on this kind of information.
cynthia
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Hi Raja,
You could try this SAS code for a start:
options MetaServer="localhost"
MetaPort=8561
MetaUser="sasadm"
MetaPass="XXXXXX"
MetaRepository="Foundation"
MetaProtocol=BRIDGE;
/*file gets created under C:\WINDOWS\system32*/
filename xmlout 'SASLibrary_Base.xml' ;
filename inxmlb temp;
data _null_;
file inxmlb;
input;
put _infile_;
cards;
$METAREPOSITORY
SASLibrary
SAS
388
;;
PROC METADATA
IN=inxmlb
out = xmlout verbose;
run;
Here's more info:
http://support.sas.com/onlinedoc/913/getDoc/en/omags.hlp/a003159943.htm
You could try this SAS code for a start:
options MetaServer="localhost"
MetaPort=8561
MetaUser="sasadm"
MetaPass="XXXXXX"
MetaRepository="Foundation"
MetaProtocol=BRIDGE;
/*file gets created under C:\WINDOWS\system32*/
filename xmlout 'SASLibrary_Base.xml' ;
filename inxmlb temp;
data _null_;
file inxmlb;
input;
put _infile_;
cards;
;;
PROC METADATA
IN=inxmlb
out = xmlout verbose;
run;
Here's more info:
http://support.sas.com/onlinedoc/913/getDoc/en/omags.hlp/a003159943.htm
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Hi:
I highly recommend that you contact a SAS Administrator at your site because this information is very specific to your installation:
[pre]
options MetaServer="localhost"
MetaPort=8561
MetaUser="sasadm"
MetaPass="XXXXXX"
MetaRepository="Foundation"
MetaProtocol=BRIDGE;
[/pre]
For example, your install people might not have used port 8561 for the Metadata server. They may have not have used a "SASADM" user-id for the administrator user-id or set a different user id with administrative privileges. Your Repository may not be called Foundation. Your server may not be on "localhost". And, last, but not least, you need to know the the right password for the user-id that must be used.
cynthia
I highly recommend that you contact a SAS Administrator at your site because this information is very specific to your installation:
[pre]
options MetaServer="localhost"
MetaPort=8561
MetaUser="sasadm"
MetaPass="XXXXXX"
MetaRepository="Foundation"
MetaProtocol=BRIDGE;
[/pre]
For example, your install people might not have used port 8561 for the Metadata server. They may have not have used a "SASADM" user-id for the administrator user-id or set a different user id with administrative privileges. Your Repository may not be called Foundation. Your server may not be on "localhost". And, last, but not least, you need to know the the right password for the user-id that must be used.
cynthia
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
I have the correct Metadata Server and User info that I can apply for these options.
Thank you for sending this and I wil try this out and see what I can get and update back here.
I appreciate your help!
Raja
Thank you for sending this and I wil try this out and see what I can get and update back here.
I appreciate your help!
Raja
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Can a metadata server used in maintaining SAS earlier version servers can be used for latest SAS version 9.2
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Any metadata servers prior to SAS 9.2 will need to upgraded in order to support SAS 9.2. There have been significant changes in SAS 9.2 to support additional functionality, improved performance, and simplified administration.
To understand what is involved in upgrading from a previous version, please visit our SAS 9.2 Migration site at:
http://support.sas.com/rnd/migration/index.html
Vince DelGobbo
SAS R&D
To understand what is involved in upgrading from a previous version, please visit our SAS 9.2 Migration site at:
http://support.sas.com/rnd/migration/index.html
Vince DelGobbo
SAS R&D