Putting "$" before a format name means the variable that you are associating that format with is character. ... View more

"Cards" isn't needed but is useful in developing and testing code. For your actual data look into using an infile statement. ... View more

I really only know the very basics of SQL and it sounds like you might need to develop some complex subqueries (though it may be simple and I just don't know SQL well enough to see it) I would listen to ssb's suggestion, he seems to know his sas. ... View more

Intersect and except are for common rows/observations, not variables/columns. ... View more

On second thought, in step 2 it would probably be better to set col(i) to . ... View more

Not sure if there are any functions to make this easy but a brute force way using arrays is. 1 make an array of col1-col100 2 if col(i) gt amount then col(i)=0 3 closest=max( of col1-col100) but this is only good if there is atleast one value less than amount and I understand you correctly about wanting the closest value without going over. Message was edited by: RickM ... View more

You really need to work out your logic in that data step. Have you even writen anything for proc tabulate? ... View more

Your code does nothing but read in data and print it (it also looks like that proc sort would fail). There is no creation of a file that holds both periods. You need to take an hour or two and study the set and merge statements and see what each does. If you did that then you wouldn't have nearly half as many questions as you do. ... View more

You are missing something in your data step ... View more

First, you really need to start researching somethings on your own. I just typed "sas scatter matrix" into a search engine and found the answer in less than a minute. Second, the answer depends on which version of SAS you have. In 9.2 it is easy. In earlier versions, not so much. ... View more

You could do something like creating an index variable that goes from 1 to n to replace x and then in an axis statement use the value= option to specify the major tick marks as the actual x-values. This is a bit tedious and involves a bit of hard coding but if the data set is relatively small and this is a one time graph it may be a good enough quick fix. Annotated data sets would probably be better but I don't know much about how to use them. ... View more

the where and keep options should be inside one set of parenthesis. See the following: http://support.sas.com/documentation/cdl/en/lrdict/62618/HTML/default/a001000998.htm ... View more

Are you putting the where and keep inside of one parenthesis or two? ie. (where=(schnum='006') keep=schnum permnum_s last_s first_s middle_s grade_s efaprim engprof_s advisor_s ela_sort math_sort science_sort social_sort) or (where=(schnum='006')) (keep=schnum permnum_s last_s first_s middle_s grade_s efaprim engprof_s advisor_s ela_sort math_sort science_sort social_sort) it is more helpful to see the code when it failed (and preferably in the log) than when things are comented out so it doesn't fail. ... View more

You really need to start looking up things for yourself. You are never going to learn how to do this on your own if you keep asking people to explain every little detail/solve your coding problem. Google proc sort and I am sure you can find lots of info and explanations. ... View more

Rather than just saying "it didn't work" you should include the relevant portion of the SAS log. if that is the exact code used then you need a space between period2A and out= in: proc sort data = period2Aout = sc.period2A; This would likely cause SAS to not even run the proc sort. ... View more