You may need an iterative solution: fix the earliest problem, then see what problems remain. Since you report no errors, we won't try to fix any errors. Instead, sort the data set fmt by FMTNAME, before feeding it in to PROC FORMAT. Last I checked, a new value for FMTNAME triggers replacement of that format, not the addition to previously defined values. ... View more

A _null_ data set has no records. There is no such thing as a "last record". IMO, you need to clarify the question by describing the inputs and results further. ... View more

You can still use end= with a null data set and a SET statement. data want; if 5=4 then set have; if done then put "final values " _all_; set have end=done; run; The trick is to move the statements around slightly, as shown. The non-executing SET statement ensures that _all_ is properly defined before the PUT statement executes. ... View more

Technically, your program instructs SAS to read 8 characters: numeric_var = input(Patients, 8.); That's what "8." means:  read 8 characters.  If you want SAS to read a different number of characters, that's the statement to change, perhaps to one of. numeric_var = input(Patients, 9.); numeric_var = input(Patients, 11.); The solution from @yabwon will work.  But technically, "best32." is a format, not an informat.  So SAS just changes "best32." automatically to be "32." and gets the proper result. ... View more

The most likely culprit is %qscan.  When macro language quotes a string, it actually inserts a character into the text.  Usually (but evidently not in this case), SAS figures out to remove that character when generating SAS code.  The problem usually occurs when using SQL, but here is appears to be happening even in a DATA step.  Just switch from %QSCAN to %SCAN.   If that fails, make sure the extra character is gone by removing it yourself:   data work.%unquote(year_&yearcounter);   ... View more

You're confusing macro language because commas serve two different purposes in your application.  Commas separate items in &remove_list, and they also separate parameters being passed to the macro.  How should SAS parse out your request when a macro with only three parameters resolves to:   %remove_values (VarRemovalTbl, Fruits, Lettuce, Honey)   A workaround would use spaces instead of commas:   %let remove_list = Lettuce Honey;   You would have add some programming to pick out the individual items from the removal list.  If you have two word items, you would have to use a different delimiter:   %let remove_list = Iceberg Lettuce ! Honey;   Then rely on the ! delimiter in your programming to separate items. ... View more

For these lines of data, what should the last number be? A89 90 4 a1b2c ... View more

To do anything with this data, it would be wise to first fix the INPUT statement. It reads the wrong columns. Also, read dates as dates. There's no advantage to reading them as text. Post again, if you don't know what any of this means. ... View more

What's the logic that tells you to exclude other combinations such as: C&D C&E D&E ... View more

What language are you programming in? ... View more

Please tell us this is just a typo and you really do have a semicolon after FILE inputf ... View more

Given the limitations and constraints you describe, one approach stands out to me. Send two integers to the mainframe, not one. Send digits before the decimal point as one field, and digits after the decimal point as a second field. Then let the mainframe programmers worry about how to put them together. You maintain the greatest accuracy by having the mainframe receive data that is 100% correct. ... View more