That's the issue: NOTE: SAS went to a new line when INPUT statement reached past the end of a line. Use TRUNCOVER. HTH Patrick data rmatrix (type = distance); infile datalines truncover; input name $ _1 _2 _3 _4 _5 _6 _7 _8 _9 _10 _11 _12 _13 _14 _15 _16 _17 _18 _19 _20 _21 _22 _23 _24 _25 _26 _27 _28 _29 _30 _34 _32 _35 _36 _37 _38 _39 _KG1 _KG2 _KG3 _KG4 _KG5 _KG6; datalines; 1 0.000 ... View more

What if: - you give us a working test dataset (valid input statement). - you give us an example showing based on the testdata showing how the desired result should look like. ... View more

What you ask for can be done but needs quite a bit of macro coding. At least I can't think of an easy way to do it. I can't help but thinking that there must be another approach for your problem. It's normally not a good idea to create a lot of datasets. Can you describe what the problem is you want to solve? Regards, Patrick ... View more

Hi Thomas "When I run the job via an %include from another job...' Does that mean you deploy the job and then in another job you're having a %include on the deployed job? If so: this wouldn't be the way you should do it in DI. Better use a loop control and embed the first job as inner object. You have to look at the code/log to see what's going wrong. One reason could be that you use the %include statement within a macro and so all macro vars created by the pre-processing step of the included job outside of a macro are "suddenly" defined inside of a macro - they would become local instead of global (and that's one of many reasons why you should do things the DI way before writing user written code). HTH Patrick ... View more

Thanks Proccontents. I was just going to write an answer before I read your post. http://groups.google.com.au/group/comp.soft-sys.sas/browse_thread/thread/382ea2336c72e44/190b2aef220ffffa?hl=en&lnk=gst&q=mahesh#190b2aef220ffffa ... View more

Hi Samuel That should do the job. HTH Patrick data have; infile datalines truncover; input var1 $1-2 var2 3-4 ; datalines; a 1 2 e 4 ; proc sql noprint; select 'sum(missing('||name||')) as '||name into :SelList2 separated by ', ' from dictionary.columns where libname='WORK' and memname='HAVE'; create table want as select &SelList2 from have; quit; title 'N Missings per Variable'; proc print data =want noobs; run; ... View more

Just a version using PROC SQL. You could also use the data set "department" to create a format (example in SAS OnlineDoc for Proc Format) and then apply this format in the Individuals table on the field "DepCode". If you need the department names for printing only this would avoid to create redundant data in a second table (using a format statement). If you still would want to create a new variable: DepartmentName=put(depcode,depfmt.); HTH Patrick data department; depcode=1; department='a';output; depcode=2; department='b';output; depcode=3; department='c';output; run; data individuals; IndCode=1;DepCode=1;output; IndCode=2;DepCode=3;output; IndCode=3;DepCode=2;output; IndCode=4;DepCode=5;output; run; proc sql noprint; create table individuals2 as select ind.*,dep.department from individuals ind left join department dep on ind.depcode=dep.depcode; quit; proc datasets lib=work nodetails nolist; delete individuals; change individuals2=individuals; quit; proc print data=individuals; run; ... View more

Do you know what datepart the timestamp part of the filename you want to read has when you run the code - or is this something you would have to determine as well (i.e. by reading the file with the most current date)? ... View more

I think the code below should do the job. Use the translate version if you want to keep as many blanks as there were 'z' - else use the compress version. HTH Patrick data name; input id$ name$ add$; array vars {*} name add; do i=1 to dim(vars); if compress(lowcase(vars{i}),'z')='' then /* vars{i}=translate(lowcase(vars{i}),' ','z');*/ vars{i}=compress(lowcase(vars{i}),'z'); put vars{i}= @; end; put; cards; mailtohim nani mainroad zzzzz zzz street raju zzAzz zzzzzzzzzzzzz zzzzzzzz zz indi run; ... View more

Hi Thomas Forget about formats when it comes to comparisons. Formats are used only for WRITING data - but calculations/comparisons are always done with the full precision. As this is user written code you can't expect DI Studio to do anything for you. And even if it wasn't user written: DI Studio does nothing else than generate SAS code - so look at the generated SAS code if you want to know what's going on. Seems as rounding the values before the UNION would be a good idea. Why not using a round() function in the select part of the SQL statement? May be that could even be implemented in a standard SQL transform (I would have to try it but I expect it to be possible). Just to show that round() works: data a; do i=1 to 5; b=i; output; end; run; data b; do i=2,3,5; b=i*1.00002; output; end; run; proc sql; select * from a union select i,round(b) from b ; quit; HTH Patrick P.S: I think it's round() you need. Have a look at the SASOnlinedoc to get the exact syntax for the precision you need (it will be something like: round(variable,0.0000001) P.P.S: The question is if the values with lower precision are rounded or truncated. You would want to do the same to the values with higher precision. If it's truncation: Use either a put/input combination or multiply by 10 power the number of digits behind the comma, use int() on the result, divide by 10 power the number of digits behind the comma. ... View more

Found something: http://support.sas.com/techsup/technote/ts654.pdf HTH Patrick ... View more

May be you use: population = sum(men,women); reason: a+b: if a or b is Missing the result will be Missing sum(a,b): Missings values are ignored, sum(a, ) resolves to value of a ... View more

Hi Deepu That's a nasty one! I remember that there is a very good SAS whitepaper or SUGI/SEUGI paper explaining why this can happen - but I just can't find it anymore!!! What I remember from this paper is that the cause of the problem is how numbers are digitally represented/stored in SAS vs. Oracle (or DB2) - and also under different platforms like Windows/Unix/zOS. It was very clear and obvious. I believe the solution was using the round() function when loading to Oracle - but I'm just no more able to recall the details. Let me know in case you find this paper. It's one I should store in "my box". Cheers, Patrick Just found this SAS note which points in the same direction. "endian byte order" seems to be a key word. Message was edited by: Patrick ... View more

Tss, tss... and what both solutions where missing so far is what I included now in the end of the code. Not very elegant - but it should work. data input; input year bank_ID cash_balance; datalines; 2000 1 0 2000 2 0 2000 3 0 2000 4 0 2001 1 10 2001 2 20 2001 3 0 2001 4 5 2002 1 15 2002 2 22 2002 3 5 2002 4 7 2003 1 0 2003 2 0 2003 3 0 2003 4 0 2004 1 10 2004 2 20 2004 3 0 2004 4 5 2005 1 15 2005 2 22 2005 3 5 2005 4 7 ; run; proc sort data=input; by bank_id year; run; proc format; value bool >0 =1 ; run; data lag; set input; by bank_id year; time_1 = input(put(lag1(cash_balance),bool.),8.); time_2 = input(put(lag2(cash_balance),bool.),8.); time_3 = input(put(lag3(cash_balance),bool.),8.); if bank_id ne lag1(bank_id) then time_1=.; if bank_id ne lag2(bank_id) then time_2=.; if bank_id ne lag3(bank_id) then time_3=.; run; Message was edited by: Patrick ... View more

If there is a SAS/Share Server and the library (the tables) is accessed via SAS/Share then this link might give you some helpful information: http://support.sas.com/onlinedoc/913/getDoc/en/shrref.hlp/a000433065.htm HTH Patrick ... View more