Can't answer all your questions, but the following might help: - Proc model can do just about everything that syslin can (ie it does non-linear models as well as linear models). The main difference is that Syslin has simpler syntax. - I think your panel data model is a fixed effects model. These can be calculated in several ways (other than using proc panel or glm absorb). Eg by actually including a dummy variable for each fixed effect (eg firm) or by transforming the data so they are deviations from within-firm means. You should look at textbook like Wooldridge's "Econometric Analysis of Cross Sectional and Panel data" for an explanation of this (I just googled it, there seems to be a PDF available via google scholar). The first of these methods (maybe both) will work with unbalanced panel data, and then you use proc model or syslin to do the 2sls. - Overidentifying test. I've never done this (finding one valid instrument is hard enough, let alone two). The idea is that it tests whether both instruments give the same result. You might be able to test it by similtaneously estimating two equations (with differrent instruments in each) and then testing for equality of coefficients - but I'm just speculating here. - Wooldridge refers to a method by Arellano to calculate robust standard errors for panel data, but I don't think is available in any canned routine. ... View more

Actually, I've discovered the scripting is not that hard. A batch file with the following single line seems to do the trick "c:\program files\SAS\SASFoundation\9.2\sas.exe" %1 -nologo -batch  -log "%~dpn1.log" -print "%~dpn1.lst" ... View more

I knew about the solution proposed by FriedEgg, however it doesn't fully solve the problem. I want the log file to automatically have the same name as the submitted program (apart from the extension). (The approach suggested by Doc@Duke doesn't work in Windows 7 or Server 2008 - the ability to configure file type associations has been removed from the user interface) I presume there must be a way to create the log file name and location within a batch file using some scripting language, but surely there must be a way of asking SAS to do this (since that is what it normally does). ... View more

Several ETS modules can do 2SLS - search for 2SLS in help. But do you have a suitable instrument? You cannot test the validity of an instrument - this must come from theory. (If you have more than on instrument you can do a test that can reject the hypothesis that they are all valid instruments, but this is only a limited test of validity). A valid instrument must - be correlated with CEO stock options (the F or R2 of this equation is a simple test of the instrument strength), and - not have any causal association with risk-taking, except via this association with CEO stock options. The second requirement is usually quite challenging. Re heteroscedasticity, there are a few options. This excerpt from the proc model help might help get you started. "Note that White’s test in the MODEL procedure is different than White’s test in the REG procedure requested by the SPEC option. The SPEC option produces the test from Theorem 2 on page 823 of White (1980). The WHITE option, on the other hand, produces the statistic discussed in Greene (1993). " ... View more

Is SPDE part of base SAS or is it licenced as a separate product? How can I tell if I have a licence for it? ... View more

Thanks for the suggestions. I hadn't seen the 2010 paper - it is looking close to what I want. Shame this feature isn't inbuilt into the SAS datastep code. The 2010 paper suggests putting the 'normal' datastep code into a separate file so it can be read by multiple SAS processes. It would be neater if this code were in a macro in the main program (like the the SAS bootstrap macros) - that way I could also use global macro variables and macros within the data step. To do this, I guess I would need to pass the global macro environment of the main process (eg defined macros and global macro variables) to the spawned processes. Is this possible in SAS? ... View more

I was suggesting changing the following line %let newvarname = %substr(&varname,2); to do whatever it is you want to do. Something like the following, if I understand your requirement correctly (untested) %let newvarname = %substr(&varname,1,1) %eval(%substr(&varname,2,1) +5) %substr(&varname,2); ... View more

Here is another approach. This macro removes the first character from almost all the variable names in a file. You can easily modify to do what you want. %macro HILDARenameStripFirst(dataset); /* Generates a rename statement of the form Xvar1=var1 Xvar2=var2 etc where XvarN includes all variables (except Xwaveid). Usage example : data long2; set hilda.rperson_a (rename=(%HILDARenameStripFirst(hilda.rperson_a)) ); run; BB. Aug07. I used SAS paper 107-28 by Derek Morgan as inspiration. -------------------------------------------------------------------- */ %let DS = %sysfunc(open(&dataset,i)); /* open dataset to get variable names */ %if (&DS = 0) %then %put %sysfunc(sysmsg()); /* if cant open */ %else %do i=1 %to %sysfunc(attrn(&DS,NVARS)); %let varname = %sysfunc(varname(&DS,&i)); /* get the ith variable name */ %let newvarname = %substr(&varname,2); /* strip off the first character */ %if %upcase(&varname)^=XWAVEID %then %do; %* output code here; &varname=&newvarname %end; %end; %let CloseCode = %sysfunc(close(&DS)); %mend HILDARenameStripFirst; ... View more

Sorry, I should have specified the system. No I'm not using EG. I'm using SAS 9.2 (TS1M0) on Windows XP. I'm pretty sure I'm using the default setup. However, your suggested code is very helpful. Eg if I go [pre]ods _all_ close; ods msoffice2k; - tabulate statements ods msoffice2k close; [/pre] Then my Results Viewer window is in the desired format !! The only problem is that this creates a html output file in the same folder as my sas program instead of the work directory - I guess I can put a file statement to relocate it. Now I'm wondering how to make this the default. ... View more

Thanks Cynthia for clarifying the difference between a style and destination. However, you say that "The results window or the LISTING window is a "monospace" destination". This is not the case on my system. The Results viewer window is html formatted output (the output window is monospace). Similarly, you state that "For tabular output, the LISTING destination does not support the use of STYLE templates to control the look and feel of the output.". But presumably this is not the case for the "Results viewer" window (does this count as a destination?) - since under the Results tab in Preferences I can choose a style for the results. So I suppose my question amounts to asking whether I can customize the Results viewer destination to make it like the msoffice2k destination. I'm guessing the answer is again No. ... View more

Thanks. Yes, I can see that I can avoid the problem by not showing 'year' where it normally appears and putting it in the box. However, this is a bit of a kludge, and is not very convenient for more complicated tables (where having the variable name or label in place is convenient). As I noted in my original post, the command 'ODS msoffice2k' can be used to create an output excel file (actually an html file) which doesn't have this problem. Is it possible to have this ODS style available in the results window? ... View more