First, there is no option to prevent comment lines from printing. Second - why would you want that? Generally, you only use a compile listing to help identify errors. From that point of view, it doesn't matter whether there are comment lines or not. Using the "f *err" option in SEU when viewing the spooled file is (as I'm sure you know) the way to find compile errors. Other than that, there is not much use for the compile listing. Usually you delete it when you've finished with it. The only other use for the compile listing is that it can be used to re-create the member source, if you ever get into a situation where you need to do that (very rare!). In that case, you NEED the comments. If you think I have misunderstood what you are actually trying to do, please let me know. Regards, JB

First, there is no option to prevent comment lines from printing. Second - why would you want that? Generally, you only use a compile listing to help identify errors. From that point of view, it doesn't matter whether there are comment lines or not. Using the "f *err" option in SEU when viewing the spooled file is (as I'm sure you know) the way to find compile errors. Other than that, there is not much use for the compile listing. Usually you delete it when you've finished with it. The only other use for the compile listing is that it can be used to re-create the member source, if you ever get into a situation where you need to do that (very rare!). In that case, you NEED the comments. If you think I have misunderstood what you are actually trying to do, please let me know. Regards, JB