Ah! What am I doing wrong? My default font is proportional and I missed that leading blank before the comment /*. I thought it was a JCL end-of-file /*.
Now, yes, it works as you describe. The source file *PROCESS statements get absorbed into the following comments. This is brilliant! I am down to one problem, a problem with the *'s in column 1 of the PROCESS statements -- now commented out -- in the source file: IBM2605I W 6.0 Invalid carriage control character. Blank assumed. IBM2605I W 7.0 Invalid carriage control character. Blank assumed. IBM2605I W 8.0 Invalid carriage control character. Blank assumed. IBM2605I W 9.0 Invalid carriage control character. Blank assumed. That gives me a 4 return code, which screws up the bigger process that this is all part of. Any easy way to get around that warning? Charles On Thu, 13 Jun 2024 20:18:52 +0000, Robert Prins <[email protected]> wrote: >There should be, assuming that you use "margins(2,72,1)", a space before >the '/*' comment in your sysin. It works because PL/I doesn't allow nested >comments, so the '/*' will just match on the first '*/' ignoring any '/*' >in between. The 2506W message seems to indicate that the '/' is in column 1 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
