About Author

Jennifer Parks

SAS platform administrator, Federal government sector

Jenni Parks is a seasoned Systems Administrator who has been working with SAS in the federal sector as a SAS Platform Administrator since 2006. She was thrust into a complex implementation project at hire and her continued successes in designing, deploying, and administering SAS EBI platforms has highlighted her value to the companies and clients she has worked for as well as the SAS user community. She attends DCSUG meetings as she is able and is a frequent SAS Global Forum attendee. In addition to her roles at CSC as a SAS Consultant and SAS Strategic Partner Development Lead, Jenni is also enrolled as a graduate student in the Master's program for Computer Science and Information Systems at the University of Michigan-Flint. When she's not racking up billable hours, Jenni typically spends her time researching and constructing gourmet menus for fabulous dinner parties or jet setting to foreign countries on weekends to indulge in airline status climbing (mileage running).

Related Posts

2 Comments

  1. Hi Jennifer,

    Thanks for posting such useful information. Personaly, I didn't know about the METAFIND tool until now so I am really grateful. The doc also mentions a third one, METACON (a font-end GUI to manage the Metadata Connection Profiles used by Metabrowser and Metafind) :

    http://support.sas.com/documentation/cdl/en/lrmeta/63180/HTML/default/viewer.htm#n19pqa08iiu0c2n1l8ulhp7z7jj4.htm

    A few comments:

    - It seems (and remains officially unconfirmed) that the Metabrowser edit mode requires to be logged in as "sasadm@saspw". No other accounts, even Unrestricted users, *would* be allowed to be given modification privilege with the Metabrowser. The 'browse mode' is available to every other accounts.

    - changing a single value with the Metabrowser is sometimes useful, even required in order to perform post-installation tasks with some HotFixes. However, since (as far as I know) the metabrowser doesn't log its transactions or return codes, I' rather advise the admins to write down a little sas code instead when the query modifies several metadata objects. It helps to track down the error, think up twice before running the code and record somewhere the modification once applied.

    - the metadata utility is especially helpful as a OMI XML generating tool. The OMI requests in plain XML are easily generated with a few clicks. Great. But, I remember the same tool back in 9.1 used to carry out large queries against the referential made crash without notice the metadata server (on Windows). No errors or warning left in the metadata server log file or even in the server log (metadata running as a windows service) . So I strongly advise the potential users to run this tool only in sandboxed or private Metadata installments, never in a production area. The authors have wisely put this warning message which pops up when you open the Metadata utility 'Manipulation of repository metadata using the XML Metadata Interface is an advanced feature that could result in inacessible or invalid metadata". This is real warning, not a formal disclaimer of responsibility.

    Ronan

    • Christina Harvey
      Christina Harvey on

      Reply from Jennifer Parks

      I am able to utilize the Metabrowse tool using my SAS Administrator account (which is part of the SAS Administrators group in our 9.2 installation but not an unrestricted user).

      As i noted at the beginning of the post, I'm writing toward the perspective of a SAS Administrator, versus a SAS Programmer and so I wanted to focus on non-programmatic approaches. Many SAS Administrators (such as myself) have a background in system and application administration and are not SAS programmers.

      I agree with you about the tremendous power that is vested in the Metadata Utility and that its use should be highly limited in production environments and monitored carefully. The situation that I presented - needing to update hundreds of hostnames buried inside the metadata in a production environment and lacking any other practical tools for doing so - is one such instance where the tool is the best choice for making these changes.

Back to Top