If there are embedded ./ IEBUPDTE in the JCL, I write a .# ADD card as the header and then use my PUTPDS REXX code.
The odds of a .# ADD appearing I guesstimate as nil. Yes, it's annoying but really, who cares? On Mon, Apr 15, 2024 at 10:37 AM Paul Gilmartin < 0000042bfe9c879d-dmarc-requ...@listserv.ua.edu> wrote: > On Sun, 14 Apr 2024 19:47:38 -0400, Steve Thompson wrote: > > >JES3 is not retarded. > > > I may have judged hastily from such as that the OUTPUT JCL statement > came to JES2 before JES3. You could pay extra to not get the feature. > > >JES3 has this: > >//*DATASET parameters..... > > > >//*ENDDATASET > > > Those look like comments. I guess it provides a sort of compatibility > in that JES2 will ignore them. At the cost of making it harder to > detect and report typos. > > Can the delimiter be changed to allow such lines within instream data? > > > >This is what the z/OS MVS JCL REF has for the parameters: > > ... > >//*DATASET DDNAME=ddname[,parameter]... > > >This allows one to put that data in-stream, define what DD will > >be using it..... And then the JOB Step that gets it, the data is > >encapsulated better than JES2 does it. > > > I see little use in the feature. But if I don't like it, or dln't > understand it, I don't have to use it. > > >So I think this can handle the problem of "IEBUPDTE". > > > No. The problem is not in JES[23], but in IEBUPDTE, which > has nothing like a DLM= parm which would allow data lines > resembling IEBU{DtE commands to appear instream. > > -- > Thanks, > gil > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > -- Wayne V. Bickerdike ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN