Not sure what you're after but you can always query dictionary.macros (or sashelp.vmacro). http://www.codecraftersinc.com/pdf/DictionaryTablesRefCard.pdf HTH Patrick ... View more

Hi Liv What your code shows is that your variable DIAG is actualy numeric. The statement 'PUT(DIAG,8.)' uses the numeric format w.d. The result of this 'put' is a character string without leading zeros. As Geniz demonstrates: If you want leading zeros you have to use the Zw.d format; 'PUT(DIAG,z8.)' No clue how your outer put statement using $&FMNAME.. will digest this string with leading zeros. Does this format expect such a string? HTH Patrick ... View more

I think the only problem with this code is exactly what the error message expresses. There is no matching '%if' case for the '%else' case. ..... %else &PoolAdj = &PoolAdj * 0.97; ; %else %if &effdate > '09May2002' %then .... Formulate it this way and it should work: ..... %else &PoolAdj = &PoolAdj * 0.97; ; %if &effdate > '09May2002' %then .... As all conditions are on the same level you will have to check that the %if statements are exclusive to each other or your logic will be flawed. From a programming perspective I consider a %do...%end structure as easier to read and maintain. HTH Patrick ... View more

Hi Thomas Could it be that you're just after that? %MACRO start(Zahl); proc sql; select ID, VERSION into :ID, :VERSION from myLib.mytable where LOOK_HERE = &Zahl. AND LOOK_THERE = 'T'; quit; data test_port; test_601_ID = &ID.; test_601_VERSION = &VERSION.; run; proc print data = test_port; run; %MEND start; %start(601) BUT - Then one would may be write it this way: %MACRO start(Zahl); proc sql; select ID as test_&Zahl._ID, VERSION as test_&Zahl._Version from myLib.mytable where LOOK_HERE = &Zahl. AND LOOK_THERE = 'T'; quit; %MEND start; %start(601) HTH Patrick ... View more

Hi Geniz But this was exactly what I was talking about: SAS generates some SQL code and sends this SQL to the DBMS - it just depends on how the clauses in the SAS code are done for SAS to be able to generate efficient SQL code sent to the DBMS. Pass-Through SQL is of course always a way to send exactly what one wants - but it also means that one has to get into the different SQL flavors. I find it often much more efficient (from a programming point of view) to use PROC SQL with a sas libname and then to control what kind of SQL SAS sends to the DBMS (looking at the log using the options I've posted). And another reason not to use pass-through SQL: If the DBMS changes all pass-through SQL code has to be changed. If the technique was using SAS libnames then only these libname definitions have to be changed. Well: Just an opinion. I actually used already a lot of pass-through SQL. I just think it's always a second choice. Cheers, Patrick ... View more

Hi Daniele In the end-of-the-day also the data step approach results in some SQL code sent to the SQL server. To see what code is sent to SQL and executed there the following options can be helpful: options sastrace=',,,ds' sastraceloc=saslog nostsuffix; The most time consuming part will be I/O. It also depends if you load the whole table or only a part into SAS. If it's only a part of the table then make sure that the selection is done on the SQL side - and do not download the data first to SAS and then select. - The options I've sent you will tell you if SAS is handling things. It often helps to avoid SAS specific functions for data selection - as SAS often can't resolve such functions into SQL statements (and therefore selects only later). HTH Patrick P.S: I know that there are quite a bit of SAS papers about performance. Just too lazy right now to do this search job for you 😉 ... View more

Hi Jeff The array statement you use in your code is not correct (have a look at the log). To get the desired result you have to write something like: array thenums{3} num1-num3 ; You can't initialise array vars using other variables. An array is created and array elements are initialised during data step initialisation - but you have only during data step iteration values for variables (and that's too late). You don't need the variables a1-a3. If you use the array statement as above you're getting the expected result. What you're doing is initialising the variables a1-a3 in the following way: a1='myvar1'; as value, the string 'myvar1' passed to the variable a1 a2='myvar2'; ...... ..... And then you're using the format z3. on a string which is not a number. That just can't work. I was quite astonished that SAS didn't throw a ERROR when I was running your original code (in SAS 8.2). By the way: Running a Job in SAS DI and in SAS EG creates sessions exactly in the same way (using the SAS object spawner to create a session on the SAS workspace server). PC SAS works a bit different. You run jobs in DI normally only during development in a session. SAS DI is a development tool. The final jobs are most of the time run in batch. HTH Patrick P.S: You don't have to use 'putn' and 'putc' in SAS Base. The 'put' statement works for both numeric and character. P.P.S: data postfrank; set frank; array thenums{3} num1-num3 ; myresult=put(thenums(_N_),Z3.); run; Hope you're aware that an additional line of data would lead to an error 'out of array subscript' SAS code generated by DI is often quite hard to understand. You best get the DI project and look at the job flow from within SAS DI to understand what's going on. Message was edited by: Patrick ... View more

Hi Rao I can't promise that this works - but you could give it a try: attach =("datasetname" ct='text/plain' extension="TXT" encoding='ebcdic037' outencoding='latin1' ) http://support.sas.com/onlinedoc/913/getDoc/en/lrdict.hlp/a002058232.htm Cheers, Patrick ... View more

Hi Chris Tks for the info. Cheers, Patrick ... View more

Hey Chris Tell me more! Could you point me to some docu/papers please? I'm an experience SAS'er (I think so at least) and I have some experience with VS2005. What you mention here sounds very interesting. Cheers, Patrick ... View more

Just to be careful: upcase(name) not lt "F" ... View more

data want; infile datalines; input MyDateTimeVar ANYDTDTM.; put 'As a number: ' MyDateTimeVar= ' Formatted: ' MyDateTimeVar= datetime21.; datalines; 2008-09-06-03.30.45.101010 ; HTH Patrick ... View more

As Linus said: You will have to specify a bit more what you have and what you want to achieve in order to make us understand. Just some ideas: Have a look at the array statement, Proc Transpose, Proc Format and may be hash tables - Proc Format and Hash Tables would be used for table lookup. Cheers, Patrick ... View more

Hey yes, nice proposition Doc@Duke And if urchin wants to use this generic dataset names later on he/she could do something like this: data; a=1; run; %let ThisIstheFirstDS=&syslast; data; a=2; run; %let ThisIstheSecondDS=&syslast; proc print data=&ThisIstheFirstDS; run; Cheers, Patrick ... View more

Hi rao A statement that I've seen working sending attachements from a Mainframe was: attach =("datasetname" ct='text/plain' extension="TXT") If it's 'only' about special characters: If you dare not to be part of the (US-) English realm in the world then I remember quite a bit of problems with finding the accurate translation table for EBCDIC/ASCII conversions. Does it work in 'normal" email text with the translation of special characters? HTH Patrick ... View more