Things I need to remember!
We have been doing some trouble shooting with the new Grid environment, and one of the guys on the customers site found this great piece fo SAS code:
%put _all_;
Run it in EG and the log will tell you a whole heap about what and where you are running your code on!
Example results from SAS 9.2 (GRID)
Because I always forget!
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):
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.
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).
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.
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.
SAS 9.2 now has the concept of External Identities against a user or group.
The following is an extract of the online help:
Recent Comments