I know this thread only got "reanimated" because of a SPAM message, but this post is a perfect example of why you should (almost) never be using the ancient MISSOVER infile option. @zekeT_sasaholic wrote: First.  This process looks strange to me.  The reading of input criteria as card statements. I wont judge as maybe you are using that as a mock up.   but try this...   data layout; infile cards missover; input a $1-500 ; cards; /** your card stuff **/ ; run; hth   zeke torres www.wcsug.com Using the MISSOVER option will prevent the input statement from moving to the next line when the current line does not have 500 remaining characters. But it will also discard any line that has less than 500 characters (actually less than 481 since in-line data lines are always padded with spaces to the next multiple of 80 bytes).   Instead use the newer TRUNCOVER option (I think it is only 30 years old).   ... View more

And the question is what exactly?   Best practice is to post code in a code or text box opened with the "running man" or </> icon above the message window. The text box will prevent the forum from reformatting code and possibly inserting/removing characters resulting in code that will not run or replaces some strings with odd characters such as bullet points.   Actual lines of data should be preceded by a CARDS; or DATALINES; statement with the semicolon. If your inline data contains semicolons then use CARDS4; or DATALINES4; and end your data section with 4 semicolons. ... View more