If I understand that you are looking for a count of valid records for each rstr (non-missing) and the number of ones, then try this for generating a table of frequencies. /* using one of the example data sets above*/ proc tabulate data=sample; class facility_id; var rstr_1 rstr_2; table facility_id, (rstr_1 rstr_2)*(n='Patients' sum='Restrained'); run; If this looks like what you want but need an output dataset tabulate supports output datasets as well. ... View more

The following code fragments will create a dichotomous 0 or 1 for the condition, depending on whether you are concerned about exactly 2 or 2 or more are ones. Proc means and sum on the variable of choice will give you the count. Exactly two ones: two_ones= (sum((q2=1),(q06=1),(q14=1)) =2); Two or more ones: two_or_more_ones= (sum((q2=1),(q06=1),(q14=1)) ge 2); This will also handling missing values. ... View more

If I understand your question, you're looking for the CNTLOUT= option on the Proc Format statement to create a data set with the format information. Specify the library and dataset name like any other. I'd look at the contents closely before exporting as there is likely to be lot's of stuff you're not interested in. ... View more

If using one of the Markup, Printer or RTF outputs the style attribute of POSTTEXT works in some procedures. My experience with ODS TEXT is that the text usually has two blank lines before the text but POSTTEXT is immediately after the table. ... View more

You may have a SAS supplied macro named dm608clr in the core\sasmacro folder (I haven't used UNIX so I'm not sure of this). This macro will set the DM colors to the defaults in 6.08 but the code is easily modified. ... View more

The NEWLINE function may be something to investigate for this use as well. ... View more

> Thanks. How do you deduplicate selecting for the > latest date within a week? There's a unique > time/date stamp field within each week. Depending on how you're using this: Proc summary data=(input data) nway; class id week; var (variable with date/time stamp as a SAS datetime variable); output out=(output data set name) max=; run; May want to have option (drop= _type_ _freq_) with the output data. The output dataset will have the largest date/time within each combination of ID and WEEK. As a side effect the output data will be sorted by ID and week but no sort is needed beforehand. ... View more

> Thanks for the reference. I had found that Note > earlier and I concluded it was possible if the > DLM='09'X was specified. Does that only work with > certain operating systems? A secondary issue that MIGHT affect this code is whether your settings in the editor are set to convert tabs to spaces on saving the file. ... View more

I think you need to define a single escape character for SAS to send the right bits to pdf. Something like: ODS ESCAPECHAR = '^'; Ods pdf text= '^S={"/path/logo.jpg"}'; ... View more

> kmg, > > Do you know if there is a way to put a return between > the notes? From the first response modify: if last.ONum then output; run; To: if last.ONum then do; output; total_notes= ""; output;/* this puts a blank value for the note field, insert appropriate character code if you want an actual return character */ end; run; > > Currently the field is defined as length notes > $32767. If the field is defined as that big is there > anything bigger? I have no control over the field > size i'm just afraid that if they have 4 rows that > have almost that many characters what will happen > when it tries to concatenate them? > No clue but some create use of a FILE statement and PUT with @ and @@ may create a text file without that size limitation. ... View more

I'd be tempted to start with a filename like: Filename mydata ' \*.txt'; /*expanding path to your location and the appropriate wildcard for your system. This will attempt to read ALL files with TXT extension in the location. */ Then in the data step have : LENGHT FILEVARNAME $ 80 ; /*long enough to include entire path and file names above. */ and add the option FILENAME= Filevarname on the INFILE statement used to read the data. This reads all of the text data files with a temporary variable that is not added to your data named FILEVARNAME (or what ever you'd like to call it) that can then be parsed using string functions to identify your original files and add additional variables describing the groups you want to look at later. With out knowing which summary statistics you want cant go much further but CLASS statements in PROC SUMMARY with attention to _type_ in output might get you started. ... View more

It may be necessary to move any of the "support" steps to outside of the ods pdf area of the code. The intermediate data sets or macro variables will persist unless explicitly removed. It may not make the program code quite as clear when the final displayed output is separated from the parts creating the data but it will correct the display issue. ... View more

Not really eligant but you could pull the PATHNAME value from DICTIONARY.LIBNAMES into a macro variable with SQL for the given library. ... View more

Also look into the SYSERR automatic macro variable. ... View more