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

And yes, I have tried it!

Robert

On Thu, 13 Jun 2024 at 17:04, Charles Mills <[email protected]> wrote:

> Okay, I tried this. Does not seem to work. What am I doing wrong?
>
> 1. I override the SYSIN in the PROC with -- and I checked the job output,
> the override worked --
>
> //SYSIN    DD   *
> /*
> //         DD   DSN=original.sysin,DISP=SHR
>
> 2. The EXEC PARM is still 'TEST(BLOCK,SEP)'
>
> 3. Not sure of the relevance but yes, there are multiple comment lines
> following the four *PROCESS statements in the source file.
>
> The behavior is as before. The *PROCESS TEST(BLOCK,SYM) in the source file
> still overrides the TEST(BLOCK,SEP) in the PARM statement.
>
> I also tried copying the *PROCESS statements from the source code into the
> above in-stream SYSIN, changing the TEST option to (BLOCK,SYM,SEP), and
> followed by a blank comment to "invalidate" the ensuing *PROCESS statements.
>
> That worked as far as the options were concerned, but I also get
>
> IBM1859I S       6.0    The first statement must be a PROCEDURE or PACKAGE
> statement.
> IBM2605I W       6.0    Invalid carriage control character. Blank
> assumed.
>
> In other words, the *PROCESS statements in the source file give me S-level
> errors.
>
> If I eliminate the blank comment, then the compiler sees all 8 PROCESS
> statements and honors the last TEST it sees, the one in the source file,
> and the problem is the same as before.
>
> Am I missing something?
>
> Charles
>
> On Thu, 13 Jun 2024 19:07:46 +0000, Robert Prins <
> [email protected]> wrote:
>
> >OK, I found another way to transiently zap any *PROCESS statements in the
> >source, but it will only work if your source starts with a comment line
> >after any of them. To do so you also need to be able to access the compile
> >JCL, which you obviously) can do using the SJ command in SDSF. Just change
> >the
> >
> >//SYSIN DD DSN=MYPLI.SOURCE(WHATEVER),DISP=SHR
> >
> >in
> >
> >//SYSIN DD *
> > /*
> >// DD DSN=MYPLI.SOURCE(WHATEVER),DISP=SHR
> >
> >And note that this will wipe out *ALL* "*PROCES" statements, so you might
> >want to add the ones you need before the /* in SYSIN.
> >
> >Robert
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>


-- 
Robert AH Prins
robert(a)prino(d)org
The hitchhiking grandfather <https://prino.neocities.org/index.html>
Some REXX code for use on z/OS
<https://prino.neocities.org/zOS/zOS-Tools.html>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to