PL/1 works the same way. Been like that for a while...(JCL parms with slash).
On Wed, Dec 18, 2019 at 1:29 PM Attila Fogarasi <fogar...@gmail.com> wrote: > "/" in program parms is fully supported and only gets complex for old Cobol > programs which are a special case. Normally LE parms come first, > PARM='leparm/programparm' with any chars allowed by LE for program > parms.... for compatibility with old cobol (OS/VS Cobol and couple of other > compilers, all decades obsolete :) ), reverse sequence is supported. For > new Cobol this is controlled by yet another option CBLOPTS. Lots of > complexity to keep things working as is for old programs (and often set > wrong for new programs :) ). > > On Wed, Dec 18, 2019 at 12:53 PM Paul Gilmartin < > 0000000433f07816-dmarc-requ...@listserv.ua.edu> wrote: > > > On Tue, 17 Dec 2019 19:44:37 -0600, Dale R. Smith wrote: > > > .. > > >Followup for those who might be interested. For COBOL Programs, parms > to > > the program are before the "/" and parms to LE are after the "/". > > > > > What if the parm to the program needs to contain a "/", as e.g. > > a UNIX pathname? > > > > -- gil > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > > > ---------------------------------------------------------------------- > 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