%quote(...) with %str(..) works -- also a technique I sometimes use is to simply append a period/dot character in the expression to remove the resemblence of a Boolean operator, such as shown below. Scott Barry SBBWorks, Inc. %macro x(state); %if %quote(&state) = %str(OR) %then %put yep; %else %put nope; %Mend x; %x(NE); %macro x(state); %if .&state = .OR %then %put yep; %else %put nope; %Mend x; %x(OR); ... View more

Yes, look at using FILENAME statement with PIPES, where you can supply a suitable command in quote marks for the OS to execute, such as an "ls" or "dir". This topic has been discussed in these forums and also you will find sample material / content at the SAS support http://support.sas.com/ website. Also, the SAS support website has SAS-hosted product documentation and there will be a useful "companion" guide for your particular OS environment. Scott Barry SBBWorks, Inc. Suggested Google advanced search argument, this topic / post: filename pipes os command read directory folder site:sas.com ... View more

Check your PROC SQL output (turn on OPTIONS MACROGEN SYMBOLGEN; to start) -- no selected rows, so &nt resolves to "0" (zero). Scott Barry SBBWorks, Inc. ... View more

Share what SAS code you have today that is not generating the expected output. Reply to your post and COPY/PASTE your SAS log with all code revealed. Scott Barry SBBWorks, Inc. ... View more

You will find an explanation in the SAS Language Dictionary discussion on the INPUT statement processing -- it has to do with how SAS reacts to an invalid-data or missing-data condition for the particular INFORMAT being used. Scott Barry SBBWorks, Inc. Suggested Google advanced search argument, this topic / post: input informat question mark site:sas.com ... View more

While you are running SAS programs in "batch" from a "SYSIN" source (depends on your SAS session/environment though), consider that there is current-environment information available, if you wanted to do something with that. Your interest/purpose is unclear, based on your post -- so what would you with the info and when would you want to know about the "event"?? Mostly you will find info about the SYSIN option in the particular SAS companion guide for your Operating System. Scott Barry SBBWorks, Inc. Suggested Google advanced search argument, this topic / post: batch program source sysin option site:sas.com ... View more

I tested the process posted by the OP. On Windows 7 Pro, when I double click a *.SAS named file, the SAS 9.2 system will open the file content (SAS program code) in a separate SAS Program Editor window. Scott Barry SBBWorks, Inc. Suggested Google advanced search argument, this topic / post: sas 9.2 companion windows dlgopen site:sas.com ... View more

Move your "filter logic" (grep component) to operate as part of the SAS DATA step. And, with that suggestion, have you at least verified the SAS FILENAME and associate specifications work correctly without the "grep" component? Scott Barry SBBWorks, Inc. ... View more

Your best option is to contact SAS tech support and open a track (support issue/contact -- from the SAS.COM support website) to report your problem symptom condition for assistance and guidance. Scott Barry SBBWorks, Inc. ... View more

Honestly, Ksharp you need to sharpen your mouse-cursor, given recent inaccurate post-replies on the forums here. As mentioned by polingjw, a TITLE statement can be conditionally executed in various ways, one showed was with a MACRO invocation, using PROC SQL to detect a condition, setting a macro variable indicator, and testing that indicator to determine code-path. Also, consider the TOP "clause" equivalent, your SAS code post-reply provided no "group-level" TOP(nn) equivalent, only where your code generates observations that have the MAX(SALES) value, instead. Scott Barry SBBWorks, Inc. Message was edited by: sbb ... View more

Don't read too much into the diagnostic -- focus on the most basic of coding your PROC SORT statement -- refer to the DOC and you'll see the missing keyword parameter for specifying your "input" (and also optionally the "output") SAS file name. Honestly, this is simple desk-checking work while developing your SAS program -- abandon the macro to start, get some code working, and then decide if/when you need to use the SAS macro language. Scott Barry SBBWorks, Inc. ... View more

Share the actual SAS log with the specific error message revealed -- include all SAS program code revealed. You can do this with a COPY/PASTE into your next forum post-reply. Also add this statement to generate additional diagnostic message with all variable values displayed to the log: PUTLOG / _ALL_; Scott Barry SBBWorks, Inc. Message was edited by: sbb ... View more