hi Kurt,    I strongly disagree. Do we have the code for Microsoft windows, microsoft excel or hundreds of other software tools that we use on daily basis in computer, phones etc, although a lot of code is open source.   Code custom built for a client is client's property, whereas propriety code used to execute specific tasks is usually not client's property.      Vineet ... View more

It is probably best to run each block of the untested code in its own SAS environment.  That way when it fails it does not fail the master job.   So perhaps for each snippet of code generate a stand alone program that tests it and run it as a separate SAS job. Then scan the log for a success code before attempting to use the code. ... View more

Hi: I stand by my original statement. If you tested the program with simplified code and cannot reproduce the issue, then it is probably NOT PROC REPORT or ODS PDF that is the issue. There is probably some option you coded incorrectly in your program. So when you find the difference between your test code (without the issue) and your production code (with the issue), then you should be able to determine what is wrong in the production version of the code. The known conflicts in ODS PDF with or without PROC REPORT can be found in Tech Support notes. Did you find your issue by searching in the Tech Support site for your issue? cynthia ... View more

Hi: I know there have been previous posts about how to output blank lines conditionally to mimic the SKIP option in the LISTING destination. But even searching with Google would have brought you to this paper by Allison Booth https://support.sas.com/resources/papers/proceedings11/246-2011.pdf -- see pages 14 and 15. The search string I used in Google was: site: support.sas.com skip line REPORT conditionally cynthia ... View more

Thanks ballardwballardw & Cynthia for quick help. Vineet ... View more