And it appears that you will also need to keep track of the prior first DSN contribution, using a RETAIN and assigning a temporary (different named) variable. Scott Barry SBBWorks, Inc. ... View more

Then you need to add an IN= for the second dataset on the SET (not the first one), and use IF/THEN logic to conditionally output obs contributed from the second dataset. Scott Barry SBBWorks, Inc. ... View more

Specifying the LRECL= parameter should address input data line truncation condition, although you must consider the input data record content itself. Share what code you have for your DATA step to parse the HTML. As far as generating HTML, you can use a SAS DATA _NULL_ step to generate the HTML tags, or consider how you might use ODS HTML possibly, depending on your requirements. I have pasted a link to one of many technical papers found on the SAS support website http://support.sas.com/ found using a search on related keywords with your post. Scott Barry SBBWorks, Inc. http://www2.sas.com/proceedings/sugi27/p061-27.pdf ... View more

You are using SET (interleave observations) with a BY. Do you mean to use a MERGE with a BY, in order to "combine" your two files? Do consider the impact of the MERGE operation with same-named variables in the two (or more) files on the MERGE statement. Have a look at the SAS support website http://support.sas.com/ and the Product Documentation for details about the Data step's MERGE statement processing. Scott Barry SBBWorks, Inc. ... View more

As I understand your post, you want to extract the "filename.extension" information from a complete file-path data string? If this is true, you can use the SCAN function in a DATA step with the third argument "-1" with the delimiter "\" as you have explained. If you are using the SAS macro language, you can use the function %SYSFUNC along with SCAN, as explained above. Scott Barry SBBWorks, Inc. SAS.COM support website resources: -- SAS 9.2 DOC on SCAN function: http://support.sas.com/documentation/cdl/en/lrdict/59540/HTML/default/a000214639.htm -- SAS Documentation web page: http://support.sas.com/documentation/onlinedoc/base/index.html ... View more

The SAS support website http://support.sas.com/ contains technical documentation and also user community papers and submitted examples for many different topic areas. Also, you can use Google search, if preferred, and limit your search to the SAS.COM site by adding the parameter below to your argument string: site:sas.com The link below is a SAS example. Scott Barry SBBWorks, Inc. Example 9. Combining Graphs and Reports in a Web Page http://support.sas.com/documentation/cdl/en/graphref/59607/HTML/default/gr08ods1-ex.htm ... View more

Please share your SAS code (ODS and PROC FREQ related statements, at a minimum). Scott Barry SBBWorks, Inc. ... View more

The correct INFORMAT to use is IBn. (or PIBn.) combined with the INPUT function. Scott Barry SBBWorks, Inc. ... View more

Having searched the SAS support website http://support.sas.com/ I find reference to p-values but not p-levels. Recommend visiting the SAS support site for DOC and technical papers. Also, a Google advanced search using the argument below also will generate some matches: Glimmix p-values site:sas.com I hope this info is helpful, as I admit to not having personal experience on your topic question. Scott Barry SBBWorks, Inc. SUGI/SGF technical paper: 189-31: A Comparison of the MIXED Procedure and the GLIMMIX Procedure http://www2.sas.com/proceedings/sugi31/189-31.pdf SAS Documentation: http://support.sas.com/documentation/ ... View more

What CPU environment and operating system? You mention SAS code or do you mean SAS CONFIG option? The CONFIG option is CPUID, it must be specified at SAS invocation time, and the information is presented at the start of the SASLOG. Depending on your SAS processing environment, there may be an external call to get the desired info. Scott Barry SBBWorks, Inc. ... View more

What is the exact error in your SASLOG? Best approach is to paste the SASLOG before and after the error condition. Also, it is unclear why you cannot combine the two DATA steps, presuming what you want to accomplish is to have the first DATA step's PUT reference inside the body of the EMAIL. There are several technical and DOC references on this topic at the SAS support website http://support.sas.com/ and also you will likely find references by doing a Google advanced search against the SAS.COM site (include the parameter site:sas.com in your search string), using related keywords. Scott Barry SBBWorks,Inc. http://www2.sas.com/proceedings/forum2008/038-2008.pdf ... View more

You must have some extraneous PUTs or like I mentioned, if you are generating output to FILE PRINT or if you have a print-type output file, you will likely get additional noise, including pagination between DATA steps. It's still unclear if you are actually execution a DATA _NULL_ step 99 times or if you have one DATA _NULL_ step which iterates 99 times?? I encourage you to start with a small subset of data / variables, and analyze your generated SAS code closely, looking for all possible PUT refrences. Maximize the SASLOG output with: options source source2 macrogen symbolgen mlogic; If unable to determine cause, then copy/paste your code into the post - no attachments. Scott Barry SBBWorks, Inc. ... View more

You may want to share code to get a more complete response. Also, since the logic is macro-based, is there any reason for having a separate DATA _NULL_ step for each variable. At a minimum, you will have SAS-generated pagination if outputing to a PRINT-type file. But if you are controlling a data file, there should be no extraneous lines generated unless data-wrap or possibly some additional PUTs to consider removing. Lastly, examine the RTF code using a text edit session to validate what is actually being generating, when you mention "..blank lines between the output...". Scott Barry SBBWorks, Inc. ... View more

Explore the ODS HTML options NO_BOTTOM_MATTER and NO_TOP_MATTER, possibly. Scott Barry SBBWorks, Inc. ... View more

From the code you shared, the PROC FORMAT is not coded correctly, to generate the SAS numeric format NEVER. Also, consider the MISSING operand on the TABLES statement, as well. Scott Barry SBBWorks, Inc. SAS DOC on PROC FREQ - link below: http://support.sas.com/documentation/cdl/en/procstat/59629/HTML/default/freq_toc.htm ... View more