The next time your boss asks what you do all day or why it takes you so long to answer a question, show him or her this …
Now, unlike this blog. where I basically drink Chardonnay and say whatever the hell I feel like, when people are paying me for answers, I take my work pretty seriously. Years ago, on the very cool resource, SAS-L there was a (thankfully, short) trend where people would post answers with the note “Code not tested”, which is a polite way of saying, “I don’t know if this will work.”
When anyone asks me a question, unless it is something like “Do you end SAS statements with a period or a semi-colon?”, I test my answer before I send it. For one thing, with changes in versions, different operating systems and other variations, something that may work in one situation may not work in another.
So… the very simple question asked was:
“How do I renew SAS for Linux 64?”
First problem: I do not have SAS installed on a 64-bit Linux system to renew, so, I decide to install it on this Ubuntu VM I happen to have , and it doesn’t work at all. Well, I had ASSUMED that since it is a VM running on a 64-bit Mac that also has a 64-bit Windows 7 VM and a 64-bit Vista VM that it must be a 64-bit Ubuntu VM.
The first time the install failed I thought, gee, maybe I should check. Well, I had created this VM about a year ago to test some things on the 32-bit version of Ubuntu for someone so …
Delete VM I no longer need.
Download the 64-bit iso.
Curious that it says not recommended for daily desktop usage. Read several posts speculating on why it said that but nothing to convince me it was a big problem.
Downloaded and installed anyway.
Second problem: COULD NOT GET PAST LOGIN SCREEN! Ubuntu would not take my password. It was as if it did not recognize the keyboard. Turns out this is a known problem with VMware/Mac/Ubuntu combination.
Must be relatively new because I did not have it before.
I’ve had the keyboard problem with Ubuntu 10.04 in VMware Fusion 3.0.2 on a MacBook, US keyboard layout. I got around the problem as follows:
- At the logon screen, go to the Accessibility Preferences at the bottom of the screen, and tick on screen keyboard.
- You may have to reboot if the virtual keyboard doesn’t start.
- You can now type in your password using the virtual keyboard on the logon screen. Once logged in, your physical keyboard works.
To fix the problem with your keyboard
- *Open a terminal, and reconfigure your console using the command:
sudo dpkg-reconfigure console-setup
Once logged in, I went to
cd to the external hard drive where all my SAS deployment folders are (we have MANY versions of SAS for many different operating systems)
cp -R sas92Linux64 ~/sasinst
This copied all the files and directories in the deployment folder to the ~/sasinst folder on my hard drive
I changed to bash
sudo rm /bin/sh
sudo ln -s /bin/bash /bin/sh
I then went to the folder where I had copied the deployment files, typed
Third problem: The deployment wizard started …. and then stopped
Now, at this point I have created a new VM, gotten around the keyboard problem, copied over the files and still nothing
I then found this FABULOUS web page from the National Center for Ecological Analysis and Synthesis
VERY IMPORTANT ADVICE …
install required packages:
sudo apt-get install xauth x11-apps libstdc++5 ia32-libs libxp6
Then, of course, comes the question, where do you find libstdc++5
So…. I download libstdc++5 , run the command above to get everything I need installed.
I go back and typed
sudo bash setup.sh
Getting SAS to work
First, create a directory to act as your working directory. I called mine tmp
I went to usr/local and typed
Give everyone access to write to the tmp directory
sudo chmod 777 /usr/tmp
To get SAS to start the first time I had to type
/usr/local/SAS/SASFoundation/9.2/sas - work /usr/local/tmp
———– One more thing —-
Since I always like to tie up the loose ends, I took one final bit of advice from the wonderful NCEAS site and typed the following :
sudo ln -s /usr/local/SAS/SASFoundation/9.2/sas /usr/bin/sas
Now when I start SAS all I need to do is type
sas -work /tmp
I like that better.
Fourth problem: I get an error message telling me that there is a mismatch between my license and the version of SAS I have installed. I talk to a few people at SAS and get several other things I need, like an electronic software download for the latest version of SAS for Linux 64, the SID file to renew Linux 64 for a different site, and I have a long conversation with someone who tells me that what I have installed is Linux 32. Since the current (expired) SID file says Linux 64 and when I run a PROC SETINIT it says Linux 64, and the original ESD from a year ago says Linux 64, I tell her that while it is theoretically possible that it is, in fact, Linux 32 which was mislabeled in four different ways, I kind of doubt it. She finally gives in to my superior logic, tracks down the SID file for this version and emails it to me.
Once you do actually have the correct SID file …
Here is the answer I actually sent on how to renew SAS on Ubuntu (Remember, that was the original question)
1. Open up a terminal window (under applications > accessories)
2. cd to where you have your sas software installed
3. Start the renewal utility by typing
4. Hit enter to continue
5. Type 1 for Run Setup Utilities
6. Type 1 for Renew SAS Software
7. You’ll be prompted for the file containing the SAS installation data file. If you downloaded it from an email sent to you by your SAS Administrator, it will probably be something like
(by the way, when I tried ~/Downloads/SAS92_Linux64.txt it didn’t work )
The Setup Utilities Menu will pop up again.
You have now renewed.