Today's Project: Learn SAS
 

We'll see how it goes.

For those that don't know, SAS is an analytics system that can be run on multiple platforms and has a system of commands that work similarly to a programming language.

I don't know what your goals are, but you might want to take a look at R as well.

S.A.S. has a totally different meaning in the Navy.

This course is infuriating! :mad:

All of the skill tests really test my ability to type JCL, not how well I understand SAS. I failed the first skill test because I could not psychically guess how the person who wrote the test wanted the JCL to be indented. I had all of the correct information and the JCL would run, but I didn't have the spaces in the right places to make it look pretty, per the eye of whomever wrote the course.

As for R, I'm not sure what that will get me. SAS is what we use in-house for analytics, so knowing it can get me more work in that area.

As long as it's not "Opsware/HP SAS." If it is run, don't walk away from it.

legion - if you're stuck, gimme a PM - I program in SAS (though I prefer REXX) and am pretty well versed in JCL as well.

-Z

What's your back-end?

I'm learning SAS for the zOS (used to be called OS/390).

I'll slog through it as usual. It will be somewhat funny if I "fail" this class because I don't indent the same as the person who wrote the course.

z/Os 1.9.
Mainframe - 'cause that's how I roll... :)
-Z

Well, I finished 7 segments out of 26 today. The first segment had 151 slides, the others had around 75 each. The "skill tests" consisted mostly of how well I could guess what the course-writer wanted as an answer, as when I typed something logically correct that would work, it was often marked "incorrect". I found myself retaking each skill test at least twice.

I love it when you guys talk dirty. :p

It all depends on what you're actually using it for. Is this a canned self-pace or instructor led? Either way, if they expect you to adapt to their style that should be clearly spelled out up front.

I don't know how much SAS has changed over the years, or what modules you are covering? I did all my Masters work in SAS and learned it by reading the books cover to cover (I know, I was crazy!). That really paid off later though. When I needed to do something I knew that there were usually several ways and could jump right to those sections for more details. The coding is just like anything else, fairly siimple. As I remember the more difficult parts were in interworking with the underlying OS and/or with other software and systems.

JCL on the other hand.. Ugh! Started on the "Big Iron", ended up on DEC/VMS & HP/UX and some PC/SAS.

I'm not using it for anything in particular at the moment.

The ironic thing is that I've already converted a SAS program into an AION program and I was reading SAS code without really knowing it. I actually wrote a small program that can convert SAS code to AION code.

At this point, I'm just looking for things to keep me occupied and SAS seemed interesting. Like I've said before, my management is intentionally keeping me with "excess capacity". I've already taken every DB2 class the company offers and could step into some DBA-type work if I was allowed. (The project I'm on is the number one priority for the company right now, so I'm not allowed to do "less important" work.)

The analytics stuff does seem interesting. In a past life I was an actuarial intern. (How I landed that job without a pure math background is another story.) Right now I'm at the end that does stuff. It would be a nice change of pace to be at the end that discovers stuff and tells other people how to fix it. ;)

Chris, my experience with SAS is somewhat dated (OK, I'm an IT dinosaur :)), but used SAS quite a bit much earlier in my (now extinct) IT career. SAS isn't difficult, but seemed "different" from almost all languages that I've used (more than I care to think about). I personally didn't care for the programming aspects of SAS (I'm old school, and prefer to flip bits rather than high level languages), but it is a VERY powerful statistical analysis system (imagine that... S(tatistical) A(nalysis) S(ystem)), and for some tasks, is a great "tool" for achieving the desired results. Prior to the advent of PCs, I utilized SAS to develop a statistical and graphical representation of "my" network's performance (I was a communications systems programmer/networking guy), and as others have alluded, simply focus on the task at hand and you won't have any problems. I've always been a RTFM kind of person, and prefer to learn things on my own (rather than follow a "course"), so I'd just pick up a manual and go for it. FWIW, I think learning DBs is much more likely to provide a better return on your "knowledge base" as your career progresses...good luck!

When I learned SAS at USF it started to click when us classmates were able to get together in lab. The TA and others present often makes the difference. Once it clicks for all of you each will be able to run faster together.

I can't believe SAS is still around!

Good Luck - it was a fabulous stat. pkg. (in the '70's).

I prefer the British version that drops in unannounced at 2 AM and cleans house.

This SAS class isn't getting any better. The class sometimes contradicts the skill tests. On some skill tests, I've typed in exactly what it said it wanted, and it didn't work (it will tell you the answer after three wrong guesses--and what it tells you is often wrong).

It's a strange language. Considering that I've worked in VB6, COBOL, and Aion, SAS is nothing like them. It makes you do things that would be very bad in other languages (like having multiple variables with the same name).

I won't "get" it until I do some actual work with it.

Actually, the job I'm angling for is to support the analytics systems--I wouldn't be using the language but supporting the databases that the SAS users pull from.

I remeber SPSS in my early college days. That was 70's cause it came straight from the mainframe..

Don't kid yourself, SAS still thrives (although I haven't used it in years). My first exposure was also back in the late 70s, as SAS was initially developed at NC State a few years earlier. FWIW, while "under the radar" for most, SAS has to be one of the very best companies in the USA to work for, bar none. I interviewed there after I left IBM many years ago, but alas, they were looking for a software engineering heavyweight, and I was still pretty fresh out of college and lacked the requisite experience...my loss :)! Chris, trust me, you will "get it" once you forget about the "course" and just dig in to accomplish a task at hand...good luck!