The whole slash business in COBOL goes back to the OS/VS COBOL days,
before LE was even a blip on the PL/I radar (yes, that's where the LE
stuff originated, and why COBOL had to adapt to LE).
I remember setting COBOL runtime options after the slash back in the
early 1980's. PL/I X (and probab
In article <[EMAIL PROTECTED]> you wrote:
> At 03:43 PM 11/26/2005, you wrote:
> >The LE runtime is interpreting the slash as the way to pass LE execution
> >parameters.
> Dave,
> Thanks. I needed someone to jog me memory. I've seen and used that
> convention before to pass LE parms, but it slip
In <[EMAIL PROTECTED]>, on 11/26/2005
at 03:20 PM, Gerry Palmer <[EMAIL PROTECTED]> said:
>I've run into an oddity when passing an EXEC PARM to a COBOL program.
>I don't see anything in the JCL reference
Nor should you; it belongs in the COBOL and LE documentation.
>Basically, it seems that
For all but COBOL, i.e., for C, FORTRAN, HLASM, and PL/I, the historical LE
parm-string sequence was and is (first ordering)
PARM='/'
Initially, COBOL got it backwards, as (second ordering)
PARM='/'
This second ordering is called the COBOL-options convention.
Specifying CBLOPTS(OFF) at LE in
>I can "double up" on the trailing Forward Slash as a work
around to get
what I need in the COBOL program, but I'm surprised by
this behavior.
Should I be?
Slashes are special delimeters in LE/370.
This is how you separate the runtime options from the
programme options.
-teD
Me? A skeptic? I
At 03:43 PM 11/26/2005, you wrote:
The LE runtime is interpreting the slash as the way to pass LE execution
parameters.
Dave,
Thanks. I needed someone to jog me memory. I've seen and used that
convention before to pass LE parms, but it slipped my mind when this
happened and I kept thinking o
frame Discussion List'
Subject: RE: EXEC PARM "bug" or "feature"?
Gary,
The LE runtime is interpreting the slash as the way to pass LE execution
parameters. If your data parm has a trailing slash, add a second one
like this:
//PS020 EXEC PGM=GPDIRLNK,PARM='S:\Technical
AMA.UA.EDU
Subject: EXEC PARM "bug" or "feature"?
I've run into an oddity when passing an EXEC PARM to a COBOL program. I
don't see anything in the JCL reference that seems to directly address
this, but I'm wondering if I'm missing something. This is on a z/OS
I've run into an oddity when passing an EXEC PARM to a COBOL program. I
don't see anything in the JCL reference that seems to directly address
this, but I'm wondering if I'm missing something. This is on a z/OS 1.4 system.
Basically, it seems that if the last character of the EXEC PARM string i
9 matches
Mail list logo