Desktop productivity for business analysts and programmers


Not applicable
Posts: 0


Am I the only person totally confused by the switch to metadata in SAS9 (and E.G. of course). Maybe it was there in ver. 8.2 and I was just oblivious - now I am somewhat familiar with the information contained in the dictionary tables and corresponding sashelp views. However, where I am working we go thru contortions to create new permanent SAS datasets, can *not* write to "sasuser" and the list goes on.

I recently came across a SAS note, SN-014080, supplied by one of the terrific Tech Support consultants. But shouldn't there be an easier way to understand how metadata impacts the way we use SAS in SAS9, especially if we've used the product for a while.

In closing I have to repeat "Am I the only one" confused by all this.

Bernie Zimmerman
Community Manager
Posts: 3,456

Re: Metadata

Posted in reply to deleted_user

You are not alone! There is no denying that SAS 9 introduces a whole new dimension of metadata to the traditional concepts of SAS libraries, and that this is a source of confusion for many traditional SAS users. The metadata is necessary to provide access permissions and facilitate new concepts such as Information Maps.

As much as possible, we are working to make this "just work" for the users of our client products like Enterprise Guide. Enterprise Guide 4.1, in conjunction with SAS 9.1.3 SP4, does provide some more options for library behavior that can get you closer to the behavior you are accustomed to.

For example, using the SAS Enterprise Guide Explorer (off the Tools menu), an administrator can "tag" your library definitions so that EG can assign them:
- with the native library engine (bypassing metadata)
- with the META engine showing only registered tables (as EG 3.0 does now)
- with the META engine, showing all tables -- even those not registered yet in metadata.

As you note, SASUSER is "read-only" in the default SAS 9 deployment (via the -RSASUSER option). This is done to accomodate multiuser-type servers (such as Stored Process servers) where the concept of a SASUSER area doesn't apply. Workarounds include:

- designating another user-specific library location to save your "permanent" output.

- removing the -RSASUSER option from workspace server configurations if you don't need it. Keep in mind that if you publish your EG project work as a stored process, the stored process server will not be able to write output to SASUSER.

Ask a Question
Discussion stats
  • 1 reply
  • 2 in conversation