A SAS PROC SQL step generates the SAS automatic variable SQLOBS based on your query results. The value will be from zero to a maximum value for the observation count selected. Suggest a DOC review of the SAS SQL procedure and SQLOBS. Scott Barry SBBWorks, Inc. ... View more

The SAS support website http://support.sas.com is chock full of code samples and SAS documentation, which can be amazingly helpful with learning the SAS language to hone one's skills. Another option is to use GOOGLE.COM or another search engine to search the SAS.COM site for code snippets and SAS User Group SUGI/SGF technical papers on these and other SAS programming topics. Lastly, the SAS-L list archives are also a wealth of information for your benefit and ever-increasing knowledge opportunity. Scott Barry SBBWorks, Inc. http://support.sas.com/ ... View more

Here is some PROC SQL code I frequently use to generate a sorted variable list of periods (PDyymmdd -- output from PROC TRANSPOSE) as columns, output as a SAS macro variable. Do consider that there is a max length for a macro variable, which may limit use of this technique: data TEST_DATA; RETAIN PD200801-PD200807 2.2222 A1 'xxxxxx'; RUN; proc sql noprint; select name into :PDLIST separated by ' ' from dictionary.columns where upcase(libname) = 'WORK' and upcase(memname) = 'TEST_DATA' and upcase(name) like 'PD%' order by name descending; quit; %put sorted var list (descending): &pdlist; proc print u ; id a1; var &pdlist; run; Scott Barry SBBWorks, Inc. ... View more

Your computing OS and environment is unspecified. Consider the info in the SUGI/SGF paper below, on SAS/Connect, for remote or batch-script processing using SAS. Scott Barry SBBWorks, Inc. http://www2.sas.com/proceedings/forum2007/241-2007.pdf ... View more

The technique to use is with a DATA step that precedes the PROC PRINT -- you would add the NOBS= to a SET statement, and code an IF/THEN DO;/END; *AHEAD OF THE SET STATEMENT* to check your SAS variable supplied on the NOBS= parameter for a zero value, and then use CALL SYMPUT to set the macro variable. And remember to end your DATA step with a RUN; so SAS will compile the code. Important to understand here is that the macro variable is resolved by the SAS compiler, so your DATA step must complete, before you can test the SYMPUT macro variable. If you want conditional execution of the PROC PRINT, you will need to code a SAS macro to test the SYMPUT variable. Sample code below: %MACRO X; %* data step below purpose to generate test data. ; DATA test_file; AAA = 'BBB'; RUN; %* presume we will have data to process. ; %LET GOTDATA = 1; DATA _NULL_; IF OBSCOUNT = 0 THEN CALL SYMPUT('GOTDATA','0'); SET test_file NOBS=OBSCOUNT; WHERE AAA = 'AAA'; RUN; %IF &GOTDATA %THEN %DO; %* your conditional code goes here. ; %END; %MEND X; %X; Scott Barry SBBWorks, Inc. ... View more

Need to see some SASLOG session output with PUTLOG _ALL_; commands in order to understand your data conditions -- you also may find this debugging technique revealing as well. Also, you should confirm that SP1 is consistent in both input files, specifically, if a "formatted value" is being displayed for diagnosis, you may find that the "SAS internal value" shows that the two sources are not equal. Lastly, using the PUTLOG _ALL_; command will show the IN= variable values from your MERGE operation -- info that could be very revealing for your own diagnosis. Scott Barry SBBWorks, Inc. ... View more

From your recent post, you gave some indication that there is only one row and variable/column you wish to pass to another DATA step. So, yes, you can use CALL SYMPUT in "data step #1" to generate a SAS macro variable. And in "data step #2", you can use a RETAIN statement to access the macro variable, assigning a SAS data variable / column value, referencing the macro variable using double-quote marks in the RETAIN statement. Scott Barry SBBWorks, Inc. ... View more

You would get most effective feedback by sending the diagnostic output from your SASLOG to include a PUTLOG _ALL_; command revealing all variable values. Any other feedback is a virtual crap-shoot, especially given that we don't know what your input WORK.A and WORK.B variable values contains with each DATA step pass. Scott Barry SBBWorks, Inc. ... View more

