I know exactly what you mean. I prefer to work in base SAS, but was forced recently to migrate to EG. I found this on Google, not sure if it works : dm 'clear log'; ... View more

@milts Please don't post new questions to old tracks but create a new question and reference the old track. ... View more

You will have a timing issue when using a macro %let statement in a data step. The %let statement will get executed before the data step so it won't be part of the data step iteration and you also can't pass a SAS data step variable to the %let statement. There your "i" will simply be interpreted as the character 'i'. Not sure why you need a macro at all but as this is a code snippet reality might look different and there are good reasons for a macro. Below should make your code snippet work: %macro DefineInputArray;       ARRAY BYLINE(50) $16.  BYLINE1 - BYLINE50;    array iVal (50)    %do i=1 %to 50;      %let iter = %eval(1000+(&i-1)*1000);   iVALUE&iter    %end;     %str(;) %mend; data sims;   set data_inputs;   %DefineInputArray;   do i=1 to dim(BYLINE);    BYLINE = iVALUE;   end; run; ... View more

ballardw make a very good point about setting date/time lengths. The way you have the length statements written, e.g.: length time 6. time1 6.; suggests that you may be confusing format specifications with length specifications. In a length statement, do not include a period after the numerical length specified. If you actually wanted the time and time1 variables to be internally stored as 6 bytes, specify: length time 6 time1 6; without the periods. ... View more

The LIKE operator uses underscore to match any single character.  So like '%_DUP' would match 'A_DUP' and 'ABDUP'. By escaping it you can search for the underscore character itself. ... View more

Yep, fun and games with long fields. I found it better to use pass-through sql than the libname statement. I download lots of tables using pass through SQL with the database dbmax_text=32767 option. I use global macro variables for the database log on information: &GLB_USER &GLB_PASSWORD &GLB_DBname &GLB_DSN_NAME &GLB_ServerIPaddr ** macro to pull all the data from the table ; %macro SQLPullDataBig (outputdataset,SQLtableName,DatasetLabel); PROC SQL; CONNECT TO ODBC AS ODBCref   (NOPROMPT="UID=&GLB_USER;PSW=&GLB_PASSWORD;DSN=&GLB_DSN_NAME; SERVER=&GLB_ServerIPaddr;DATABASE=&GLB_DBname"  dbmax_text=32767); Create table &outputdataset(compress=binary label="&DatasetLabel") as Select * from connection to ODBCref ( Select  * From &SQLtableName ); quit; %mend; %SQLPullDataBig(libName.outputDatasetName,SQLtableName,Label for you dataset); Now when the fields are longer than 32,767 characters life get more interesting as the only way seems to be to chop the field up and download from SQL in sections. I have SAS code which does this by working out the maximum length of the field and generating the download code as required. If anyone is interested. ... View more