About Kurt_Bremser

Kurt_Bremser · ‎07-04-2014

Since you try to read with the $256. format, every time you have a line in the input file with less that 256 characters, SAS skips to the next line, until there are enough characters on one line. Obviously you have "only" 66 lines in the input file with > 256 characters. You will find a NOTE in the log about this like "SAS went to a new line ...." You need Tom's truncover option to avoid this (default) behaviour, which is "missover".

Kurt_Bremser · ‎07-03-2014

Since you never actually call the macros, all your SAS system ever "sees" is OPTIONS MPRINT MLOGIC SYMBOLGEN SPOOL MACROGEN; DATA _NULL_; OPTIONS MPRINT MLOGIC SYMBOLGEN SPOOL MACROGEN; - keep your scopes in line (eg. if the DATA statement is outside a macro, the associated RUN should also be outside, and vice versa) - the macro processor is a generator of program text, it does NOT execute any statements. In your second macro, you have a completely meaningless statement: %if devmntmx > &THMVDEV %then %do ; output bvir_base; %end; In case the condition is not met, no output statement is generated. In that case, the data step will always output to the dataset named in the DATA statement, which also is bvir_base! But the condition will always be met, because the letter "d" is always higher in the collating sequence than any number. You most probably do not need the second macro at all, just do a standard data step comparison of devmntmx to &THMVDEV What you wanted to do looks like this to me: %let THMVDEV=any value that you want to test for; Data bvir_base; set pdb.bvir; where devmntmx > &THMVDEV; attrib cluster label='Cluster*id' ; attrib dlibseqn label='Dist Lib Seq num' ; attrib glibseqn label='Grid Lib Seq num' ; attrib machserl label='Machine Serial' ; attrib vdevinst label='Virt Dev Installed' ; attrib devmntav label='Avg Virt Dev Mounted' ; attrib devmntmx label='Max Virt Dev Mounted' ; attrib devavgdl label='Device Average Delay' ; attrib devmaxdl label='Device Maximum Delay' ; attrib devintdl label='Device Interval Delay %' ; * Thresh_Max_Vdev = 70; * Thresh_Max_Vdel = 10 ; Date = datepart(startime) ; Time = timepart(startime) ; format date date7. time time5. ; machserl = substr(machserl,4,5) ; run;

Kurt_Bremser · ‎07-03-2014

SAS/ACCESS(R) 9.2 for Relational Databases: Reference, Fourth Edition and http://support.sas.com/documentation/cdl/en/acpcref/63184/HTML/default/viewer.htm#titlepage.htm

Kurt_Bremser · ‎07-03-2014

You either connect to the sql database directly (using the appropriate ACCESS to ... module) or via ODBC, which requires ACCESS to ODBC. Either way, you need to install and license the respective ACCESS module. If you want to avoid this, you best set up an export procedure in the database and import the resulting file into SAS (once you have a valid structure, almost anything is possible in a data step).

Kurt_Bremser · ‎07-03-2014

Try this and see if it meets some of your requirements: data lookup; * this is your list with names; length name $20; input name; datalines; George Harry John ; run; data have; * this is the dataset having the field you want to explore; infile cards truncover; input line1 $100.; datalines; Some text that contains George Some text that contains Harry Some text that contains nothing ; run; data _null_; * build a piece of code dynamically; set lookup end=last; length commandstring $100; if _N_ = 1 then call execute("data want;set have;"); commandstring = "if index(line1,'"!!strip(name)!!"') ne 0 then count_"!!strip(name)!!" = sum(count_"!!strip(name)!!",1);"; call execute(commandstring); if last then call execute("run;"); run;

Kurt_Bremser · ‎07-02-2014

By default, PROC SUMMARY does not produce print output. Either use PROC MEANS or specify the PRINT option on the PROC SUMMARY statment.

Kurt_Bremser · ‎07-02-2014

Could you provide information about the data set and its variables, and the actual log?

Kurt_Bremser · ‎07-02-2014

The sasv9.cfg file only contains the configuration data for Base SAS. Your other applications have their own settings, usually found in Tools - Options. Web Applications must be configured on the respective server.

Kurt_Bremser · ‎07-02-2014

ACCESS to PC files is support for certain file formats typical on PCs, like dBase, MS Office and so on. If you want to connect (from SAS) to a data source using ODBC, you need ACCESS to ODBC. What is it that you want to connect to, anyway?

Kurt_Bremser · ‎07-02-2014

You most probably have not installed/licensed SAS/ACCESS to ODBC, or the installation has failed. If you enter "The ODBC engine cannot be found" in google, you will find several threads dealing with the same error condition, maybe one of those is helpful for you. The ODBC driver for SAS is a freely installable Windows driver that allows other SW (Office etc) access to any SAS data source (workspace server, SAS/SHARE, ..) via ODBC, so that is not a solution to your problem.

Kurt_Bremser · ‎07-02-2014

The question is, what do you want to do in Excel with that kind of data? Excel is a spreadsheet calculator and not a BI package, so you should use it for what it was designed for. Hint: A "sheet" is usually something the size of Legal or A4. The fact that MS tries to frankenstein Excel into some kind of database bastard by repeatedly increasing the maximum number of rows does not magically turn Excel into Oracle.

Kurt_Bremser · ‎07-02-2014

You absolutely need to avoid duplicate varnames in a data step w/ merge if you want to preserve the contents. The only vars that should be common across the input data sets are those in the by statement. So I suggest that you rename those variables that exist in more than one dataset to something that identifies the originating dataset, like merge .... dataX (rename=(var3=var3X)) dataY(rename=(var3=var3Y)) ... ;

Kurt_Bremser · ‎07-01-2014

Then you basically have to include the firmID in the by statements, extend the control string and compare for the right pattern(s) at the end.

Kurt_Bremser · ‎06-30-2014

I knew there was a DWO loop solution, just couldn't get myself to find it! But you need to compare >=2, or you will only catch three Ys in succession Edit: saw you already fixed it.

Kurt_Bremser · ‎06-30-2014

proc sort data=have (keep=director year) out=inter nodupkey; by director year; run; data want (keep=director); set inter; by director; retain control; if first.director then control = ' '; * six blanks; substr(control,year-&start,1) = 'X'; if last.director and control = 'XXXXXX' then output; run; Set macro variable start to a suitable start year.

Online Status	Offline
Date Last Visited	Tuesday