I couldn't find another note than the one Duke already mentioned. Did you read that? "One workaround for this problem is to define the entire expression as a macro earlier in your job definition, then invoke this macro in the Expression Builder window." Not that this is pretty but: You could assign the whole expression to a macro var in the pre-processing part of your job and then just call this macro var in the expression builder window (I think that's under advanced where you can write your own expression - click, click...) You have always the possibility to open a support track with our friends from SAS Tech Support: http://support.sas.com/ctx/supportform/index.jsp HTH Patrick ... View more

Does this the job for you? data have; do i= 2 to 14,16,17,41; _TEMG001=i; ma_pd_ind='PD'; month=7;output; _TEMG001=i; ma_pd_ind='xx'; month=7;output; _TEMG001=i; ma_pd_ind='PD'; month=10;output; end; run; proc sql noprint; select distinct _TEMG001, cats('work.temp',_TEMG001), cats('when(',_TEMG001,') output temp',_TEMG001,';') into :IndList separated by ' ', :OutDS separated by ' ', :SelectDs separated by ' ' from have order by _TEMG001; quit; %put OutDs =%bquote(&OutDs); %put SelectDs=%bquote(&SelectDs); data &OutDS; set have; where ma_pd_ind='PD' and month<10; select (_TEMG001); &SelectDs otherwise; end; run; ... View more

Just two more variants how to do it: HTH Patrick /* variant 1: %do %while with %scan */ %macro CreateTempDSVers1(ind=); %let i=1; %do %while(%scan(&ind,&i) ne ); data TempDS%scan(&ind,&i); var='hello world'; run; %let i=%eval(&i+1); %end; %mend; %CreateTempDSVers1(ind=2 3 4 5 6 7 8 9 10 11 12 13 14 16 17 41) /* variant 2: Call Execute */ %macro CreateTempDSVers2(ind); data TempDS&ind; var='hello world'; run; %mend; data _null_; do i=2 to 14,16,17,41; call execute(cats('%CreateTempDSVers2(',i,')')); end; run; ... View more

That worked. Thanks data _null_ ! Do you also have an explanation why this %unquote is needed? I don't get it. Cheers, Patrick .... Think I got it! And I thought always that %' means "masking" the following character for macro resolution. I was never aware that this is a "quoting". Learnt something 🙂 Message was edited by: Patrick ... View more

I can only agree with Linus that there should be a file specification. Browsing the Internet a bit it seems that there might be ways to determine (sometimes!) what encoding is used: http://codesnipers.com/?q=node/68 But also a interesting task to determine programmatically the encoding I think it would be the wrong approach. What you need is a defined interface (file specification). Cheers, Patrick ... View more

SAS EG is "only" a client. The code is always processed on the SAS Workspace Server. There can't be such a thing like a EG modification allowing to run SAS code which would run otherwise. How does this EG generated SQL code look like? And does it make sense from a business point of view? Cheers, Patrick ... View more

Using %include means that you have to look at your program as if it would be one big bunch of code. It's the same like having all the code in one single file. It will therefore depend on the error in the included code whether SAS can recover from it or not (i.e. a unbalanced quotation mark would be "desasterous"). %syserr is an automatic read-only macro variable. The following gives you some more information about error handling: http://support.sas.com/onlinedoc/913/getDoc/en/lrcon.hlp/a000993436.htm If you want your jobs to run independently together with some error handling you might want to look at commands like 'x', 'system' or 'systask' - or consider to use a scheduler. HTH Patrick ... View more

O.K. - But why then works case1 and case4 doesn't? The only thing I can think of right now would be 'precision'. ... View more

Hi You're always using "Base SAS" no matter how you execute the code. If this is a macro variable created in a autoexec then there might be a difference between a SAS DI session (like SAS EG created by the Object Spawner) and a PC SAS session - and you might not have fully access to this macro var from within the session (as soon as you batch the job you will have full access). I can be wrong here but I think that strings assigned to macro vars are always stripped of leading and trailing blanks. What could be is that you're string is quoted - and an %unquote() could solve the problem. Have a look at the following example: %let TESTVAR1= xxx y ; %put TESTVAR1 unquoted: Length is: %length(&TESTVAR1), Value is: &TESTVAR1; %let TESTVAR2=%quote( xxx y ); %put TESTVAR2 quoted: Length is: %length(&TESTVAR2), Value is: &TESTVAR2; %let TESTVAR3=%quote( xxx y ); %let TESTVAR3=%trim(&TESTVAR3); %put TESTVAR3 quoted/trim: Length is: %length(&TESTVAR3), Value is: &TESTVAR3; %let TESTVAR4=%quote( xxx y ); %let TESTVAR4=%unquote(&TESTVAR4); %put TESTVAR4 quoted/unquoted: Length is: %length(&TESTVAR4), Value is: &TESTVAR4; ... View more

That looks like a bug to me. Report it to SAS TechSupport. data c; y=-3.1**-3.1; put 'Case 1: ' y=; x=3.1; y=x**-3.1; put 'Case 2: ' y=; x=-3.1; y=-3.1**x; put 'Case 3: ' y=; x=-3.1; y=x**-3.1; put 'Case 4: ' y=; run; ... View more

Hi Below a code example to get what you asked for. Have also a look at Proc Mixed and the like - may be that's in the end what you're aiming for. HTH Patrick data have; do CatVar='a','b','c','d','e','b'; output; end; run; proc sql; create view Vhave as select Distinct CatVar from have order by CatVar; quit; proc transpose data=Vhave out=TransHave; var CatVar; run; proc summary data=TransHave; class col:; output out=CombHave(where=(_type_ ne 0)); run; data want; set CombHave; CombVar=cats(of col:); run; proc print data=want; run; ... View more

As Cynthia wrote already: Get rid of the quotes! The way you do it your macro var &dataview resolves to the quoted string 'TIMD.v_Feed_Results_INT' and not to the unquoted string you're using: TIMD.v_Feed_Results_INT - you're therefore comparing apples with oranges. HTH Patrick ... View more

Hi coba Have a look what Proc Summary/Proc Means can do for you. To get a more specific answer you have to provide much more information: What do you have, what do you want - and best some code creating some sample data. Cheers, Patrick ... View more

Hi Kumar This 'date' thing is a very common cause of confusion. There is a difference of what you see (what you see is what format is applied on a field) and what field type data are stored in. If the date in your database is already in a field of type 'date' or similar then you won't have problems - just access it with SAS. It the date is stored as a character string then you will have to tell SAS how to read it - that would then be a Informat. SAS would then convert the string to a SAS date (that's a number). To look at it this SAS data you then best apply a Format to the variable (else you just will see a number). HTH Patrick ... View more