Blogging about all things SAS

I have been doing a bit more Solution Architecture work around SAS 9.2 lately, and I keep needing to validate what versions of Operating System works with what version of SAS etc.

So here are the links (please note I have only included links to SAS 9.2 TM2Mx, not TM1M0):

• SAS 9.2 Supported Operating Environments
• SAS 9.2 Support for Web Application Servers and HTTP Servers
• SAS 9.2 Support for Additional Software Products
• SAS 9.2 Support for Web Browsers and Plug-Ins
• SAS® Product Support for Virtualization Environments
• SAS/ACCESS 9.2 Validation Matrix
• SAS 9.2 (TM2Mx) System requirements
• SAS 9.2 Support for Java Development Kits
• SAS 9.2 Support for Java Runtime Environments
• Metadata Bridges

Every now and again I get to right some SAS code.

And every know and again I need to transform SAS dates, from Date/Time to Date9 or from Date to Date/Time etc.

Its one thing that I always end up looking at SAS support for the correct syntax.  So Im going to post each one I use here so I can find them easily.

SAS Date to Date/Time

To convert a SAS date to a SAS Date/Time, by adding a time of 00:00:00 to it use:

dhms(<date_variable_name>,0,0,0)

In SAS 9.2 two different typos of connection profiles are stored for each user, one for windows applications (AMO, EG etc) and the pother for Java applications (DI Studio, Info Map Studio etc).

Java Applications:

Connection profiles are stored on the hosts of the desktop applications at C:\Documents and Settings\user name\Application Data\SAS\MetadataServerProfiles. In the Windows Vista operating environment, the path is C:\Users\user name\AppData\Roaming\SAS\MetadataServerProfiles. The names of the profiles use the file extension.swa.

Windows Applications:

These profiles are stored in the ConfigurationV42.xml file in the users home directory C:\Documents and Settings\user name\Application Data\SAS\MetadataServerProfiles.

And of course recommended good practice is to only change these files via the profile editing capability provided within each of the SAS client applications.

And following on with the theme of migrating SAS formats …..

SAS Support article here:

http://support.sas.com/kb/22/194.html

Outlines how to migrate formats across SAS systems.

Basically you just:

1) Export the formats to a transport file by using the follwing code:

  libname library 'location-of-existing-formats-catalog';
  libname trans xport 'transport-file-name';
  proc format library=library cntlout=trans.cntlfmt;

2) Import the formats from the transport file using the following code:
  libname library 'output-library-for-format-storage';
  libname trans xport 'transport-file-name-from-sending-site';
  proc format library=library cntlin=trans.cntlfmt;

This is of course assuming you don’t have the code that originally created teh formats, because you could just run that instead. But bet you dont as you have just searched for something that made you find this blog post

If you are ever looking for a list of SAS 9.2 procedures or trying to work out what SAS product you need to buy to use a certain procedure, you can find them here on the SAS support site:

SAS Procedures by Name
SAS Procedures by Product

Just saw this post on Chris H’s blog here and I am replicating it so I can find it when I need it. (cause half my posts are there so I can find them when I need them)

If you want to know what version of SAS/Access works with what operating system and what release and what database etc, then look here:

http://support.sas.com/matrix/list?SAS=All&Engine=All&OS=All&googleTrack=on

Well course is over and I passed, so wahoo for me!

I am blogging all my tweets from the course so it is easier for me to search them in the future.

(more…)

SAS 9.2 now has the concept of External Identities against a user or group.

The following is an extract of the online help:

(more…)

Setting up SAS Share to enable you to Import and Export ABM models is one of those things that always seems to be a bit tricky to get working.

I found a public doc on the old ABC Tech support site here, that explains the steps. I have also cut and paste the content below in case the doc disappears.

One thing to note is that if you have two SAS servers wanting to talk via this SAS Share link (i.e one with SAS ABM and the other with SAS DI or EG etc) you need to make sure the SAS Share names are identical on both servers or it wont work!

Oh and don’t forget that you need SAS Share OLEDB client on every PC that wants to export/import. You can install this from the SAS ABM Client install page on your ABM Webserver.

(more…)

While researching and testing the default Web Report Studio metadata security I noticed this little trick for young players, which means changes to WRS/WRV Metadata Security for a user are not instantly applied/recognised in WRS/WRV.

Words from the SAS tech support note “Changes to SAS® Web Report Studio role memberships might not immediately be enforced“:

“SAS Web Report Studio analyzes role memberships every 30 minutes. So, for example, if you move a user from the WRS Report Author role to the WRS Report Consumer role, the user will continue to have author privileges until the next time that he logs in after the next role membership analysis is performed. ”

So effectively the WRS/WRV applications are caching the Metadata security to remove the need for the web server to query the Metadata Server each time a user logins.

So try not to be fast when testing your WRS Metadata security changes, else you will think you have done something wrong. And remember to logout and log back in after the cache has been updated.

You can update the LocalProperties.xml file to change the refresh time, and therefore make the changes appear sooner. Details on how to do this are in the SAS Tech Support note.