{"id":654,"date":"2010-08-05T18:57:09","date_gmt":"2010-08-05T23:57:09","guid":{"rendered":"http:\/\/www.thejuliagroup.com\/blog\/?p=654"},"modified":"2010-08-21T01:47:48","modified_gmt":"2010-08-21T06:47:48","slug":"ubuntu-64-sas-9-2-what-i-do-all-day","status":"publish","type":"post","link":"https:\/\/www.thejuliagroup.com\/blog\/ubuntu-64-sas-9-2-what-i-do-all-day\/","title":{"rendered":"Ubuntu 64, SAS 9.2 &#038; What I Do All Day"},"content":{"rendered":"<p><em>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 &#8230;<\/em><\/p>\n<p>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 <a href=\"http:\/\/www.sascommunity.org\/wiki\/SAS-L\">very cool resource, SAS-L<\/a> there was a (thankfully, short) trend where people would post answers with the note &#8220;Code not tested&#8221;,  which is a polite way of saying, &#8220;I don&#8217;t know if this will work.&#8221;<\/p>\n<p>When anyone asks me a question, unless it is something like &#8220;Do you end SAS statements with a period or a semi-colon?&#8221;, 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.<\/p>\n<p>So&#8230; the very simple question asked was:<br \/>\n<em>&#8220;How do I renew SAS for Linux 64?&#8221;<\/em><\/p>\n<p><strong>First problem:<\/strong> 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&#8217;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.<\/p>\n<p>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 &#8230;<\/p>\n<p>Delete VM I no longer need.<\/p>\n<p>Go here:<br \/>\n<a href=\" http:\/\/www.ubuntu.com\/desktop\/get-ubuntu\/download\"><br \/>\nhttp:\/\/www.ubuntu.com\/desktop\/get-ubuntu\/download<\/a><\/p>\n<p>Download the 64-bit iso.<\/p>\n<p>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.<\/p>\n<p><a href=\"http:\/\/ubuntuforums.org\/showthread.php?p=9370540\">http:\/\/ubuntuforums.org\/showthread.php?p=9370540<\/a><\/p>\n<p>Downloaded and installed anyway.<\/p>\n<p><strong>Second problem:<\/strong> 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.<\/p>\n<p>Must be relatively new because I did not have it before.<\/p>\n<p>Searching Google, source of all knowledge, I found the answer on the source of all knowledge on Ubuntu, the Ubuntu forums<br \/>\n<a href=\" http:\/\/ubuntuforums.org\/showthread.php?t=1467905\"><br \/>\nhttp:\/\/ubuntuforums.org\/showthread.php?t=1467905<\/a><\/p>\n<blockquote><p>\nI&#8217;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:<\/p>\n<ul>\n<li> At the logon screen, go to the Accessibility Preferences at the bottom of the screen, and tick on screen keyboard.<\/li>\n<li>You may have to reboot if the virtual keyboard doesn\u2019t start.<\/li>\n<li>You can now type in your password using the virtual keyboard on the logon screen. Once logged in, your physical keyboard works.<\/li>\n<\/ul>\n<p>To fix the problem with your keyboard<\/p>\n<ul>\n<li> *Open a terminal, and reconfigure your console using the command:<\/li>\n<\/ul>\n<p><code>sudo dpkg-reconfigure console-setup<\/code>\n<\/p><\/blockquote>\n<p>Once logged in, I went to<\/p>\n<p><code>cd \/media<\/code><\/p>\n<p>cd to the external hard drive where all my SAS deployment folders are (we have MANY versions of SAS for many different operating systems)<\/p>\n<p>Then did<\/p>\n<p><code>cp -R sas92Linux64 ~\/sasinst<\/code><\/p>\n<p>This copied all the files and directories in the deployment folder to the ~\/sasinst folder on my hard drive<\/p>\n<p>I changed to bash<br \/>\n<code><br \/>\nsudo rm  \/bin\/sh<br \/>\nsudo ln  -s  \/bin\/bash  \/bin\/sh<\/code><\/p>\n<p>I then went to the folder where I had copied the deployment files, typed<br \/>\n<code><br \/>\nsudo .\/setup.sh<\/code><\/p>\n<p><strong>Third problem:<\/strong> The deployment wizard started &#8230;. and then stopped<\/p>\n<p>Nothing&gt;<\/p>\n<p>Now, at this point I have created a new VM, gotten around the keyboard problem, copied over the files and still nothing<\/p>\n<p>I then found this FABULOUS web page from the National Center for Ecological Analysis and Synthesis<\/p>\n<p><a href=\"http:\/\/help.nceas.ucsb.edu\/Install_SAS_on_Ubuntu\">http:\/\/help.nceas.ucsb.edu\/Install_SAS_on_Ubuntu<\/a><\/p>\n<p>VERY IMPORTANT ADVICE &#8230;<\/p>\n<p>install required packages:<br \/>\n<code><br \/>\nsudo apt-get install xauth x11-apps libstdc++5 ia32-libs libxp6<\/code><\/p>\n<p>Then, of course, comes the question, where do you find libstdc++5<\/p>\n<p>Here is one place<br \/>\n<a href=\" http:\/\/packages.debian.org\/stable\/base\/libstdc++5\"><br \/>\nhttp:\/\/packages.debian.org\/stable\/base\/libstdc++5<br \/>\n<\/a><br \/>\nSo&#8230;. I download libstdc++5 , run the command above to get everything I need installed.<\/p>\n<p>THEN &#8230;<\/p>\n<p>I go back and typed<\/p>\n<p><code>sudo bash setup.sh<\/code><\/p>\n<p>Everything installed.<\/p>\n<p><strong>Getting SAS to work<br \/>\n<\/strong><br \/>\nFirst, create a directory to act as your working directory. I called mine tmp<br \/>\nI went to  usr\/local  and typed<\/p>\n<p><code>mkdir tmp<\/code><\/p>\n<p>Give everyone access to write to the tmp directory<\/p>\n<p><code>sudo chmod 777 \/usr\/tmp<\/code><\/p>\n<p>To get SAS to start the first time I had to type<\/p>\n<p><code>\/usr\/local\/SAS\/SASFoundation\/9.2\/sas - work \/usr\/local\/tmp<\/code><\/p>\n<p>&#8212;&#8212;&#8212;&#8211; One more thing &#8212;-<\/p>\n<p>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 :<\/p>\n<p><code>sudo ln -s \/usr\/local\/SAS\/SASFoundation\/9.2\/sas \/usr\/bin\/sas<\/code><\/p>\n<p>Now when I start SAS all I need to do is type<\/p>\n<p><code>sas -work \/tmp<\/code><\/p>\n<p>I like that better.<\/p>\n<p><strong>Fourth problem:<\/strong> 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.<\/p>\n<p>Once you do actually have the correct SID file &#8230;<\/p>\n<p>Here is the answer I actually sent on how to renew SAS on Ubuntu (Remember, that was the original question)<\/p>\n<p>================<\/p>\n<p>1. Open up a terminal window (under applications > accessories)<br \/>\n2. cd to where you have your sas software installed<br \/>\n<code>cd \/usr\/local\/SAS\/SASFoundation\/9.2<\/code><\/p>\n<p>3. Start the renewal utility by typing<br \/>\n<code>sudo .\/sassetup<\/code><\/p>\n<p>4. Hit enter to continue<br \/>\n5. Type 1 for Run Setup Utilities<br \/>\n6. Type 1 for Renew SAS Software<br \/>\n7. You&#8217;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<br \/>\n<code><br \/>\n\/home\/ademars\/Downloads\/SAS92_Linux64.txt<\/code><\/p>\n<p>(by the way, when I tried ~\/Downloads\/SAS92_Linux64.txt  it didn&#8217;t work )<\/p>\n<p>The Setup Utilities Menu will pop up again.<br \/>\nType q<\/p>\n<p>You have now renewed.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>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 &#8230; 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&#8230;<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"_kad_post_classname":"","_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[9,8],"tags":[],"class_list":["post-654","post","type-post","status-publish","format-standard","hentry","category-software","category-technology"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.thejuliagroup.com\/blog\/wp-json\/wp\/v2\/posts\/654","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.thejuliagroup.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.thejuliagroup.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.thejuliagroup.com\/blog\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/www.thejuliagroup.com\/blog\/wp-json\/wp\/v2\/comments?post=654"}],"version-history":[{"count":7,"href":"https:\/\/www.thejuliagroup.com\/blog\/wp-json\/wp\/v2\/posts\/654\/revisions"}],"predecessor-version":[{"id":688,"href":"https:\/\/www.thejuliagroup.com\/blog\/wp-json\/wp\/v2\/posts\/654\/revisions\/688"}],"wp:attachment":[{"href":"https:\/\/www.thejuliagroup.com\/blog\/wp-json\/wp\/v2\/media?parent=654"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.thejuliagroup.com\/blog\/wp-json\/wp\/v2\/categories?post=654"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.thejuliagroup.com\/blog\/wp-json\/wp\/v2\/tags?post=654"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}