Please share your code *AND* your SASLOG output (with all source code revealed). Scott Barry SBBWorks, Inc. ... View more

Possibly consider PROC FREQ with a CLASS ID X; and an OUTPUT statement but no VAR statement, and use the output variable _FREQ_ as your count of the unique ID and X combinations. Scott Barry SBBWorks, Inc. ... View more

It's unclear - your reference to "value label". SAS maintains variable labels and SAS member labels, but there is no "label information" associated with a given observation (row) within a SAS member. Can you provide more details about what you are trying to accomplish? Scott Barry SBBWorks, Inc. ... View more

Have a look at the (ID=n) parameter coded on the ODS HTML statement, permitting two different output destinations with a single PROC/DATA step execution. Scott Barry SBBWorks, Inc. ... View more

I tested very similar code on Windows and also on IBM z/OS mainframe, both are at SAS 9.1.3 Service Pack 4. The results are different -- Windows generates an EMAIL that is treated as text-format, not HTML, as you explained. I sent the same EMAIL from the IBM mainframe environment, and the EMAIL client read the content correctly, showing the HTML-rendered output. So, I do not have time to test it, but there is a SAS HOTFIX (maintenance) Bundle that applies on top of SAS 9.1.3 SP4 (HOTFIX E9BC05 for Windows, incorporated into HOTFIX bundle E9BX03, dated Mar 2008), and I do see where several SMTP mail issues are addressed (link to SAS support site provided below). You may want to investigate the maintenance, or possibly contact SAS support for more specific guidance, possibly even a circumvention. Scott Barry SBBWorks, Inc. ftp://ftp.sas.com/techsup/download/hotfix/e9_win_sbcs.html ... View more

Hello, I agree the SUBJECT is unrelated to the post content, so I will focus on the post content, not the SUBJECT. The code below demonstrates how to use the PUT function with assigning a SAS variable, representing your input and output file names. SAS code below uses the DO LOOP technique but without requiring macro language, only using SAS DATA step language to generate the SAS code. You have some choices with SAS -- depending on your SAS expertise using DATA step and MACRO language to generate (and execute) SAS code using SAS code. Here is one technique that does not require any MACRO language. Obviously you will need to fill-in your data-input and data-output coding portions. Suggest you take this template example, add your own code for the INPUT and OUTPUT processing, and come back to the discussion forum if there are any more questions -- very important to share what code you have in order to get the most valuable and meaningful feedback. Scott Barry SBBWorks, Inc. * One technique using DATA step logic to generate SAS code. ; * No MACRO coding involved -- for some, a good thing to consider. ; filename tempsas temp; /* temp file to store instream generated SAS code */ data _null_; file tempsas; do i=1 to 500; * build input file name string - demo shows suffix # 1 to 500, as in: ; * c:\data\InputFile_500.txt for illustration purposes only. ; length input_file output_file $255; input_file = "c:\data\DetailInputFile_" !! put(i,3. -l) !! ".txt"; output_file = "c:\data\MEANSOutputFile_" !! put(i,3. -l) !! ".txt"; put "filename MyInputData " input_file "; " / "DATA _your_sas_file_;" / "INFILE MyInputData;" / "* more DATA step code goes here; " / "RUN;" / "* Maybe PROC MEANS step code goes here; " / "RUN;" / "filename MyOutputData " output_file "; " / "DATA _NULL_;" / "FILE MyOutputData;" / "* DATA step code for PUT to flat file goes here; " / "RUN;" ; end; stop; run; * now include the SAS code generated in the DATA step above. ; %include tempsas; ... View more

For consideration, if it is possible to have a "zero observations selected for your format", then you should consider outputting a "stub" format so that your PUT function look-up does not fail. One technique I might use is to code a PROC FORMAT execution and only specify an OTHER='???'; clause -- obviously you will want to put this code ahead of the PROC FORMAT CNTLIN=...; step so that if there are observations selected, your final SAS format will be complete, not the generated stub. Scott Barry SBBWorks, Inc. ... View more