On Wed, 18 Dec 2019 at 15:24, Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
>
> >Well, it was a PL/I thing decades before LE existed.
> >
> "That way"? What did the "/" delimit before LE existed?
>
PL/I runtime library options.
Tony H.
PARM to a PROCSTEP where no PARM is coded
It's a LE thing.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Wayne Bickerdike
Sent: Tuesday, December 17, 2019 6:50 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Adding a PAR
Yep, right you are, there is a CEE function that will also give you the
Parmstring.
Scott
On Wed, Dec 18, 2019 at 3:24 PM Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
> On Wed, 18 Dec 2019 14:53:36 -0500, Tony Harminc wrote:
>
> >On Wed, 18 Dec 2019 at 12:05, Charles M
On Wed, 18 Dec 2019 14:53:36 -0500, Tony Harminc wrote:
>On Wed, 18 Dec 2019 at 12:05, Charles Mills wrote:
>
>> It's a LE thing.
>
>Well, it was a PL/I thing decades before LE existed.
>
"That way"? What did the "/" delimit before LE existed?
>
>> PL/1 works the same way. Been like that for a w
On Wed, 18 Dec 2019 at 12:05, Charles Mills wrote:
> It's a LE thing.
>
Well, it was a PL/I thing decades before LE existed.
Tony H.
> PL/1 works the same way. Been like that for a while...(JCL parms with
> slash).
>
--
For
It's a LE thing.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Wayne Bickerdike
Sent: Tuesday, December 17, 2019 6:50 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Adding a PARM to a PROCSTEP where no PARM is coded
Heres how we do it:
Using a PARM= in your JCL.
LINKAGE SECTION.
01 RUN-PARM.
05 RUN-PARM-LENPIC S9(4) COMP.
05 RUN-PARM-DATA PIC X(100).
PROCEDURE DIVISION USING RUN-PARM.
000-MAIN.
UNSTRING RUN-PARM-DATA
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 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/pr
"/" 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
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
On Tue, 17 Dec 2019 17:59:14 -0500, Steve Smith wrote:
>I don't even know how to spell COBOL, but LE programs typically must have a
>"/" either before or after the application's parms. LE execution parms go
>on the other side of the "/", but can be null. So possibly
>PARM='/PARM,DATA' is what y
-Original Message-
> From: IBM Mainframe Discussion List On Behalf Of
> David W Noon
> Sent: Tuesday, December 17, 2019 7:16 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Adding a PARM to a PROCSTEP where no PARM is coded
>
> On Tue, 17 Dec 2019 22:42:45 +,
On Tue, 17 Dec 2019 22:42:45 +, Farley, Peter X23353
wrote abour Adding a PARM to a PROCSTEP
where no PARM is coded:
> I thought I know this stuff, but my employer's z/OS V2.2 system is saying I
> don't.
>
> I have a simple one-step PROC which executes a COBOL program but has no
> keyword
PROCSTEP where no PARM is coded
On 2019-12-17 17:42, Farley, Peter x23353 wrote:
> I thought I know this stuff, but my employer's z/OS V2.2 system is saying I
> don't.
>
> I have a simple one-step PROC which executes a COBOL program but has no
> keyword parameters on the E
On 2019-12-17 17:42, Farley, Peter x23353 wrote:
I thought I know this stuff, but my employer's z/OS V2.2 system is saying I
don't.
I have a simple one-step PROC which executes a COBOL program but has no keyword
parameters on the EXEC statement, like this:
//MYPROC PROC OUT=*
//MYPGM EXEC
I don't even know how to spell COBOL, but LE programs typically must have a
"/" either before or after the application's parms. LE execution parms go
on the other side of the "/", but can be null. So possibly
PARM='/PARM,DATA' is what you need. If that's the problem, I'd expect the
program to ac
16 matches
Mail list logo
